[05:57] <RAOF> Sarvatt: 7PM EST?  No chance. :)
[06:05] <ulysses> morning
[06:06] <ulysses> Maverick freezes after login with latest drm/mesa, anyone noticed? https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/644740
[06:06] <ubot4> Launchpad bug 644740 in xserver-xorg-video-intel (Ubuntu) "[i915] drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung (affects: 1) (heat: 8)" [Undecided,New]
[06:08] <RAOF> Hm, fun.
[06:09] <RAOF> Oh, I see you've got the same GPU as I do.
[06:09] <RAOF> And I don't see that crash.
[06:09] <ulysses> I have KDE 4.5.1, the crash appears only when I enable desktop effects
[06:11] <RAOF> Sarvatt: I got up at 11am today (which I had organised to take off, because I *knew* I'd be totally worthless at work)
[06:14] <RAOF> ulysses: Since I don't see that problem, could you try disabling individual effects and seeing which one kills it for you?
[06:14] <Sarvatt> ahh sorry RAOF, I was just guessing you got home sunday and had time to recover already and had no idea
[06:14] <ulysses> I'll try later, now I have to go
[06:15] <RAOF> Sarvatt: I _left_ Sunday :0
[06:15] <RAOF> I *arrived* Tuesday, late afternoon.
[06:15] <RAOF> No need to apologise!
[06:19] <RAOF> Now to go congratulate/commiserate with my brother after his driving test!
[06:29] <bryceh> heya raof
[07:05] <RAOF> bryceh: Howdie!
[07:05] <RAOF> Alex said hi :)
[07:05] <bryceh> cool
[07:46] <bryceh> RAOF, anything noteworthy happen?
[07:47] <RAOF> There was a particularly interesting discussion of unpriviledged X.
[07:47] <RAOF> Keith wants to make X unpriviledged in a particularly strong sense of the word.
[07:47] <bryceh> for meego?
[07:47] <RAOF> As in “no part of X is trusted”.
[07:48] <RAOF> No; meego doesn't have multiple users, so the trust issues aren't there.
[07:48] <RAOF> IE: the basic reason why you can't just strip off the setuid bit of X right now is (a) ums drivers, and (b) input arbitration.
[07:49] <RAOF> As you, of course, know :)
[07:49] <bryceh> yep
[07:49] <RAOF> Meego doesn't care about input arbitration.
[07:49] <RAOF> So it's a bit easier.
[07:49] <RAOF> Keith wants X out of *all* trusted paths, and hence out of the input arbitration business.
[07:50] <RAOF> So one (or more) X server per user, with the kernel+ConsoleKit handling input arbitration.
[07:51]  * bryceh nods
[07:51] <RAOF> By changing input devices from broadcast to one-fd-gets-it (like current serial devices)
[07:51] <RAOF> + a syscall for ConsoleKit to tell the kernel which fd should get input.
[07:52] <bryceh> speaking of ums, any word regarding 8xx?
[07:53] <RAOF> No one cares about it :/
[07:54] <bryceh> hrm
[07:54] <RAOF> Chris' shadow, that's now merged to trunk, looks like it'll provide a stable and somewhat featureful intel driver for i8xx.
[07:54] <RAOF> At the cost of 3D, of course :(
[07:56] <RAOF> I mean, fundamentally some of the hardware is broken, and old enough that there are more productive uses of time.
[07:56] <bryceh> I found a community guy with hw experience that might work on it
[07:56] <RAOF> On the X mailing list?  Yeah, that'd be great to have i830 better supported.
[07:57] <bryceh> ubuntu-x@ yeah
[07:58] <bryceh> I have a feeling this is one of those things that people don't volunteer to help with because they assume "someone else will do it"
[07:58] <RAOF> There's of course that other bug where there's no kernel driver for the interface thingy on some i810 cards, too.
[07:58] <bryceh> so it may be the best thing we can do to help it would be to declare it unsupported in ubuntu, and that no further developer time from canonical will go into it
[07:59] <RAOF> bryceh: Yeah.  It requires an unusual conjunction of willingness to get one's hands dirty, hardware, and some driver confidence.
[07:59]  * bryceh nods
[10:43] <tseliot> RAOF, Sarvatt: shall I use bug 630599 as a reference for fglrx's incompatibility with maverick's xserver or do you have a better bug report?
[10:43] <ubot4> Launchpad bug 630599 in fglrx-installer (Ubuntu) "Upgrade to 10.10 fails to load xorg (affects: 6) (dups: 5) (heat: 264)" [Undecided,New] https://launchpad.net/bugs/630599
[12:56] <RAOF> tseliot: That seems like a perfectly cromulent bug report o have as a reference.  I'd probably add the reason to the description, though.
[12:57] <jcristau> hi RAOF 
[12:57] <RAOF> Hey there jcristau 
[13:02] <RAOF> jcristau: I trust your journey back was substantially less epic than mine? :)
[13:02] <jcristau> it was very much un-epic
[13:02] <jcristau> so, probably :)
[13:08] <tseliot> RAOF: yes, good point
[19:40] <patrickdickey> I came in yesterday afternoon asking about the proper driver for an ATI Graphics Card (RC410 Radeon Xpress 200M). I've got another question.  It seems that my xorg.conf is uisng the "radeon" driver. Is that the correct driver (I was told to install the -ati package), or should it be "ati" in xorg.conf?
[19:41] <patrickdickey> Ultimately I'm trying to eliminate a really annoying screen flicker on my external monitor, whenver I open things like a virtual machine in VMWare Player, or Rosetta Stone (through Wine).
[19:42] <Sarvatt> patrickdickey: that is the default driver, you dont need an xorg.conf for it. that problem should be fixed if you boot with radeon.new_pll=0 added to your kernel command line
[19:43] <Sarvatt> you can hold shift while booting, select the kernel and press e to edit it, then where it says quiet splash, add radeon.new_pll=0 to the end of that line
[19:44] <Sarvatt> if that works you can edit /etc/default/grub and add it to the GRUB_CMDLINE_LINUX_DEFAULT= line, like GRUB_CMDLINE_LINUX_DEFAULT="quiet splash radeon.new_pll=0", save it, sudo update-grub and reboot
[19:48] <patrickdickey> Wow, you must have been reading my mind. I was just going to ask you if I needed to put it in that line.  Currently I have i915.powersave=0 there, but I don't think that works for me. 
[19:50] <patrickdickey> The other issue I have (and it may be related to the flickering) is that in dmesg, it shows that it found my external monitor, but couldn't get it's EDID? From it (It's an Acer P241W monitor). Is there a way of fixing that?  I realize that's probably out of scope from this room.
[19:56] <patrickdickey> Anyhow, I'll give the radeon.new.pll=0 a try.  Thanks for all of your help (and bryceh's help yesterday also).  Have a great day:)