Is RPMfusion on strike?

[William Case]

On Sat, 2009-08-22 at 06:28 -0400, Matthew Saltzman wrote:
> On Sat, 2009-08-22 at 03:06 -0400, William Case wrote:
> > Hi;
> 
> > If it is any consolation to you, I am having exactly the same problem
> > with the 2.6.29.6-217.2.8.fc11.x86_64 kernel.
> > akmod-nividia-185.18.14-1.fc11.x86_64 doesn't work and 
> > kmod-nvidia-2.6.29.6-217.2.7.fc11.x86_64-185.18.14-1.fc11.5.x86_64q is
> > the last nvidia module I have received.
> 
> In what sense does akmod "not work"?  Do you get messages at boot, in
> dmesg, or in /var/log/messages?
> 

I removed the akmod-nvidia and reinstalled, just to see.  On rebooting,
both the 2.7 and the 2.8 kernels freeze during init with "r8169: eth0:
link up" showing on an otherwise blank screen.  I have waited for over 5
minutes for the kernel(s) to rebuild but my machine just remained
inactive.

> 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.


> 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