Re: F16,F15 & F14 Nvidia driver guides
 

Thanks. That's much appreciated.

F16 - 3.1.x kernel + nvidia
 

Hi Leigh, and everyone.

I need to get a 3.1.x kernel to work, since my Blackmagic Intensity Pro does not support kernels above yet.

Can someone give me any advice on how to do so?

If I boot my 3.1.0-7 kernel, the nvidia drivers don't run, .. probably because I have 290.10 nvidia driver?

However, I can not hunt down the right combination of packages - kernels and nvidia drivers.
Yum is failing in dependency resolution. I had official nvidia drivers installed, but that didn't work well. (100% CPU usage on one core, and freezing). I also attempted to build a custom kernel, but still no go.

Any advice appreciated.

Re: F16 - 3.1.x kernel + nvidia
 

Use akmod-nvidia

Re: F16,F15 & F14 Nvidia driver guides
 

Thank you, that worked.

Re: F16,F15 & F14 Nvidia driver guides
 

Hi, another computer, another problem.

I have (eventually) upgraded to F16 using preupgrade. I *think* I'm using the nvidia driver for my GeForce 8600 GT (is there some way of checking?), but the resolution for my monitor isn't being detected. I've had the same issue previously (for some reason this monitor doesn't readily get detected), and usually have sorted it by adding things to xorg.conf such as the following:

Section "Monitor"
Identifier "Configured Monitor"
HorizSync 48.36-49.702
VertRefresh 59.81-60.00
Modeline "1280x768_60.00" 79.50 1280 1344 1472 1664 768 771 781 798 -hsync +vsync
Option "PreferredMode" "1280x768_60.00"
EndSection

Section "Screen"
Identifier "Screen0"
Monitor "Configured Monitor"
Device "nVidia Corporation G84 [GeForce 8600 GT]"
DefaultDepth 24
Option "AddARGBGLXVisuals" "True"
SubSection "Display"
Depth 24
Modes "1280x960" "1280x800" "1280x768" "10072x800" "1024x768" "800x600"
EndSubSection
EndSection

Section "Device"
Identifier "nVidia Corporation G84 [GeForce 8600 GT]"
BusID "PCI:01:00:0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection

When I've done this, it seems that when the xserver attempts to restart (e.g. by logging out), I get a black screen with a flashing cursor in the top left - i.e. X never quite starts, and I never get to the graphical logon screen.


But I'm getting the impression that this kind of thing shouldn't really be done via xorg.conf any more, and I'm wondering what the correct way to do this is.

Cheers in advance for all assistance (this forum has saved my bacon on many an occasion). Much appreciated.

Re: F16,F15 & F14 Nvidia driver guides
 

hi

I have been using akmod-nvidia for long time now without problems but for past few weeks I am getting problems e.g
glxinfo
name of display: :0
X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 137 (NV-GLX)
Minor opcode of failed request: 4 ()
Resource id in failed request: 0x4000003
Serial number of failed request: 34
Current serial number in output stream: 34
[leonc16@localhost ~]$ sudo glxinfo
name of display: :0
X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 137 (NV-GLX)
Minor opcode of failed request: 4 ()
Resource id in failed request: 0x4000003
Serial number of failed request: 34
Current serial number in output stream: 34


I have kernel 3.3.0-8.fc16.x86_64 and I think my graphics card is geforce GTS 450.

Any idea?

Re: F16,F15 & F14 Nvidia driver guides
 

have you updated to the latest 295.33 akmod

Re: F16,F15 & F14 Nvidia driver guides
 

I have rpm -q akmod-nvidia
akmod-nvidia-295.33-2.fc16.x86_64

Re: F16,F15 & F14 Nvidia driver guides
 

I have a problem with the nvidia driver, glx support. This was working prior to my holidays, on my return I updated a few modules via the "yum update", performed from a working Cinnamon shell. The driver for this is that my GNOME Cinnamon shell broke, and this, with advice, pointed to my nvidia driver.

The problem was found on the nvidia-290.10 driver

On checking a short while ago, the nvidia-295.33 driver became available, and I though that this would have solved my issues, but afraid not. The kernel was also upgraded is now: 3.3.0.8

After a reboot:

The Persistant Issue:-
[PASTE]
[root@naipaulpc ~]# glxinfo
name of display: :0.0
X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 137 (NV-GLX)
Minor opcode of failed request: 4 ()
Resource id in failed request: 0x5000003
Serial number of failed request: 33
Current serial number in output stream: 33
[PASTE]

The basic environment info:
[PASTE]
[root@naipaulpc ~]# rpm -qa *\nvidia\* *\kernel\*|sort;uname -r;lsmod |grep -e nvidia -e nouveau;cat /etc/X11/xorg.conf

abrt-addon-kerneloops-2.0.7-2.fc16.x86_64
akmod-nvidia-295.33-2.fc16.x86_64
kernel-3.2.9-2.fc16.x86_64
kernel-3.3.0-4.fc16.x86_64
kernel-3.3.0-8.fc16.x86_64
kernel-devel-3.2.9-2.fc16.x86_64
kernel-devel-3.3.0-4.fc16.x86_64
kernel-devel-3.3.0-8.fc16.x86_64
kernel-headers-3.3.0-8.fc16.x86_64
kernel-tools-3.3.0-8.fc16.x86_64
kmod-nvidia-3.2.9-2.fc16.x86_64-290.10-1.fc16.18.x86_64
kmod-nvidia-3.3.0-4.fc16.x86_64-295.33-2.fc16.x86_64
kmod-nvidia-3.3.0-8.fc16.x86_64-295.33-2.fc16.1.x86_64
libreport-plugin-kerneloops-2.0.8-4.fc16.x86_64
nvidia-settings-1.0-15.fc16.x86_64
nvidia-xconfig-1.0-13.fc16.x86_64
xorg-x11-drv-nvidia-295.33-3.fc16.x86_64
xorg-x11-drv-nvidia-libs-295.33-3.fc16.x86_64
3.3.0-8.fc16.x86_64
nvidia 12281762 26
i2c_core 37991 3 nvidia,videodev,i2c_i801
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 295.33 (mockbuild@builder1.ovh.rpmfusion.lan) Sun Mar 25 14:14:04 CEST 2012

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 290.10 (mockbuild@) Wed Nov 23 22:25:15 CET 2011

Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection

Section "Files"
FontPath "/usr/share/fonts/default/Type1"
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

Section "InputDevice"

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

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "LEN L2251x Wide"
HorizSync 30.0 - 83.0
VertRefresh 50.0 - 75.0
Option "DPMS"
EndSection

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "Quadro FX 880M"
EndSection

Section "Screen"

# Removed Option "metamodes" "DFP-0: nvidia-auto-select @1600x1080 +0+0, CRT: nvidia-auto-select +1600+0"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "1"
Option "TwinViewXineramaInfoOrder" "DFP-0"
Option "metamodes" "CRT: nvidia-auto-select +1600+0, DFP-0: nvidia-auto-select @1600x1080 +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection

[PASTE]

The current xorg.conf was created today with the nvivia-xconfig utility.

---------- Post added at 03:40 PM ---------- Previous post was at 03:18 PM ----------

I have followed Leigh's advice and replaced the xorg.conf not with the newly created nvidia-xconfig but with a copy of the /etc/X11/nvidia-xorg.conf

After a reboot, I no longer have the glxinfo issue.

Thanks very much Leigh for the additional instructions.
- Happy Bunny once more ....:dance:

Re: F16,F15 & F14 Nvidia driver guides
 

Followed TrickyHarry's advise and added couple of things from 1st page to xorg.conf and now seems to work. Can now get back to World of Goo.

glxinfo
name of display: :0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
server glx extensions:

Strange because I did not touch xorg.conf lately.

Thanks

Re: F16,F15 & F14 Nvidia driver guides
 

Hi,

I guess I tried trick described in this thread, but there's no way I can get my F16 to work with my Nvidia card. Even worse, I can't even het into runlevel 3 (has this changed?). After the starting-bars I get a cursor flashing in the left upper corner of the main screen. So I am constantly logging into my system using another computer and making an ssh connection.

I had no problems whatsoever when running F14. The only reason why I upgraded was because of that nagging screen telling me to do so. I didn't get a screen after the upgrade, so apparently the nouveau drivers weren't even working. So I tried to install the kmod and akmod drivers, according to this thread. Eventually I had a semi-working config. But it missed certain options (like a shutdown button), so I tried again.

I fear I ****ed up big time, when "yum erasing" something, cos it erased a whole bunch of atuff (some 157 files) because of dependencies. And I guess I erased some important stuff with it.

Anyway, here is standard info of my current setup.

Re: F16,F15 & F14 Nvidia driver guides
 

Gnome 3 has a hidden shutdown menu, try reinstalling it


http://live.gnome.org/GnomeShell/CheatSheet#The_top_bar

Re: F16,F15 & F14 Nvidia driver guides
 

Thanks a huge lot man! This made my easter.
Still a lot to do as only one screen is working. But I'll get there...

A lot of these files, that got deleted, were re-installed, and when I rebooted I saw the dreaded cursor blinking again. But when I just finished sighing, Gnome emerged :)

Re: F16,F15 & F14 Nvidia driver guides
 

I'm using kernel 3.3.1-3.fc17.i686
After using Fedora for about two weeks, I found that this was the best way to install the NVIDIA driver. I guess I was lucky that this kernel wasn't a debug one (or is it?; I missed this point) because it kind of worked.

I ran the instructions for F16 (first post) for akmod-nvidia, rebooted, got a progress bar then when it was to load X the bar flicked about four times and nothing.
Then I had an inspiration to run nvidia-xconfig, rebooted and X loaded.
The problem is that I don't have GLX.

First particularity is that a while ago, while testing if the sgfxi script would work in Fedora, this script created an xorg.conf file. While using nouveau this file actually didn't interfere (as nouveau doesn't use it, I think) but I'm mentioning it because I don't know if this interfered when I installed the NVIDIA package.

/etc/X11/nvidia-xorg.conf is very small:
(proper xorg.conf created by nvidia-xconfig has normal size)

/etc/X11/xorg.conf.d/00-nvidia.conf
I'm thinking if maybe the system is just having trouble with finding the alternate path for libglx because ever since I installed Fedora it always fails to find/auto-complete executables in /usr/local/bin for instance (it actually finds them but I have to open different shell sessions, sometimes more than once until it 'gets it').

Here's the general info:
Thank you.

---------- Post added at 10:06 PM ---------- Previous post was at 10:02 PM ----------

The error in Xorg0.log is:


---------- Post added at 11:47 PM ---------- Previous post was at 10:06 PM ----------

I see that xorg-X11-nvidia-libs installs the libs in /usr/lib/nvidia but it keeps the libs from mesa-libGL in /usr/lib/libGL.so.1*
Maybe it's this that's conflicting?
I'll rename the ones from mesa-libGL to test.

---------- Post added at 11:57 PM ---------- Previous post was at 11:47 PM ----------

Leigh, I renamed /usr/lib/xorg/modules/extensions/libglx.so and linked the one from nvidia to its place and also renamed /usr/lib/LibGL.so.1* and linked the one from nvidia to /usr/lib/LibGL.so.1 and now GLX is working.
I'll try it out but I suspect the latter is the one that was conflicting so if it's the case then xorg-X11-nvidia-libs should rename the mesa-libGL libs and then restore in case of un-installation.

Re: F16,F15 & F14 Nvidia driver guides
 

So basically an extra step is needed after the 1st page how-to:
The xorg-x11-drv-nvidia and xorg-x11-drv-nvidia-libs provide that their libs are found by the system but the ones from xorg-x11-server-Xorg (libglx.so) and mesa-libGL (libGL.so.1*) need to be renamed to get out of the way. This must be done every time those packages are updated, I suppose.

I don't know why I had to generate a new xorg.conf manually, though. I suppose it's because I already had one and X prefers xorg.conf to nvidia-xorg.conf (supposing it actually parses the latter).