ubuntu-x-swat team mailing list archive

[Chris Halse Rogers <raof@xxxxxxxxxx>]

There seem to be two or three bugs here - one is that the nouveau kernel
module is trying to initialise your hardware, and fails.  In a pleasant
change of pace, it fails in such a way that the nouveau X driver doesn't
try to work, so X then tries the other drivers we've listed as possible
drivers for your hardware.

Then, the possible second bug - rather than trying the -nv driver, X
tries the vesa driver.

Then, the the third bug - the vesa driver either doesn't know how to
drive your display or doesn't know how to recover from whatever the
nouveau kernel module has done.

Since you can get to a terminal there are some things that you can try:
1) To see whether it's the fault of the nouveau module corrupting the GPU state, could you please boot the livecd, adding “nouveau.fakeparam=yes” to the kernel command line (near the “quiet splash” part is fine).  That will cause the nouveau module to fail to load.  If this works, please attach the /var/log/Xorg.0.log file.
2) Boot up, switch to a terminal, and create the following /etc/X11/xorg.conf:
Section "Device"
    Identifier "nvidia"
    Driver "nouveau"
EndSection
and then run “sudo service gdm restart” (or “sudo service gdm start” if the restart doesn't work).  That should see if the -nv driver can drive your hardware successfully.

-- 
lucid beta2: impossible to install on notebook K50IN
https://bugs.launchpad.net/bugs/560122
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in ubuntu.