/srv/irclogs.ubuntu.com/2008/05/09/#ubuntu-x.txt

brycetjaalton: -intel merge: http://people.ubuntu.com/~bryce/Uploads/08:31
brycetjaalton: also included a couple other patches.  builds ok.  would appreciate a review.  I'll upload tomorrow.08:32
tjaaltonbryce: why not merge 2.3.0 from experimental?-)08:34
tjaaltonand could we finally drop i81008:34
brycetjaalton: in part because I want to get 2 patches validated that I'm looking to backport to hardy08:35
tjaaltonno-one uses intrepid..08:35
bryceheh, I do!08:35
tjaaltonso using hardy-proposed is a better way imho08:35
bryce(well, for my test box)08:35
tjaaltonah ok :)08:35
brycethe one patch is already in hardy-proposed08:36
tjaaltonthe packages don't have to be in sync between intrepid and hardy-updates08:36
brycealso, I think for 2.3.0 we'll be dropping a lot of patches08:36
tjaaltonsure08:36
brycetjaalton: also I got word that 2.3.1 is coming out very soon; perhaps that's the one we should merge.08:39
tjaaltonok08:39
tjaaltonanyway, doing a merge to get one patch in hardy is maybe overkill :)08:40
tjaaltonand probably will get turned down08:41
bryceactually the reason I'm doing a merge is because I tried doing a regular upload of the patch, and got a reject due to md5sum issues, and I'm guessing the merge needs to go through first08:42
tjaaltonI think it's because -2ubuntu13 is not yet in -updates08:44
tjaaltonhm no08:44
tjaaltonyou should be able to upload ubuntu1408:44
tjaaltonto -proposed08:44
tjaaltoner, I meant -1ubuntu13 and 1408:45
bryceno, I mean I wasn't able to upload to intrepid.  I was able to upload it to hardy-proposed08:45
tjaaltonah ok08:45
tjaaltondo you have the error message08:46
tjaalton?08:46
bryceyeah08:46
bryceRejected:08:46
bryceMD5 sum of uploaded file does not match existing file in archive08:46
bryceFiles specified in DSC are broken or missing, skipping package unpack verification.08:46
bryceit's rather obscure what the problem is.  I tried redoing it from scratch 2-3 times, exact same error.08:46
bryceeh, perhaps it's all not worth the bother.08:47
tjaaltonyou tried to upload -1u13 to intrepid? that would fail yes08:47
bryceoh?  why would it fail?08:47
tjaaltonbecause it's there already :)08:48
brycehmm, I could swear I'd checked08:48
tjaaltononly that the pocket is hardy-proposed08:48
tjaaltonyou uploaded it :)08:48
bryceoh08:48
brycefeh!08:48
tjaaltonyou should use different versioning08:48
tjaaltonlike if intrepid had -1ubuntu1, then to get that in hardy you'd upload it as -1u1~hardy108:49
brycelike -1u12.1 ?08:49
tjaaltonthat's another way yes08:49
tjaaltonbut merge 2.3.0 and be done with it for good :)08:49
bryceyeah08:49
brycealthough not for the reasons I'd assumed ;-)08:49
tjaaltonthen when 2.3.1 is released it's easy to re-merge08:49
bryceyup08:50
tjaaltonso, apart from some patches, there shouldn't be any other changes that we need08:50
tjaaltonlibpciaccess should be pushed to main though08:50
brycewell, I'll do -2ubuntu1 first, just to get all the patches together and since I have it ready, then work on 2.3.x next 08:51
bryceyeah we definitely need to put a priority on that08:51
tjaaltonok, the merge looks good08:51
tjaaltonis 19_check_exa_pitch_to_fix_rotate_crash.patch from upstream or your head?-)08:51
tjaalton(didn't look in the diff, just .changes)08:52
bryceupstream08:52
tjaaltonok cool08:52
brycebut it's not one I'm super confident about.  Probably ok for intrepid but I wanted more testing/verification before putting in for hardy08:52
tjaaltonyep08:54
bryceuploaded09:09
jcristaui'm guessing intrepid will likely have xserver 1.5?10:18
bryceyeah10:18
jcristaui'll upload a new xorg-server rev today, rebased against the latest server-1.4-branch, fwiw10:19
jcristau(but first i need the new xtrans)10:24
tjaaltonjcristau: it builds against mesa 7.0.3?10:25
jcristautjaalton: "it"?10:25
tjaaltonthe server10:25
jcristau1.5 doesn't10:25
tjaaltonah so you don't have packages yet, only the tree?10:26
tjaaltonI'm just confused :)10:26
jcristaui have packages in experimental, built with --disable-glx --disable-dri --disable-dri210:26
jcristau:)10:26
tjaaltonright, remember seeing those10:27
jcristaubut there's a good chance lenny will release with 1.4 anyway :/10:28
tjaaltonis it still planned for sep/oct?10:28
jcristausomething like that10:29
tjaaltonin that case 1.4 is definately a safer bet ;)10:29
jcristauyeah10:29
tjaaltonalthough so does intrepid, but we've decided to push the envelope with it :)10:30
tjaalton1.4 is getting boring10:31
jcristauhmm. still shipping the old i810 driver?11:32
tjaaltonyes.11:39
tjaaltonfor testing..11:39
tjaaltonyay, pixman synced.. that was fast13:07
kahrytanHow does Screen Resolutions applet get it's mode list ?13:21
tjaaltonit uses xrandr13:22
kahrytanHow does Screen Resolutions applet or X server get it's mode list ?13:22
jcristauthe X server gets it from the monitor13:22
kahrytanokay. xrandr is wrong in detecting modes for my monitor13:22
tjaaltonkahrytan: log?13:22
jcristauand xrandr gets it from the X server13:22
kahrytanWhat log? it's a GUI app13:22
jcristauthe X log13:23
tjaaltonkahrytan: the xserver log, /var/log/Xorg.0.log13:23
kahrytanSo13:23
james_wkahrytan has reported this issues as bug 22095213:24
ubottuLaunchpad bug 220952 in mandriva "X Support and Config needed for Viewsonic VA1916W" [Unknown,Confirmed] https://launchpad.net/bugs/22095213:24
kahrytanX in Hardy is bugged. 13:24
kahrytanIt doesnt know how to detect my monitor. 13:25
tjaaltonnvidia blob13:25
kahrytanIt has nothing to do with nvidia13:25
tjaaltonhow so?13:25
kahrytanI have tried with NV, Nvidia and without either.13:26
tjaaltonno logfile on the bug13:26
tjaaltonplease attach one13:26
jcristautjaalton: http://launchpadlibrarian.net/14028337/NV_Output_Xorg.log13:26
kahrytanYou want one w/o the nvidia/nv use13:26
tjaaltonoops13:26
jcristauno xorg.conf though13:27
jcristauand, that's not the full log13:27
jcristauplease attach both13:27
kahrytanxorg.conf is messy13:27
jcristauthen remove it and try again13:27
jcristauand attach the log from that13:28
kahrytanHow13:28
kahrytansafely13:28
tjaaltonmove the xorg.conf aside and restart the server13:28
kahrytanit will generate new one from default?13:28
jcristaumv /etc/X11/xorg.conf /etc/X11/xorg.conf.bak; /etc/init.d/gdm restart13:28
jcristauor something13:28
kahrytanIt wont use NV/Nvidia will it?13:29
tjaaltonit will use nv13:29
jcristauit should use nv13:29
tjaaltonshould, yes13:29
kahrytanNV doesnt do OpenGl 13:29
jcristauyou don't need 3d to test this13:30
kahrytani know13:30
kahrytanbrb13:30
kahrytanXorg.conf didnt regenerate on it's own13:42
tjaaltonno need to13:42
tjaaltonthe server autoconfigures itself13:42
kahrytanbut it doesnt create the file13:42
jcristauno, it doesn't13:43
kahrytanSo no need to attach13:43
tjaaltonthe log...13:43
jcristauneed to attach the full log13:43
jcristau(if there is still a problem)13:43
kahrytanX uses NV driver?13:43
tjaaltonjust attach the log and we'll see13:43
tjaaltonit detects your card and uses the best match13:44
tjaaltonfalls back to vesa13:44
tjaaltonif no better alternative13:44
kahrytanIt must rely on NV for modes13:45
tjaaltonplease. attach. the. log :)13:46
kahrytani know NV detects cuz log says it13:47
kahrytanhttps://bugs.launchpad.net/ubuntu/+source/xorg/+bug/22095213:48
ubottuLaunchpad bug 220952 in mandriva "X Support and Config needed for Viewsonic VA1916W" [Unknown,Confirmed] 13:48
tjaaltonreading13:48
tjaaltonwhat does 'xrandr' on the terminal say?13:50
jcristaukahrytan: so the problem is that when you start some games they change the resolution and end up with something the monitor doesn't like?13:50
kahrytanDDC did a crappy job at detecting13:50
kahrytanjcristau,  Yes.13:50
kahrytantjaalton,  attach that too?13:52
jcristauyes please13:52
kahrytani did turn nvidia back on though13:52
jcristausigh13:52
kahrytancuz gnome was slow w/o it13:53
kahrytanNvidia does the same in detecting when in verbose mode. 13:53
jcristaudoes xrandr -s 800x600 work?13:54
kahrytan_jcristau, thank you for that great suggestion. I had to reboot13:57
tjaaltonthen try with nv13:58
tjaaltonso we can blame nvidia :)13:58
=== kahrytan_ is now known as kahrytan
kahrytanlol13:59
kahrytanPlease, no nvidia bashing13:59
tjaaltonwhy not? take a look at the bugs against linux-restricted-modules*14:00
kahrytanHow do I reset xrandr to good rate ?14:00
kahrytanBecause it is not very uh.. ubuntu thing to do. 14:01
tjaaltonwhich?14:02
tjaaltondamn14:02
kahrytanIm back14:07
kahrytanIve tested xrandr -s 800x600 w/o nv and with it. 14:07
kahrytantjaalton, jcristau; guess the verdict14:08
tjaaltoneverythin works like a charm?14:08
kahrytanx likes to use the lowest rate for resolution.14:08
tjaaltong14:08
tjaalton56Hz?14:09
kahrytanLowest for NV is 5614:09
kahrytanIt worked with NV/non-NV14:10
kahrytanAnd Nvidia does list 56hz14:11
kahrytanX forked nvidia reports.14:12
kahrytanHello?14:14
kahrytanNo talkers?14:14
=== jw2328_ is now known as james_w
tjaaltonwork14:14
tjaaltonwhat do you mean "It worked with NV/non-NV"?14:15
kahrytanyeah14:15
kahrytanNV does say 56, Nvidia does say 56. 14:15
kahrytanX just does 56 for NV and not for Nvidia.14:15
tjaaltonso with nv 56Hz works?14:15
kahrytanyeah14:15
tjaaltonso nvidia bug14:16
kahrytanno14:16
kahrytanX bug14:16
tjaaltonexplain why14:16
kahrytancuz it's obviously not using 56hz for Nivida14:16
tjaaltonuh14:16
tjaaltonf*ck14:17
kahrytanHow do i tell xrandr to use a specifix rate?14:18
tjaaltonman xrandr14:18
tjaaltonbut nvidia doesn't support randr-1.214:19
tjaaltonso I don't think you can specify the rate14:19
kahrytanor maybe it is that kind of bug14:19
kahrytannvidia not supporting new version of xrandr?14:19
tjaaltonif you change the driver and it then fails to work -> driver  bug14:19
tjaaltonyes, that's how it goes in the proprietary world14:20
tjaaltonthey lag behind14:20
kahrytanNot lag14:20
tjaaltonnv doesn't support it either, except for G8x chips14:20
kahrytanNvidia will eventually open up14:21
kahrytanwhen others do the same14:21
jcristauothers already did14:21
kahrytanI hear ATI hasnt really14:21
tjaaltonkahrytan: look, I adminster 300+ desktops which use nvidia, so I know the driver is not perfect14:22
tjaalton+i14:22
jcristauyou hear weird stuff14:22
kahrytanDoes the driver for ati suck ?14:22
jcristaufglrx certainly does14:22
tjaaltonevery driver sucks for some hardware, sure14:22
kahrytanWho makes that driver?14:22
tjaaltonfglrx? ATI/AMD14:24
kahrytanAnd wheres the oss one?14:24
kahrytanI blame xrandr for breaking nvidia14:25
tjaaltonno, if nvidia can't do 56Hz then it's nvidia bug14:27
tjaaltonbug reassigned already14:27
tjaaltonback to work->14:27
kahrytandoes X uses xrandr for changing resolutions/rates?14:27
kahrytantjaalton,  answer?14:28
kahrytandoes X uses xrandr for changing resolutions/rates?14:30
* bryce reads backlog - tjaalton erf that looked painful19:52
brycetjaalton: anyway I agree when 2.3.1 is merged that would be a good time to finally turn off i810.  We should probably also put a priority on upstreaming all the remaining 8xx bugs in our tracker19:53

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!