nvidia-glx installed itself over Nvidia propriatary

Bug #105285 reported by sojourner on 2007-04-10
Affects Status Importance Assigned to Milestone
nvidia-kernel-common (Ubuntu)
update-manager (Ubuntu)

Bug Description

Binary package hint: update-manager

during one of todays updates update-manager installed nvidia-glx(9631) over top of my Nvidia propriatary driver (9755) crashing x on my next bootup and forcing a reinstall of my chosen driver. Note I do not have nvidia-glx installed (and according to synaptic it is not installed now). I have NEVER installed any ubuntu supplied nvidia driver , not nvidia-glx or nvidia-glx-legacy.in other words update manager updated a driver that did not exist on my system.

As far as I know nvidia-glx is also proprietary and needed to use the nvidia kernel module.

After an update I made about the same time as the reporting user, X couldn't load nvidia module because of an API mismatch: kernel module was version 9755 while X module stayed 9631. I have fortunately noticed there is a difference between nvidia-glx, using 9631, and nvidia-glx-new, correctly using 9755.

I installed nvidia-glx-new which is working now. However I must say I've had problems loading nvidia since I installed Feisty three days ago: I fell back to 20-13 kernel and had to reinstall linux-restricted-modules after each reboot and manually modprobe nvidia. The API issue appeared only once, after getting back to kernel 20-14. The previous times it just couldn't have found a module file.

Krymzon (krymzon) wrote :

I think it should be marked as a bug of nvidia-glx, not update-manager, but there seems to be no such a package on Launchpad...

sojourner (itsmealso2) wrote :

Kryzmon I believe that it is a bug in update manager , I do not and have never had nvidia-glx (any flavor) installed .Update manager should not have updated a prg that does not exist on my machine. try the real nvidia driver from nvidia.com that should cure your problems starting nvidia, nvidia-glx has been causing lots of people headaches judging from the forum.

sojourner (itsmealso2) wrote :

just rebooted after todays updates (april 11 2007 11:30 US edt) it did it again , it apears that update-manager is substuting nvidia-kernal-common for my 2.6.20-14-generic or else substituting the nvidia-glx module for my propriatary driver module , my grub specifies 2.6.20-14-generic .

Joseph Price (pricechild) wrote :

nvidia-glx-new will install the 9755 driver for you, replacing nvidia-glx

that is exactly the problem ! read my original bug
report . I do not have nvidia-glx installed .
Nvidia-glx has NEVER been installed. I use the nvidia
driver from nvidia.com (9755-pkg2 (amd64)).the bug is
that a package was "updated" which did not exist on my
system , and furthermore was not shown by synaptic as
being installed after the update.

Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around

sojourner (itsmealso2) wrote :

addenda to the above : in any case nvidia-glx (9631 ) would be the wrong driver for my card (fx5200-128mb). yet that is the one that was installed each time.

Sitsofe Wheeler (sitsofe) wrote :

By default, all nvidia kernel modules are installed (they come with linux-restricted-modules). Whether they are used or not depends on the setting in /etc/default/linux-restricted-modules-common .

Installing nvidia-glx-new will make Ubuntu Feisty use the 97xx series of drivers but if you want to use manually installed drivers then this is of little consequence.

Timo Aaltonen (tjaalton) wrote :

probably something to do with update-manager, although I'm quite sure it's not possible anymore.

Changed in nvidia-kernel-common:
status: New → Invalid
sojourner (itsmealso2) wrote :

as far as I am concerened you can close this bug has fixed , it has not recured with later hardy updates and has not occured with intrepid.

Chris Coulson (chrisccoulson) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

Changed in update-manager:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers