F22 Nvidia Guide Link
FedoraForum.org - Fedora Support Forums and Community
Page 1 of 3 1 2 3 LastLast
Results 1 to 15 of 34
  1. #1
    Join Date
    Jul 2004
    Location
    Colton, NY; Junction of Heaven & Earth (also Routes 56 & 68).
    Age
    76
    Posts
    24,436
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    F22 Nvidia Guide Link

    Leigh's mentioned that this guide: http://rpmfusion.org/Howto/nVidia?hi...tegoryHowto%29 is a decent one for working with F22. Of course, F22's default is dnf, so consider that when it refers to yum. And, Leigh reports that there is NO Kmod support for F22. Kmod support for other versions will be slow due to lack of manpower.
    Linux & Beer - That TOTALLY Computes!
    Registered Linux User #362651


    Don't use any of my solutions on working computers or near small children.

  2. #2
    Join Date
    Oct 2008
    Location
    Bend, OR
    Posts
    18
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Question Re: F22 Nvidia Guide Link

    Thanks. I have been trying off and on since FC22 was released to get nvidia from rmpfusion installed. It worked very well indeed with FC2.

    Example output from Xorg.0.log

    [ 21.034] (II) Loading /usr/lib64/nvidia/xorg/libglx.so
    [ 21.076] (II) Module glx: vendor="NVIDIA Corporation"
    [ 21.076] compiled for 4.0.2, module version = 1.0.0
    [ 21.076] Module class: X.Org Server Extension
    [ 21.077] (II) NVIDIA GLX Module 346.72 Tue May 5 17:11:15 PDT 2015
    [ 21.077] (==) Matched nouveau as autoconfigured driver 0
    [ 21.077] (==) Matched nv as autoconfigured driver 1
    [ 21.077] (==) Matched modesetting as autoconfigured driver 2
    [ 21.077] (==) Matched fbdev as autoconfigured driver 3
    [ 21.077] (==) Matched vesa as autoconfigured driver 4
    [ 21.077] (==) Assigned the driver to the xf86ConfigLayout
    [ 21.077] (II) LoadModule: "nouveau"
    [ 21.079] (II) Loading /usr/lib64/xorg/modules/drivers/nouveau_drv.so
    [ 21.081] (II) Module nouveau: vendor="X.Org Foundation"
    [ 21.081] compiled for 1.17.1, module version = 1.0.11
    [ 21.081] Module class: X.Org Video Driver
    [ 21.081] ABI class: X.Org Video Driver, version 19.0
    [ 21.081] (II) LoadModule: "nv"
    [ 21.083] (WW) Warning, couldn't open module nv
    [ 21.083] (II) UnloadModule: "nv"
    [ 21.083] (II) Unloading nv
    [ 21.083] (EE) Failed to load module "nv" (module does not exist, 0)
    [ 21.083] (II) LoadModule: "modesetting"
    [ 21.083] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
    [ 21.084] (II) Module modesetting: vendor="X.Org Foundation"
    [ 21.084] compiled for 1.17.1, module version = 1.17.1

  3. #3
    Join Date
    Oct 2008
    Location
    Bend, OR
    Posts
    18
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Thumbs up Re: F22 Nvidia Guide Link

    I noted that there was a kernel update today so I tried the nvidia RPMs from rpmfusion and this time installation succeeded and I am able to use the Nvidia driver.

    In addition to the new kernel (kernel-4.0.5-300.fc22.x86_64), I followed the instructions to install these rpms on JR page at http://www.if-not-true-then-false.co...-nvidia-guide/ (keeping an eye on the rpmfusion how to also).

    I used this: sudo dnf install akmod-nvidia xorg-x11-drv-nvidia-devel (ie adding the devel package as this seemed to help others).

    And this was followed by JRs instructions at 2.5:
    ## Backup old initramfs nouveau image ##
    mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-nouveau.img

    ## Create new initramfs image ##
    dracut /boot/initramfs-$(uname -r).img $(uname -r)

    I rebooted. Verified nvidia module was running and then installed i686 support.
    sudo dnf install xorg-x11-drv-nvidia-libs.i686

    The above worked for me. Your milage may vary.

    brad

  4. #4
    Join Date
    Jul 2004
    Location
    Colton, NY; Junction of Heaven & Earth (also Routes 56 & 68).
    Age
    76
    Posts
    24,436
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F22 Nvidia Guide Link

    Thanks, Brad! That might help quite a few.
    Linux & Beer - That TOTALLY Computes!
    Registered Linux User #362651


    Don't use any of my solutions on working computers or near small children.

  5. #5
    Join Date
    Jun 2010
    Posts
    54
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    I now have a method for making step 3 persistent on F22. First let me mention two things that did not work, that have been suggested for previous versions of fedora.
    Code:
    #vi /etc/modprobe.d/blacklist.conf - append 'blacklist nouveau'
    #vi /etc/sysconfig/grub - append 'rd.driver.blacklist=nouveau' to end of 'GRUB_CMDLINE_LINUX=
    #grub2-mkconfig -o /boot/grub2/grub.cfg
    This method of blacklisting did not work, but is close to the final solution. Basically there are extra things that need to be added to GRUB_CMDLINE_LINUX. Amazingly the following code also does not work:
    Code:
    #yum remove xorg-x11-drv-nouveau.x86_64
    It seems that this does not remove nouveau from /lib/modules/..., and so in fact nouveau is still detected in the boot process.

    To discover what to put after GRUB_CMDLINE_LINUX=, I did step 3, rebooted, then ran
    Code:
    cat /proc/cmdline
    This told me that fromy configuration /etc/sysconfig/grub should have the following line:
    Code:
    GRUB_CMDLINE_LINUX="nomodeset rhgb quiet nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off"
    So basically there are three things to add to the line: nouveau.modeset=0, rd.driver.blacklist=nouveau, and video=vesa:off (the rest was already there). I then ran
    Code:
    #grub2-mkconfig -o /boot/grub2/grub.cfg
    And that does it. By the way, I am pretty sure that the blacklist.conf file does not help at all, but I admit I have not removed it from my system.

  6. #6
    Join Date
    Dec 2007
    Location
    Albuquerque, New Mexico USA
    Age
    69
    Posts
    161
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F22 Nvidia Guide Link

    The blacklist.conf modification works, but you have to use dracut to update the initramfs image to make it take effect.
    Hope is not a plan

  7. #7
    Join Date
    Jun 2010
    Posts
    54
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F22 Nvidia Guide Link

    brmorse is correct about dracut needing to be run afterwards to build a new initramfs image, however in my case dracut has been run several times since I created the file. I think this may do some explaining:
    http://http://forums.fedoraforum.org...te=1&p=1736316
    This seems to indicate that dracut only checks in /etc/modprobe.d when the host-only option is used. The standard folder for blacklisting is actually /usr/lib/modprobe.d. This link has been around since F18, and yet almost all explanations that can be found by google for blacklisting nouveau refer to /etc/modprobe.d without the host only option. why?

    Interestingly, there is already a file for blacklisting nouveau in /usr/lib/modprobe.d on my computer, yet it seems to be ignored. The file explains that if it is ignored, then dracut should be run with the -f option. I did this, but it was still ignored. Do they mean the -H option? I mean, if nouveau is really blacklisted it seems like xorg should not try loading nouveau at all, but the log still shows an attempt to load nouveau.

  8. #8
    Join Date
    Sep 2007
    Location
    London, England
    Posts
    109
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Thumbs up Re: F18-F20: Nvidia guide

    This seems to work for me on F22 64 bit.

    1. Clean install of Live via USB.
    2. Update system.
    3. Reboot.
    4. Setup RPM Fusion repos (free and nonfree).

    In a terminal install Nvidia as follows and includes 32 bit libs for e.g. steam:

    5. dnf install akmod-nvidia xorg-x11-drv-nvidia-libs.i686 kernel-devel dkms

    6. mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-nouveau.img

    7. dracut --omit-drivers nouveau /boot/initramfs-$(uname -r).img $(uname -r)

    You may need to change akmod-nvidia and libs selection depending upon the type of card in use, see http://rpmfusion.org/Howto/nVidia

    I will report back if there are any issues after next kernel update - hopefully not.
    Linux the root to no GPFs

  9. #9
    Join Date
    Oct 2006
    Location
    Melbourne
    Age
    50
    Posts
    594
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F22 Nvidia Guide Link

    You don't need to remove nouveau from the initramfs with fedora 22 as shown below:

    Code:
    mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-nouveau.img
    dracut --omit-drivers nouveau /boot/initramfs-$(uname -r).img $(uname -r)

    To install the driver nvidia driver from rpmfusion for the Newer GeForce VGA as described on the rpmfusion website open a terminal and copy and paste the following:

    First install the rpmfusion repository:
    Code:
    su
    dnf install --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm
    To install the driver nvidia driver

    Code:
    su
    dnf -y update && dnf -y install gcc kernel-devel kernel-headers 
    dnf install akmod-nvidia xorg-x11-drv-nvidia-libs.i686

    Reboot


    If your nvidia-kmod failed to build during the reboot copy and paste the following into a terminal with root privileges (use crtl+alt+f2 to gain access to a terminal if required) :

    [root@jonathon-i7 jonathon]#
    Code:
    akmods --force
    Checking kmods exist for 4.0.7-300.fc22.x86_64 [ OK ]
    Building and installing nvidia-kmod [ OK ]
    [root@jonathon-i7 jonathon]#

    Reboot and you should be good to go..)

    To remove the nvidia driver (if it failed to build or install) and move back to the nouveau driver instead of the vesa driver:

    Code:
    su
    dnf remove *\nvidia\*
    Reboot

    Thanks to CronoCloud http://forums.fedoraforum.org/showpo...6&postcount=81 for letting me know the fix.
    Last edited by jonathonp; 26th July 2015 at 11:16 AM.
    PC CPU 3.60 Gigahertz Intel Core i7-4790, Motherboard Gigabyte H97M-D3H, RAM: 32GB, Graphics: AMD: Fedora 32 MATE
    Asus Zenbook: Ubuntu 20.04, Lenovo Yoga: Fedora 32 MATE

  10. #10
    Join Date
    May 2006
    Location
    Germany
    Age
    40
    Posts
    31
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F22 Nvidia Guide Link

    So, why not put a warning on the RPMFusion page, that installing the Nvidia a-/kmod packages will require additional steps in order to work. As of now, installing this packages will 100% guaranteed leave you with a broken, unbootable system.

    I know the drill because the kmod-packages break my systems since 2010 or something, since nouveau came up, and I know the solution and fix is hidden somewhere deep inside the fedora forums. But I think about new Fedora users, who expect a quick and easy way to install the Nvidia drivers.

  11. #11
    Join Date
    Jul 2004
    Location
    Colton, NY; Junction of Heaven & Earth (also Routes 56 & 68).
    Age
    76
    Posts
    24,436
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F22 Nvidia Guide Link

    Eos, we don't control RPMFusion, FedoraProject, etc. and all we can do is to put a Guide that people should find if they come to this Forum. Not perfect, but until we rule the world, it's what's available.
    Linux & Beer - That TOTALLY Computes!
    Registered Linux User #362651


    Don't use any of my solutions on working computers or near small children.

  12. #12
    Join Date
    Aug 2011
    Location
    ~
    Posts
    2,087
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F22 Nvidia Guide Link

    Needed the proprietary driver last night to play some game (let's hope the new mesa with OpenGL 4 arrives soon and nouveau stability and performance improves).
    Where some time ago it was enough to use "dnf install akmod-nvidia xorg-x11-drv-nvidia-libs.i686" from RPMfusion, this time I was greeted with a kernel trace.
    Code:
    kernel: BUG: unable to handle kernel paging request at ffffffffa0a503a8
    kernel: IP: [<ffffffff81298280>] proc_get_inode+0xc0/0x170
    kernel: PGD 3c0e067 PUD 3c0f063 PMD 42267c067 PTE 0
    kernel: Oops: 0000 [#1] SMP 
    kernel: Modules linked in: xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun nf_conntrack_netbios_ns nf_conntrack_broadcast ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle vboxpci(OE) iptable_security vboxnetadp(OE) vboxnetflt(OE) iptable_raw vboxdrv(OE) it87 hwmon_vid snd_hda_codec_hdmi eeepc_wmi asus_wmi sparse_keymap rfkill vfat fat kvm_amd kvm snd_hda_codec_realtek fuse snd_hda_codec_generic crct10dif_pclmul crc32_pclmul ghash_clmulni_intel joydev snd_hda_intel snd_hda_controller snd_hda_codec
    kernel:  snd_hda_core snd_hwdep snd_seq edac_core fam15h_power snd_seq_device k10temp edac_mce_amd snd_pcm sp5100_tco i2c_piix4 snd_timer snd soundcore shpchp acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd grace sunrpc binfmt_misc hid_logitech_hidpp btrfs hid_logitech_dj xor nouveau video i2c_algo_bit raid6_pq drm_kms_helper crc32c_intel ttm serio_raw drm mxm_wmi r8169 mii wmi
    kernel: CPU: 0 PID: 1771 Comm: gnome-shell Tainted: P        W  OE   4.1.3-200.fc22.x86_64 #1
    kernel: Hardware name: To be filled by O.E.M. To be filled by O.E.M./M5A99X EVO, BIOS 1708 04/10/2013
    kernel: task: ffff88042c2b9da0 ti: ffff88041d054000 task.ti: ffff88041d054000
    kernel: RIP: 0010:[<ffffffff81298280>]  [<ffffffff81298280>] proc_get_inode+0xc0/0x170
    kernel: RSP: 0018:ffff88041d057bf8  EFLAGS: 00010246
    kernel: RAX: 0000000000008000 RBX: ffff880002fa3938 RCX: 0000000000000018
    kernel: RDX: ffffffffa0a50360 RSI: 0000000000000001 RDI: ffff880002fa3938
    kernel: RBP: ffff88041d057c08 R08: ffff88043ec1b3d0 R09: ffff88041c242460
    kernel: R10: 2f2f2f2f2f2f2f2f R11: 0000000000000000 R12: ffff880428b6b6c0
    kernel: R13: ffff880002fa36d8 R14: ffff88041d057df8 R15: 0000000000000000
    kernel: FS:  00007f81ab6f3a80(0000) GS:ffff88043ec00000(0000) knlGS:0000000000000000
    kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    kernel: CR2: ffffffffa0a503a8 CR3: 000000041c74f000 CR4: 00000000000407f0
    kernel: Stack:
    kernel:  ffff88041dca4600 ffff880428b6b300 ffff88041d057c38 ffffffff8129dc13
    kernel:  ffff88041d057eec ffff88041dca4600 0000000000008000 ffff88041d057d90
    kernel:  ffff88041d057c48 ffffffff8129dc9b ffff88041d057c78 ffffffff81234c3d
    kernel: Call Trace:
    kernel:  [<ffffffff8129dc13>] proc_lookup_de+0x53/0xc0
    kernel:  [<ffffffff8129dc9b>] proc_lookup+0x1b/0x20
    kernel:  [<ffffffff81234c3d>] lookup_real+0x1d/0x70
    kernel:  [<ffffffff8123a35c>] do_last+0xb5c/0x1330
    kernel:  [<ffffffff8123ba4f>] path_openat+0x8f/0x680
    kernel:  [<ffffffff8123d57e>] ? user_path_at_empty+0x6e/0xd0
    kernel:  [<ffffffff8123d699>] do_filp_open+0x49/0xd0
    kernel:  [<ffffffff813c266a>] ? find_next_zero_bit+0x1a/0x30
    kernel:  [<ffffffff8124a4ce>] ? __alloc_fd+0x7e/0x120
    kernel:  [<ffffffff81229ffa>] do_sys_open+0x13a/0x250
    kernel:  [<ffffffff8179da97>] ? schedule+0x37/0x90
    kernel:  [<ffffffff8122a12e>] SyS_open+0x1e/0x20
    kernel:  [<ffffffff817a1a6e>] system_call_fastpath+0x12/0x71
    kernel: Code: 00 48 89 43 20 49 8b 54 24 28 48 85 d2 74 14 0f b7 03 66 25 00 f0 66 3d 00 80 74 0f 48 89 93 48 01 00 00 48 89 d8 5b 41 5c 5d c3 <48> 83 7a 48 00 48 c7 c0 60 7a 82 81 48 c7 c2 80 79 82 81 48 0f 
    kernel: RIP  [<ffffffff81298280>] proc_get_inode+0xc0/0x170
    kernel:  RSP <ffff88041d057bf8>
    kernel: CR2: ffffffffa0a503a8
    kernel: ---[ end trace 0996b5ce35a8ba5a ]---
    I first thought this was related to running a fresh 4.1.3 kernel but after booting into emergency mode I saw that nouveau was still being loaded.
    Ran the command "dracut -f /boot/initramfs-$(uname -r).img $(uname -r)" as stated in /usr/lib/modprobe.d/blacklist-nouveau.conf and afterwards all was good.
    Next I noticed the monitors were reversed on GDM, so after logging in, configuring the screens and copying ~/.config/monitors.xml to /var/lib/gdm/.config/ all was fine.

  13. #13
    Join Date
    May 2006
    Location
    Germany
    Age
    40
    Posts
    31
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F22 Nvidia Guide Link

    Quote Originally Posted by bob
    Eos, we don't control RPMFusion, FedoraProject, etc. and all we can do is to put a Guide that people should find if they come to this Forum. Not perfect, but until we rule the world, it's what's available.
    I understand that, but I thought that maybe some of the package maintainers from RPMfusion show up here from time to time.

    Anyway I followed jonathonps instructions now, and it just worked. No blacklisting nouveau needed. That was a pleasent surprise. All I had to do manually was a "dnf update"

  14. #14
    Join Date
    Jun 2006
    Location
    New Orleans
    Posts
    25
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F22 Nvidia Guide Link

    I followed jonathonp's post and everything else that I could have thought of, but my F22 kernel 4.1.3 still does not have a working graphics. gdm starts successfully, but after login, the oops message still shows up, and I cannot get to usual screen. I have the same problem since the kernel 4.0.8 update.

    By the way, akmods --force returns that

    Code:
    Checking kmods exist for 4.1.3-201.fc22.x86_64             [  OK  ]
    I am still using kernel 4.0.7. I hope next kernel update will fix the problem.

  15. #15
    Join Date
    May 2006
    Location
    Germany
    Age
    40
    Posts
    31
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: F22 Nvidia Guide Link

    Strange, the akmod is still working flawlessly for me, now using the Kernel 4.1.3-201.fc22.x86_64.

    My installation steps were:

    Installed the rpmfusion-free and nonfree packages.

    Ran "dnf install akmod-nvidia" in a terminal window.

    The first reboot after this failed, and the Gnome oops-message showed up. I switched to a log-in screen with crtl+alt+fx, logged in as root, and tried akmods --force. This failed however, because there were some kernel-header packages missing or something. So I ran dnf update which acutally installed a couple of kernel related packages.

    After the next reboot the akmod just worked and I had no problems whatsoever since then.

Page 1 of 3 1 2 3 LastLast

Similar Threads

  1. F18-F20: Nvidia guide
    By Dan in forum Guides & Solutions (Not For Questions)
    Replies: 364
    Last Post: 30th November 2015, 09:30 AM
  2. Hostapd guide using D-Link DWA-525
    By amirhamzah in forum EOL (End Of Life) Versions
    Replies: 1
    Last Post: 5th May 2012, 10:35 AM
  3. Nvidia guide
    By leigh123linux in forum F16 Development
    Replies: 31
    Last Post: 31st October 2011, 07:04 AM
  4. F15 Nvidia Guide
    By leigh123linux in forum F15 Development
    Replies: 128
    Last Post: 24th May 2011, 02:40 PM
  5. Nvidia guide for Rawhide.
    By leigh123linux in forum F16 Development
    Replies: 77
    Last Post: 15th February 2011, 11:08 PM

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
  •