Restricted Manager pushes wrong driver

Bug #139544 reported by zeddock
6
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.22 (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-restricted-modules-2.6.24 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Fresh load of Gusty
System / Prefs / Appearances
Select Desktop Effects TAB
Click Extra Effects

R-M comes up and tries to install nvidia - NEW driver.
My card, a GeForce4 Go Ti AGP 8x, in a Dell Latitude D800 should not use the NEW version of the driver. Yet, that is what is loaded!

Upon reboot X will not start back up without a manual edit to xorg.conf; changing nvidia back to nv.

zeddock

Revision history for this message
zeddock (zeddock) wrote :

What other information would be helpful to you?
Please give me specific steps to gain logs / settings / etc.

Thanx!

zeddock

Revision history for this message
DanielDeboer (scatterfingers-gmail) wrote :

I'd like to confirm this bug. I've got an nVidia NV44 [GeForce 6200 LE] installed. This is what 'lspci' tells me, and it is correct. Gutsy detects the card and monitor properly, but Restricted Manager is pushing the 'Nvidia-glx-new' driver to me, which does NOT work with this card. Nvidia-glx, when I install it separately and run 'dpkg-reconfigure xserver-xorg', works perfectly.

Revision history for this message
Bryan Quigley (bryanquigley) wrote :

I'm on a 5200 and jockey pushes the nvidia-glx-new which doesn't work. While nvidia-glx does.

unksi (unksi)
Changed in restricted-manager:
status: New → Confirmed
Revision history for this message
Martin Pitt (pitti) wrote :

This is actually a bug in the mappings exported by linux-restricted-modules. Can you please cut&paste the output of

  lspci -n | grep 0300:

for your hardware? Thank you!

Revision history for this message
Martin Pitt (pitti) wrote :

Is this still true for the Hardy versions of l-r-m?

Changed in linux-restricted-modules-2.6.24:
status: New → Incomplete
Revision history for this message
Bryan Quigley (bryanquigley) wrote :

It still pushed the wrong driver... or maybe not. According to http://us.download.nvidia.com/XFree86/Linux-x86/169.12/README/appendix-a.html
my card should be supported by the nvidia-glx-new driver.

lspci -n | grep 0300 output
01:00.0 0300: 10de:0322 (rev a1)

Any suggestions?

Revision history for this message
Martin Pitt (pitti) wrote :

gQuigs, I also have a GeForce 5200 (10de:0322), and nvidia-glx-new has worked well in both Gutsy and Hardy. However, the default in Gutsy was nvidia-glx, and in Hardy nvidia-glx-new. So I'm a bit surprised that it does not work for you? Are you on Gutsy (Ubuntu 7.10)?

zeddock has a different card, though.

Revision history for this message
Bryan Quigley (bryanquigley) wrote :

I am on hardy, 64-bit. Hmm.. there is one residual config package left, that is linux-restriced-modules from the 2.6.22 kernel. It won't let me remove it through synaptic. Could this be the problem?

Revision history for this message
Martin Pitt (pitti) wrote : Re: [Bug 139544] Re: Restricted Manager pushes wrong driver

Hi,

gQuigs [2008-03-04 17:15 -0000]:
> I am on hardy, 64-bit.

Me too..

> Hmm.. there is one residual config package
> left, that is linux-restriced-modules from the 2.6.22 kernel. It won't
> let me remove it through synaptic. Could this be the problem?

I doubt it, it's part of the old Gutsy kernel packages. You can remove
the entire set of 2.6.22 packages to clean up your system, of course.

--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)

My 5 today: #193521 (jockey), #151025 (gnome-mount), #195548 (jockey),
#194963 (jockey), #194052 (gnome-power-manager, hal)
Do 5 a day - every day! https://wiki.ubuntu.com/5-A-Day

Timo Aaltonen (tjaalton)
Changed in linux-restricted-modules-2.6.22:
status: Confirmed → Won't Fix
Revision history for this message
Bryan Quigley (bryanquigley) wrote :

A fresh install, and it works fine. I'm thinking it was something I did trying out experimental drivers, myself.

Changed in linux-restricted-modules-2.6.24:
status: Incomplete → 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.