F16,F15 & F14 Nvidia driver guides

[weitjong]

A suggestion on step 2.

When installing F12, I chosen to use LVM and I have a LV root partition. My grub entry has something like this:
kernel ........ root=/dev/mapper/vgXXX-lvRoot

Thus the "sed -i '/root=UUID/s|$| rdblacklist=nouveau|' /boot/grub/grub.conf" does not work for me. To make it more generic this would be better.

# sed -i '/root=/s|$| rdblacklist=nouveau|' /boot/grub/grub.conf

p.s. may be that is why nouveau refuses to die for some who follow the guide to the dot.

[leigh123linux]

Originally Posted by weitjong

A suggestion on step 2.

When installing F12, I chosen to use LVM and I have a LV root partition. My grub entry has something like this:
kernel ........ root=/dev/mapper/vgXXX-lvRoot

Thus the "sed -i '/root=UUID/s|$| rdblacklist=nouveau|' /boot/grub/grub.conf" does not work for me. To make it more generic this would be better.

# sed -i '/root=/s|$| rdblacklist=nouveau|' /boot/grub/grub.conf

p.s. may be that is why nouveau refuses to die for some who follow the guide to the dot.

Thanks for the tip

[DivadP]

I have been trying for two days to get my 5200 card working but the closest I could get to it installing was a crash on boot.

I have it working now because:

(a) It was the first thing I did after re-installing F12

(b) I did not do two things that I had been doing

(1) I did not install "yum-plugin-protectbase"

(2) I did not install "yum-plugin-fastestmirror"

I am just offering this in the hope that it may help someone who has been doing this

Thanks Leigh for the dedication you have shown to getting this to work for all of us

[JohnnyLinux]

Originally Posted by Hlingler

The instructions are generic, and intended to work for all users. On a 32-bit OS, the 64-bit packages will simply be unavailable and therefore skipped/ignored.

V

So any questions regarding 64 bit errors will not be addressed?
I have not tried to reinstall my system since I noticed the drivers were in "testing" repos's, but it seems they are in the regular updates now.
I will try the drivers again soon... hopefully they will work this time.

Thanks.

[Hlingler]

So any questions regarding 64 bit errors will not be addressed?

Incorrect: I meant that, when following the instructions on a 32-bit Fedora OS, any of the instructions which command installation of 64-bit packages will be ignored/skipped by YUM, since those 64-bit packages will not be available in Fedora 32-bit repos. Any "error" messages issued by YUM about "no package *x86-64 available" during the installation may be safely ignored by you.*

I have not tried to reinstall my system since I noticed the drivers were in "testing" repos's, but it seems they are in the regular updates now.

Correct: pushed to RPMFusion stable/updates (from *-testing).

V

EDIT: *At least: I think that's what you meant. If not: please clarify. We will, of course, always attempt to answer all (relevant) questions here, no matter how hard our teeth are grinding.

[CarlosMosca]

I was reading and trying every single configuration change possible to try and get the nvidia driver working (installing wasn't an issue) the way it's supposed to when I came about this post:

http://forums.fedoraforum.org/showpo...0&postcount=36

And followed the instructions at the top of the page. Everything worked flawlessly and I'm now enjoying Fedora 12 KDE with enhanced window management as I type.

I thought perhaps posting this here will help somebody else as well.

[Boricua]

Hi, I followed early instructions when F12 was still beta that disabled plymouth in order to allow the nvidia driver to load. Now that F12 is more stable, I was wondering if I can bring back graphical plymouth, that is, deleting the parameters inserted in grub.conf. I have being checking this thread and others without success, so any guidance would be appreciated.

[pablaasmo]

I upgraded from F11 to F12 yesterday using preupgrade. The upgrad went well, but i have a small chaning in the behavior of the wallpaper.

I Use nvidia 9500GT card in TwinView mode. In F11 the wallpaper covered both monitors. But in F12 I get the same picture on each monitor.

Anyone have an explanation for that?
What has changed? Is it Gnome, X11, Compiz or nVidia drivers?

[Eos]

Originally Posted by Hlingler

Correct: pushed to RPMFusion stable/updates (from *-testing).

Does that mean they can now be installed safely via "yum install kmod-nvidia", without any further system-adjustments? Because that's what I just did, but after the reboot X won't start anymore. The logs say something about another driver (probably nouveau)blocking the hardware

[Hlingler]

Does that mean they can now be installed safely via "yum install kmod-nvidia", without any further system-adjustments? Because that's what I just did...

Yes.

...but after the reboot X won't start anymore. The logs say something about another driver (probably nouveau)blocking the hardware

Follow all of the instructions to suppress, and if necessary uninstall, nouveau.

V

[miltbos]

I have been reading the posts on the nvidia issues for F12. Have had absolutely no success getting anything to allow me to use dual screen mode. If I try the automatically generated xorg.conf from the "settings-nvidia" app I get a message about the driver is not an nvidia driver the next time I try to access that app to get my second screen set up. All screen addresses and names appear correct.

Changed to latest released kernel yesterday with no success. Running the x86_64 variant.

File follows:

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 1.0 (mockbuild@builder.wilsonet.com) Sun Nov 22 21:42:15 EST 2009

# Xorg configuration created by livna-config-display

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" RightOf "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "1"
EndSection

Section "Files"
ModulePath "/usr/lib64/xorg/modules/extensions/nvidia"
ModulePath "/usr/lib64/xorg/modules"
EndSection

Section "ServerFlags"
Option "AIGLX" "on"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "ViewSonic VX2035wm"
HorizSync 30.0 - 82.0
VertRefresh 50.0 - 75.0
EndSection

Section "Monitor"
Identifier "Monitor1"
VendorName "Unknown"
ModelName "SHARP HDMI"
HorizSync 15.0 - 75.0
VertRefresh 55.0 - 76.0
EndSection

Section "Device"
Identifier "Videocard0"
Driver "nvidia"
Option "AddARGBGLXVisuals" "True"
EndSection

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 8400 GS"
BusID "PCI:3:0:0"
EndSection

Section "Device"
Identifier "Device1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "nForce 750a SLI"
BusID "PCI:2:0:0"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "Videocard0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection

Section "Screen"
Identifier "Screen1"
Device "Device1"
Monitor "Monitor1"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection

Section "Extensions"
Option "Composite" "Enable"
EndSection

I manually deleted this from the xorg.conf file to get KDE to run. If I do not remove the following pointer information, KDE locks soon after login.

Section "InputDevice"
# generated from data in "/etc/sysconfig/keyboard"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "us"
Option "XkbModel" "pc105"
EndSection

Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Have never had issues with configuring the dual screens before. What am I missing.

[leigh123linux]

Originally Posted by miltbos

I have been reading the posts on the nvidia issues for F12. Have had absolutely no success getting anything to allow me to use dual screen mode. If I try the automatically generated xorg.conf from the "settings-nvidia" app I get a message about the driver is not an nvidia driver the next time I try to access that app to get my second screen set up. All screen addresses and names appear correct.

Changed to latest released kernel yesterday with no success. Running the x86_64 variant.

File follows:

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 1.0 (mockbuild@builder.wilsonet.com) Sun Nov 22 21:42:15 EST 2009

# Xorg configuration created by livna-config-display

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" RightOf "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "1"
EndSection

Section "Files"
ModulePath "/usr/lib64/xorg/modules/extensions/nvidia"
ModulePath "/usr/lib64/xorg/modules"
EndSection

Section "ServerFlags"
Option "AIGLX" "on"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "ViewSonic VX2035wm"
HorizSync 30.0 - 82.0
VertRefresh 50.0 - 75.0
EndSection

Section "Monitor"
Identifier "Monitor1"
VendorName "Unknown"
ModelName "SHARP HDMI"
HorizSync 15.0 - 75.0
VertRefresh 55.0 - 76.0
EndSection

Section "Device"
Identifier "Videocard0"
Driver "nvidia"
Option "AddARGBGLXVisuals" "True"
EndSection

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 8400 GS"
BusID "PCI:3:0:0"
EndSection

Section "Device"
Identifier "Device1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "nForce 750a SLI"
BusID "PCI:2:0:0"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "Videocard0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection

Section "Screen"
Identifier "Screen1"
Device "Device1"
Monitor "Monitor1"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection

Section "Extensions"
Option "Composite" "Enable"
EndSection

I manually deleted this from the xorg.conf file to get KDE to run. If I do not remove the following pointer information, KDE locks soon after login.

Section "InputDevice"
# generated from data in "/etc/sysconfig/keyboard"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "us"
Option "XkbModel" "pc105"
EndSection

Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Have never had issues with configuring the dual screens before. What am I missing.

delete the red bits

[CaptainH]

The answer to this question may be obvious but after doing this step "setsebool -P allow_execstack on" if I wanted to undo it and put it back to how it was would I just run this "setsebool -P allow_execstack off" ? I had another computer were I omitted this step and it still worked fine so I wanted to try and undo it on a different one to see if it still worked. Thanks.

[JohnnyLinux]

Originally Posted by Hlingler

EDIT: *At least: I think that's what you meant. If not: please clarify. We will, of course, always attempt to answer all (relevant) questions here, no matter how hard our teeth are grinding.

Yes, you answered my question. I have decided to reinstall and will use the nouveau drivers for now....

Thanks Hlingler

---------- Post added at 11:18 PM CST ---------- Previous post was at 09:38 PM CST ----------

Originally Posted by weitjong

A suggestion on step 2.

When installing F12, I chosen to use LVM and I have a LV root partition. My grub entry has something like this:
kernel ........ root=/dev/mapper/vgXXX-lvRoot

Thus the "sed -i '/root=UUID/s|$| rdblacklist=nouveau|' /boot/grub/grub.conf" does not work for me. To make it more generic this would be better.

# sed -i '/root=/s|$| rdblacklist=nouveau|' /boot/grub/grub.conf

p.s. may be that is why nouveau refuses to die for some who follow the guide to the dot.

Thanks to this comment I decided to skip Step 2 since it would be redundant.

Nvidia akmod works on 64bit.

Thanks weitjong!

[AdoNNeN]

i have fedora 12 64 bit with the kernel 2.6.31.6-145.fc12.x86_64
nvidia driver starts normally, i can access nvidia settings without a problem, however, KDE won't start, it hangs by the startup. desktop effects in gnome also won't work, i receive the message that Accelerated 3D graphics is not available. interestingly that startkde command works from gnome and kde starts with 3d effects!!! what is going on in here?
i've followed all the installation points and also retried to reenable the nvidia-config-display , i get the following error :

adonnen]# nvidia-config-display disable
Traceback (most recent call last):
File "/usr/sbin/nvidia-config-display", line 146, in <module>
app = nvidiaConfigDisplay()
File "/usr/sbin/nvidia-config-display", line 52, in __init__
self.run()
File "/usr/sbin/nvidia-config-display", line 134, in run
self.disable()
File "/usr/sbin/nvidia-config-display", line 94, in disable
prevDriver = self.config.getOldDriver()
File "/usr/lib/python2.6/site-packages/livnaConfigDisplay/ConfigFile.py", line 112, in getOldDriver
return self.get('Configuration', 'OldDriver')
File "/usr/lib/python2.6/site-packages/livnaConfigDisplay/ConfigFile.py", line 76, in get
value = self.config.get(section, property)
File "/usr/lib64/python2.6/ConfigParser.py", line 540, in get
raise NoOptionError(option, section)
ConfigParser.NoOptionError: No option 'olddriver' in section: 'Configuration'


thanks for the reply in advance