[02:00] <bryce> tjaalton: btw I tried manually copying the libdrm-dev headers back into /usr/include/drm, but it made no difference; -ati still hangs on X start.
[02:01] <bryce> surprisingly, vesa actually looks pretty good, although it's a lower res and no dual-head
[08:02] <tjaalton> bryce: the headers are used only when building the drivers
[08:02] <tjaalton> or do you mean you rebuilt -ati?
[08:05] <bryce> ah.  no didn't rebuild it
[08:08] <tjaalton> shouldn't make a difference
[08:08] <tjaalton> so it just hangs?
[08:08] <bryce> yep, I'd had it working fine and dandy with intrepid, then did the upgrade
[08:09] <bryce> X fails to start, and switching to vts just displays corrupted screens
[08:09] <bryce> so my next hypothesis is an EXA/XAA problem
[08:09] <tjaalton> ah, so you can change the vt when it happens?
[08:09] <tjaalton> is it a r5xx?
[08:10] <bryce> RV630
[08:10] <tjaalton> hmm, dunno which generation that is
[08:10] <tjaalton> if it's DRI capable, try disabling it
[08:11] <bryce> RV630 [Radeon HD 2600XT]
[08:11] <tjaalton> ok, it's not that
[08:11] <tjaalton> maybe it's trying to use the wrong output?
[08:12] <bryce> bryceharrington.org/files/Xorg.0.log.old
[08:14] <bryce> I don't think it's a wrong output issue - the card has 2 outputs and I have monitors connected to both.
[08:14] <tjaalton> heh, ok
[08:14] <tjaalton> there's a new upstream version in experimental.. try that
[08:16] <bryce> yeah
[08:16] <bryce> hmm, this looks suspicious:
[08:16] <bryce> Output 69 disable success
[08:16] <bryce> Output 51 disable success
[08:16] <bryce> Blank CRTC 0 success
[08:16] <bryce> Disable CRTC 0 success
[08:16] <bryce> Blank CRTC 1 success
[08:16] <bryce> Disable CRTC 1 success
[08:17] <tjaalton> right
[08:17] <tjaalton> that's why I suspect an initialization issue
[08:31] <tjaalton> bug 312924 looks similar
[08:44] <bryce> yeah
[08:45] <tjaalton> and bug 311748
[08:50] <tjaalton> I've duped them
[08:50] <tjaalton> em, the former with the latter
[08:51] <bryce> great
[08:51] <bryce> I'm back to work tomorrow, and I think I'll focus the day on sorting out this particular bug (or upstreaming it at least)
[08:52] <tjaalton> the new upstream version didn't help
[08:52] <tjaalton> ?
[08:52] <bryce> right, I'll try that tomorrow first
[08:53] <tjaalton> ah, ok
[08:53] <bryce> (today I've been doing shop project stuff, and tonight am installing the new bookcase I made)
[08:56] <bryce> my wife's excited because I've got a pile of old books out in the main room that will be moved in now, and it'll eliminate clutter she's had to look at
[08:56] <tjaalton> hehe
[08:57] <tjaalton> it's -12C outside, so I'll stay in and weed the bugs
[08:58] <bryce> ouch :-)
[09:01] <tjaalton> btw, I've changed my contract to 20h/week so I can concentrate on my studies the next two months (at least), so might be that I need to lower my commitment to X/ubuntu for a while :/
[09:07] <bryce> ah, good to know
[09:07] <bryce> how'd your tests go btw?
[09:07] <tjaalton> good practice :)
[09:07] <tjaalton> next ones the week after next week
[09:08] <tjaalton> I was just so jetlagged the whole week, and I actually had to skip the first one because I couldn't stay awake for more than 5min
[09:09] <tjaalton> ..at a time
[09:09] <bryce> :-/  I was worried something like that'd happen.  Hope your professors were sympathetic
[09:11] <tjaalton> well they want to get rid of us (slackers), so they have no choice :)
[09:11] <tjaalton> I'll merge -ati, it can't be worse than the current version :)
[09:15] <Q-FUNK> howdy!  any chance to get the fix to bug #255991 moved from hardy-proposed to hardy-updates?
[09:18] <tjaalton> Q-FUNK: isn't that something for an archive-admin?
[09:20] <bryce> yeah, need to talk to pitti or slangasek
[09:20] <Q-FUNK> tjaalton: I'm not sure.  last time I asked, I was told to test and ensure that it doesn't introduce any regression.
[09:20] <Q-FUNK> ok
[09:25] <tseliot> tjaalton: what are you studying?
[09:27] <tjaalton> tseliot: major in semiconductors & materials in electronics (blech), minor in software engineering & business
[09:28] <tjaalton> so the courses I have left are real gems, like physics II, inorganic chemistry etc :)
[09:29] <tseliot> hehe, a lot of fun
[09:29] <tjaalton> a lot, yes
[09:30] <tseliot> will it give you the chance to be paid more? How does it work in Finland?
[09:30] <tjaalton> sure
[09:30] <tjaalton> if you have a degree it gives you more options
[09:30] <tseliot> ok, then it's definitely worth the effort
[09:31] <tjaalton> although there are plenty of experts who have dropped out and made a good living
[09:32] <tseliot> you already have a job, right?
[09:32] <tjaalton> sure, had one for ten years now.. one reason why it's been taking so long :)
[09:33] <tseliot> aah, I thought you started your degree course recently
[09:34] <tseliot> more recently
[09:34] <tjaalton> heh
[09:34] <tseliot> good luck then
[09:35] <tjaalton> thanks
[18:52] <tjaalton> bryce: the new ati version didn't help your setup?
[18:53] <bryce> I've installed it; I'll reboot after I finish fiddling with a few bug reports
[18:53] <tjaalton> looks like evertjan didn't get the new version yet
[18:53] <tjaalton> II) Module radeon: vendor="X.Org Foundation" compiled for 1.5.99.3, module version = 6.9.0
[19:45] <CShadowRun> Hi guys, i was just reading http://blog.qa.ubuntu.com/node/9 and i hear you need testers
[19:46] <CShadowRun> I have a quad screen setup (2 nVidia 8800GT cards, both dual head) and i currently run 2 X screens to manage it
[19:46] <CShadowRun> i'd love to help you guys test, so just give me a call :)
[19:46] <CShadowRun> love the sound of xrandr :)
[19:56] <bryce> CShadowRun: thanks, welcome to the ubuntu-x team :-)
[19:57] <bryce> CShadowRun: I assume you're using the -nvidia driver?
[19:57] <CShadowRun> yup :)
[19:58] <bryce> what are you interested in testing particularly?
[19:58] <CShadowRun> well i'd like to see the xrandr stuff for multiple heads
[19:58] <CShadowRun> because xinerama is a bit crap, and so are multiple X screens lol
[20:01] <CShadowRun> it's a shame to see multiple X screens fall into a state of disrepair, though
[20:01] <bryce> heh, well you're sort of stuck, since you're using the -nvidia proprietary binary driver
[20:01] <CShadowRun> ah
[20:01] <CShadowRun> well i can always put another installation of ubuntu on one of my drives to test with
[20:01] <bryce> with -nvidia you first need to wait for them to provide xrandr 1.2 support
[20:02] <CShadowRun> yea
[20:03] <CShadowRun> i well, i shall just twiddle my thumbs till it comes along
[20:03] <CShadowRun> unless theres any better ideas :)
[20:05] <bryce> CShadowRun: are you using nvidia-graphics-drivers-177?  Do you have jaunty installed?
[20:06] <bryce> if so, one area you could help is by looking at bugs in https://bugs.edge.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177
[20:08] <bryce> some documentation for how to check bug reports is at https://wiki.ubuntu.com/X/Triaging
[20:12] <bryce> bbl - testing new -ati
[20:54] <CShadowRun> I can probably load jaunty on one of my spare drives and check out some of those bugs :)
[22:29] <bryce> tjaalton: yep reverting the EXA patch and going back to XAA solved the issue for me
[22:30] <tjaalton> bryce: ok, so it was the same bug then
[22:30] <tjaalton> strange that the patch _looks_ ok
[22:31] <bryce> I'll need to look it over a bit more
[22:31] <bryce> there's actually 2 bugs - one is why EXA isn't working (which may or may not be the same issue as graber), and the other is why XAA can't be specified
[22:31] <tjaalton> it's the same
[22:32] <tjaalton> I bet EXA works for you if you force it in the conf
[22:32] <bryce> ok lemme try
[22:33] <bryce> you're right
[22:33] <bryce> bryce@chideok:~$ grep XAA /var/log/Xorg.0.log
[22:33] <bryce> bryce@chideok:~$ grep EXA /var/log/Xorg.0.log
[22:33] <bryce> (**) RADEON(0): Option "AccelMethod" "EXA"
[22:34] <bryce> btw, I subbed ubuntu-x to radeontool
[22:34] <bryce> there's no bugs against it, but I think we should probably get the package up to date with what's in airlied's git tree
[22:35] <tjaalton> ok
[22:48] <bryce> aha, found one issue...  setting AccelMode to XAA does not actually turn off useEXA, it ust leaves the default
[22:50] <bryce> ahaa!!
[22:50] <bryce> tjaalton: ok I understand what's going wrong
[22:51] <tjaalton> great :)
[22:51] <bryce> it *is* an EXA problem
[22:51] <bryce> graber actually isn't getting EXA (neither am I)
[22:51] <bryce> (==) RADEON(0): No acceleration support available on R600 yet.
[22:51] <tjaalton> heh
[22:52] <bryce> there's logic that prevents considering EXA if CHIP_FAMILY_R600
[22:52] <bryce> so it forces XAA for that
[22:52] <bryce> however my patch ignored that and set EXA as the default before that condition was checked
[22:52] <bryce> so I was forcing EXA on R600 for graber and I, thus exposing the EXA problem
[22:53] <tjaalton> maybe the other bug should be closed as well then (311748), or marked as dupe of the first?
[22:53] <bryce> secondarily, there's another problem I mentioned above where specifying XAA doesn't switch you to XAA, only to the default
[22:54] <bryce> tjaalton: no, I think that's a different problem actually
[22:55] <tjaalton> ok
[22:55] <bryce> they are reporting seeing that issue on intrepid, which doesn't have my patch so could not be seeing this problem
[22:55] <tjaalton> ah
[22:55] <tjaalton> right
[22:56] <tjaalton> well, now there's a change it might work
[22:56] <tjaalton> chance
[22:57] <bryce> yep
[22:58] <bryce> hmm
[22:58] <bryce> interesting; in reading the logic it sounds like even XAA is unsupported on this chipset.  bummer
[22:59] <tjaalton> well, r6xx only gained acceleration support a couple of days ago :)
[23:00] <tjaalton> but not something for jaunty..
[23:00] <bryce> well, basic performance seems fine
[23:07] <bryce> ok, made a new patch... time to build and test
[23:10] <bryce>  hrm, the j key on my keyboard is not producing j's reliably... not a good keyboard for development of uanty
[23:10] <tjaalton> heh
[23:11] <bryce> ok here we go
[23:12] <bryce> seems okay
[23:15] <bryce> I can't test setting XAA though
[23:15] <bryce> at least, not easily right now
[23:15] <tjaalton> right
[23:15] <tjaalton> ship it
[23:16] <bryce> heh, done
[23:16] <bryce> hmm, with sufficient firefox windows open, performance issues become evident
[23:20] <bryce> tjaalton: where'd you see r6xx gaining accel support?  The mainline tree seems to still have it disabled
[23:21] <tjaalton> bryce: not the -ati driver, but the fuss about the DRM code etc. radeonhd has exa support with the experimental code, probably will land in -ati too after a while
[23:21] <bryce> ah right
[23:29] <stgraber> yeah, scrolling pages with the ati driver on r6xx with 1680x1050 as resolution is really a pain :)
[23:29] <stgraber> for now I'm using my laptop as a server and using my Asus EEE (intel graphic :)) with an external screen ssh-ing my laptop
[23:30] <bryce> stgraber: I've uploaded a new -ati which should fix the problem you were seeing
[23:30] <bryce> stgraber: sorry it was my lousy coding that broke it
[23:32] <stgraber> bryce: no problem, thanks for fixing it :)