kernel module mismatch

Bug #32715 reported by JasperM
8
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.15 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I updated to dapper on 24/2/2006.
Using an old nvidia card (Geforce MX400) I loaded nvidia-glx-legacy and configured xorg to load the nvidia driver. This results in a version mismatch between the kernel module (1.0.8.x) and the driver (1.0.7.x). In the repository however there is no package to load the legacy nvidia kernel module. The nvidia-kernel-common module seems to load the nvidia kernel module 1.0.8x). Is the legacy package not been build ?

Revision history for this message
Adam Conrad (adconrad) wrote :

The legacy nvidia module should be loaded automatically by modprobe when you have nvidia-glx-legacy installed. Of course, this trick may not work if you already have the non-legacy module loaded, so a reboot would be required.

Can you still reproduce this error on a current dapper installation?

Revision history for this message
Gregor Rosenauer (grexe) wrote :

I got a similar error on Edgy Etch and also on a freshly installed Feisty beta (x86).
After installing legacy-drivers, X works fine as long as you do not install any kernel-updates (that adept_updater proposes). Even after updating the nvidia-legacy packages, X won't start and first complained about a missing module "wfb" and now about mismatch in module versions.

To solve this I previously tried the envy-script, and also "update-modules" sometimes helped. But in Feisty I am lost since envy does not yet support this version and "update-modules" as well as "module-assistant" did not help now.

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

JaparM:
A geforce mx 400 should not use the 71xx legacy drivers (see http://us.download.nvidia.com/XFree86/Linux-x86/1.0-9755/README/appendix-a.html ). I guess in dapper (I no longer use it so I can't check) your card should be using the 8xxx series of drivers. Could you indicate if this is a problem on Feisty (perhaps by not installing anything and using a livecd)?

Gregor:
Please create a separate bug report for your Feisty issue rather than overloading this one. In that bug report please give the output of:
lspci | grep -i nv
dmesg
dpkg -l nvidia* | grep ii

You may also want to indicate what the results of using
restricted-manager
in that new bug report too. If you can subscribe me after you have made that will be helpful too.

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

Setting to needsinfo pending reply from JaparM.

Changed in linux-restricted-modules-2.6.15:
status: Unconfirmed → Needs Info
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux-restricted-modules-2.6.15 (Ubuntu) because there has been no activity for 60 days.]

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.