This morning, after kernel + nvidia driver update I get this error:
Mar 11 08:46:45 lesca kernel: NVRM: API mismatch: the client has the version 195.36.08, but Mar 11 08:46:45 lesca kernel: NVRM: this kernel module has the version 190.53. Please Mar 11 08:46:45 lesca kernel: NVRM: make sure that this kernel module and all NVIDIA driver Mar 11 08:46:45 lesca kernel: NVRM: components have the same version.
then I boot with previous kernel.
This is my rpm situations:
[root@lesca ~]# rpm -qa|grep 2.6.32.9-70|sort kernel-2.6.32.9-70.fc12.x86_64 kernel-devel-2.6.32.9-70.fc12.x86_64 kernel-firmware-2.6.32.9-70.fc12.noarch kernel-headers-2.6.32.9-70.fc12.x86_64 kmod-nvidia-2.6.32.9-70.fc12.x86_64-190.53-2.fc12.x86_64 perf-2.6.32.9-70.fc12.noarch
now I have "yum remove kernel-devel-2.6.32.9-70.fc12.x86_64 kernel-2.6.32.9-70.fc12.x86_64"
But if I run yum update:
Loaded plugins: fastestmirror, presto, refresh-packagekit Loading mirror speeds from cached hostfile
- fedora: ftp.colocall.net
- livna: ftp-stud.fht-esslingen.de
- rpmfusion-free: mirror.karneval.cz
- rpmfusion-free-updates: mirror.karneval.cz
- rpmfusion-nonfree: mirror.karneval.cz
- rpmfusion-nonfree-updates: mirror.karneval.cz
- updates: ftp.colocall.net
Setting up Update Process Resolving Dependencies There are unfinished transactions remaining. You might consider running yum-complete-transaction first to finish them. --> Running transaction check ---> Package kernel.x86_64 0:2.6.32.9-70.fc12 set to be installed ---> Package kernel-devel.x86_64 0:2.6.32.9-70.fc12 set to be installed --> Finished Dependency Resolution
Dependencies Resolved
======================================================================================================================== Package Arch Version Repository Size ======================================================================================================================== Installing: kernel x86_64 2.6.32.9-70.fc12 updates 21 M kernel-devel x86_64 2.6.32.9-70.fc12 updates 6.2 M
Transaction Summary
Install 2 Package(s) Upgrade 0 Package(s)
Total download size: 27 M Is this ok [y/N]:
The nvidia module is missing.
Besides, yum "There are unfinished transactions remaining. You might consider running yum-complete-transaction first to finish them."
but if I run the suggested command:
# yum-complete-transaction Plugin caricati:fastestmirror, presto, refresh-packagekit Loading mirror speeds from cached hostfile
- fedora: ftp.colocall.net
- livna: ftp-stud.fht-esslingen.de
- rpmfusion-free: mirror.karneval.cz
- rpmfusion-free-updates: mirror.karneval.cz
- rpmfusion-nonfree: mirror.karneval.cz
- rpmfusion-nonfree-updates: mirror.karneval.cz
- updates: ftp.belnet.be
Checking for new repos for mirrors No unfinished transactions left.
none happens
I have also force the nvidia module install with:
yum install kmod-nvidia-2.6.32.9-70.fc12.x86_64.x86_64 Loaded plugins: fastestmirror, presto, refresh-packagekit Loading mirror speeds from cached hostfile
- fedora: ftp.colocall.net
- livna: ftp-stud.fht-esslingen.de
- rpmfusion-free: mirror.karneval.cz
- rpmfusion-free-updates: mirror.karneval.cz
- rpmfusion-nonfree: mirror.karneval.cz
- rpmfusion-nonfree-updates: mirror.karneval.cz
- updates: ftp.wsisiz.edu.pl
Setting up Install Process Resolving Dependencies There are unfinished transactions remaining. You might consider running yum-complete-transaction first to finish them. --> Running transaction check ---> Package kmod-nvidia-2.6.32.9-70.fc12.x86_64.x86_64 0:190.53-2.fc12 set to be updated --> Processing Dependency: kernel-uname-r = 2.6.32.9-70.fc12.x86_64 for package: kmod-nvidia-2.6.32.9-70.fc12.x86_64-190.53-2.fc12.x86_64 --> Running transaction check ---> Package kernel.x86_64 0:2.6.32.9-70.fc12 set to be installed --> Finished Dependency Resolution
Dependencies Resolved
======================================================================================================================== Package Arch Version Repository Size ======================================================================================================================== Installing: kmod-nvidia-2.6.32.9-70.fc12.x86_64 x86_64 190.53-2.fc12 rpmfusion-nonfree-updates 2.3 M Installing for dependencies: kernel x86_64 2.6.32.9-70.fc12 updates 21 M
Transaction Summary
Install 2 Package(s) Upgrade 0 Package(s)
Total download size: 23 M Is this ok [y/N]:
but if I install and reboot the error "NVRM: API mismatch:" appears and X don't start.
Someone have some suggest?
Many tanks
On Thursday 11 March 2010, Dario Lesca wrote:
This morning, after kernel + nvidia driver update I get this error:
Mar 11 08:46:45 lesca kernel: NVRM: API mismatch: the client has the version 195.36.08, but Mar 11 08:46:45 lesca kernel: NVRM: this kernel module has the version 190.53.
Please, check
rpm -qa | grep nvidia
If you have xorg-x11-drv-nvidia-libs-195.36.08-* and xorg-x11-drv-nvidia-195.36.08-*
you can run
yum downgrade xorg-x11-drv-nvidia xorg-x11-drv-nvidia-libs
to get 190.53 version.
Also, it is better to
yum install akmod-nvidia
This will automatically install proper nvidia module even for older kernel if you need to downgrade in case if new kernel will not work.
I have the same problem ( X won't startup ) with the new kernel. There are these lines in /var/log/messages that seem to indicate what serguei wrote:
Mar 11 16:39:17 DoronPc kernel: NVRM: this kernel module has the version 190.53. Please Mar 11 16:39:17 DoronPc kernel: NVRM: make sure that this kernel module and all NVIDIA driver Mar 11 16:39:17 DoronPc kernel: NVRM: components have the same version. Mar 11 16:39:17 DoronPc gdm-binary[3080]: WARNING: GdmDisplay: display lasted 0.063718 seconds Mar 11 16:39:17 DoronPc gdm-binary[3080]: WARNING: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors Mar 11 16:39:17 DoronPc init: prefdm main process (3080) terminated with status 1 Mar 11 16:39:17 DoronPc init: prefdm main process ended, respawning Mar 11 16:39:17 DoronPc init: prefdm respawning too fast, stopped
isn't there another workaround without downgrading?
Doron Bar Zeev wrote:
I have the same problem ( X won't startup ) with the new kernel. There are these lines in /var/log/messages that seem to indicate what serguei wrote:
Mar 11 16:39:17 DoronPc kernel: NVRM: this kernel module has the version 190.53. Please Mar 11 16:39:17 DoronPc kernel: NVRM: make sure that this kernel module and all NVIDIA driver Mar 11 16:39:17 DoronPc kernel: NVRM: components have the same version. Mar 11 16:39:17 DoronPc gdm-binary[3080]: WARNING: GdmDisplay: display lasted 0.063718 seconds Mar 11 16:39:17 DoronPc gdm-binary[3080]: WARNING: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors Mar 11 16:39:17 DoronPc init: prefdm main process (3080) terminated with status 1 Mar 11 16:39:17 DoronPc init: prefdm main process ended, respawning Mar 11 16:39:17 DoronPc init: prefdm respawning too fast, stopped
isn't there another workaround without downgrading?
I am also having these issues after the recent kernel update. I even installed the up-to-date akmod-nvidia package, to no end.
I was able to boot into the previous kernel and it worked though, so that is my temporary workaround until I have more time to troubleshoot the issue.
Andre Goree
On Thu, Mar 11, 2010 at 09:16:55AM -0600, Andre Goree wrote:
I am also having these issues after the recent kernel update. I even installed the up-to-date akmod-nvidia package, to no end.
I was able to boot into the previous kernel and it worked though, so that is my temporary workaround until I have more time to troubleshoot the issue.
I'm also having issues. Both nouveau and the Nvidia drivers fail with the last two kernels. I'm back to 2.6.31.12-174.2.22.fc12.x86_64 and nouveau.
Here's the last chunk of my Xorg.0.log file:
(--) NOUVEAU(0): Chipset: "NVIDIA NV98" (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Loading /usr/lib64/xorg/modules/libint10.so (II) Module int10: vendor="X.Org Foundation" compiled for 1.7.5.901, module version = 1.0.0 ABI class: X.Org Video Driver, version 6.0 (II) NOUVEAU(0): Initializing int10 (II) NOUVEAU(0): Primary V_BIOS segment is: 0xc000 (II) Loading sub module "dri" (II) LoadModule: "dri" (II) Reloading /usr/lib64/xorg/modules/extensions/libdri.so (II) NOUVEAU(0): Loaded DRI module drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: node name is /dev/dri/card0 drmOpenByBusid: Searching for BusID pci:0000:01:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card1 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card2 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card3 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card4 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card5 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card6 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card7 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card8 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card9 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card10 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card11 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card12 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card13 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card14 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card15 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: node name is /dev/dri/card1 drmOpenDevice: node name is /dev/dri/card2 drmOpenDevice: node name is /dev/dri/card3 drmOpenDevice: node name is /dev/dri/card4 drmOpenDevice: node name is /dev/dri/card5 drmOpenDevice: node name is /dev/dri/card6 drmOpenDevice: node name is /dev/dri/card7 drmOpenDevice: node name is /dev/dri/card8 drmOpenDevice: node name is /dev/dri/card9 drmOpenDevice: node name is /dev/dri/card10 drmOpenDevice: node name is /dev/dri/card11 drmOpenDevice: node name is /dev/dri/card12 drmOpenDevice: node name is /dev/dri/card13 drmOpenDevice: node name is /dev/dri/card14 drmOpenDevice: node name is /dev/dri/card15 (EE) [drm] drmOpen failed. (EE) NOUVEAU(0): [drm] error opening the drm (EE) NOUVEAU(0): 879: (II) UnloadModule: "nouveau" (II) UnloadModule: "dri" (II) UnloadModule: "int10" (II) Unloading /usr/lib64/xorg/modules/libint10.so (EE) Screen(s) found, but none have a usable configuration.
On Thu, Mar 11, 2010 at 4:02 AM, Dario Lesca d.lesca@solinos.it wrote:
The nvidia module is missing.
I haven't updated yet because I'm still waiting for kmod-nvidia, the module needed by the kernel for nvidia cards (proprietary driver only, I'm not sure. I suppose so,) Now, when I do "yum update", kmod-nvidia is still not there, the new kernel is also missing... but the kernel's firmware and headers are there.
Once again NVIDIA drivers are creating a mess. Go to Google, enter 2.6.32.9-70 and fedora, you'll see. People with no experience give all kind of solutions that are very unlikely to work. You just need to wait for kmod-nvidia to arrive. And, every time you update, you have to check if there's a kernel update and if the accompanying nvidia module is there.
Howdy. Just to add my $0.02, we've got a couple of dual-monitor systems around here, both running Fedora 12, 64-bit. We're using akmod-nvidia on both systems, and both systems are fully patched and rebooted with the latest kernel.
Our experience is that the video works flawlessly on both systems, EXCEPT that only ONE monitor is recognized on each system. I haven't tried to track this issue in detail, but I do know that before the recent patches -- and reboots -- both systems could "see" two monitors.
I note that there seems to be some activity related to nvidia in the "updates-testing" section of the RPMFusion site:
http://download1.rpmfusion.org/nonfree/fedora/updates/testing/12/x86_64/repo...
so it may be that a fix is on the way. I hope so.
-- Mike
Il giorno gio, 11/03/2010 alle 17.51 -0500, Marcel Rieux ha scritto:
Once again NVIDIA drivers are creating a mess. Go to Google, enter 2.6.32.9-70 and fedora, you'll see.
<IMHO> This should not happen.
The kernel's dependencies should be linked with any additional kernel modules installed to avoid updating the kernel until modules are not available.
Why not? </IMHO>
I solved my problem by removing all nvidia package and install akmod-nvidia.
Now all work fine.
Why there are two way for install proprietary driver? Why one works and the other not?
Thanks for reply.
On Friday 12 March 2010, Marcel Rieux wrote:
On Thu, Mar 11, 2010 at 4:02 AM, Dario Lesca d.lesca@solinos.it
wrote:
The nvidia module is missing.
I haven't updated yet because I'm still waiting for kmod-nvidia, the module needed by the kernel for nvidia cards (proprietary driver only, I'm not sure. I suppose so,) Now, when I do "yum update", kmod-nvidia is still not there, the new kernel is also missing... but the kernel's firmware and headers are there.
yum install akmod-nvidia
Once again NVIDIA drivers are creating a mess. Go to Google, enter 2.6.32.9-70 and fedora, you'll see. People with no experience give all kind of solutions that are very unlikely to work. You just need to wait for kmod-nvidia to arrive. And, every time you update, you have to check if there's a kernel update and if the accompanying nvidia module is there.
akmod-nvidia will solve this problem installing proper module for your kernel.