Comment 10 for bug 232012

I have now experimented with three other ways to use then restricted driver:- Manually editing xorg to change nv driver to nvidia, running sudo nvidia-xconfig in a console, and running sudo apt-get purge nvidia-glx and then reselecting the restricted driver in the "hardware Drivers Manager".

In each case, after a reboot the results are the same:- Booting stops in console mode and auto-invokes the displayconfig dialog in "low resolution mode". The dialog has the "vesa" driver used, as it says no card could be detected. I can manually select "geforce2 DDR (generic)" from the list but only the OpenSource driver is available, the button for this is greyed out. Click OK and this takes me back to console login with no message as to what to do! But I now know from experience just to Ctrl+Alt+Del to restart. The reboot then logs in as normal with all setting correctly detected, but on the open driver. Also, if you press "Continue" in the displayconfig dialog, you are sent back to console login. sudo displayconfig says there is "no X server available" to run it! startx gives some error messages which says something like the Nvidia kernel module has a mismatch with the Nvidia driver and gives some different number for each. This has always worked before from Feisty through the upgrade to Gutsy, and pre-Ubuntu Linux.

The lack of a splash KDE was due to a missing mood..something plugin. So this plugin must be missing on the live CD too.