nvidia kernel module has version mismatch with nvidia xorg module (manual install?)

[mewt]

I have just upgraded to feisty and I am having some problems with X. on first installation of both of nvidia-glx, nvidia-glx-new and the manual drivers from nvidia.com x works well...however on reboot x fails to start giving the error that there is an API mismatch between the nvidia kernel module and the xorg module..the xorg module being on version 9755 while the kernel module being on (if i remember well) on 7184. I am re-sumbitting this bug as it seems that in all occurences of it, it has been disregarded as an nvidia problem but with the same driver as the one i was using in edgy this problem only happened once i upgraded to feisty.

[sarge84 (awanderson)]

I, too, have this problem after upgrading to Feisty.

[Sitsofe Wheeler (sitsofe)]

sarge84:
Could you attach the following files:
/var/log/Xorg.0.log
/etc/X11/xorg.conf
dmesg.txt produced by
dmesg > dmesg.txt

Could you add the output produced by the following commands to this bug:
dpkg -l nvidia-\* | grep ii
lspci | grep -i nv
ls -al /lib/linux-restricted-modules/
uname -a

[Sitsofe Wheeler (sitsofe)]

The above comment was actually mean to be to be to mewt too.

[Sitsofe Wheeler (sitsofe)]

Setting to needsinfo pending reply from mewt, sarge84

[mewt (mewt-reaper)]

Sure here comes:

Xorg.0.log

[mewt (mewt-reaper)]

mewt@tehgraveyard:~$ dpkg -l nvidia-\* | grep ii
ii nvidia-glx-new 1.0.9755+2.6.20.5-15.20 NVIDIA binary XFree86 4.x/X.Org 'new' driver
ii nvidia-glx-new-dev 1.0.9755+2.6.20.5-15.20 NVIDIA binary XFree86 4.x/X.Org 'legacy' dri
ii nvidia-kernel-common 20051028+1ubuntu7 NVIDIA binary kernel module common files
ii nvidia-new-kernel-source 1.0.9755+2.6.20.5-15.20 NVIDIA binary 'new' kernel module source

mewt@tehgraveyard:~$ lspci | grep -i nv
01:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600 GS] (rev a2)

mewt@tehgraveyard:~$ ls -al /lib/linux-restricted-modules/
total 28
drwxr-xr-x 5 root root 4096 2007-04-18 19:26 .
drwxr-xr-x 17 root root 8192 2007-04-18 10:31 ..
drwxr-xr-x 18 root root 4096 2006-12-13 14:37 2.6.17-10-386
drwxr-xr-x 16 root root 4096 2007-04-09 18:03 2.6.17-10-generic
drwxr-xr-x 17 root root 4096 2007-04-18 19:26 2.6.20-15-generic
-rw-r--r-- 1 root root 58 2007-04-18 19:04 .nvidia_new_installed

mewt@tehgraveyard:~$ uname -a
Linux tehgraveyard 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux

[mewt (mewt-reaper)]

I wonder why when i do lspci | grep -i nv, the card is detected as a 6600gs :S when it's an 6800 :S

[Sitsofe Wheeler (sitsofe)]

mewt:
You've been conned into buying a fake! :P

OK seriously, that can happen due to simple mislabeling. It could be the database of device IDs is incorrect or the card itself simply has the wrong identity set in its BIOS. I think it's the former because the binary nvidia driver seems to detect it as a 6800. It might be worth spinning that off into a separate bug report.

Looking at version mismatch problem... Hmm this is very odd. Something is loading the nvidia-glx-legacy/71xx version of the nvidia driver before the correct version can be loaded. Did you use a 3rd party tool like envy to previously install the nvidia binary drivers on edgy?

It would be useful to have:
/etc/default/linux-restricted-modules-common
attached to this bug too.

[mewt (mewt-reaper)]

no nothing else used...I used synaptic to install the nvidia-glx-new
packages...never installed legacy drivers..now im using the manual
installation or else i wont be able to get into graphical interface

will attack requested file with next post

On 4/21/07, Sitsofe Wheeler <email address hidden> wrote:
>
> mewt:
> You've been conned into buying a fake! :P
>
> OK seriously, that can happen due to simple mislabeling. It could be the
> database of device IDs is incorrect or the card itself simply has the
> wrong identity set in its BIOS. I think it's the former because the
> binary nvidia driver seems to detect it as a 6800. It might be worth
> spinning that off into a separate bug report.
>
> Looking at version mismatch problem... Hmm this is very odd. Something
> is loading the nvidia-glx-legacy/71xx version of the nvidia driver
> before the correct version can be loaded. Did you use a 3rd party tool
> like envy to previously install the nvidia binary drivers on edgy?
>
> It would be useful to have:
> /etc/default/linux-restricted-modules-common
> attached to this bug too.
>
> --
> nvidia kernel module has version mismatch with nvidia xorg module
> https://bugs.launchpad.net/bugs/107646
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Sitsofe Wheeler (sitsofe)]

mewt:
Had you done a manual install throughout this whole bug?

[mewt (mewt-reaper)]

doing a manual install of the nvidia driver is the only way which allows me to enter gui right now...and i still need to reinstall the driver after every restart

[Sitsofe Wheeler (sitsofe)]

mewt:
If I'd known I would have asked you to switch to the nv or vesa driver which would have at least given you a GUI. However now all bets are off because you may no longer be running Ubuntu provided software...

I'm going to stop posting replies to this bug because I only post on issues where all the software involved was supplied from Ubuntu repositories (it's hard enough debugging these issues as it stands, with 3rd party downloads and configuration there are just too many possible problems for me). If you don't get any replies here you may want to post about your issue on http://www.nvnews.net/vbulletin/forumdisplay.php?f=14 which is the forum that NVIDIA look at, http://ubuntuforums.org/ (which probably has people willing to support non-ubuntu software) or using the answers section over at https://answers.launchpad.net/ .

A few hints before I go though:
You can use the configuration in
/etc/default/linux-restricted-modules-common
to control whether your system will try and use the Ubuntu provided drivers or manual drivers. There is however a bug covering the use of this file when nvidia-glx-new has been used at some point in the past (see Bug #105756 ).

Good luck!

[Sitsofe Wheeler (sitsofe)]

Setting back to unconfirmed as mewt answered every question very quckly.

[mewt (mewt-reaper)]

HI,

I was using nvidia-glx-new, I only reverted to the manual installation as I needed to use the graphical interface...anyhow..your hint about /etc/default/linux-restricted-modules-common made me check that file and i added nv as one of the modules to not be loaded at startup and i restarted..The system booted up immediately into gui..altho seemingly slower.. Beryl works well, no slowing down of animations or anything..the restricted drivers manager shows i am using a restricted driver. I am probably using the manually installed nvidia driver right now but id like to be able to use nvidia-glx-new since this is what was not working when i first reported the bug.

Going over to the bug you mentions #105756 seems like it is exactly what i did to fix my current problem and what I should do to get nvidia-glx-new to work again...(I hate breaking the dependancy tree) ;)

Kudos on that and thanks..

[kahuuna (kahuuna)]

Also getting version mismatch between
1.0-7184 nvidia kernel module
and
1.0-9755 X module

This is after having manually installed latest nvidia.com drivers with beryl (http://www.nvidia.com/object/linux_display_ia32_1.0-9755.html)

[unomateo (matt-realivent)]

I just got the same error:

1.0-7184 nvidia kernel module
and
1.0-9755 X module

I'm trying to match these 2 but having a hard time.

[Sitsofe Wheeler (sitsofe)]

kahuuna:
You have manually installed the binary drivers so it doesn't make sense to report problems to this part of launchpad I'm afraid. See https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/107646/comments/15 for hints about better places to ask queries about manual installs.

unomateo:
I suspect your problem is different too this too. If you have manually installed the nvidia driver or used a 3rd party tool to do so see the response to kahuuna. If you have only ever used Ubuntu provided drivers I suggest filing a new bug report (although at a wild guess your problems might be linked to Bug #106365 but it's impossible to say without more information hence the request for a new bug report)

[Yongsu Park (pcpenpal)]

I found the reason. When the script /sbin/lrm-manager (executed by upstart during boot on /etc/rcS.d/S07linux-restricted-modules-common) loads kernel modules, it loads all so nvidia, nvidia_legacy, nvidia_new will be loaded, respectively. So after loading nvidia, loading nvidia_legacy and nvidia_new has no effect. Essentially, loading them all is not appropriate. I found useful script /sbin/lrm-video but I cannot find what uses it. I think lrm-manager should behave differently to fix this problem.

Workaround: Modify /etc/default/linux-restricted-modules-common to skip unnecessary kernel modules. For new driver (9755) users, the content is

DISABLED_MODULES="nvidia nvidia_legacy"

[saads (shakhshir)]

Having this problem too. Installed the nvidia-glx-new package and the kernel module mismatches. Can't start X.

[vax_fortran (ken-cc)]

@Yongsu Park: Thanks!

>> Workaround: Modify /etc/default/linux-restricted-modules-common to skip unnecessary kernel modules. For new driver (9755) users, the content is
>> DISABLED_MODULES="nvidia nvidia_legacy"

This worked for me, I had the same problem with the 1.0-7184 module being loaded and had used the 3rd party nvidia installer to install the 1.0-9755 driver.

[DrFaNaTiC (drfanatic)]

I have the same Problem. I have test the nvidia-glx-new and go back to nvidia-glx. The kernel module mismatches. Can`t start X

[Bjaardker (bjaardker)]

[quote]Workaround: Modify /etc/default/linux-restricted-modules-common to skip unnecessary kernel modules. For new driver (9755) users, the content is

DISABLED_MODULES="nvidia nvidia_legacy"[/quote]

This worked perfectly... thank you so much!

[Sitsofe Wheeler (sitsofe)]

(There are now instructions on doing manual Ubuntu NVIDIA driver installs which include steps on disabling the existing drivers on https://help.ubuntu.com/community/NvidiaManual )

[krahim (karim-rahim)]

I have had this problem in edgy with amd64 since the upgrade to the
2.6.17-12-generic kernel. At the time I was busy and just booted the older kernel where everything works. I have the nvidia beta and have been using it without problems with earlier kernels.

Today I tried reinstalling everything in the 2.6.17-12-generic kernel, from the console of course, but with no luck. The x system still works in the -11 and earlier kernels.
I.e. it works in 2.6.17-11-generic It is amd 64.
I have a hp dv2000 laptop.

The error says kernel module mismatch. I attached the log file.

Thanks very much!
Karim

[Jorge Moraleda (jorge-moraleda)]

I have the same Problem. I have test the nvidia-glx-new and go back to nvidia-glx. The kernel module mismatches. Can`t start X.

I was able to solve it by deleting the file /lib/linux-restricted-modules/.nvidia_new_installed

[Simon1701 (cmon)]

For me, /sbin/lrm-video fglrx did not load the fglrx.ko kernel module as well. The Problem was the line: "modprobe --ignore-install -Qb $@ $MODULE". I looked at the man page of modprobe and didn't find the option "b"...so I removed the "b", so that the line was
 "modprobe --ignore-install -Q $@ $MODULE", then it worked!! Seems like an error in the original file /sbin/lrm-video, since I installed Ubuntu right before.

Simon

[Bryce Harrington (bryce)]

This package has become obsolete so we're closing out the bug report as WONTFIX.
Thanks for reporting it though!

[Dan Quade (danquade)]

So, if I'm still getting this problem, should I reopen this bug or make a dupe?