/srv/irclogs.ubuntu.com/2009/04/01/#ubuntu-x.txt

stgraberbryce: do you know of cases where glxinfo is extremely slow ?01:04
stgraberlike a few mins to run01:04
brycestgraber: glxinfo?  hmm01:04
brycein general glx can be slow to run if software rendering is enabled, but even there glxinfo should be quick01:05
stgraberyeah, it's making the session open time to go up to a few minutes because compiz is calling glxinfo a few times01:05
bryceno, this is not a bug I've run across so far01:05
brycedid you find any bugs about it in LP?01:05
superm1that sounds like something that might happen with a half installed -fglrx?01:05
stgraberthat's on an Intel classmate, I believe you're familiar with the hardware ? (a few person at Canonical got one at UDS-Boston)01:05
superm1oh nvm01:05
stgraberthat's with 100% intel hardware :)01:05
brycestgraber: no I've not touched the classmate myself01:06
stgraberhmm, I guess I just found the issue, not sure if it's a bug actually.01:10
stgraberglxinfo doesn't work if the current vt isn't X01:10
stgraberso having X start in background, glxinfo doesn't work until I switch to vt701:10
* stgraber notices that the classmate doesn't have a pause/sysrq key ...01:23
tjaaltonbryce: don't know if tseliot is working on it05:06
tjaaltonbut we're an "all-nvidia" shop :( so I'd be interested in seeing a new bugfix release..05:12
tjaalton(we = HUT)05:12
bryce_tjaalton: ok, well it's been quite a while since I did a -nvidia release.  I'd be game to give it a go, though.05:21
tjaaltonbryce_: yeah, I'm willing to try as well05:46
tjaaltongot a 8600GT to try it on05:46
tjaaltonbut first the couple of input drivers..05:47
tjaaltonbryce_: acecad, aiptek, fpit are now in experimental, elographics, penmount, void pushed to git and waiting for an upload07:04
bryce_excellent07:04
tjaaltonuploaded mesa with the texture bump to my ppa 07:16
tjaalton+size07:16
bryce_nice07:21
* bryce swats a couple more -intel bugs09:22
tormodbryce: re your ML post, I think "taking on tasks" scares everybody to silence :)10:33
bryceit's ok, if no one volunteers I have a fallback plan for 8xx.  It's just pretty nasty.  Want to give 8xx users a chance to help grind grain before I start taking the bread away from them.  ;-)10:35
tormodtjaalton: maybe you can consider 324854 (uxa) for your mesa ppa10:38
tjaaltontormod: seems a bit invasive11:04
tjaaltonand since uxa is not used by default..11:04
tjaaltonwhat's the commit-id?11:04
tjaaltonnevermind, got it11:05
tormodok. if it only would touch uxa code it wouldn't be so bad, but I am not able to judge from the patch11:06
Ngtormod: thanks for doing the xorg-edgers PPA, it's very handy :)11:07
tormodNg: you're welcome :) hope I will get some co-uploaders some time11:09
Ngtormod: do you happen to know offhand how huge the difference is between -intel 2.6.3 and 2.6.99/git?11:10
tjaaltontormod: well, looks like it should affect only DRI2, which means EXA users are safe11:10
Ngtormod: I promised bryce I'd see if I could figure out what's changed between jaunty's package and yours that makes my 965 much nicer, but if it's going to be thousands of lines of diff then I'm probably going to fail ;)11:11
tormodNg: git diff would tell you, but yes, it is quite a lot of code11:11
tjaaltongit bisect is your friend11:11
tormodyes that should actually be efficient here11:12
* Ng should read up about that11:12
mifritscherhi11:14
Ngohhhh, nice, bisect does the middle-point searching thing11:16
* Ng wonders if it'll be happy to go backwards though. the kernel.org docs are mostly about "current is broken, current-20 worked, find where it broke", where I need to work out where's it's fixed between 2.6.3 and 2.6.9911:17
tjaaltonsure will11:18
Ngwin :)11:18
Ngso with my fresh checkout of git://anongit.freedesktop.org/git/xorg/driver/xf86-video-intel how would I figure out which commit corresponds to 2.6.3?11:29
Ngaha, there's a tag11:32
bryceok, 18hrs of bug work is enough for one day.  cya tomorrow.11:33
bryce%-P11:33
tjaaltonheh :)11:34
mifritscherhi11:41
Ngso 2.6.3 seems to be about 3 months ago11:41
Ngwhich works out to 8k5 lines of diff ;)11:42
mifritscheryust tested the 2.6.99 on  https://launchpad.net/~xorg-edgers with a g96511:43
mifritscherall works well, but the 3dmark0111:43
mifritscherstill stable, but extrme, simialiar aartefacts on all tests (old objects which got moved are still there)11:43
mifritscherIm running9.0411:43
Ngmifritscher: out of interest, is the jaunty intel driver working ok for you?11:43
mifritscheryes11:44
mifritscherbut the 2.6.3 has a funny dependencie on pae11:44
mifritscheruxa runs only without pae, exa DOES need pea *G*11:44
mifritscher(with 4 GB ram)11:44
mifritscherdidn't try that with 2.6.99 again, I've running it without pae + uxa11:45
NgI only have 2GB of RAM, I'm just trying to work out why 3d stuff is a bit slow for me, but not for everyone :)11:46
Ng(works fine with the edgers PPA, but like you I see some artifacts, and I've had a couple of X hangs)11:46
mifritscherhmm, 3dmark01 gave me 1280 points on 2.6.3 and 1484 points on 2.6.9911:47
mifritscheron VIsta I got 378311:47
mifritschertrac gets ca. 20 fps (and no artefacts)11:47
mifritschertrying 2003 *G*11:48
Ngis 3dmark available freely for linux? it might help my case if I can produce objective numbers rather than subjective workspace-flipping tests11:48
mifritscherkilled X right after starting the program (not the acutal test)11:49
Ngwould we expect 2.6.3 to work with a snapshot of libdrm? I just realised that both of those will have been replaced by the edgers PPA so the fix I need could be in either. I know it can't be mesa because I tried tjaalton's 2.4 packages and there was no change11:51
mifritscherbacktrace: http://rafb.net/p/i3S8KQ46.html11:51
mifritschernow it starts, but it is missind DXT1 and DXT3 texture compression11:55
mifritscher(as with the old driver)11:55
tormodNg: newer libdrm should be fine for intel 2.6.312:22
mifritschertormod, you are one of the maintainers of https://launchpad.net/~xorg-edgers/+archive/ppa, right?12:25
tormodmifritscher: de facto the only one12:25
mifritscheris the artefacts problem already known or do you need more details?12:25
mifritscherah ;)12:25
tormodyou have to check upstream. that's the point of this PPA :)12:26
mifritscher#intel-gfx is sort of dead :-/12:27
tormodit's the time of day12:28
tormodcheck the bug tracker as well12:28
mifritscherdidn't found anything12:30
mifritscher( http://bugs.freedesktop.org/buglist.cgi?quicksearch=Drivers%2FDRI%2Fi965 )12:30
mifritscherand for the pae I found only http://bugs.freedesktop.org/show_bug.cgi?id=1799312:32
ubottuFreedesktop bug 17993 in Driver/intel "[GEM] kernel with PAE panics when starting X" [Normal,Assigned]12:32
mifritscherbut for me it is the other way around: I actually need pae to use exa ;-)12:33
mifritscher(for uxa, I must not use pae)12:33
BUGabundobryce ping15:37
BUGabundowhat about intel 815? is there a master bug for it?15:38
jcristauthe i815 driver hasn't changed in years afaik15:39
thiebaudei hope someone might help me, i cant log into gnome, but only fluxbox15:39
thiebaudei have the i81515:39
hyperairthiebaude: wrong channel15:39
BUGabundohyperair: actually I asked him to come here15:39
hyperaireh?15:39
thiebaudeBUGabundo sent me over here15:39
BUGabundowith all this intel probs on 8x515:39
hyperairwell yeah but fluxbox works15:40
hyperairobviously X starts15:40
jcristauBUGabundo: 810 is completely separate15:40
thiebaudei thought i had the bug 30487115:40
ubottuLaunchpad bug 304871 in xserver-xorg-video-intel "[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)" [High,Fix released] https://launchpad.net/bugs/30487115:40
thiebaudeits halfway fixed15:40
BUGabundothiebaude: can you try to logout and select Safe Gnome Session?15:40
jcristauthiebaude: if your chip is a 810/815, then that bug is irrelevant15:40
thiebaudeok thanks again BUGabundo15:40
* BUGabundo goes back to +115:41
thiebaudesee you15:41
BUGabundoguys sorry for the noise15:58
BUGabundobut thiebaude is reproducing the bug15:58
BUGabundoof X freezing a few secs after login15:58
BUGabundowith a 815... it looks pretty much like all other 8x515:59
BUGabundowhat can he do to debug it?15:59
jcristauBUGabundo: i already told you, 815 is not like all other 8xx...15:59
BUGabundobut symptoms are very much the same16:00
BUGabundoon gnome , at least16:00
thiebaudei can only get into fluxbox16:03
mnemowill mesa 7.4 be included in time for the testday tomorrow?17:51
Ngbryce: how much will I be mocked if I suggest rolling jaunty back to Intrepid's intel driver? :D18:30
Ngis such a thing even possible?18:30
NgI fully appreciate that my view of the driver is very small and I may be missing wider issues, but I've yet to encounter anyone with an improved experience, but I am encountering lots of regressed ones18:30
Ngwhere "lots" is an unquantified value18:31
Ngso I just thought I'd throw the idea out there18:32
jcristauyou'd probably have to revert the kernel, too...18:32
Ngjcristau: as in, patches we've applied to the kernel? or does intel's 2.4.x simply not work on a 2.6.28 kernel?18:33
Ng(I really wish they wouldn't have release numbers that are so confusingly similar to kernel ones ;)18:34
jcristauas in, "it worked better in intrepid" is not only related to the intel ddx, that's only one component18:36
jcristauso 2.4.x with 2.6.28 might work, but it might not work better than what you have right now, and it is probably not as tested18:38
jcristauso i'm just saying it's hard to know beforehand what will work best :)18:38
Ngok, these are good points :)18:39
NgI have the impression that we are somewhat stuck between a rock and a hard place until we are fully in the land of UXA and KMS!18:39
Ngwhich can only really be Intel's fault, imho18:40
jcristaui get the feeling we're between a rock and a hard place until we are until the next rock and the next hard place :/18:40
jcristaus/until/between/218:41
Ngheh18:43
Ngsurely after we're all using DRI2 and UXA and KMS there's no more big architecture stuff and Intel will actually fix bugs? :)18:44
Ngthey seem to have been bug fixing a lot recenlt18:44
bryceNg: well, back when we were on XAA and Intel was pushing EXA I remember thinking, "Once we're fully in the land of EXA, Intel will fix all their bugs, and it will be all milk and honey after that."18:51
bryceso I disoptimistically have to agree with jcristau18:52
bryceNg: also even if reverting to the Intrepid driver were feasible, it would also result in losing some hardware support for newer hardware18:52
Ngbryce: you're filling me with confidence here, man ;)19:02
Ngbryce: if you're on -platform you will shortly get a horrific braindump from me of what I'm seeing and trying to do about it. It's a mess of information which I apologise for, I just wanted to braindump everything I have about it in the hopes that something good can come from it!19:03
bryceI unsubbed from platform when I moved to the desktop team19:04
bryceso you might cc ubuntu-x@ if you think it's worth me reading19:05
Ngah right, so everyone on platform won't care. go me ;)19:05
Ngsent to -x :)19:08
bryceok, bating breath and waiting19:08
NgI really should subscribe to -x19:09
bryceyep19:09
Nghah, especially since that mailman reply was not "lala wait for moderation", but "go away" ;)19:11
* Ng subscribes and resends19:11
bryceheh19:11
tjaaltonNg: the mesa version on my ppa is 7.4 ;)19:43
tjaaltonnot 4.319:43
mnemobryce, tjaalton: what is the mesa 7.4 ETA right now? also, I heard a rumor that EXA perf might be fixed by some patch that disables GEM, have you heard that as well?21:11
Ngtjaalton: doh, I fail ;)21:46
LLStarks...21:57
brycemnemo: tjaalton has put 7.4 in his ppa.  I think he is awaiting sufficient tester feedback before putting it in21:57
LLStarksbryce.21:58
LLStarksi21:58
LLStarksi'm having trouble with my intel git compiles21:59
LLStarksi have all the deps and followed directions, but x breaks.21:59
albert23mnemo: switching of gem plus an additional patch on -intel indeed fixed performance with I945 for me.21:59
albert23mnemo: debdiff http://paste.ubuntu.com/142337/21:59
albert23patch 203 was accepted upstream 2 days ago22:00
bryceLLStarks: sympathies22:01
LLStarksany advice?22:01
brycealbert23: bug# ?22:01
albert23bryce: freedesktop bug 2079722:02
ubottuFreedesktop bug 20797 in Driver/intel "[i945] Performance regression in 2.6.3 from 2.6.1 with non-gem kernel" [Normal,New] http://bugzilla.freedesktop.org/show_bug.cgi?id=2079722:02
bryceLLStarks: I recommend nuking from orbit, it's the only way to be sure22:03
LLStarks...wut?22:03
brycealbert23: thanks22:03
albert23bryce: performance on 945 is 30301122:03
bryceLLStarks: oh you mean advice on your build issue?  you didn't show any details so I can't give any advice.  I do advocate nuking from orbit as a general solution to random build problems though.  It helps.22:04
LLStarksthere's no problem with the actual build.22:05
LLStarksi just can't get the binaries to start x.22:05
brycealbert23: thanks for the performance bug; is there also a corresponding launchpad bug (so I can set up subscriptions and such)22:06
bryceLLStarks: you can't find the binaries?22:07
albert23bryce: no, I didn't consider it an Ubuntu bug, as jaunty does have gem22:07
albert23that patch only helps if you switch of gem22:07
LLStarksno. they just won't start x when i restart.22:07
LLStarksthey are pathed to /usr22:08
bryceLLStarks: try http://wiki.ubuntu.com/X/Troubleshooting/.22:08
brycealbert23: give that we're not using uxa, I wonder if it hurts anything to turn off gem as well22:10
albert23bryce: see the debdiff. UXA still works :-)22:11
brycehmm, I thought gem was a prerequisite for UXA22:11
albert23bryce if (pI830->accel == ACCEL_EXA is the trick22:12
albert23see the pastebin22:12
LLStarksdoes the debdiff work with the 2.6.99 ppa packages?22:12
LLStarksalso, does the patch negate the need for anholt's pending a17 fix?22:13
albert23bryce: my concern would be that the fake bufmgr code hasn't been tested in jaunty22:13
* bryce nods22:14
albert23LLStarks: the debdiff has two parts. 1 switch of gem, 2 the TILE_NONE fix22:16
albert23LLStarks: the a17 fix should fix gem, so you don't need the first part anymore22:17
LLStarksi see.22:17
LLStarksso the patch right now is just a stop gap?22:17
albert23for me it is22:17
albert23and I am really not sure if it would be good for jaunty, given where we are in the release cycle22:18
LLStarksi severely doubt a performance patch would be denied a freeze exemption22:24
albert23LLStarks: btw, latest intel from git needs libdrm 2.4.6 and kernel 2.6.2922:29
LLStarksi knew  about 2.4.622:30
albert23I needed a patch to build with kernel headers from 2.6.28 and it still only runs on 2.6.29 kernel22:30
LLStarksbut not the kernel22:30
LLStarksi do have a few mainline and self-built 2.6.29 kernels.22:34
LLStarksi don't think i got intel to work with those either.22:34
LLStarkshi.22:45
LLStarksi just uploaded some photos for my lvds bug: freedesktop bug 2095122:46
ubottuFreedesktop bug 20951 in Driver/intel "[945GM] Fullscreen graphical corruption on LVDS" [Normal,New] http://bugzilla.freedesktop.org/show_bug.cgi?id=2095122:46
LLStarkshopefully they are helpful22:46

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