Is RPMfusion on strike?
William Case
billlinux at rogers.com
Sat Aug 22 14:10:07 UTC 2009
Hi;
On Sat, 2009-08-22 at 09:22 -0400, William Case wrote:
> On Sat, 2009-08-22 at 06:28 -0400, Matthew Saltzman wrote:
> > On Sat, 2009-08-22 at 03:06 -0400, William Case wrote:
> > What happens if you run akmods --force from the command line (as root)?
> > (If you aren't running the kernel you want to build for, add --kernels
> > <kernel-version>.)
> >
> I haven't tried akmods -- force. I will try it now and check my dmesg
> and /var/log/messages afterwards.
>
/var/log/messages warns:
NVRM: API mismatch: the client has the version 185.18.31, but
NVRM: this kernel module has the version 185.18.14. Please
NVRM: make sure that this kernel module and all NVIDIA driver
NVRM: components have the same version.
But for 2.8 ]# akmods --force --kernels 2.6.29.6-217.2.8.fc11.x86_64
Checking kmods exist for 2.6.29.6-217.2.8.fc11.x86_64 [ OK ]
and for 2.7;
]# akmods --force --kernels 2.6.29.6-217.2.7.fc11.x86_64
Could not find files needed to compile modules for
2.6.29.6-217.2.7.fc11.x86_64
>
> > FWIW, aknod worked smooth as silk here (Quadro NVS 140M
> > 2.6.29.6-217.2.8.fc11.x86_64) and even with legacy drivers (GeForce FX
> > 5400 2.6.29.6-217.2.8.fc11.i686.PAE).
> >
> I never had a problem with akmod-nvidia before either. I have been
> using it for a least a year now -- until the
> 2.6.29.6-217.2.8.fc11.x86_64 kernel and the 2.6.29.6-217.2.7.fc11.x86_64
> kernel. They wouldn't rebuild but my system would default to the vesa
> driver after akmod-nvidia was removed. The 2.6.29.6-217.2.3.fc11.x86_64
> kernel works fine.
>
> >
> --
> Regards Bill
> Fedora 11, Gnome 2.26.3
> Evo.2.26.3, Emacs 23.1.1
>
--
Regards Bill
Fedora 11, Gnome 2.26.3
Evo.2.26.3, Emacs 23.1.1
More information about the fedora-list
mailing list