nVidia mismatch client and driver

Asked by abisen on 2007-04-12

I had a perfectly working system (it still is working fine) but during the cycle's of aptitude upgrade (regular) on my Fiesty (installed from HERD 5 initially and upgraded regularly using aptitude) I have started getting the following messages in my dmesg

[161485.844282] NVRM: API mismatch: the client has the version 1.0-9631, but
[161485.844284] NVRM: this kernel module has the version 1.0-9755. Please
[161485.844285] NVRM: make sure that this kernel module and all NVIDIA driver
[161485.844287] NVRM: components have the same version.

It seems that there is some kind of mismatch in a way where the kernel and the kernel drivers were updated but the other related apps were not. It's not causing any problems other that this and I am not sure whether it should be a bug or not.

System: Intel Core 2 Duo with 4Gig RAM
Ubuntu: Feisty Fawn 7.04 i386

Thanks

------------

I had the same error message on a new Feisty install. There is a mismatch and to resolve it I had to:
1. sudo apt-get install nvidia-glx-new nvidia-glx-new-dev
2. Edit the xorg.conf file by hand replacing the driver "vesa" with "nvidia" and remove dri loading.
3. sudo modprobe -r nvidia
4. startx

When I reboot, gdm does not start because some other nvidia driver is being loaded and I have to do steps 3 and 4 above to get accelerated X. But I do have 3D acceleration now and am workingto see what it takes to get gdm to start.
--sjl

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
2007-04-13
Last reply:
2008-08-01
abisen (anandbisen) said : #1

abisen@pluto~>uname -a
Linux pluto 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007 i686 GNU/Linux

abisen@pluto~>dpkg-query -l | grep nvidia
ii nvidia-glx 1.0.9631+2.6.20.5-14.18 NVIDIA binary XFree86 4.x/X.Org driver
ii nvidia-kernel-common 20051028+1ubuntu7 NVIDIA binary kernel module common files

John Haitas (jhaitas) said : #2

seems as if you have a nvidia-glx / linux-restricted modules version mismatch....

did you try installing your nvidia driver outside of the apt / aptitude / synaptic system?

This could be related to a kernel upgrade: if you upgraded your kernel version without installing the new nvidia linux restricted modules for the new kernel version, than it could come up to this kind of mismatch.

abisen (anandbisen) said : #4

I did not do anything outside synaptic/aptitude because I don't want to. My point being that if a kernel is getting upgraded then all the related things should too (that's the apt way?). I can do things to fix it but since i am not having any issues as of now i'll just leave it till it works fine :)

I thought I should notify the community to see if it's eligible to be marked as bug ?

Thanks

Anand

John Haitas (jhaitas) said : #5

first of all you must remember feisty is still a beta - this stuff can happen...

it just so happens that i'm running the nvidia-glx drivers and have not had any problems with drivers and i use 3d acceleration for work...

looking at your error message above your kernel module(1.0-9755) is clearly more recent than you driver (1.0-9631)...

this means your linux-restricted-modules is newer that your nvidia-glx ...

like i said i do not have this problem... no need to report a bug just yet
i use synaptic for gui and aptitude in the console...

can you explain the conditions when you get the error? perhaps someone can replicate the issue

John Haitas (jhaitas) said : #6

first of all you must remember feisty is still a beta - this stuff can happen...

it just so happens that i'm running the nvidia-glx drivers and have not had any problems with drivers and i use 3d acceleration for work...

looking at your error message above your kernel module(1.0-9755) is clearly more recent than you driver (1.0-9631)...

this means your linux-restricted-modules is newer that your nvidia-glx ...

like i said i do not have this problem... no need to report a bug just yet
i use synaptic for gui and aptitude in the console...

can you explain the conditions when you get the error? perhaps someone can replicate the issue

Actually I don't know if this is a problem concerning Feisty...
When I was still using Edgy, it has given me more than once this same problem... I guess it could be connected to the dependencies... I am sure nvidia-glx requires the restricted module... But can the restricted module require nvidia-glx? Isn't it a cycle? How could apt resolve such a dependence?
I think this could be related to such a thing... Just guessing :)

John Haitas (jhaitas) said : #8

are you still having this problem?

I'm running into the same problem. My video card doesn't appear in the Restricted Driver Manager, so I tried to install the nvdia-glx package, but the X Server crashes with an error very similar to the one described by abisen.

I have installed Feisty Fawn (the 64 bit version that might be important) into my HP Laptop. The machine comes with a NVIDIA® GeForce® Go 7400. I can give you additional details if needed.

huiii (a00ps) said : #10

same probleme here,
api mismatch, blablabla,
is getting boring,
everything gl related broken after ubuntu feisty updates,
when trying to fix it by deinstalling nvidia drivers to install it back again, i got this message api mismatch nvidia-kernel-module being 1-0.7184 but i installed 1-0.9755.
bah
i don' t know how to fix this mess right now

nowayout (smashthestate81) said : #11

I just had this problem, fixed it by (in synaptic) removing nvidia-glx and installing nvidia-glx-new, which shows version 9755, which matches linux-restricted-modules version. Only problem was in restricted manager, checking enabled for the nvidia driver was changing these two back again (ie, pulling through the previous version) so I've just left it unchecked, but the new driver seem to be loaded and working fine.

Apparently my issue was resolved by a kernel update yesterday. I have installed nvidia-glx and it doesn't complain about the versions anymore.

John Haitas (jhaitas) said : #13

can we mark this as solved?

It's looking good, I didn't have any more problems, so yes I think so.

John Haitas (jhaitas) said : #15

could somebody please mark this as solved?

krahim (karim-rahim) said : #16

please do not mark this as solved. there is still a mismatch

Nvidia with all the latest updates running amd 64, with the following sources list does not work with the edgy newest kernel

##from my sources file.
##nvidia latest worked with -11 kernel not -12 sept 13/07
deb http://www.albertomilone.com/drivers/edgy/latest/64bit binary/

current working kernel
karim@ubuntult01:~$ uname -a
Linux ubuntult01 2.6.17-11-generic #2 SMP Fri May 18 22:25:27 UTC 2007 x86_64 GNU/Linux

I will upgrade to Fiesty shortly as Edgy is nearing end of life, but this bug has not been solved at this point.

Karim

Stas Sușcov (sushkov) said : #17

Still unsolved!

After installing nvidia-glx-new-envy and then rolling back to nvidia-glx-new, you'll get the same error:
[ 76.190665] NVRM: API mismatch: the client has the version 169.12, but
[ 76.190668] NVRM: this kernel module has the version 96.43.05. Please
[ 76.190669] NVRM: make sure that this kernel module and all NVIDIA driver
[ 76.190670] NVRM: components have the same version.

The problem is caused by envy drivers which I would remove from repository due to incompatibility with the rest of the system.

I also had some problems after installing envy with file permissions wich I had to change every time I was starting nvidia-settings!

It was ok to have envy somwhere for the back-up but not in repos.
Too much problems for actually small benefit!

vnevoa (vasco-nevoa) said : #18

I had this problem just now in 8.04 Hardy after playing around with the "-envy" version of the drivers.
The only way to get the system back was to forcefully reinstall the kernel drivers.

sudo rm -rf /lib/modules/2.6.24-20-generic/kernel/drivers/video/nvidia
sudo apt-get --reinstall install linux-generic nvidia-glx-new

Can you help with this problem?

Provide an answer of your own, or ask abisen for more information if necessary.

To post a message you must log in.