<---- template headericclude ----->
F18-F20: Nvidia guide - Page 9
FedoraForum.org - Fedora Support Forums and Community
Page 9 of 25 FirstFirst ... 789101119 ... LastLast
Results 121 to 135 of 365
  1. #121
    Join Date
    May 2004
    Location
    Mexico City, Mexico
    Age
    46
    Posts
    4,428
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F17 Nvidia guide

    Is there word from the guys over @RPMFusion as to when can we expect the 310.3x driver series? Apparently they correct a number of issues with Steam and other gaemes... I know how to install them manually, only I'd rather do it through yum.
    If ain't broken, don't fix it! :eek:
    If can be improved, go for it! :cool:

    FedoraForum Community forums lurker.
    Fedora user since RHL 5.2 :cool:

  2. #122
    Join Date
    Jun 2007
    Posts
    61
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F17 Nvidia guide

    After updating my f17 system X won't start complaining about nvidia as a missing module:

    [ 31.349] (II) Loading extension DRI2
    [ 31.349] (II) LoadModule: "nvidia"
    [ 31.350] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so
    [ 31.351] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 31.351] compiled for 4.0.2, module version = 1.0.0
    [ 31.351] Module class: X.Org Video Driver
    [ 31.357] (EE) NVIDIA: Failed to load the NVIDIA kernel module. Please check your
    [ 31.357] (EE) NVIDIA: system's kernel log for additional error messages.
    [ 31.357] (II) UnloadModule: "nvidia"
    [ 31.357] (II) Unloading nvidia
    [ 31.357] (EE) Failed to load module "nvidia" (module-specific error, 0)
    [ 31.357] (EE) No drivers available.
    [ 31.357]
    Fatal server error:
    [ 31.357] no screens found
    [ 31.357]
    Please consult the Fedora Project support
    at http://wiki.x.org
    for help.
    [ 31.357] Please also check the log file at "/var/log/Xorg.1.log" for additional information.
    [ 31.358]
    Everything works ok when running the previous kernel. Amy ideas or suggestions to get the new kernel/driver combination working?

    [dan@laminimachine ~]$ rpm -qa *\nvidia\* *\kernel\*|sort;uname -r;lsmod |grep -e nvidia -e nouveau;cat /etc/X11/xorg.conf
    akmod-nvidia-304.64-2.fc17.5.x86_64
    kernel-3.6.11-1.fc17.x86_64
    kernel-3.6.11-5.fc17.x86_64
    kernel-3.7.3-101.fc17.x86_64
    kernel-devel-3.6.11-1.fc17.x86_64
    kernel-devel-3.6.11-5.fc17.x86_64
    kernel-devel-3.7.3-101.fc17.x86_64
    kernel-headers-3.7.3-101.fc17.x86_64
    kmod-nvidia-3.6.11-1.fc17.x86_64-304.64-1.fc17.6.x86_64
    kmod-nvidia-3.6.11-5.fc17.x86_64-304.64-2.fc17.5.x86_64
    kmod-nvidia-3.7.3-101.fc17.x86_64-304.64-2.fc17.5.x86_64
    nvidia-settings-1.0-22.fc17.x86_64
    nvidia-xconfig-1.0-20.fc17.x86_64
    xorg-x11-drv-nvidia-304.64-3.fc17.x86_64
    xorg-x11-drv-nvidia-libs-304.64-3.fc17.i686
    xorg-x11-drv-nvidia-libs-304.64-3.fc17.x86_64
    3.6.11-5.fc17.x86_64
    nvidia 11283758 40
    i2c_core 38354 3 i2c_i801,nvidia,videodev
    # nvidia-settings: X configuration file generated by nvidia-settings
    # nvidia-settings: version 304.60 (mockbuild@) Thu Oct 25 17:56:54 CEST 2012

    Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "Screen0" 0 0
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "Mouse0" "CorePointer"
    Option "Xinerama" "0"
    Option "StandbyTime" "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 "keyboard"
    Option "XkbLayout" "gb"
    Option "XkbModel" "pc105"
    EndSection

    Section "Monitor"
    # HorizSync source: edid, VertRefresh source: edid
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "Samsung SyncMaster"
    HorizSync 30.0 - 81.0
    VertRefresh 50.0 - 60.0
    Option "DPMS"
    EndSection

    Section "Device"
    Identifier "Device0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "ION"
    # Force Powermizer to a certain level at all times
    # level 0x1=highest
    # level 0x2=med
    # level 0x3=lowest
    # AC settings:
    Option "RegistryDwords" "PowerMizerLevelAC=0x3"
    # Battery settings:
    Option "RegistryDwords" "PowerMizerLevel=0x3"
    EndSection

    Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    Option "Stereo" "0"
    Option "metamodes" "nvidia-auto-select +0+0"
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection
    [dan@laminimachine ~]$ lspci | grep VGA
    02:00.0 VGA compatible controller: nVidia Corporation GT218 [ION] (rev a2)
    [dan@laminimachine ~]$

  3. #123
    Join Date
    Dec 2006
    Posts
    154
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    F18 Nvidia guide help

    I've read through all that I could find, but I'm not certain of my understanding.

    I have an ASUS x93S notebook with an nVidia GeForce GT 540M.
    I installed kmod-nvidia, and now fail to get a Gnome log-in screen on Fedora 18 standard install. The boot process seems normal, I see the animated Fedora 'balloon' fill up, it changes to the Fedora symbol, then drops out to a text based screen with the boot log shown.

    Can someone please indicate where I have gone wrong, and how to correct it.

    Many thanks.

  4. #124
    Join Date
    May 2004
    Location
    Mexico City, Mexico
    Age
    46
    Posts
    4,428
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    The fact that you are seeingthe fedora logo fill up, means that the nouveau driver is not being successfully black listed, and thus what you get is a driver conflict. Check that nouveau is indeed disabled in the initrd and kernel lines in the GRUB2 configuration (/etc/grub2.cfg). For me this was done automatically after the installation of the kmod-nvidia package, I later installed akmod.

    Enviado desde mi GT-I9100 usando Tapatalk 2
    If ain't broken, don't fix it! :eek:
    If can be improved, go for it! :cool:

    FedoraForum Community forums lurker.
    Fedora user since RHL 5.2 :cool:

  5. #125
    Join Date
    Mar 2011
    Location
    /
    Posts
    5,242
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F18 Nvidia guide help

    Quote Originally Posted by Thetargos
    Is there word from the guys over @RPMFusion as to when can we expect the 310.3x driver series? Apparently they correct a number of issues with Steam and other gaemes... I know how to install them manually, only I'd rather do it through yum.
    I see the 313.xx driver in rpmfusion rawhide repo. Nothing in the 31x.xx series for F18 though. I was also checking this out because I wanted to launch counter strike.

    Quote Originally Posted by Smit-Tay
    I've read through all that I could find, but I'm not certain of my understanding.

    I have an ASUS x93S notebook with an nVidia GeForce GT 540M.
    I installed kmod-nvidia, and now fail to get a Gnome log-in screen on Fedora 18 standard install. The boot process seems normal, I see the animated Fedora 'balloon' fill up, it changes to the Fedora symbol, then drops out to a text based screen with the boot log shown.

    Can someone please indicate where I have gone wrong, and how to correct it.

    Many thanks.
    Did you already blacklist nouveau? If you are seeing the bubble it probably means nouveau is still handling the graphics card.

    You can try to blacklist either by adding nouveau to blacklist.conf in /etc/modprobe.d or by adding a blacklist.conf file to /etc/dracut.d. ..

  6. #126
    Join Date
    Dec 2006
    Posts
    154
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F17 Nvidia guide

    I've added the nouveau driver to the blacklist in /etc/modprobe.d and also ran dracut with "--omit-drivers kmod-nouveau".

    I have the exact same behavior as before.

    Any suggestions ?

  7. #127
    Join Date
    Jun 2007
    Location
    Aubagne France
    Age
    69
    Posts
    675
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F17 Nvidia guide

    Quote Originally Posted by Smit-Tay
    I've added the nouveau driver to the blacklist in /etc/modprobe.d and also ran dracut with "--omit-drivers kmod-nouveau".

    I have the exact same behavior as before.

    Any suggestions ?
    dracut with "--omit-drivers kmod-nouveau

    kmod-nouveau does not exist....

  8. #128
    Join Date
    Mar 2011
    Location
    /
    Posts
    5,242
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F17 Nvidia guide

    This is what I had.

    Code:
    $ cat /etc/dracut.conf.d/10-blacklist.conf 
    omit_drivers+=" nouveau "
    I don't think if kmod-nouveau exists. See if the above helps.

  9. #129
    Join Date
    Apr 2010
    Posts
    100
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Exclamation Re: F17 Nvidia guide

    Has anyone managed to get the graphical Plymouth boot back after installing the Nvidia proprietary driver?
    I followed this guide.
    The result? I got the graphical boot back, but the GDM login screen didn't appear and only the mouse cursor on a black background was displayed...

    Kernel: 3.7.9-201.fc18.x86_64
    Nvidia akmod: akmod-nvidia-1:304.64-6.fc18
    Operating system: Fedora 20 "Heisenbug" x86_64
    Desktop environment: Gnome

  10. #130
    Join Date
    Nov 2011
    Location
    Baton Rouge, Louisiana, US
    Posts
    16
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F17 Nvidia guide

    Code:
    warning: /var/cache/yum/x86_64/18/rpmfusion-nonfree-updates/packages/xorg-x11-drv-nvidia-libs-304.64-5.fc18.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID e31b30ca: NOKEY
    Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-18-x86_64
    
    
    GPG key retrieval failed: [Errno 14] Could not open/read file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-18-x86_64
    Edit:Workaround:

    Code:
    # yum --nogpgcheck install akmod-nvidia xorg-x11-drv-nvidia-libs
    Last edited by benbullard79; 28th February 2013 at 03:33 AM. Reason: To post work around.
    Thanks,
    Ben Bullard

  11. #131
    Join Date
    Feb 2013
    Location
    On the Moon
    Posts
    86
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F17 Nvidia guide

    Quote Originally Posted by Thetargos
    Is there word from the guys over @RPMFusion as to when can we expect the 310.3x driver series? Apparently they correct a number of issues with Steam and other gaemes... I know how to install them manually, only I'd rather do it through yum.
    RPMFusion-Rawhide has an akmod for nvidia: 313.18-2.fc19. (Hell, nvidia's website only lists 310.32 as the latest for Linux) I am running kernel 3.7.9-205, and it ran on prior kernels, 3.7.9-201 & 3.7.8-202. Can't speak for earlier kernels as I was using nvidia's 310.32 from the geforce.com site and recompiling every time I upgraded kernels. What a pain. The 313 akmod has so far recompiled on the fly after a kernel upgrade, what a relief. Highly recommended!!!

    Hope this helps.

  12. #132
    Join Date
    Jan 2007
    Posts
    80
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F17 Nvidia guide

    I installed fedora 18 yesterday, I followed this thread, the resolution was right, but I got a problem.
    When I play a movie with mplayer, it told me my system is too slow.
    I run glxgears, this is the result:
    $ glxgears
    Running synchronized to the vertical refresh. The framerate should be
    approximately the same as the monitor refresh rate.
    301 frames in 5.0 seconds = 60.120 FPS
    300 frames in 5.0 seconds = 59.999 FPS
    301 frames in 5.0 seconds = 60.003 FPS
    It is only 60 fps! I remember very well that it was 18000 fps when I run in fedora 17.

    $ rpm -qa *\nvidia\* *\kernel\*|sort;uname -r;lsmod |grep -e nvidia -e nouveau;cat /etc/X11/xorg.conf
    abrt-addon-kerneloops-2.0.20-1.fc18.x86_64
    akmod-nvidia-304.64-7.fc18.x86_64
    kernel-3.6.10-4.fc18.x86_64
    kernel-3.8.2-206.fc18.x86_64
    kernel-3.8.3-201.fc18.x86_64
    kernel-devel-3.8.2-206.fc18.x86_64
    kernel-devel-3.8.3-201.fc18.x86_64
    kernel-headers-3.8.3-201.fc18.x86_64
    kernel-modules-extra-3.6.10-4.fc18.x86_64
    kernel-modules-extra-3.8.2-206.fc18.x86_64
    kernel-modules-extra-3.8.3-201.fc18.x86_64
    kmod-nvidia-3.8.2-206.fc18.x86_64-304.64-7.fc18.1.x86_64
    kmod-nvidia-3.8.3-201.fc18.x86_64-304.64-7.fc18.x86_64
    libreport-plugin-kerneloops-2.0.20-1.fc18.x86_64
    nvidia-settings-1.0-26.fc18.x86_64
    nvidia-xconfig-1.0-25.fc18.x86_64
    xorg-x11-drv-nvidia-304.64-5.fc18.x86_64
    xorg-x11-drv-nvidia-libs-304.64-5.fc18.x86_64
    3.8.3-201.fc18.x86_64
    nvidia 11283757 84
    i2c_core 38353 2 i2c_i801,nvidia
    # nvidia-xconfig: X configuration file generated by nvidia-xconfig
    # nvidia-xconfig: version 304.60 (mockbuild@) Fri Oct 19 02:28:58 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

    lspci |grep VGA
    01:00.0 VGA compatible controller: NVIDIA Corporation G92 [GeForce 9800 GT] (rev a2)

  13. #133
    Join Date
    Jun 2007
    Location
    Aubagne France
    Age
    69
    Posts
    675
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F17 Nvidia guide

    Quote Originally Posted by ildg
    I installed fedora 18 yesterday, I followed this thread, the resolution was right, but I got a problem.
    When I play a movie with mplayer, it told me my system is too slow.
    I run glxgears, this is the result:


    It is only 60 fps! I remember very well that it was 18000 fps when I run in fedora 17.
    I have same issue with nvidia card GeForce GT 525M on my Toshiba laptop.
    Code:
    [dominique@chepioq ~]$ glxgears
    Running synchronized to the vertical refresh.  The framerate should be
    approximately the same as the monitor refresh rate.
    297 frames in 5.0 seconds = 59.264 FPS
    297 frames in 5.0 seconds = 59.225 FPS
    299 frames in 5.0 seconds = 59.628 FPS
    300 frames in 5.0 seconds = 59.828 FPS
    300 frames in 5.0 seconds = 59.828 FPS
    300 frames in 5.0 seconds = 59.829 FPS
    300 frames in 5.0 seconds = 59.824 FPS
    ^C
    [dominique@chepioq ~]$
    I don't use MPlayer but VLC, and no problem with movies.

    But I remember with F17, glxgears show me a FPS more bigger...

  14. #134
    Join Date
    Jan 2007
    Posts
    80
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F17 Nvidia guide

    Quote Originally Posted by chepioq
    I have same issue with nvidia card GeForce GT 525M on my Toshiba laptop.
    Code:
    [dominique@chepioq ~]$ glxgears
    Running synchronized to the vertical refresh.  The framerate should be
    approximately the same as the monitor refresh rate.
    297 frames in 5.0 seconds = 59.264 FPS
    297 frames in 5.0 seconds = 59.225 FPS
    299 frames in 5.0 seconds = 59.628 FPS
    300 frames in 5.0 seconds = 59.828 FPS
    300 frames in 5.0 seconds = 59.828 FPS
    300 frames in 5.0 seconds = 59.829 FPS
    300 frames in 5.0 seconds = 59.824 FPS
    ^C
    [dominique@chepioq ~]$
    I don't use MPlayer but VLC, and no problem with movies.

    But I remember with F17, glxgears show me a FPS more bigger...
    what about 1080p movies? Can you try one and tell me?
    I have no problem with playing most of my movies, but when I play a 3d sbs movie, the problem occurs.

  15. #135
    Join Date
    Jun 2007
    Location
    Aubagne France
    Age
    69
    Posts
    675
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F17 Nvidia guide

    I have no 1080p video for test, but I download that for test : http://www.demo-world.eu/trailers/re...ox_blu_ray.jpg
    and with vlc no problem, no lag..

Page 9 of 25 FirstFirst ... 789101119 ... LastLast

Similar Threads

  1. Installing Nvidia Drivers In F20 Questions
    By terry_g in forum Hardware
    Replies: 3
    Last Post: 31st December 2013, 08:14 PM
  2. [SOLVED]
    F20 Beta to F20 Final yum update - core groups not found
    By blueflame in forum Installation, Upgrades and Live Media
    Replies: 6
    Last Post: 20th December 2013, 03:47 AM
  3. hints needed F18>F20 upgrade
    By PatMcLJr in forum Installation, Upgrades and Live Media
    Replies: 5
    Last Post: 19th December 2013, 07:31 PM
  4. F20 Nvidia no screen detected
    By b4time in forum F-20 Development Forum
    Replies: 2
    Last Post: 11th November 2013, 05:47 AM
  5. F20 Beta TC5: Problem with F17 NVIDIA Guide
    By taytong888 in forum F-20 Development Forum
    Replies: 1
    Last Post: 24th October 2013, 06:11 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
[[template footer(Guest)]]