Is RPMfusion on strike? [SOLVED -- at least for me]
William Case
billlinux at rogers.com
Mon Aug 24 21:31:59 UTC 2009
Hi gilpel;
On Tue, 2009-08-25 at 02:04 +0500, gilpel at altern.org wrote:
> > On Mon, 2009-08-24 at 09:36 +0500, gilpel at altern.org wrote:
> > Again, any messages in dmesg or /var/log/messages
> > or /var/log/Xorg.0.log?
>
> Yes this one, in dmesg:
>
> NVRM: API mismatch: the client has version 185.18.31 but this kernel
> module has version 185.18.14
>
> If I boot with kernel 2.6.29.6-217.2.3.fc11.x86_64 and I uninstall/install
> kmod-nvidia, I still get version 185.18.14.
>
and for
kernel.x86_64 2.6.29.6-217.2.7.fc11 s
kernel.x86_64 2.6.29.6-217.2.8.fc11
kmod-nvidia version 185.18.14 is what you are supposed to get.
> If I boot with kernel 2.6.29.6-217.2.9.fc11.x86_64 and I uninstall/install
> kmod-nvidia, will I get version 185.18.31 ?
Where did you get kernel 2.6.29.6-217.2.9.fc11.x86_64?
kmod-nvidia-185.18.31 comes from rpmfusion-nonfree-updates-testing repo.
Add that and then you have got my previous problem.
Why not stick with kernel-2.6.29.6-217.2.8.fc11 ?
--
Regards Bill
Fedora 11, Gnome 2.26.3
Evo.2.26.3, Emacs 23.1.1
More information about the users
mailing list