binary nvidia 1.0.9631 crashes X on startup

Bug #105928 reported by infopipe
6
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.20 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: linux-restricted-modules-2.6.20-14-generic

As suggested in bug 89290, I open a new report:

In march I had problems with a crashing X when using the binary nvidia driver version 1.0.9631.
This was fixed when linux-restricted-modules dependency changed to version 1.0.9755 of the nvidia driver.
With revision 2.6.20.5-14.18 of linux-restricted-modules the dependency was changed back to version 1.0.9631 of the nvidia driver. And now my crashes are back :-(
The crashes happen on startup of X and this bug occurs on feisty.
nv driver is working fine (but slow...)

Revision history for this message
infopipe (infopipe) wrote :

xorg log

Revision history for this message
infopipe (infopipe) wrote :

xorg.conf
driver is changed to nv at the moment

Revision history for this message
infopipe (infopipe) wrote :

dmesg output

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

just install nvidia-glx-new?

Revision history for this message
infopipe (infopipe) wrote :

Thank you! I didn't know that this package existed. It's working now.
Should this bug marked as fixed?

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

I guess it depends upon the circumstances this happens in. If restricted-manager is getting this wrong then it's still a bug. If its a transitory thing that would only occur for people who have been testing and upgrading through the Feisty pre-releases then I guess it's a non issue.

Revision history for this message
PrivateUser132781 (privateuser132781-deactivatedaccount) wrote :

I had this same problem. Why is the nvidia-glx package retained - if it is, will this not cause problems for everyone with it installed who upgrade from edgy? Shouldn't nvidia-glx be replaced by nvidia-glx-new rather than introducing a new package?

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

https://launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/96430/comments/77 indicates that for brief time nvidia-glx turned into the 97xx series of drivers causing various problems. nvidia-glx will now remain at the 93xx series of drivers (to keep parity with what people had before because you don't want GeForce 3 owners being put on drivers that no longer support their card) and a new package called nvidia-glx-new has been introduced for the latest series of cards.

Revision history for this message
PrivateUser132781 (privateuser132781-deactivatedaccount) wrote :

My X continues to crash with "failure to load Nvidia kernel module" error, with either nvidia-glx or nvidia-glx-new installed.

lspci lists my card as: VGA compatible controller: nVidia Corporation C51G [GeForce 6100] (rev a2)

Installed packages are as follows:
ii nvidia-glx 1.0.9631+2.6.20.5-15.20 NVIDIA binary XFree86 4.x/X.Org driver
ii nvidia-kernel-common 20051028+1ubuntu7 NVIDIA binary kernel module common files

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Eduard:
I think you are going to have to spin off a separate bug report. I noticed you have posted in several bugs and I have no idea what you have tried. In that bug report the following files / information needs to be attached or added:
lscpi | grep -i nv
dpkg -l nvidia\* | grep ii
Whether your card has a TV-Out socket.
uname -a
The dmesg.txt file produced by doing
dmesg > dmesg.txt
The /var/log/Xorg.0.log created when this problem occurred.

When you are done either include a link back here or subscribe me to the bug.

Revision history for this message
PrivateUser132781 (privateuser132781-deactivatedaccount) wrote :

Thanks, Sitsofe, will do.

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

Closing the bug since it's very old without any activity in a long time. Please open a new bug against the graphics driver package if you have problems in 8.04 or later.

Changed in linux-restricted-modules-2.6.20:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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