On Fri, Jan 15, 2010 at 13:40:21 +0100, Vincent Lefevre wrote: > On 2010-01-15 11:57:15 +0000, Julien Cristau wrote: > > On Fri, Jan 15, 2010 at 12:28:13 +0100, Vincent Lefevre wrote: > > > > > On 2010-01-15 12:24:24 +0200, Anton Zinoviev wrote: > > > > I suppose this means you are using xserver-xorg-video-nv (not the > > > > non-free driver by nvidia). > > > > > > No, I'm using the non-free driver by Nvidia (the free driver is > > > unfortunately unusable on this machine). > > > > Then I guess you'll have to contact nvidia for support. > > I'm wondering: what does the X driver have to do with a console > problem? Shouldn't the console code do this by itself? > > Also, I'm not sure whether the problem is related, but the > console-setup FAQ says: > > And sometimes the console setup is never remembered. In this case > you will have to use framebuffer (try "modprobe vga16fb"). Another > uption is to to use the "setupcon" utility whenever you need to > restore the console setup and hope that the problem will be fixed > in some future version of X Window. You may want to send a bug > report to the X developers. > ^^^^^^^^^^^^^^^^^^^^^^^^^^ > > But is it dependent on the X driver or not? > nvidia ships an X driver, a kernel driver and a libGL. While the last one is probably not the culprit, any of the first two can mess up the video state.
Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
