[04:01] <LLStarks> hi, is there any reason why i'd be unable to access a tty using recovery mode or ctrl+alt+num?
[04:02] <RAOF> Because something's messed up your VTs?
[04:02] <RAOF> Such as… da da da DAAAAM, nvidia? :)
[04:04] <RAOF> Bah.  Stupid intel stupid dpms stupid waaaaaaraghrfl
[04:05] <ScottK> Nvidia is much simpler.  "Meh.  Nothing I can do."
[04:16] <LLStarks> raof, 945gm
[04:16] <LLStarks> i always get a blinking cursor
[04:16] <LLStarks> no VT
[04:17] <LLStarks> cleared 99% of my home's hidden folders and wiped /
[04:17] <LLStarks> no luck
[04:17] <RAOF> Maybe getty's not being spawned?
[04:17] <LLStarks> would a xorg log be helpful?
[04:22] <RAOF> Not really.
[04:22] <RAOF> Unless X isn't coming up properly.
[04:23] <LLStarks> x is loading fine, but there's no backend terminal i can use.
[04:32] <RAOF> The x log is unlikely to be very interesting.
[04:36] <LLStarks> raof, do you have any recommendations for triaging?
[04:36] <RAOF> I'd suggest that upstart is actually what you want to be debugging.
[04:37] <LLStarks> i have a bootchart, would that reflect getty's non-presence?
[04:38] <RAOF> Yes.
[06:43] <RAOF> Ok, so it looks like GM45 at least won't GPU hang on dpms events.  Or, rather, the missing vblank issue will kill X before it triggers.
[07:36] <Sarvatt> RAOF: that was reported on ati too, but heck if I can find it
[07:37] <RAOF> What, missing vblanks?
[07:38] <Sarvatt> almost identical backtrace, the _CallCallbacks/DRI2WaitMSCComplete one?
[07:39] <Sarvatt> you were talking to the guy in #xorg-devel a few weeks ago actually, let me see if I can find the log
[07:39] <RAOF> Oh, that one.
[07:40] <RAOF> So, I know how to trigger *something* like that with reckless abandon on intel - have a client hang waiting for vblank, and then start another GL app :)
[07:41] <Sarvatt> RAOF: which bug are you talking about then? btw they dont really want intel_gpu_dump output anymore, /sys/kernel/debug/dri/0/i915_error_state has the good info
[07:55] <LLStarks> this really sucks. i have no access to a tty unless i chroot through a liveusb. is there anyway to Xorg -configure without a tty and shut-down x?
[08:03] <tjaalton> LLStarks: try putting 'GRUB_GFXPAYLOAD_LINUX=text' in /etc/default/grub
[08:04] <tjaalton> and run update-grub
[08:04] <LLStarks> thanks timo
[08:05] <tjaalton> if that works, follow the instructions here https://lists.ubuntu.com/archives/ubuntu-devel/2010-December/032244.html
[08:05] <tjaalton> to file a bug
[08:06] <LLStarks> i'll see if this works
[08:25] <ripps> I added libbluray to the Natty builds of mplayer2 in my ppa. Too bad this won't allow it to play commercial bd's with aacs or bd+
[08:25] <tjaalton> surprised?
[08:27] <ripps> well, it would require installing libaacs and having a valid key set for the disc being played. I haven't discovered an easy way of implementing this. Not to mention it would probably get my ppa shut down if it was discovered
[13:24] <maxb> Is there a better way to toggle between radeon and fglrx than installing and uninstalling fglrx?
[13:28] <maxb> ooh, gl_conf alternative
[13:28]  * maxb tries it
[13:40] <tseliot> maxb: and make sure you do "sudo ldconfig" and "sudo update-initramfs -u" after you change the alternative
[14:32] <maxb> Can anyone offer me any advice on writing a useful bug report for my mouse pointer disappearing when positioned close to one edge of my secondary monitor?
[14:33] <maxb> It does not occur if I switch from radeon to fglrx, but does that mean I should report it against the radeon driver, or could it be in mesa? (I believe fglrx replaces that too?)
[14:35] <maxb> tseliot: Ah, thanks. I failed to do so, but I will remember for next time :-)
[14:36] <maxb> I also had a catalyst control centre autogenerated xorg.conf I needed to nuke
[14:36] <tseliot> right, that too
[16:10] <LarsTorben> are here developers ??
[16:35] <zniavre> good afternoon 
[16:36] <zniavre> do i need to report that nvidia updated their 173 driver ? > ftp://download.nvidia.com/XFree86/Linux-x86/173.14.30/
[16:36] <zniavre> but unity can't work with them 
[17:02] <tseliot> zniavre: there's no need to do that. I'll upload it today
[17:03] <bjsnider> znaii don't see why it wouldn't run compiz/unity
[17:04] <bjsnider> zniavre,  don't see why it wouldn't run compiz/unity
[20:15] <Sarvatt> RAOF: YokoZar said he'd update ia32-libs tonight so 32 bit mesa will work again \o/
[20:23] <zniavre> bjsnider, the fact is ...  unity works with nouveau+dri-experimental but does not with the 173.14.30 (after gdm unity can't load the desktop its blinking ad-vitam)
[20:51] <bjsnider> zniavre, the driver hasn't been packaged yet
[21:11] <zniavre> bjsnider,  they are 
[21:11] <zniavre> https://launchpad.net/ubuntu/natty/+source/nvidia-graphics-drivers-173/173.14.30-0ubuntu1
[21:12] <bjsnider> does opengl work at all?
[21:12] <zniavre> yes
[21:12] <bjsnider> compiz won't start?
[21:13] <zniavre> compiz can work with gnome-classic session only
[21:13] <zniavre> not with unity after gdm the desktop is blinking and does not load unity-panel and launcher 
[21:15] <zniavre> https://bugs.launchpad.net/ubuntu/+source/unity/+bug/767613
[21:15] <bjsnider> well i think you shuld report a unity bug
[21:15] <ubot4> Launchpad bug 767613 in unity (Ubuntu) "unity does not start with nvidia173.14.30 (affects: 1) (heat: 6)" [Undecided,New]
[21:15] <bjsnider> ok
[21:15] <zniavre> :o)
[21:15] <zniavre> i reported with driver from repos
[21:16] <bjsnider> there's no real reason to use the 173 if it can't run unity
[21:16] <bjsnider> unless you're a kde user i guess. there are still a few of them kicking around
[21:16] <zniavre> nouveau can run unity but that s all in fact the rest is a real apin to use (flash opengl apps etc...)
[21:17] <bjsnider> if you've got no unity with the 173 and have to run the classic desktop i think nouveau can probably do it better than the 173
[21:18] <zniavre> i m not against you 
[21:18] <Sarvatt> hmm, didn't someone report unity not working with nvidia-current on a opengl 2.1.2 era nvidia too? a 7500gt I think?
[21:19] <bjsnider> well, that would have to be a geforce pre-8k