[upstream] nvidia-glx doesn't restore state on NV35/NV36 cards. Causes random mess on screen or system hang.

[Lambros Lambrou]

Upgraded to Dapper from Ubuntu Breezy, AMD64, using online repositories. System works just fine until I try to shut down, or if I switch out of X to a virtual console using Ctrl-Alt-F1. The display goes black and about 1 second later fills up with random noise. Machine completely hangs - it won't switch back with Ctrl-Alt-F7, nor will the power button do anything; have to use the reset button to switch off the PC.

I suspected usplash might be responsible. This was confirmed when I uninstalled usplash, everything worked just fine (I was able to switch back and forth between X and virtual consoles). And when I installed usplash again, this problem reappeared.

'uname -a' gives:
Linux lambros-home 2.6.15-15-amd64-k8 #1 SMP PREEMPT Thu Feb 9 19:59:33 UTC 2006 x86_64 GNU/Linux

usplash version is 0.1-30 (dapper)

sysvinit and sysv-rc are 2.86.ds1-6ubuntu11

Graphics card is nVidia GeForce FX 5950 Ultra

I'm running X with nvidia drivers - 3D-accelerated games run perfectly

Please do let me know if you need further information or clarification. The problem seems to be quite serious as it prevents the PC from ever being shut down cleanly (except it works fine if I uninstall usplash).

Lambros

[Lambros Lambrou (lambros)]

A bit more info: I've discovered that if I disable graphics hardware acceleration, this problem no longer occurs. I modified my xorg.conf by replacing "nvidia" with "vesa", and installed usplash. My system then worked fine (albeit with software-rendered flickery low-res display :-) and I was able to switch back and forth between virtual consoles.

In summary, my system works fine if I either have
* usplash installed
or
* nvidia drivers enabled
but not both.
So I'm no longer sure if this bug is filed in the right place :-)

Versions are:
xserver-xorg 7.0.0-0ubuntu17
nvidia-kernel-common 20051028+1
nvidia-glx 1.0.8178+2.6.15.6-1
usplash 0.1-31
sysvinit (and sysv-rc) 2.86.ds1-6ubuntu17
kernel is now upgraded slightly: 2.6.15-16-amd64-k8

Not sure what other experiments are worth trying. I tried using a lower screen resolution and refresh-rate, didn't make any difference. I had a look at my 'dmesg' output but there didn't seem to be anything relevant to this. I can only guess it must be a weird hardware combination that I have - I haven't noticed any other discussion about this on the forums.

[Lambros Lambrou (lambros)]

Changed to "Major" since I think this could severely impact a small proportion of users, hope that's OK. It would be a shame if this persisted through to the Dapper release - please let me know if there's anything I can do to help debug this.

[Nicholas Wheeler (dragoncow2)]

I have a similar problem - I get a black screen after switching to console using the nvidia drivers. Switching to the 'nv' driver fixes this problem. Uninstalling usplash did not fix this issue.

[Erik Ferguson (muraiki)]

I have the same problem in both Breezy and Dapper. When logging out, rebooting, or shutting down, I get colored lines all down my screen and have to reboot. This only occurs when using the nvidia binary drivers; the nv driver works fine. Uninstalling usplash did not resolve this problem.

I did not experience this problem in Hoary, and I do not have problems using the nvidia drivers under other distros.

[Erik Ferguson (muraiki)]

Oops, I spoke too soon. I forgot that on the first reboot usplash would still be active. On the second reboot (the first boot when usplash wasn't present) my computer rebooted fine.

[Steven Black (stevenblack141)]

I wonder if this is actually related to usplash or if it is actually related to the framebuffer kernel driver. Which framebuffer driver is being used? ("cat /proc/fb" should provide a list of the loaded framebuffer drivers.)

If this is related to the setup or tear down of the videocard, it is very possible that it is in the domain of the framebuffer driver (and/or the "nvidia" X driver) and not usplash.

[Lambros Lambrou (lambros)]

Fascinating! :-)
With usplash not installed, "cat /proc/fb" returns no output at all.
With usplash installed and active, that command returns
"0 VGA16 VGA"
You could be right, it may be a problem with the VGA16 driver that only shows up when usplash is used.
Are there simple commands I could type to switch this VGA16 driver on and off? Would be interesting to know what difference this makes.

[Matthew Garrett (mjg59)]

Ok, sounds like a bug in the nvidia binary drivers.

[Daedalus (daedalus-online2002)]

Im running Kubuntu Dapper
Uname -a gives
"Linux ubuntu 2.6.15-19-386 #1 PREEMPT Mon Mar 20 16:46:02 UTC 2006 i686 GNU/Linux"

Installed the latest nvidia glx drivers (running a geforce2 mx 100/200)

X works fine when i boot pc. If i haveto restart X for whatever reason (ctrl-alt-bksp) the comp just freezes with the power led blinking. Only works again when i press the reboot button or a cold boot. What gives?

[Sitsofe Wheeler (sitsofe)]

mjg59:
I believe nvidia have always said it was dangerous to have two different pieces of software trying to control the video card at the same time...

[Matthew Garrett (mjg59)]

vga16fb assumes no significant quantity of state. If the system is crashing when switching from X to the console, then that's because the nvidia driver is failing to restore the state that it's expected to.

[Sitsofe Wheeler (sitsofe)]

mjg59:
Sounds like you know far more about what should be happening than I do (I'm meerly paraphrasing a document I read).

I've been wondering for some time, what Ubuntu's policy is on nvidia binary bugs... Does Ubuntu have a policy like Red Hat to resolve such bugs invalid and point users towards nvidia or is Ubuntu more like SUSE where they can ask a designated nvidia developer to look at certain bugs (and presumably take such bugs on) and give feedback?

[Brian Geppert (briangeppert)]

I'm having identical problems, but I'm running an up-to-date Ubuntu Hoary.

With a virgin Hoary install, this problem does not occur, but if I update, it will (tested on numerous installs).

I have a 5700U.

[Ben Li (bli-linsang)]

I also experienced this problem upgrading to dapper through apt. Another temporary fix is to add "vga=normal" as a kernel boot option. However, this effectively disables usplash.

[Loïc Corbasson (cnb)]

I'm having the same problem with Dapper, and had it for a few months with Debian Sid. Some info about my system can be found here: http://www.ubuntuusers.de/paste/579/

[Thrift (thrift24)]

Happens to me as well. It definately only happens when using the framebuffer. Adding vga=normal works until the next kernel update at which point it loads the framebuffer driver and crashes.

I get garbled console when switching from X to the console. When switching back to X i get a crash.

When I log out or switch users it hard locks.

I am fully up to date right now.

Relevant lspci linage:
0000:01:00.0 VGA compatible controller: nVidia Corporation NV36.1 [GeForce FX 5700 Ultra] (rev a1)

This does not happen on other distros I have tested such as Suse Linux Enterprise Server 9.

I reported this as a bug way back in Hoary and never recieved any response as to whether it was being looked into.

Trying to debug this is extremely annoying as it leads to hardlocks. Can anyone test what would occur when using alternate frame buffer drivers?

[Thrift (thrift24)]

With how many Linux users have nvidia in their rigs letting this slip into Dapper would be a real shame. Willing to torch my system to help.

[Matthew Garrett (mjg59)]

This is, sadly, a bug in the nvidia drivers rather than in Ubuntu. Since we don't have the source code, it's difficult to fix without Nvidia showing more willingness to assist.

[Sitsofe Wheeler (sitsofe)]

Over in Bug #38788 it looks like someone managed to get contact inside NVIDIA and this problem might be fixed in the new binary driver release...

[Lambros Lambrou (lambros)]

Just got the updated 8756 drivers through synaptic/apt-get. They didn't appear to fix the problem, but I can't say for certain because my graphics card has now died! I'm sorry I can't test if this problem gets fixed, because I no longer have the hardware :-(

I'm using a spare card now, it's an nVidia GeForce4 Ti 4200 (NV25), and I'm happy to report it isn't affected by this bug. Hope it lasts me until I get a new 'puter :-)

[Sitsofe Wheeler (sitsofe)]

Could folks seeing this problem check whether their motherboard has an updated BIOS? Apprently buggy BIOSes can cause these sorts of problems...

[Sitsofe Wheeler (sitsofe)]

(Flashing your BIOS is done at your OWN RISK. If you flash your BIOS and turn your computer into a paperweight don't blame me).

[Thrift (thrift24)]

nForce 3 board, bios was updated less than 6 months ago.

I had this issue before the bios update, and continue to have it after the bios update.

[Joseph Maillardet (jokx)]

This problem appear to occurs for all n'vidia user on all ubuntu dapper drake flight and beta with all kernel release (386, 686, k7, k8, 32 and 64bits)...

Hi have tested myself a lot of nvidia powered computer with nvidia binairy driver on dapper (up to date) at work and I have the same error everytime : Black screen on console or when shutdown/restart machine. First boot work greate with uspash, x/gdm boot proprerly .. but any try to switch on console get a black screen.

Tested plateform :
* Athlon Thunderbird 1,2 GHz | GeForce MX 440 | linux-k7
* Athlon64 4000+ | GeForce 6800GT | linux-k8
* Pentium M 2.2 GHz | QuadroFX 1400Go | linux-686
* Pentium 4 3.0GHz | GeForce 6600GT | linux-686

[Paul Sladen (sladen)]

Yup, this issue exists and affects quite a few people.

The problem here is fixing it; these are binary drivers supplied by Nvidia - there's no source code and no way of (us) fixing it directly in the driver.

If anyone knows of a work-around (or manages to work one out) then it's fairly easy to apply it; this also needs people with access to the hardware to test and try to find a work-around.

The real solution is with Nvidia fixing their driver and then only way that is going to happen is if people pursuade them that there's a bug and enough people nag/ask them to concentrate on it.

The tag above isn't really WONTFIX. But more "CANTFIX".

[Richard Brooklyn (rbrooklyn)]

As this bug isn't likley to be fixed before June 1st, is there a way to make Dapper disable usplash gracefully if a NVidia card is detected?

It's far from ideal, but many, less tech savvy, people won't give Ubuntu a second look if they experience these bugs. At least with usplash disabled the system is fully usable.

[Paul Sladen (sladen)]

This was the type of thing I was thinking of; and it might actually be doable because the Nvidia binary drivers aren't configured/installed by default and actually have to have the user select them.

When the binary drivers are configured, it should be possible to have them deselect the splash option (by some means) from the grub commandline or by adding a hook to somewhere under:

  /etc/mkinitramfs/*

jbailey: does you have any thoughts about a proper way to make this happen?

[Christian Kroll (tunix79)]

Possible workaround: The nvidia-glx(-legacy) package should collide with the usplash package, so that the package management refuses to install both. At least this prevents users from screwing up their systems accidentally. This workaround is fairly easy to apply because only the "control.stub.in" file has to be edited. Just add a "usplash" to the corresponding "Conflicts:" line of the nvidia-glx(-legacy) package description.

[Paul Sladen (sladen)]

This is going to produce a scary "removing 'ubuntu-desktop'" message.

But maybe that is worth doing; needs more thinking about.

[Dave Morley (davmor2)]

I still believe the easiest work round is to remove the word usplash from the /boot/grub/menu.lst (current Kernel Line)

[Christian Kroll (tunix79)]

Fiddling around with bootloader configs isn't trivial. Such files have to be parsed and constructed carefully to ensure a clean boot process. You also have to consider extensive customizations of the menu.lst which go beyond the scope of an 'update-grub' generated file. Besides, users may not be amused to see their carefully crafted bootloader configs being modfied. Another problem is, that you don't know if a user actually uses grub to start his/her system. You have to consider many cases and all of them require a fair amount of testing.
By letting the nvidia-glx package collide with usplash, you don't need to mess around with user configs. In addtion, users get aware of the problems _before_ they install the driver. You see at once that you can't have both the nvidia binary driver and usplash. This is what the apt package management is made for.
The removal of ubuntu-desktop might be scary, but it is still better than a screwing up a system (which might not be trivial to fix for a beginner). On the other hand, is the dependency of ubuntu-desktop mandatory? All that usplash does is to add some eye candy to hide some cryptical boot messages. Or does it peform some other tasks I'm not aware of?

[Dave Morley (davmor2)]

This is a working edit by removing the word splash from the kernel line everything else works as it should it is only the boot splash ans the closing splash screen (graphical) that don't show. Instead you get a generalise text boot screen which tells you the same info but without the pretty graphics. This work around has had my machine working perfectly since I reported the fault to Nvidia who told me what to do. That was back between flight 5 and 6 the only hassle is if there is a new Kernel module installed you have to remember to edit out the splash line before you reboot.
Other than that I have a fully functional pc which shutsdown reboots and goes into ALT-CTRL-F(1-7) and works well with xgl too. The splash word only removes the graphical boot eliment to the splash screen but with the frame buffer empty the card works correctly, the guy at Nvidia has reported it as an official bug and in my experience if any other cards are having this problem it is now that they should be reports to nvidia they are quite open to the idea that there are bugs and it is their goal to eliminate them but if they don't know they exist they can do nothing. This work round works on nv35 and now it appears nv36's as well ref bug 38788.

[Sitsofe Wheeler (sitsofe)]

If you go ahead with this can you leave the nvidia-glx-legacy package alone? I have a creaky old Geforce 256 that works fine with usplash and all these reports seem to be from owners with newer cards...

[Ricardo Pérez López (ricardo)]

Hi.

I have a nVidia card (integrated into the motherboard, really), I use the "nv" driver, and I don't have that problem.

My motherboard is a MSI K7N2G-ILSR, with nForce2 chipset.

I don't know if this bug could be related with the Bug #40597.

[Ricardo Pérez López (ricardo)]

How many nVidia users are affected by this bug? Maybe it could be a matter of equilibrium: if only 10% users are affected, removing usplash from ALL nVidia users could be too much radical.

Obviously, I'm an nVidia user which is not affected by this bug: I'm using "nv" driver and my console works well... So I'm not objective in this case.

[Chris Jones (cmsj)]

Perhaps not so useful, but I am using dapper on amd64 (fresh install) with an nVidia FX5900 on an ABit AV8 (latest BIOS) and I see no problems with the splash screens while booting or shutting down. from my perspective it would be a shame if those screens went away, but I appreciate that this is a bug that Ubuntu has very little control over.

[Dave Morley (davmor2)]

Ricardo It is only Nvidia-glx drivers that are effected, standard 2d nv modules don't have the same problem. Only the official Nvidia driver for 3d graphics. Chris are you running the nv modules or have you upgraded the the nvidia-glx modules?

[Ben Collins (ben-collins)]

On Mon, 2006-05-15 at 12:23 +0000, Chris Jones wrote:
> Perhaps not so useful, but I am using dapper on amd64 (fresh install)
> with an nVidia FX5900 on an ABit AV8 (latest BIOS) and I see no problems
> with the splash screens while booting or shutting down. from my
> perspective it would be a shame if those screens went away, but I
> appreciate that this is a bug that Ubuntu has very little control over.

I think this only affects the legacy nvidia driver, right?

[Ricardo Pérez López (ricardo)]

Oh, sorry, very sorry! I'm not an "nv" driver user. I'm an "nvidia" driver user, nvidia-glx, with 3D acceleration.

Sorry for the mistake.

[Sitsofe Wheeler (sitsofe)]

Ben:

> I think this only affects the legacy nvidia driver, right?

No! I am a legacy nvidia driver user with an old card (NV10) card who *does not* have (and never has) this problem.

The legacy driver is meant for old (approximately any card which is a geforce 2 or older but excluding the geforce 2mx) cards only. All the people I've seen reporting these problems have had "new" nvidia cards. Consequently they should all be using nvidia-glx.

Some people with new cards are using the nvidia-glx-legacy because they are having various problems but such a system (new card + legacy driver) is not a combination supported by nvidia.

[Ian Griffiths (ianrgriffiths)]

I'm using an nforce2 motherboard with integrated graphics (essentially geforce 4mx), and the nvidia driver. I ran into this bug earlier in the dapper process. When i shut down, instead of seeing the nice usplash progress bar i'd get random junk. However recently (at least after a fresh flight 7 install) it has been fixed for me.

Currently usplash, VT switching etc. is all working fine with the 3D accelerated drivers, so just making nvidia-glx conflict with usplash may be a bit too drastic.

[Lukas Sabota (punkrockguy318)]

I can't confirm with a geforce 4mx running dapper, usplash, and nvidia driver.

[Ricardo Pérez López (ricardo)]

> Currently usplash, VT switching etc. is all working fine with the 3D accelerated drivers, so just making nvidia-glx conflict with usplash may be a bit too drastic.

I totally agree. +1.

Ankur Kotwal <email address hidden> said recently in ubuntu-devel:

"Upon installation of the nvidia driver, the user could be asked
whether they would like to disable usplash. This could trigger an edit
of /boot/grub/menu.lst and a subsequent update-grub.

Perhaps we could provide a command line utility that allows the user
to easily turn on and off usplash (i.e.
usplash-enable/usplash-disable)?

Putting a conflict on the package would mean that there is no way
people who want usplash, the nvidia driver and don't care for a TTY
terminal could have all of the above. I propose we just make this
configurable to apease as many people as possible."

I totally agree, too. +1, too.

[Scott James Remnant (Canonical) (canonical-scott)]

On Mon, 2006-05-15 at 10:57 +0100, Paul Sladen wrote:

> I need some guidance here. The Nvidia binary evilness drivers are broken
> and don't restore the terminal on console switch:
>
Works just fine here.

Dual Nvidia GeForce 7800 GTX with the binary evil.

Scott
--
Scott James Remnant
<email address hidden>

[Yagisan (yagisan)]

I can't reproduce this bug on dapper, with 64bit amd64 and Geforce 6800LE setup with the binary driver.

[Dave Morley (davmor2)]

this bug as far as I am aware only effects NV35 Cards it now appears it may effect NV36 Cards also.

These are 5000 series cards, most cards are not effected which is why Nvidia didn't discover it. I repeat if this Bug effects your card it is not an Ubuntu or Linux problem but a problem with the driver from Nvidia they have logged an official bug for their developers but please inform Nvidia about your problems in the same manner you would inform Ubuntu about a problem with their software.

[Roshan Shariff (roshan.shariff)]

I can confirm this problem is card-specific. I've tested the following cards

1. Nvidia TNT2 M64 with Nvidia legacy driver in Breezy - Usplash worked fine

2. Nvidia GeForce 3 Ti200 with non-legacy driver in both Breezy and Dapper: Usplash doesn't work

3. Nvidia GeForce 6600 GT PCI-Express with non-legacy drivers in Breezy and Dapper: Usplash works fine if an explicit vga=... option is not passed at boot time.

The nv driver works perfectly fine in all cases.

Also, when I say Breezy and Dapper above, I mean the version of the driver packaged with those distros.

[Matthew Garrett (mjg59)]

Not a usplash bug

[Richard Brooklyn (rbrooklyn)]

It's worth noting that the latest nvidia-glx package (1.0.8762+2.6.15.11-1) which came into my system this morning (hence bringing Ubuntu up to the latest offical drivers) does not fix this issue.

Given the severity of this bug is being marked as "major", would it be reasonable to assume that if NVidia do release a fix for this after June 1st, that Dapper users will see an update? Or would we only see this for Edgy Eft?

[Dave Morley (davmor2)]

With the desktop being supportted for three years I would hope that this module would be one to be considered for update.

[Kai Schroeder (kai-schroeder)]

One workaround ist to add "vga=795" to the boot options. somehow everything works fine after that.

[Richard Brooklyn (rbrooklyn)]

There is a new nvidia driver out now. Version 1.0-8774.

This doesn't appear to fix what we need, however. The only hint of this is "Improved interaction with newer Linux kernels." as part of the list of changes, which is a tad vauge.

Can anyone confirm that this does not help us?

[wheels53 (wheels531)]

Sony VGN-AR170 with Ubuntu Dapper using 1.0-8774 with my Nvidia Go 7600 GT. Removing the splash argument from menu.lst for my current kernel solved my problems with virtual terminals as well as Hibernation and Suspend to memory.

[Chris Lord (cwiiis)]

Happens with latest edgy (updated a few minutes before this post) on a laptop with a Geforce Go 7600.

[Chris Lord (cwiiis)]

Furthermore, I couldn't find a (non-hacky) way with edgy to disable loading of the framebuffer modules - black-listing them doesn't stop them from being loaded and nor does disabling the splash... Any advice?

[Chris Lord (cwiiis)]

A further note, this bug still exists using the new 9629 nvidia drivers.

[sl1pkn07 (sl1pkn07)]

my PC:

Amd FX-60
Abit AV8- 3rd eye with latest BIOS version (v28)
2Gb Ram Geil (4x512Mb)
Audigy 2 paltinum
RAID-IDE PCI Kronwell (Silicon Image PCI0680)

Ubuntu Edgy 6.10 with kernel 2.6.17-11.35
Nvidia drivers 9755 (Latest)

booting kernel message:
[ 49.536917] BUG: warning at kernel/irq/manage.c:126/enable_irq()
[ 49.536919]
[ 49.536919] Call Trace: <ffffffff802b6788>{enable_irq+136} <ffffffff803a3832>{probe_hwif+1714}
[ 49.536937] <ffffffff803a43f2>{ideprobe_init+130} <ffffffff802a37ec>{kthread_stop_sem+188}
[ 49.536945] <ffffffff880cb009>{:ide_generic:ide_generic_init+9}
[ 49.536949] <ffffffff802a8e87>{sys_init_module+199} <ffffffff802657d6>{system_call+126}

NV drivers: Working in ALL condition

NVIDIA Drivers: Booting in recovery mode and normal mode with dmesg command

[ 50.649263] nvidia: module license 'NVIDIA' taints kernel.
[ 50.654310] Unable to handle kernel paging request at 0000000077c9b8b0 RIP:
[ 50.654362] {:nvidia:_nv005490rm+0}
[ 50.654654] PGD 78702067 PUD 0
[ 50.654797] Oops: 0002 [1] SMP
[ 50.654941] CPU 0
[ 50.655038] Modules linked in: nvidia libusual snd_hwdep sg usbhid via_velocity i2c_viapro snd evdev parport_pc parport shpchp pci_hotplug crc_ccitt i2c_core serio_raw emu10k1_gp gameport pcspkr soundcore psmouse ext3 jbd ohci1394 ieee1394 ehci_hcd uhci_hcd usbcore ide_generic ide_cd cdrom ide_disk via82cxxx sd_mod generic sata_via libata scsi_mod siimage thermal processor fan fbcon tileblit font bitblit softcursor vesafb cfbcopyarea cfbimgblt cfbfillrect capability commoncap
[ 50.657535] Pid: 3313, comm: modprobe Tainted: P 2.6.17-11-generic #2
[ 50.658203] RIP: 0010:[] {:nvidia:_nv005490rm+0}
[ 50.658379] RSP: 0000:ffff810078211e58 EFLAGS: 00010292
[ 50.658491] RAX: ffff810077c9b800 RBX: 0000000077c9b800 RCX: ffff81007872a800
[ 50.658553] RDX: ffff810077c9b800 RSI: 0000000000000006 RDI: 0000000077c9b800
[ 50.658614] RBP: 0000000000000001 R08: 0000000000000000 R09: ffff810077c9b800
[ 50.658675] R10: 0000000000000001 R11: ffffffff80280020 R12: ffffffff889c4b00
[ 50.658737] R13: 00002b6abbc18000 R14: 00000000005082c8 R15: 00002b6abbc18000
[ 50.658798] FS: 00002b6abbc176d0(0000) GS:ffffffff805f3000(0000) knlGS:0000000000000000
[ 50.658868] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 50.658928] CR2: 0000000077c9b8b0 CR3: 0000000078384000 CR4: 00000000000006e0
[ 50.658989] Process modprobe (pid: 3313, threadinfo ffff810078210000, task ffff810037e08fa0)
[ 50.659061] Stack: ffffffff8827bef9 0000000077c9b800 ffffffff8827be65 0000000077c9b800
[ 50.659299] ffffffff8827be39 ffffffff8827cef8 0000000000000788 ffff81007872a800
[ 50.659588] 0000000000000000 ffffffff8827ccdf
[ 50.659776] Call Trace: {:nvidia:_nv005426rm+9}
[ 50.660038] {:nvidia:_nv005417rm+9} {:nvidia:_nv011480rm+17}
[ 50.660423] {:nvidia:_nv011440rm+80} {:nvidia:_nv003625rm+41}
[ 50.660809] {:nvidia:_nv011448rm+20} {:nvidia:_nv011471rm+33}
[ 50.661195] {:nvidia:_nv002561rm+72} {:nvidia:rm_init_rm+9}
[ 50.661587] {:nvidia:nvidia_init_module+227} {__up_read+33}
[ 50.661903] {sys_init_module+199} {system_call+126}
[ 50.662209]
[ 50.662210] Code: 48 c7 87 b0 00 00 00 16 f2 28 88 48 c7 87 b8 00 00 00 a2 f9
[ 50.663247] RIP {:n...

[sl1pkn07 (sl1pkn07)]

Nvidia Gforce FX5600GT (NV31) card

sorry :S

[sl1pkn07 (sl1pkn07)]

Usplash uninstall, but the error persist

i'm uninstall Nvidia 9755 drivers (official page). and install (apt-get) nvidia-glx 8776 drivers (Official .deb for edgy )

the kernel oops it disappears (no BUG kernel). but the black screen persist (the xorg.0.log
without errors )

[Sitsofe Wheeler (sitsofe)]

sl1pkn07:

The fact that you are getting problems when you are starting up rather than switching VTs suggests that your problem is different to this one. Please file a separate bug report (your best bet is probably to probably report your problems to NVIDIA though. See http://us.download.nvidia.com/XFree86/Linux-x86/1.0-9755/README/chapter-06.html for how to do this)

[Sitsofe Wheeler (sitsofe)]

Subscribing sl1pkn07 to this bug.

[jaimesilva (jaimealbsilva)]

I'm also having this problem in a Compaq Presario F572US with Ubuntu 7.04 (Feisty). I removed the usplash package, the splash kernel boot option and added the vga=normal boot option and now I can swith to virtual console (Ctrl-Alt-F1) and back to X (Alt-F7) only if I am using the metacity (normal) window manager but if I enable compiz (composite manager) the problem comes back (blank screen with mouse pointer and must reset the machine).

Here is the hardware info:

$ uname -a
Linux f572us 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux
$lspci
...
00:05.0 VGA compatible controller: nVidia Corporation C51 PCI Express Bridge (rev a2)
...

I can't make suspend work with any window manager :'(

[Sitsofe Wheeler (sitsofe)]

jaimesilva:
VT crashing when using AIGLX is bug #88152 .

[GaryParr (gary-garyparr)]

Problem exists on gutsy with GeForce Go 6200 and 100.14.19 glx-new drivers. Removing usplash did not help. Neither did changing vga boot settings. Only option seems to be to remove the nvidia drivers.

[GaryParr (gary-garyparr)]

Additional tidbit of information. A display connected through a docking station works fine with the "nvidia" driver but fails miserably when using the "nv" driver. When the laptop display gets the noise on shutdown, the external display does not and will show the splash screen (or shutdown scripts if splash is disabled) correctly. I no next to nothing about hardware and this may or may not be of any benefit but I thought I'd throw it out there.

[Tomihotedavyndej (coolfighter)]

I also have the same problem with Gutsy, nVidia NV43 [GeForce Go 6600], nvidia-glx-new 100.14.19+2.6.22.4-14.10. When I switch to integrated Intel 915GMS graphics controller with i810 driver, problem disappears. I didn't experience this problem on Fiesty, this occured after upgrade to Gutsy. IMHO it's definitely driver related bug.

[GaryParr (gary-garyparr)]

I'm not sure how these bugs are tracked, but this is assigned to restricted module 2.6.17. Can this be re-assigned/attached to version 2.6.22.x since it is still happening? Also the nvidia-new 100.14.23 drivers have not resolved the issue.

[LimCore (limcore)]

Ubuntu 7.10 amd64, nvidia (closed) driver, geforce 6100, xorg

00:05.0 VGA compatible controller: nVidia Corporation C51G [GeForce 6100] (rev a2)

When I swithch VT (alt-ctrl-F9 etc) between graphical ones then

1) after switch there is often garbage
2) the textures stored in memory (i.e. in 3d games) are sometimes corrupted (some, or all - are totally random)
3) sometimes (when switching fast) the computer locks up:
a) sounds still play
b) keyboard (usb) dies (even caps. evne sysrq often)
c) power button (ACPI script) and alt+ctlr+del doesnt work
d) other keyboard (ps2) reacts at least to sysrq+b (reboot) I think sometimes the normal USB keyboard also reacred

happens often (3 times so far)

[Timo Aaltonen (tjaalton)]

Please try to reproduce this on Hardy, which has version 169.09

[GaryParr (gary-garyparr)]

I finally got Gutsy stable... I think Hardy can wait a while. I did install the 169.09 nvidia drivers in Gutsy though and no change. Laptop LCD shows random noise during logout and shutdown as well as in a virtual console while an externally attached LCD is fine.

[LimCore (limcore)]

Would it be possible to pute newer nvidia driver into ubuntu Gutsy (including amd64) so that we all can test?

[cosmicgreen (cosmicgreen)]

I still have this problem on Hardy with 169.12 version of nVidia driver.

[cleersf (cleersf-earthlink)]

Just installed Hardy, and have this issue. It didn't occur until I enabled the Nvidia restricted drivers. After partially disabling them (nvidia-glx-new would not uninstall for some reason) I did not get the mess on my screen, and it shut down correctly. I decided to install a fresh Hardy system and using EnvyNg this time. The same mess upon sutdown/restart began to occur on my screen after that install. I'm running HP dv6448se, Nvidia GeForce Go 6150.

[GaryParr (gary-garyparr)]

No change for me with a fresh Hardy install. Same ugly mess.

[Kingwad (adamwilliamking)]

Same condition on my Hardy. Also /proc/fb is empty instead of the "0 VGA16 VGA" reported by Lambros Lambrou.

[Jonathan Thomas (echidnaman)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[Sergio Zanchetta (primes2h)]

The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
linux-restricted-modules-2.6.22 task. It would be helpful if you could test the
new Jaunty Jackalope 9.04 release and confirm if this issue remains -
http://www.ubuntu.com/getubuntu/releasenotes/904overview. If the issue still exists with the Jaunty
release, please update this report by changing the Status of the "linux (Ubuntu)"
task from "Incomplete" to "New". Thanks in advance.

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!