[00:42] <horstle> is anybody interested in a reproducable "NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context"?
[00:43] <horstle> im running NVIDIA 275.19 with a gf 9300 onboard
[00:46] <RAOF> horstle: nvidia might be; bug reports go to the nvnews forums.
[00:47] <horstle> well im waiting for response from bjsnider, afaik he is from nvidia
[01:56] <bjsnider> you're waiting for a response from me?
[01:56] <bjsnider> this is the first i've heard of it
[01:56] <bjsnider> and i'm not from nvidia
[01:56] <bjsnider> i'm from canada
[02:00] <bjsnider> horstle, http://www.nvnews.net/vbulletin/showthread.php?t=46678
[07:21] <ripps> well, the lastest xorg-edgers has been causing my i5-2400 igp to hang alot. It loses all 3d/2d acceleration until I reboot after dmesg says I fails from a gpu hang
[07:21] <RAOF> ripps: Kernel problem, or DDX/mesa?
[07:22] <BigWhale> Greetings... Where can I find some more info what's going on with intel drivers and 855GM chipset?
[07:22] <RAOF> BigWhale: There's not much going on.  Hm.  Maybe we should turn them back on; it's apparently possible that they work now.
[07:22] <RAOF> Upstream is where you want to be, though.
[07:23] <ripps> RAOF: I don't know. I've gotten these gpu hangs in the recent past, but I could always recover from them. I wouldn't lose my acceleration altogether, I just had to restart compiz.
[07:24] <RAOF> ripps: Feel like trying an older/newer kernel, then?
[07:24] <ripps> RAOF: I'm using 3.0.0-7
[07:24] <BigWhale> I instaled Natty on some old laptop and then enabled intel drivers and the results were poor... windows flickering and disappearing...
[07:24] <ripps> This is a natty machine with xorg-edgers
[07:25] <RAOF> ripps: You could try the drm-intel-next mainline build, and/or go back to an older kernel.
[07:27] <ripps> It's kinda late for me now, I'm going to bed. I'll pastebin my dmesg and any other logs you want the next time it happens, then I'll try out an older kernel
[07:32] <RAOF> ripps: If you want to help debug, i915_error_state is pretty much mandatory.
[07:32] <RAOF> BigWhale: I'd want to be sure that you successfully enabled the intel drivers, but I wouldn't expect flickering windows; I'd expect it to hang pretty frequently, though.
[07:35] <ripps> Just FYI, the hang usually happened when switch mplayer between fullscreen and windowed
[09:03] <BigWhale> RAOF, I installed this driver https://launchpad.net/~glasen/+archive/intel-driver
[09:04] <BigWhale> RAOF, enabled modeset and there was a lot of flickering and unity failed to start so it was a fallback to classic desktop. Flickering was take care of by disabling effects.
[09:05] <BigWhale> 3D support seems to work only partially glxgears will run but there's a game that doesn't work
[14:19] <Sarvatt> ripps: try again after updating now, I didn't see there was a new update to fix that a few days ago
[15:02] <kirkland> howdy, I have a video/unity/x issue, thinkpad x201, lspci at http://paste.ubuntu.com/653832/
[15:02] <kirkland> I can't get 1920x1080 to my external monitor
[15:02] <kirkland> worked in lucid,maverick, regressed in natty (and I just lived with 1280x800), and I just upgraded to oneiric hoping it might have been fixed
[15:03] <kirkland> but no dice
[15:06] <seb128> kirkland, what output do you use?
[15:07] <kirkland> seb128: okay, so the thinkpad sits in a docking station, connected externally by SVGA to a 24" Samsung monitor
[15:07] <kirkland> seb128: i want to disable the output on the laptop screen, and only have one output, to the external monitor
[15:08] <kirkland> seb128: i can only do that up to 1280x800 resolution, which is what the laptop screen maxes out at
[15:08] <seb128> kirkland, https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/729788
[15:08] <kirkland> seb128: however, the external monitor can certainly do 1920x1080
[15:08] <ubot4> Launchpad bug 729788 in xserver-xorg-video-intel (Ubuntu) "xrandr reports incorrect max resolution from displayport in laptop dock i915 (affects: 2) (heat: 23)" [Undecided,Confirmed]
[15:09] <seb128> seems similar
[15:09] <kirkland> seb128: yeah, definitely
[15:10] <seb128> kirkland, I don't know the specific, I asked because I know pitti or some others had issue which were happening on the displayport but not on the standard vga output I think
[15:10] <kirkland> seb128: hmm, okay, maybe i'll poke pitti?
[15:11] <kirkland> seb128: any known workarounds?
[15:11] <seb128> kirkland, he's on holidays until end of next week
[15:11] <seb128> kirkland, did you try the commands from this bug?
[15:11] <kirkland> seb128: okay
[15:11] <seb128> I'm looking for the other bugs I read on the topic, wait
[15:12] <kirkland> seb128: not yet, do you recommend those?  I'm not as familiar with xrandr as I should be ...
[15:12] <seb128> kirkland, bug #737891 is the one I was thinking about
[15:12] <ubot4> Launchpad bug 737891 in xserver-xorg-video-intel (Ubuntu Natty) (and 5 other projects) "[Arrandale] gnome-display-properties unable to correctly enable monitors connected to VGA (affects: 15) (dups: 2) (heat: 98)" [Wishlist,Invalid] https://launchpad.net/bugs/737891
[15:12] <kirkland> seb128: yes, that one I am familiar with
[15:12] <kirkland> seb128: I'm subscribed, and have commented a few times
[15:13] <kirkland> seb128: i sort of gave up on that one being solved for Natty
[15:13] <kirkland> seb128: but really, really hoping it gets solved for Oneiric
[15:13] <kirkland> as 1280x800 resolution on a 24" monitor looks comical :-)
[15:13] <kirkland> seb128: i've nominated it for Oneiric
[15:14] <seb128> kirkland, it shouldn't hurt to try to set the resolution with the second call from the first bug I pointed
[15:14] <seb128> if that doesn't work wait for some of the x guys to reply
[15:14] <seb128> they probably know better than me ;-)
[15:14] <kirkland> seb128: thanks man :-)  will try now
[15:15] <kirkland> seb128: hmm, hang on a second ...
[15:15] <kirkland> seb128: in the displays dialog, I have 1920x1080 as an option
[15:15] <kirkland> seb128: but when I switch to it, I get unity offset from the center, some big black, unusable areas of the screen, and the display is just not coherent
[15:15] <seb128> kirkland, what happen if you try to use it?
[15:16] <kirkland> seb128: I can shoot a picture with my phone, one second ...
[15:16] <seb128> kirkland, that seems a compiz bug, just alt-f2 compiz --replace
[15:16] <seb128> or alt-f2 unity
[15:16] <seb128> compiz doesn't like dynamic resizing it seems
[15:16] <kirkland> seb128: oh?
[15:16] <kirkland> seb128: that sounds promising
[15:17] <kirkland> seb128: it certainly looked to me to be a unity/compiz bug from my first guesses, but most of the time when I talk to someone about it, they point me to X, and then to the kernel :-)
[15:21] <kirkland> seb128: actually, that worked
[15:21] <kirkland> seb128: so here's what i had to do:
[15:21] <kirkland> seb128: 1) go to displays, select 1920x1080, apply
[15:21] <kirkland> seb128: 2) very quickly do the alt-f2 unity <enter>
[15:22] <kirkland> seb128: 3) very quickly click keep configuration
[15:22] <kirkland> seb128: not that alt-f2 compiz --replace did NOT work
[15:22] <kirkland> seb128: and note that it took me a couple of tries to get it right within the 15 seconds before it automatically reverted
[15:23] <kirkland> seb128: so now I wonder if it persists across reboots ...