Just discovered these messages in /var/log/messages, while looking at the USB problem I just posted about, separately.
Apr 27 20:23:16 fcshome kernel: NVRM: API mismatch: the client has the version 331.67, but Apr 27 20:23:16 fcshome kernel: NVRM: this kernel module has the version 331.49. Please Apr 27 20:23:16 fcshome kernel: NVRM: make sure that this kernel module and all NVIDIA driver Apr 27 20:23:16 fcshome kernel: NVRM: components have the same version. Apr 27 20:23:16 fcshome kernel: NVRM: nvidia_frontend_ioctl: minor 255, module->ioctl failed, error -22 Apr 29 19:22:30 fcshome kernel: NVRM: API mismatch: the client has the version 331.67, but Apr 29 19:22:30 fcshome kernel: NVRM: this kernel module has the version 331.49. Please Apr 29 19:22:30 fcshome kernel: NVRM: make sure that this kernel module and all NVIDIA driver
but I cannot find anything relating to Nvidia that has a 331.49 version number. "yum list installed | grep 331.49" returns no hits "yum list installed | grep 331.[0-9]" returns ONLY hits on 331.67. "find 331" finds lots of things, but none of them is 331.49.
So, I'd be appreciative if someone could shine a light on this for me.
thanks!
On 05/01/2014 12:32 PM, Fred Smith wrote:
Just discovered these messages in /var/log/messages, while looking at the USB problem I just posted about, separately.
Apr 27 20:23:16 fcshome kernel: NVRM: API mismatch: the client has the version 331.67, but Apr 27 20:23:16 fcshome kernel: NVRM: this kernel module has the version 331.49. Please Apr 27 20:23:16 fcshome kernel: NVRM: make sure that this kernel module and all NVIDIA driver Apr 27 20:23:16 fcshome kernel: NVRM: components have the same version. Apr 27 20:23:16 fcshome kernel: NVRM: nvidia_frontend_ioctl: minor 255, module->ioctl failed, error -22 Apr 29 19:22:30 fcshome kernel: NVRM: API mismatch: the client has the version 331.67, but Apr 29 19:22:30 fcshome kernel: NVRM: this kernel module has the version 331.49. Please Apr 29 19:22:30 fcshome kernel: NVRM: make sure that this kernel module and all NVIDIA driver
but I cannot find anything relating to Nvidia that has a 331.49 version number. "yum list installed | grep 331.49" returns no hits "yum list installed | grep 331.[0-9]" returns ONLY hits on 331.67. "find 331" finds lots of things, but none of them is 331.49.
So, I'd be appreciative if someone could shine a light on this for me.
thanks!
You updated the NVIDIA driver/kernel module while the old one was loaded into the kernel.
As root: # telinit 3 # rmmod nvidia # telinit 5
- Thomas
On Thu, May 01, 2014 at 12:50:55PM -0700, Thomas Eriksson wrote:
On 05/01/2014 12:32 PM, Fred Smith wrote:
Just discovered these messages in /var/log/messages, while looking at the USB problem I just posted about, separately.
Apr 27 20:23:16 fcshome kernel: NVRM: API mismatch: the client has the version 331.67, but Apr 27 20:23:16 fcshome kernel: NVRM: this kernel module has the version 331.49. Please Apr 27 20:23:16 fcshome kernel: NVRM: make sure that this kernel module and all NVIDIA driver Apr 27 20:23:16 fcshome kernel: NVRM: components have the same version. Apr 27 20:23:16 fcshome kernel: NVRM: nvidia_frontend_ioctl: minor 255, module->ioctl failed, error -22 Apr 29 19:22:30 fcshome kernel: NVRM: API mismatch: the client has the version 331.67, but Apr 29 19:22:30 fcshome kernel: NVRM: this kernel module has the version 331.49. Please Apr 29 19:22:30 fcshome kernel: NVRM: make sure that this kernel module and all NVIDIA driver
but I cannot find anything relating to Nvidia that has a 331.49 version number. "yum list installed | grep 331.49" returns no hits "yum list installed | grep 331.[0-9]" returns ONLY hits on 331.67. "find 331" finds lots of things, but none of them is 331.49.
So, I'd be appreciative if someone could shine a light on this for me.
thanks!
You updated the NVIDIA driver/kernel module while the old one was loaded into the kernel.
As root: # telinit 3 # rmmod nvidia # telinit 5
That could well be the problem,... I tend to lose track of such things sometimes.
for some reason telinit 3 went bonkers so I ended up doing a reboot which should (and seems to have) also solve(d) the problem.
Thanks!