[08:43] <bryce> tjaalton: btw for colin's bug #310857, I am guessing it would be worth-while to have a new xserver git snapshot package to re-test.  There's several changes from ajax in the 1.6 branch for randr-related issues
[08:46] <tjaalton> bryce: yeah
[08:47] <tjaalton> I'll prepare one
[08:48] <bryce> fwiw, I dug through the libxrandr changelog between 1.2.3 and 1.2.99.4 (and newer), but didn't see any obvious smoking guns.  I'm thinking it's just that we got a slightly too old xserver for this libxrandr
[08:52] <tjaalton> it should be the other way around
[08:52] <tjaalton> the library doesn't need the server :)
[08:52] <tjaalton> or use
[08:53] <tjaalton> and the problem only affects some intel chips
[08:53] <bryce> well, I mean a version incompatibility 
[08:54] <bryce> yeah I've not reproduced it locally here, however I've only got two intel boxes I can easily test against
[08:55] <tjaalton> for the newer xserver we also need a newer libxrandr
[08:55] <tjaalton> well, no. the server doesn't need the lib
[08:55] <tjaalton> and no driver uses the new stuff
[08:55] <tjaalton> that's currently in jaunty
[09:01]  * bryce nods
[09:07] <tjaalton> I'll disable patch 107 too
[09:08] <tjaalton> for now
[09:11] <bryce> tjaalton: good idea
[09:15] <tjaalton> a final 1.6 within a week? there are still blocker bugs on the list..
[09:16] <tjaalton> like the fact that having two cards installed you need to use BusID
[09:24] <tjaalton> eh, no randrproto 1.2.99.4
[09:33] <tjaalton> so much for updating libxrandr then
[09:34] <bryce> tjaalton: keith mentioned he wants to try doing quarterly releases
[09:34] <tjaalton> bryce: of -intel?
[09:34] <bryce> no, of the xserver
[09:34] <tjaalton> oh
[09:34] <bryce> -intel already does quarterly releases since some time
[09:34] <tjaalton> like 1.x or 1.x.x?
[09:34] <bryce> 1.x
[09:35] <tjaalton> ok, sounds like X7.5 won
[09:35] <tjaalton> duh
[09:35] <tjaalton> won't have 1.7 then
[09:35] <tjaalton> but 1.8 or so
[09:35] <bryce> yup
[09:35] <tjaalton> I'm not sure what shape MPX etc are in
[09:37] <bryce> I would imagine they would take the approach of pushing it off to a future release if it's decided not ready for that quarter's release
[09:37] <tjaalton> hmm, I might have the power to cut a randrproto release myself, but no guts :)
[09:37] <bryce> hehe
[12:04] <Ng> what's coherent mode when it's at home, and how do I toggle it? ;)
[12:06] <tjaalton> no idea, I ment to ask if you found it :)
[12:41] <Ng> tjaalton: hehe
[12:41] <Ng> I think it might be a radeon thing, but it's proving pretty hard to find info about
[12:47] <tjaalton> yeah
[12:48] <tjaalton> great, the new xserver snapshot changed some xquartz binaries, meaning debuild -S fails
[12:48] <tjaalton> maybe those could be just removed from debian/ubuntu branches
[12:50] <Ng> I'm wondering if the ridiculous BIOS in this machine might be to blame, the "Intelligent Tweaking" page has a lot of things set to "Auto" and I have no idea if that means "Automatically pick the official values" or "Automatically try to overclock my hardware"
[12:50] <Ng> e.g. "Robust Graphics Booster" which claims to increase PCI-E bandwidth and has the options "Auto", "Fast" or "Turbo". How about "Off"? ;)
[12:53] <tjaalton> yep, bios might be something to check
[12:54] <Ng> I forced the PCI-E clock to 100MHz and gave the northbridge 100mV more food, will see how it goes
[12:54] <tjaalton> "robust graphics booster" doesn't sound too robust to me ;)
[12:54] <Ng> well that's the hilarious thing, when you are changing that setting there's a load of red text that appears and warns you that a bad setting will make your machine explode in a giant fire, or something like that ;)
[12:55] <tjaalton> hah
[13:01] <Ng> interesting side problem, the radeon claims to be showing 1920x1080, but an inch or two of picture is missing on the right&bottom
[15:47] <terli> can I get some help configuring multiple pointers