Switch tty, shutdown, reboot cause colorful screen on GeForce Go 6200

Does it actually freeze when you switch to a tty, if it's the problem I am thinking of you can still ctrl+alt+f7 back into the gdm. This is a pretty common problem dealing with usplash (see bug #63558). I won't mark it a duplicate just yet but please check it out and let me know if it's related.

Sorry for the delay...

No it doesn't seem to be related to bug #63558

My problem happens only when using the Nvidia proprietary driver - I need it to enable 3D rendering and use Beryl. However the bug happens even when Beryl is not running.

Actually the machine doesn't freeze ... when I press ctrl-F1 for example the screen turns to something like you can see on the attached file - but I can still click on ctrl-F7 to come back to my X Session then everything turns back to a normal screen behavior.

I have attached a photo picture of what I see on my screen when the problem happens.

The problem is with splash, disabling this in the grub boot should fix your problem. While the initial report does mention ATI the problem occurs with both Nvidia and Ati proprietary drivers. There is also an option of adding "vga=791" to /boot/grub/menu.lst but it has not worked for everyone.

 The fact that you can go back to F7 afterwards confirms for me that this is indeed a duplicate so I am going to mark it as such.

I see your point so - yes - this could be a duplicate of the other bug. I had some doubts because it was only talking about ATI drivers.

However I've deleted "splash" and add "vga=791" to my /boot/grub/menu.lst file with no success. I still have the problem.

If it can be of any help I have attached the Nvidia bug report that can be created when using the NVvidia proprietary driver.

Here is my config:
Linux kernel 2.6.20-8-generic #2 SMP
X version 7.1.1
Nvidia GeForce Go 6200 Turbocache with the latest linux driver 1.0-9746
I have the latest BIOS version R0092V0 for my Sony VAIO S3XP

Thank you for your help and hopefully this annoying problem will be resolved in the future ;-)

If removing "splash" does not help, it is not a duplicate of bug #63558. Are you sure your changes to menu.lst are taken in effect? If you changed the #defoptions line you have to run sudo update-grub afterwards. Please run "cat /proc/cmdline" and see if lists "splash".

Sorry, I only checked your nvidia report just now, and it contained a /proc/cmdline entry. Yes, you are booting without "splash".

Did you try removing "splash" and _not_ adding any "vga=" options?

Just tried without "splash" and without any "vga=" option (but leaving the quiet option) - unfortunately same problem...

BTW, are you using the driver shipped with Ubuntu, or did you install something on your own (from the nvidia web site etc)?

Using the installer from Nvidia:
http://us.download.nvidia.com/XFree86/Linux-x86/1.0-9746/NVIDIA-Linux-x86-1.0-9746-pkg1.run

Ok, unless you can reproduce it with the Ubuntu drivers, we'll have to reject the bug, and you must contact Nvidia for support...

Good point ... installing the nvidia-glx (1.0.9631) resolved the problem.

However I have now another problem when resuming from suspend/hibernate mode > black screen and freeze.

I will first gather more information about this behavior on the internet...

If needed, file a new bug for that other issue.

I'm back with this bug because it's happening again with the last update of the nvidia-glx package v1.0.9755 - it was working before with the nvidia-glx v1.0.9631 - please advice.

Please attach xorg.conf, Xorg.0.log, and output from lspci -vv. Is the screenshot from comment #2 still valid? You are booting without splash?

Yes the screenshot is still valid and suppressing the option "splash" at boot time doesn't change anything...

same/very similar problem here with nvidia-glx-new

hardware id:
ca9acf23e0425076546bc45cd6dbbc4d

Kernel command line: root=UUID=5c8d4d41-b351-47ba-a894-f7d2ea6220c2 ro locale=et_EE

interesting topic about this issue (with misleading title):
http://www.nvnews.net/vbulletin/showthread.php?t=81256

quote from nvidia guy: "I have no VAIO systems here, and am not able to reproduce this problem. Without a means of reproducing it, there isn't any means of investigating it further."

Kubuntu Feisty Fawn

I have the same damn thing on the same damn card. However as of feisty at least hibernation works now. The funky screen still shows up, but the machine powers off after a while and I can successfully resume.

Is this symptom still reproducible in 8.10 alpha?

It was resolved with the nvidia-glx-new driver on Gusty Gibbon.
The problem came back with Hardy Heron (version I use now).
I will update to v8.10 alpha 6 this week and give it a try then let you know...

Just updated to 8.10 alpha 6 - using NVIDIA accelerated graphic driver version 177.
Still have the same problem when switching to another tty, switching off and standing by.
Let me know if you require other information or log files.
Thanks

/etc/modprobe.d/options
options nvidia NVreg_UseVBios=0

fixes the problem for me; discussion: http://www.nvnews.net/vbulletin/showthread.php?p=1801704#post1801704

I have the same issue (ubuntu 8.10). `NVreg_UseVBios=0` is also not working. It was working fine with ubuntu 8.04.

Adding `vga=791` to my grub config has fixed the problem. Here is how my grub/menu.list looks...

===============================
title Ubuntu 8.10, kernel 2.6.27-7-generic
uuid 151f7906-5ff8-41b9-8d19-77974622c721
kernel /boot/vmlinuz-2.6.27-7-generic root=UUID=151f7906-5ff8-41b9-8d19-77974622c721 ro quiet splash vga=791
initrd /boot/initrd.img-2.6.27-7-generic
===============================

Here is a portion of output of `lspci -vv`

===============================
00:12.0 VGA compatible controller: nVidia Corporation GeForce 7000M (rev a2) (rev a2)
 Subsystem: Acer Incorporated [ALI] Device 0127
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Interrupt: pin A routed to IRQ 23
 Region 0: Memory at f3000000 (32-bit, non-prefetchable) [size=16M]
 Region 1: Memory at d0000000 (64-bit, prefetchable) [size=256M]
 Region 3: Memory at f2000000 (64-bit, non-prefetchable) [size=16M]
 [virtual] Expansion ROM at 88000000 [disabled] [size=128K]
 Capabilities: <access denied>
 Kernel driver in use: nvidia
 Kernel modules: nvidia, nvidiafb
===============================

/etc/modprobe.d/options
options nvidia NVreg_UseVBios=0

Did solve the problem for me too.
Currently using Ubuntu 8.10

[This is an automated message]

In Jaunty (9.04), we are dropping the nvidia-graphics-drivers-177 package, which
is now superseded by then nvidia-graphics-drivers-180 package.

  http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180

To transition your bug into the new package, we need your help. Please do the following:

 a. Verify the bug occurs in Jaunty with the -180 driver
     (ISOs: http://cdimage.ubuntu.com/releases/jaunty/)
 b. If you haven't already, please include in the bug:
     * Your /var/log/Xorg.0.log
     * Your /etc/X11/xorg.conf
     * The output of `lspci -vvnn`
     * Steps to reproduce the issue
 c. Under Affects, click the down arrow to the left of 'nvidia-graphics-drivers-177'
 d. Edit the Package to change 'nvidia-graphics-drivers-177' to 'nvidia-graphics-drivers-180'
 e. Click Save Changes

Thank you!

[We'll expire the remaining -177 bugs in a month or so.]

this bug is still evident in Ubuntu Jaunty (9.04)

[This is an automated message]

In Jaunty (9.04), we have just updated to the latest
nvidia-graphics-drivers-180 package from nVidia, version 180.44.

This package provides fixes for a large number of bugs, and we need your
assistance in testing if it fixes the issue you reported.

To do this, please do the following:

 a. Update to the 180.44 version of -nvidia using your favorite update
     method

 b. Attempt to reproduce your bug

 c. If your bug still remains, please simply reply to this email
     indicating so.

 d. If your bug is now solved, you can help us by setting your bug
     report to Fix Released:
     * In launchpad, go to your bug report
     * Click on the downward pointing arrow under Status
     * Set the Status field to 'Fix Released'
     * Comment on the change, such as, 'Verified fixed in 180.44'
     * Click 'Save Changes'

 e. If the original problem is solved but there are now other problems,
     please close the original bug and open new ones for those issues.

Thank you!

For details on the changes in this version of -nvidia, please see:

   http://www.nvidia.com/object/linux_display_ia32_180.44.html

the bug still remains and there is no indication whatsoever that nVidia corporation will ever fix it

Same with me, still not fixed. I have just tested with Jaunty beta with latest updates. Adding `vga=789` kernel option solved the problem for me...

same bug for me on jaunty

I've posted a new version of the -nvidia driver to our xorg-edgers PPA,
would you mind testing it either on Jaunty or Karmic and see if it
resolves this bug?

Get nvidia-graphics-drivers-180 - 185.18.14 here:

  https://edge.launchpad.net/~xorg-edgers/+archive/ppa

xorg-edgers PPA nvidia drivers 185.18.14 show the same colourful screen then ever I press Ctl-Alt-F1

Still the same in 9.10 using the Nvidia 185 driver...

In Ubuntu 10.04 creating /etc/modprobe.d/options.conf does not work and I have to edit xorg.conf itself:

Section "Device"
    Identifier "Configured Video Device"
    Driver "nvidia"
    Option "NoLogo" "True"
    Option "RegistryDwords" "UseVBios=0"
EndSection

Related to bug #447765? I have had this issue since Ubuntu 9.10 when grub2 was made default and `vga` option is deprecated. I solve my issue by this https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/447765/comments/29.

https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/447765/comments/35

>Related to bug #447765?

This bug here is strictly nvidia proprietary drivers issue and can only be fixed with specific registry settings and is not affected by different vga modes lines for virtual terminals.

gco, thank you for reporting this bug to Ubuntu. Karmic reached EOL on April 30, 2011.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases .

Is this an issue in a supported release? If so, could you please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 85451

Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

[Expired for xorg (Ubuntu) because there has been no activity for 60 days.]