rpmfusion nvidia drivers

[GoinEasy9]

Edit /boot/grub/menu.lst in Debian, In Fedora it's /boot/grub/grub.conf. Heh, I came from Debian....
BTW, I get the error also, but nouveau.modeset=0 works.

[morgentao]

Originally Posted by GoinEasy9

Well, since akmod-nvidia is in the repo, I tried yum install akmod-nvidia which brought in a host of dependencies including xorg-x11-drv-nvidia-190.42-1.fc12.i686. After reboot, I was left with a blinking cursor in the upper left hand side of the screen.

i have the same error

[GoinEasy9]

@morgentao
when installing akmod-nvidia add nouveau.modeset=0 to the kernel line in grub.conf and the akmods work.

[Motero]

on my laptop @home even with nouveau.modeset=0 i'm having the problem that i can login thru kdm, but during kde init the system redisplays the nvidia logo and drops me back to kdm

i'm using the kde x86_64 spin

[edit:]
with nouveau driver the system works fine

[AdamW]

you need to _both_ blacklist nouveau _and_ set 'nomodeset'.

nomodeset stops it being brought up during initrd stage to draw the pretty splash screen. blacklisting stops it being brought up by udev. if you only do one, nouveau is still getting loaded.

[Hlingler]

So: officially, "nouveau" is now as hard to kill as a cockroach... .


V

[AdamW]

we're just trying really hard to make sure you don't do anything evil like using proprietary drivers

[Jongi]

what's the difference between kmod-nvidia and akmod-nvidia again?

[AdamW]

kmod packages contain the NVIDIA driver already 'built' against a specific kernel that's declared in their package name. the akmod package contains the NVIDIA driver 'source' ready to be built against any kernel. the akmods service checks at each boot whether a kmod package for the current running kernel exists for each akmod package you have installed, and if not, it builds one from the akmod-provided 'source'. so the akmod package protects against the case where RPM Fusion has not yet uploaded a pre-built kmod for the latest update kernel.

[Jongi]

akmod it is then. thanks.

[Motero]

after another failed attempt i finally (which i should have done first) had a look into Xorg.0.log and found the following:

dlopen: /usr/lib64/xorg/modules/extensions/nvidia/libglx.so: cannot enable executable stack as shared object requires: Permission denied
(EE) Failed to load /usr/lib64/xorg/modules/extensions/nvidia/libglx.so

selinux was the one to blame

after switching selinux off, everything works now (though the system strangely reacts much slower than with nouveau driver - even with compositing turned off)

would be happy if someone could help me out now with what to do with selinux and how to have a little performance back

[AdamW]

if you're using KDE:

https://bugzilla.redhat.com/show_bug.cgi?id=533620

explanation there, use the scratch xorg-x11-server build from my comment.

[Motero]

thank you very much!

installing the suggested packages resolved the issue

[bob]

Just as a point of info, I had about every possible problem mentioned here in trying to get 3D. No matter what, nouveau remained stubbornly in control and trying to force it out resulted in the black screen with cursor and two hours of trying to use vi with a 'hidden' cursor. Not fun!

My solution was to stop using my favorite 'configfile' entry to boot F12. If booted that way, the akmod or kmods never engage. However, booting directly with the entries in the grub.conf forces that 'nouveau.modeset=0' to take control and allow the kmod-nvidia to work.

Hmmm....now that it's reconfigured xorg.conf, wonder if my beloved configfile will be useable? BRB! Edit: And the answer is......nope! Well, that's the end of the configfile entries for me in grub.conf or menu.lst.

[GoinEasy9]

LOL....once my xorg was reconfigured, everything worked. (with nouveau.modeset=0 in the kernel line).