[03:37] <Sarvatt> incase ya guys update mesa to 7.6.1+ now it requires libdrm-radeon1 2.4.17+ to build
[07:22] <bryce_> Sarvatt, found problems with libdrm 2.4.17?
[07:34] <tjaalton> the radeon API has changed, so mesa&ati need to be rebuilt when libdrm is updated
[07:37] <tjaalton> they also need to be updated to build
[16:05] <Sarvatt> do control+alt+f-keys work for anyone in lucid to switch from a VT back to X?
[16:07] <tseliot> yep, at least with intel
[16:08] <Sarvatt> ah thanks for checking, guess its just a problem with my setup and not a general problem then
[16:24] <apw> RAOF, hey ... you about?
[20:01] <alex-weej> since we moved to xplash
[20:01] <alex-weej> my xcalib line in /etc/gdm/Init/Default does nothing
[20:02] <alex-weej> perhaps the whole file does nothing
[20:02] <alex-weej> help!
[20:37] <Sarvatt> jcristau: if it helps any, this commit completely fixes the flickering and freezing on a solid color problem on intel for me: http://git.kernel.org/?p=linux/kernel/git/anholt/drm-intel.git;a=commit;h=cf74ecbbff3e3b45bae61d28d2220f74d853e2f0
[20:37] <Sarvatt> just wish it applied to 2.6.32 :D
[20:40] <Sarvatt> i'm amazed i'm down to 6.1 watts idle power usage with the screen on with the latest drm-intel-next kernel, 2.6.32.2 and 2.6.33 are both closer to 8 watts and i'm using i915 powersave=0 on them all
[20:43] <Sarvatt> hmm, getting glyph corruption after resume on this drm-intel-next one though, all the letter a's have a line through them just in gnome terminal
[20:44] <Sarvatt> minimized and maximized and now it's just k's, weird
[20:57] <jcristau> Sarvatt: so we need a backport of that to .32?
[21:02] <Sarvatt> yeah for sure, it doesnt apply to 2.6.32.2 here as-is but eric anholt mentioned about sending it to stable here so I'm hoping http://lists.freedesktop.org/archives/intel-gfx/2009-December/005234.html
[21:23] <bryce_> heya
[21:23] <bryce_> Sarvatt, how are things looking with libdrm lately?
[21:26] <Sarvatt> hasn't changed here, haven't really been any intel commits since right before 2.4.16 released at the beginning of december when the problem started for me and a few other people. i've managed to have >24 hours uptime so far on 2.4.17 though with a drm-intel-next kernel somehow though
[21:27]  * Sarvatt is asking to crash any minute now.
[21:27] <bryce_> heh
[21:27] <bryce_> any luck getting debug data on it?
[21:28] <Sarvatt> yeah, just overwrote it all by accident last time it happend with a > instead of a >>, yay
[21:28] <bryce_> oops
[21:28] <Sarvatt> just found this bug about it though http://bugs.freedesktop.org/show_bug.cgi?id=25475
[21:38] <bryce_> hrm
[21:38] <bryce_> Sarvatt, ok I'll raise this with yingying
[21:42] <Sarvatt> i went back to the crack to try to make it crash again, looks like i might need to use the lucid kernel too because it's not happening with drm-intel-next. 
[21:48] <bryce_> http://qa.ubuntuwire.com/multidistrotools/x.html
[21:50] <Sarvatt> too funny, crashed while i was saying how it wasnt crashing
[21:50] <Sarvatt> got all the debug info though, i'll put it up after a bit of christmas shopping :)
[22:44] <RAOF> apw: Hi, I am about now.
[22:44] <RAOF> apw: Have you gone yet? :/
[23:14] <RAOF> Sarvatt: How'd you like to test a new nouveau-kernel-source that Recommends: nouveau-firmware?
[23:24] <tjaalton> RAOF: he was asking for the nouveau trees, I gave the links to the ones posted on dri-devel@
[23:36] <RAOF> Ah, OK.