nvidia-glx-new causes unusable tty's

sorry, I forgot: I'm using Hardy Heron RC...

I confirm same behaviour here on 2.6.24-17.

lspci | grep VGA
01:00.0 VGA compatible controller: nVidia Corporation G72 [GeForce 7300 LE] (rev a1)

Removing vga=xxx from menu.lst doesn't fix the problem.

Same problem on a sony vaio S4XP (with a Geforce Go 6200).
I'm running the Hardy Heron regular release
Driving me nuts, this one

I would be happy running nv for a while, but I want 24 bit and the nv driver also keeps going over-exposed (too bright, its weird)

Just run some updates and put on 2.6.24-18 ..... no change
However for me nvidia-glx from the repo (rather than nvidia-glx-new) has fixed things for now

Please attach in separate attachments the following informations: uname -a, output of dmesg, xorg.conf, Xorg.0.log, and output from lspci -vvnn .

In order to determine if this issue is usplash related, would you boot your computer with usplash disabled and reproduce the issue? To disable usplash for a single boot, you can follow these steps :

1.Press Esc during Grub boot delay to access the boot menu.
2.Select your actual Ubuntu boot line and press "e" to edit it.
3.Select the "kernel" line and press "e" to edit it.
4.At the end of the line, remove "splash" and "quiet" and press "enter".
5.Type "b" to boot the custom boot line.

Thanks in advance.

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!

I am experiencing the same problem. I'm using Ubuntu Jaunty Jackalope (9.04) and running the latest nVidia 180.44 graphics drivers. Here are the requested pieces of information to reopen the bug.

<b>uname -a</b>
http://dl.getdropbox.com/u/324709/Launchpad/Bug220951/uname-a.txt

<b>dmesg</b>
http://dl.getdropbox.com/u/324709/Launchpad/Bug220951/dmesg.txt

<b>xorg.conf</b>
http://dl.getdropbox.com/u/324709/Launchpad/Bug220951/xorg.conf

<b>Xorg.0.log</b>
http://dl.getdropbox.com/u/324709/Launchpad/Bug220951/Xorg.0.log.txt

<b>lspci -vvnn</b>
http://dl.getdropbox.com/u/324709/Launchpad/Bug220951/lspci-vvnn.txt

<b>Not</b> a usplash problem. I modified my menu.lst to remove "splash" and "quiet" as advised and when booting without those options I was able to reproduce the problem.

There is one thing I would like to mention about that though. When booting with "quiet" and "splash" options, when I try to reproduce the problem when I first hit CTRL+ALT+F1, the screen does absolutely nothing. Then I hit again and it goes to the terminal, but it is blank with nothing but a blinking cursor. When I remove the "quiet" and "splash" options, it goes to the terminal the first time I press CTRL+ALT+F1, but still just the blinking cursor

If you need anything else, please let me know, I will happy to help.

I can confirm this issue on two machines running Jaunty Jackalope:

1) amd64 laptop: MSI gx620 [NVIDIA GeForce 9600 GT 512 MB] (lspci -vvnn attached), and
2) i386 desktop: GIGABYTE 8600GTS 512MB silent pipe

I first noticed the issue on Hardy or Intrepid i386 on the desktop. Removing the NVIDIA driver fixes the problem. I have not had success removing quiet/splash from menu.lst.

When I press: CTRL-ALT-F1 the screen goes blank.
When I press: Alt-F7 my gnome desktop returns.

I'm just waiting for a situation where this causes real grief (has not occurred yet thankfully!).

I confirm this bug on a Jaunty Machine running amd64, 2 x nvidia 9400GT video cards, with bnoth the latest repo restricted drivers, and the latest binary blob direct from nvidia.

A workaround I found is to force the console into framebuffer mode with vga=791 (or whatever) as a boot parameter passed to the kernel. An alternative workaround is to use the open source driver.

I think this is possibly a duplicate of 282068; except that there the bug is reported to affect ATI users as well.

I finally solved this problem. Worked on intrepid, worked on Jaunty

In intrepid:
sudo gedit /etc/modprobe.d/options
add the line:
options nvidia NVreg_UseVBios=0

in Jaunty things have changed, you wont find the options file
create a new .conf file in /etc/modprobe.d/ with just this line as content
options nvidia NVreg_UseVBios=0
i named it nvidia-fix.conf but the name doesn't really matter

Others reported they still had blank consoles until they set
vga=791
in the boot options in /boot/grub/menu.lst

Using 9.04 Jaunty Jackalope, this did not solve my problem. The only thing
that seems to solve the problem so far is not using the third display
(television in my case).

However, the vga=791 parameter did seem to restore my TTY access, and I
thank you for that.

Note: I'm not sure which modification it was, but I did notice that the
Ubuntu Splash loading bar was in an obscure position. Instead of being
centered, it was moved to the right and down about 2 inches in each
direction.

Please disregard the first paragraph in my previous comment. I didn't read the full title and thought I was replying to another bug report (https://bugs.launchpad.net/bugs/300870)

I tested both fixes independently and found that the modprobe configuration didn't change anything, and the vga setting for the kernel does fix the TTY problem, but as I stated causes the Usplash screen to be off centered (at least for me...). The off-centered Usplash could be a result of the bug I'm experiencing when using three displays with two of them in TwinView. I'm going to do some more research into the VGA setting...

Forgive my multiple posts, it took me a lot less time to do the research than I had anticipated. I now understand why Usplash was positioned badly. 791 is for a native resolution of 1024x768 with 16bit colors. My monitors have a native resolution of 1280x1024. So this number should be changed depending upon your screen resolution. You need to use one with the same width-height ratio.

For more information -> http://wiki.antlinux.com/pmwiki.php?n=HowTos.VgaModes

I can confirm this with the legacy 96 drivers (MX400 hardware) on 10.04, none of the above makes TTYs useable, note I also have no Plymouth/splash during boot or shutdown. With nv everything works as it should.

Can confirmed a part of the bug:
My TTYs (F1-F7) does not function and display a blank screen with gribberish at the top (pixels of multiples colors).
I have no other problem.

I try changing the vga and it didnt worked.

Distro: Ubuntu 10.04
uname -a: Linux 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:28:05 UTC 2010 x86_64 GNU/Linux
dpkg --get-selections | grep nvidia :
nvidia-common deinstall
nvidia-current install
nvidia-current-modaliases install
nvidia-settings install

Thank you for reporting this issue about a driver from the
linux-restricted-modules package. lrm-2.4.24 was shipped with Ubuntu
8.04 which reached end-of-life for desktop support on May 12th, 2011.

For that reason, this bug report is being closed at this time. I'm
marking it wontfix because what you describe is probably a valid issue,
but there are no plans to work on lrm 2.4.24 bugs further.

The issue may be resolved in a newer version. If not, aside from filing
a new bug report, another angle may be to file it directly with the
driver vendor.