Bulletproof X broken for nVidia

[plun]

Binary package hint: xorg

-Gutsy > Kernel upgrade to 2.6.22-13

- Restricted manager resets info about nVidia driver enabled.

- linux-restricted-modules-2.6.22-13-generic is not installed automagic

- No Bullet proof mode... X crashes.

Solved with Envy and wget from tty

This functionality must work despite of an "dirty driver".

[Ulrik Mikaelsson (rawler)]

I had a similar result.

I got BulletProof X running, but once trying to reconfigure anything, OR continue with the low-res config, the system froze.

[plun (plun)]

The same "fiasco" with kernel upgrade to 2.6.22-14

[Monty Taylor (mordred)]

I second this. -13 and -14 are totally unusable with my nVidia Corporation Quadro NVS 140M (rev a1). I've still got -12 around, so I've just been booting with that. I suppose I could try envy, but I'd rather have this work with linux-restriced-modules and nvidia-glx-new. Let me know if there's anything I can do to help solve/troubleshoot this.

[Brian Murray (brian-murray)]

I am changing the status to Confirmed based upon the fact that this has happened to multiple people For future reference you can manage the status of bugs by clicking on the current status in the yellow line and then choosing a new status in the drop down box. You can learn more about bug statuses at http://wiki.ubuntu.com/Bugs/Status .

[Henrik Nilsen Omma (henrik)]

This bug was nominated for Gutsy but does currently not qualify for a 7.10 stable release update (SRU) and the nomination is therefore declined.
According the the SRU policy, the fix should already be deployed and tested in the current development version before an update to the stable releases will be considered. With 7.10 now released, that policy applies to this bug. See: https://wiki.ubuntu.com/StableReleaseUpdates .
The bug is not being closed as work will continue on fixing it for the next release, Hardy Heron (8.04). If the state of this bug should change such that it qualifies for the SRU process, please contact the person who originally declined it and ask them to re-evaluate it. To help improve the state of this bug see: https://wiki.ubuntu.com/Bugs/HowToTriage .

[Bryce Harrington (bryce)]

There is currently insufficient information to troubleshoot this bug. Can you please provide your Xorg.0.log files and xorg.confs showing the reason why it entered into bulletproof mode, and why bulletproof mode failed?

[plun (plun)]

Well, for me this was during Gutsys development.

For Hardy it has never failed but a big "but"... it takes
rather long time for the failsafe driver to start.

Just noticed that for "newbies" this is indeed confusing
and also annoying for an experienced user which directly wants to kill GDM
from tty and reinstall a "dirty driver" from nVidia....(or ATI)

[Timo Aaltonen (tjaalton)]

Looks like this issue is resolved with Hardy, closing the bug.

failsafe takes some time to start because it tries a normal startup a couple of times first before failsafe kicks in.

[John Pye (jdpipe)]

I don't think this issue is fixed in Hardy. After upgrading from Gutsy to Hardy, my nvidia Quadro card is not detected, and no Nividia option appears in the 'restricted drivers' box, even when I have nvidia-glx-new installed.

Suggest reopening?

[John Pye (jdpipe)]

1. Yesterday, everything was working fine with 'nvidia' being my video driver.

2. Hardy updated using Update Manager, May 276 2008

3. Rebooted, new kernel is now

Linux mycomputer 2.6.24-17-386 #1 Thu May 1 13:57:56 UTC 2008 i686 GNU/Linux

4. Nvidia video driver is no longer visible and doesn't appear in the System->Hardware Drivers menu. Can't use high resolution graphics. Can no longer use 'dpkg-recongure' to change video driver (doesn't have that option any more).

/var/log/Xorg.0.log contains:
(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)

[John Pye (jdpipe)]

Problem in my case appears to have been the absence of the 'linux-restricted-modules-386' package on my machine. I am puzzled as to how it can be possible for me to install 'nvidia-glx-new' without this package; it looks to me that it is a missing dependency, given that I was running a 386 kernel.

[Timo Aaltonen (tjaalton)]

John, if you need to run the -386 flavour, you should also have the 'linux-386' metapackage installed to make sure you always have the matching restricted package installed.