Re: Is RPMfusion on strike?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Aug 22, 2009 at 1:28 PM, Matthew Saltzman <mjs@xxxxxxxxxxx> 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?

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

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'm using the akmod for a while now (on 4 different machines) and they seem to work just fine.
However, make sure you:

1. Install the required packages: (64bit with multi-lib in this case)
xorg-x11-drv-nvidia-libs.i586
akmod-nvidia.x86_64
xorg-x11-drv-nvidia-libs.x86_64
xorg-x11-drv-nvidia.86_64

2. Build the required modules:
/etc/init.d/akmods restart
/etc/init.d/nvidia restart

3. Add the missing module configurations in xorg.conf
Section "Files"
    ModulePath      "/usr/lib64/xorg/modules/extensions/nvidia/"
    ModulePath      "/usr/lib64/xorg/drivers"
    ModulePath      "/usr/lib64/xorg/modules"
EndSection

4. Restart X.

Hope it helps,
- Gilboa
-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux