F17 Nvidia guide

Originally Posted by captainralf

Hi everyone,

first of all, thanks for re-posting this brilliant guide!
I followed it to the letter and have had some success...

I'm sitting looking at my laptop's screen at a very unhealthy angle, as I generally use an external monitor at home. When I open the gnome(3) display info, the monitor is detected as unknown and the external is not there and stops working when the login screen pops up. Everything is considerable slower as well with long lag times even though there are no CPU spikes. I tried editing the xorg.conf but then the boot sequence didn't finish - no error, it just stopped and for the next login the file was like below.

I'd really appreciate your advice on this... please let me know if you need any additional information..
I use Fedora 17 latest updates and used akmod to install the nvidia drivers for my FX1600M.

Thanks!


here the recommended output:

abrt-addon-kerneloops-2.0.16-1.fc17.i686
akmod-nvidia-173xx-173.14.35-2.fc17.i686
kernel-headers-3.6.2-4.fc17.i686
kernel-PAE-3.3.4-5.fc17.i686
kernel-PAE-3.6.2-4.fc17.i686
kernel-PAE-devel-3.6.2-4.fc17.i686
kmod-nvidia-173xx-3.6.2-4.fc17.i686.PAE-173.14.35-2.fc17.4.i686
libreport-plugin-kerneloops-2.0.16-1.fc17.i686
nvidia-settings-1.0-21.fc17.i686
nvidia-xconfig-1.0-19.fc17.i686
xorg-x11-drv-nvidia-173xx-173.14.35-1.fc17.i686
xorg-x11-drv-nvidia-173xx-libs-173.14.35-1.fc17.i686
3.6.2-4.fc17.i686.PAE
nvidia 7103834 36
i2c_core 28418 2 i2c_i801,nvidia
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 304.51 (mockbuild@) Thu Oct 11 11:40:37 CEST 2012


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

Section "Files"
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" "us"
Option "XkbModel" "pc105"
EndSection

Section "Monitor"
Identifier "LaptopInternal"
VendorName "SEC"
ModelName "Seiko"
HorizSync 54.8 - 54.8
VertRefresh 60.0 - 60.0
Option "DPMS"
EndSection

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection




EDIT: I just realized I used the output of the edited file - it didn't really do much, except that my external monitor's resolution was correct until the boot sequence halted at an arbitrary point(different steps completed). I had to reboot a second time every time to be able to login. The second login seemed to be some sort of default that did not recognize the screens resolution. so, i used the original file again, fixing the double boot problem...

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection

173xx and gnome3 = no go

Try XFCE or LXDE instead

[captainralf]

Originally Posted by Yellowman

173xx and gnome3 = no go

Try XFCE or LXDE instead

thanks for your quick reply!
I just installed lxde and it makes no difference. I created a new xorg.conf with nvidia-xconfig, but the monitor is still not recognized correctly, the external monitor stops getting a signal just before the login manager appears and the system is still very laggy.

I noticed when I start the nvidia x-server settings that I get an error in the 'X server display configuration':

Unable to load X Server Display Configuration page:

The NVIDIA X driver on cap.lap:0.0 is not new
enough to support the nvidia-settings Display Configuration page.

Hope you can help!

Originally Posted by captainralf

thanks for your quick reply!
I just installed lxde and it makes no difference. I created a new xorg.conf with nvidia-xconfig, but the monitor is still not recognized correctly, the external monitor stops getting a signal just before the login manager appears and the system is still very laggy.

I noticed when I start the nvidia x-server settings that I get an error in the 'X server display configuration':


Hope you can help!

nvidia-settings is broken for 96xx and 173xx (the 304xx nvidia-settings is not compatible).


post

cat /etc/X11/xorg.conf

[captainralf]

gee.. what's not broken with the nvidia stuff

xorg.conf:

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 304.51 (mockbuild@) Thu Oct 11 11:40:37 CEST 2012

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

Section "Files"
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" "us"
Option "XkbModel" "pc105"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection

Originally Posted by captainralf

gee.. what's not broken with the nvidia stuff

xorg.conf:

Change it to

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 304.51 (mockbuild@) Thu Oct 11 11:40:37 CEST 2012

Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection

Section "Device"
Identifier "Device0"
Driver "nvidia"
Option      "AddARGBGLXVisuals" "true"
VendorName "NVIDIA Corporation"
EndSection

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

restart X

[captainralf]

did that, but unfortunately didn't help...
As using my browser was so slow, I only tried rhythmbox which was painfully slow as well.
On the other hand, video playback is fine.

Also, my external monitor is not recognized at all.
here the xrand output:

xrandr: Failed to get size of gamma for output default
Screen 0: minimum 320 x 240, current 1440 x 900, maximum 1440 x 900
default connected 1440x900+0+0 0mm x 0mm
1440x900 50.0*
1024x768 51.0
800x600 52.0 53.0
700x525 54.0
640x512 55.0
640x480 56.0 57.0
512x384 58.0
400x300 59.0
320x240 60.0

this is the internal monitor - resolution is correct...

---------- Post added at 11:08 AM ---------- Previous post was at 10:05 AM ----------

The problem with the external monitor was solved by adding:

Option "Twinview" "Yes"

to the screen section.

The lag still persists. I am just writing this from gnome, it's not faster or slower in comparison with lxde...

Hope you have more good ideas!

I noticed that tooltips don't work at all and for example i can't use the tag options on the forum or add smileys... weird... It just takes veeery long.

[thomthom]

I'm trying to install 310.19 in telint 3 but I can't figure out how to stop xserver. I issue systemctl stop gdm.service but get this error: "Failed to issue method call: Unit gdm.service not loaded.

I figured it out, never mind.

[tux4me]

I had to put these sections back into xorg.conf, after recent update

Section "Files"
ModulePath "/usr/lib/nvidia/xorg"
ModulePath "/usr/lib/xorg/modules"
EndSection

[shreedhan]

I am trying to install nvidia driver in Fedora 17, but after I followed the post #1, I cannot get X server started anymore.
Here are the various outputs as required in post #1.

abrt-addon-kerneloops-2.0.16-1.fc17.i686
kernel-devel-3.6.2-4.fc17.i686
kernel-devel-3.6.7-4.fc17.i686
kernel-headers-3.6.7-4.fc17.i686
kernel-PAE-3.5.3-1.fc17.i686
kernel-PAE-3.6.2-4.fc17.i686
kernel-PAE-3.6.7-4.fc17.i686
kernel-PAE-devel-3.5.3-1.fc17.i686
kernel-PAE-devel-3.6.2-4.fc17.i686
kernel-PAE-devel-3.6.7-4.fc17.i686
kernel-PAE-modules-extra-3.5.3-1.fc17.i686
kernel-PAE-modules-extra-3.6.7-4.fc17.i686
libreport-plugin-kerneloops-2.0.13-2.fc17.i686

3.6.7-4.fc17.i686.PAE

nvidia              10257971  0 
i2c_core               28418  7 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,nvidia,videodev
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 304.37  (mockbuild@)  Tue Aug 14 06:34:11 CEST 2012

# RPM Fusion - nvidia-xorg.conf
# 

Section "ServerLayout"
    Identifier     "Default Layout"
    Screen         "Default Screen" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "InputDevice"

    # generated from data in "/etc/sysconfig/keyboard"
    Identifier     "Keyboard0"
    Driver         "keyboard"
    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

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Videocard0"
    Driver         "nvidia"
EndSection

Section "Screen"
    Identifier     "Default Screen"
    Device         "Videocard0"
    Monitor        "Monitor0"
    SubSection     "Display"
        Modes      "nvidia-auto-select"
    EndSubSection
EndSection

[jonnycat]

Does anyone know when/if the 310.19 (64 bit) drivers will be available through RPMFusion repos? My card (8800GT) is compatible with the newer drivers, but I'm still stuck at 304.64 drivers.

Thanks!

[madopal]

Are we going to start a F18 thread? Repo with akmod-nvidia & 3.7.2 kernel appears to be having the problem shown in the archived thread on F18 & 3.7 kernel. I'd *like* to roll back to a 3.6 kernel, but not sure that I can in F18.

[Mr Wolf]

Originally Posted by madopal

Repo with akmod-nvidia & 3.7.2 kernel appears to be having the problem shown in the archived thread on F18 & 3.7 kernel.

Do you mean this thread? If so, for me everything works fine with akmod-nvidia and kernels from release 3.7.1-5 onwards.
(To be honest, I also had to make a small change to xorg.conf; but, if such file doesn't exist on your system, you shouldn't need to do this change).

[madopal]

Originally Posted by Mr Wolf

Do you mean this thread? If so, for me everything works fine with akmod-nvidia and kernels from release 3.7.1-5 onwards.
(To be honest, I also had to make a small change to xorg.conf; but, if such file doesn't exist on your system, you shouldn't need to do this change).

Yeah, that's the thread. I'm having the exact same problem. I've dropped to the console, and it seems the module won't work, even with modprobe. If I switch back to nouveau, all is good. I was assuming it was just a kernel/kmod issue. I even manually triggered akmods to make sure it actually built after upgrade but, no dice.

Weird thing is, I have another box at work running nvidia, and I just came in this morning to find it's just fine after upgrading last night. I'll have to figure out if it's the card or what.

[BenTrein]

This is a Four-Step Process. If you don't follow all three steps, your install will fail!

Has anyone pointed out the discrepancy in one of the most clearly seen lines of text in the opening post? If I fail the fourth step, everything will still be fine?

[DBelton]

Well, the fourth step is a reboot so that the changes in the other steps take effect. Failing to reboot won't cause the install to fail, you just won't get the nviidia drivers loaded until you do so.

So failing to follow steps 1-3 will cause the install to fail, failing to do the fourth just means you can't use it until you do so.