nVidia GLX-driver breaks console

Bug #210458 reported by Thomas Reuss
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
NVIDIA Drivers Ubuntu
Incomplete
Undecided
Unassigned
linux-restricted-modules-2.6.24 (Ubuntu)
Won't Fix
Undecided
Unassigned
nvidia-graphics-drivers-180 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: nvidia-glx-new

When using the nVidia-glx(-new) drivers, any console (CTRL-ALT-F[1-6]) will be messed up with defective graphic-output and completely unreadable.

lsmod-output:

Module Size Used by
isofs 36388 1
udf 88612 0
ieee80211_crypt_ccmp 7936 2
af_packet 23812 4
rfcomm 41744 6
l2cap 25728 13 rfcomm
ppdev 10372 0
ipv6 267780 10
speedstep_centrino 9152 0
cpufreq_ondemand 9740 1
cpufreq_stats 7104 0
cpufreq_powersave 2688 0
cpufreq_userspace 5284 0
cpufreq_conservative 8712 0
freq_table 5536 3 speedstep_centrino,cpufreq_ondemand,cpufreq_stats
bay 6912 0
dock 11280 1 bay
sbs 15112 0
sbshc 7680 1 sbs
container 5632 0
iptable_filter 3840 0
ip_tables 14820 1 iptable_filter
x_tables 16132 1 ip_tables
aes_i586 33536 2
dm_crypt 15364 0
dm_mod 62660 1 dm_crypt
sbp2 24072 0
parport_pc 36260 0
lp 12324 0
parport 37832 3 ppdev,parport_pc,lp
loop 18948 0
joydev 13120 0
tuner 27340 0
tea5767 8196 1 tuner
tda8290 14212 1 tuner
tda18271 32520 1 tda8290
tda827x 11268 1 tda8290
tuner_xc2028 22704 1 tuner
xc5000 11396 1 tuner
tda9887 11908 1 tuner
tuner_simple 16400 1 tuner
tuner_types 14848 1 tuner_simple
mt20xx 13704 1 tuner
tea5761 6148 1 tuner
tvp5150 20368 0
ir_kbd_i2c 11024 0
pcmcia 40876 0
em28xx 56872 0
videodev 34944 2 tuner,em28xx
v4l1_compat 15748 1 videodev
compat_ioctl32 2304 1 em28xx
ir_common 39044 2 ir_kbd_i2c,em28xx
v4l2_common 12672 3 tuner,tvp5150,em28xx
tveeprom 13316 1 em28xx
hci_usb 16412 2
bluetooth 61156 7 rfcomm,l2cap,hci_usb
evdev 13056 6
snd_hda_intel 344088 4
snd_pcm_oss 42144 0
snd_mixer_oss 17920 1 snd_pcm_oss
ac 6916 0
battery 14212 0
video 20112 0
output 4736 1 video
snd_pcm 78596 2 snd_hda_intel,snd_pcm_oss
psmouse 40336 0
ipw2200 146120 0
snd_page_alloc 11400 2 snd_hda_intel,snd_pcm
snd_hwdep 10500 1 snd_hda_intel
pcspkr 4224 0
serio_raw 7940 0
ieee80211 35528 1 ipw2200
ieee80211_crypt 7040 2 ieee80211_crypt_ccmp,ieee80211
yenta_socket 27276 2
rsrc_nonstatic 13696 1 yenta_socket
pcmcia_core 40596 3 pcmcia,yenta_socket,rsrc_nonstatic
nvidia 7825536 40
snd_seq_dummy 4868 0
i2c_core 24832 17 tuner,tea5767,tda8290,tda18271,tda827x,tuner_xc2028,xc5000,tda9887,tuner_simple,mt20xx,tea5761,tvp5150,ir_kbd_i2c,em28xx,v4l2_common,tveeprom,nvidia
snd_seq_oss 35584 0
asus_laptop 19064 0
snd_seq_midi 9376 0
led_class 6020 1 asus_laptop
button 9232 0
snd_rawmidi 25760 1 snd_seq_midi
snd_seq_midi_event 8320 2 snd_seq_oss,snd_seq_midi
iTCO_wdt 13092 0
iTCO_vendor_support 4868 1 iTCO_wdt
snd_seq 54224 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer 24836 2 snd_pcm,snd_seq
snd_seq_device 9612 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
shpchp 34452 0
pci_hotplug 30880 1 shpchp
intel_agp 25492 0
agpgart 34760 2 nvidia,intel_agp
snd 56996 19 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_hwdep,snd_seq_dummy,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore 8800 1 snd
ext3 136712 4
jbd 48404 1 ext3
mbcache 9600 1 ext3
sg 36880 0
sr_mod 17956 1
cdrom 37408 1 sr_mod
sd_mod 30720 6
ahci 28420 0
ata_generic 8324 0
ata_piix 19588 6
ohci1394 33584 0
pata_acpi 8320 0
ieee1394 93752 2 sbp2,ohci1394
skge 43536 0
libata 159344 4 ahci,ata_generic,ata_piix,pata_acpi
scsi_mod 151436 5 sbp2,sg,sr_mod,sd_mod,libata
ehci_hcd 37516 0
uhci_hcd 27024 0
usbcore 146028 5 em28xx,hci_usb,ehci_hcd,uhci_hcd
thermal 16796 0
processor 36872 2 thermal
fan 5636 0
fbcon 42912 0
tileblit 3456 1 fbcon
font 9472 1 fbcon
bitblit 6784 1 fbcon
softcursor 3072 1 bitblit
fuse 50580 5

Thanx in advance!!

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

What does 'cat /proc/cmdline' show?

Changed in linux-restricted-modules-2.6.24:
status: New → Incomplete
Revision history for this message
Thomas Reuss (thomas-reuss) wrote :

Hi Timo,

here is the requested output:

$ cat /proc/cmdline
root=UUID=08948fd6-d296-4ec6-9baf-f9b59e88ae03 ro quiet splash

Best regards,
Thomas Reuss

Revision history for this message
Denis Rut'kov (dendron2000) wrote :

I have the same problem on my laptop with GeForce 6600Go videocard.

Changed in linux-restricted-modules-2.6.24:
status: Incomplete → Confirmed
Revision history for this message
digehode (digehode) wrote :

I'm having the same problem (I think) with my Dell CPS laptop that has a GeForce Go 7950 GTX.

I get a weird techno-plaid pattern that obscures everything. Even the F1, F2 and so on terminals are screwed. I've found that using vbetool to turn off monitor power and then back on again gets me back in, but it;s hardly great.

Using compiz seems to make it happen more frequently, but it happens even without it. About 4 or five times an hour with, once an hour without.

Revision history for this message
Denis Rut'kov (dendron2000) wrote :

The bug is still present.

Revision history for this message
Bryce Harrington (bryce) wrote :

[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.]

Revision history for this message
Denis Rut'kov (dendron2000) wrote :

I have installed 180 driver, the bug is still present. I'm sorry, I don't want to install OS in alpha version (Jaunty) on my main computer.

Revision history for this message
TJ (tj) wrote :

Confirmed here too. Jaunty amd64 with nvidia 180.29. Switching to VTs results in a black screen with no console.

uname -a
Linux hephaestion 2.6.28-7-generic #20-Ubuntu SMP Mon Feb 9 15:42:34 UTC 2009 x86_64 GNU/Linux

lspci -nn | grep nVidia
01:00.0 VGA compatible controller [0300]: nVidia Corporation G70 [GeForce Go 7600] [10de:0398] (rev a1)

apt-cache policy nvidia-glx-180
nvidia-glx-180:
  Installed: 180.29-0ubuntu2
  Candidate: 180.29-0ubuntu2
  Version table:
 *** 180.29-0ubuntu2 0
        500 http://gb.archive.ubuntu.com jaunty/restricted Packages
        100 /var/lib/dpkg/status

Revision history for this message
Bryce Harrington (bryce) wrote :

Hi thomas-reuss,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

Changed in nvidia-graphics-drivers-180:
status: New → Incomplete
Revision history for this message
Ian Corne (icorne) wrote :

Same here

 2.6.28-8-generic #26-Ubuntu SMP Wed Feb 25 04:28:54 UTC 2009 i686 GNU/Linux

Revision history for this message
Bryce Harrington (bryce) wrote :

[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

Revision history for this message
auxbuss (launchpad-auxbuss) wrote :

Same problem exists with 180.44 on Jaunty. My bedug info is in:

  https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/+bug/313306

Revision history for this message
auxbuss (launchpad-auxbuss) wrote :

What else is required for this to not be marked incomplete? Pray tell.

Revision history for this message
auxbuss (launchpad-auxbuss) wrote :

I think that this problem this is related to:

  http://www.nvnews.net/vbulletin/showthread.php?t=81256&highlight=blank+tty&page=10

The suggested fix is:

  cat /etc/modprobe.d/options | grep nvidia
  options nvidia NVreg_UseVBios=0

But it can't be tried in Jaunty because /etc/modprobe.d/options has been removed.

See:

  http://ubuntuforums.org/showthread.php?t=1117102

How can we test the above in Jaunty to see whether it fixes this problem?

Revision history for this message
Bryce Harrington (bryce) wrote :

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

Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Bryce Harrington (bryce) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
bugbot (bugbot) wrote : linux-restricted-modules-2.6.24 is obsolete

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.

Changed in linux-restricted-modules-2.6.24 (Ubuntu):
status: Confirmed → Won't Fix
Revision history for this message
x15 (x15) wrote :

Hello guys,

I have two different desktop computers and a same problem:
- i7-2600 + nVidia 460SE1024
- AMD X2 3800+ + GA nVidia 7200 card

I use kubuntu AMD64 natty.

The problem is a same: there are no console fonts and I unable to switch back to text mode, the sccreens are blank.
There are no splash screens too.

Both new install and there are no modifications to any standard config files.

Can I disable fbdev somefow? I can't get normal text screen after boot.

piotr zimoch (ebytyes)
Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: Invalid → New
Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

Could you please try a newer and supported Ubuntu version with the latest drivers? Thank you very much!

Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: New → Incomplete
Changed in nvidia-drivers-ubuntu:
status: New → Invalid
status: Invalid → Incomplete
Revision history for this message
bugbot (bugbot) wrote :

We're closing this bug since there has not been a response from the original reporter. However, the issue still exists please feel free to reopen with the requested information. If you're not the original reporter, we'd prefer you file a new bug report.

Some tips:

  * Report X.org bugs via the command: `ubuntu-bug xorg`

  * Test against the latest development Ubuntu. http://cdimage.ubuntu.com/daily-live/
    Bugs marked as affecting the development version tend to get priority attention.

  * The `xdiagnose` utility has functionality for enabling debugging and
    analyzing a few common X problems.

  * Tag your bugs with the Ubuntu versions you have reproduced the issue in.

  * See https://wiki.ubuntu.com/X/Reporting for tips on writing good bug reports.

Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.