After a dnf upgrade that included the new 5.x kernel I did my regular check to make sure that the nvidia driver got built via akmod-nvidia- 340xx-340.107-5.fc29.x86_64. It was not there, so I looked more closely at the output of the 'dnf upgrade' and found that:
dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.ReYjXp/initramfs -H --kerneldir /lib/modules/5.0.3- 200.fc29.x86_64/ -o -m =drivers/net/phy =drivers/ net/team =drivers/net/ethernet ecb arc4 bridge stp llc ipv6 bonding 8021q ipvlan macvlan af_packet virtio_net xennet
Full output is at: https://paste.fedoraproject.org/paste/qKIPdK4OB8JGmGH6g8LQEA
Line 234 is where it shows the issue.
I have not yet rebooted, but I tend to assume that a reboot into my current 4.20.16-200.fc29.x86_64 will still be fine but clearly it will have trouble trying to boot to 5.x
On Tue, 26 Mar 2019 16:38:13 -0000 "Doug Herr" fedoraproject.org@wombatz.com wrote:
After a dnf upgrade that included the new 5.x kernel I did my regular check to make sure that the nvidia driver got built via akmod-nvidia- 340xx-340.107-5.fc29.x86_64. It was not there, so I looked more closely at the output of the 'dnf upgrade' and found that:
dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.ReYjXp/initramfs -H --kerneldir /lib/modules/5.0.3- 200.fc29.x86_64/ -o -m =drivers/net/phy =drivers/ net/team =drivers/net/ethernet ecb arc4 bridge stp llc ipv6 bonding 8021q ipvlan macvlan af_packet virtio_net xennet
Full output is at: https://paste.fedoraproject.org/paste/qKIPdK4OB8JGmGH6g8LQEA
Line 234 is where it shows the issue.
I have not yet rebooted, but I tend to assume that a reboot into my current 4.20.16-200.fc29.x86_64 will still be fine but clearly it will have trouble trying to boot to 5.x
I think the new kernel version will require a new binary blob driver from nvidia. It probably just hasn't arrived yet, so you will have to use the previous kernel until it does. You could go to nvidia's website to see if it is there, and update it manually, but it is a lot easier to let the good folks at rpmfusion do the driving for you.
On Tue, 2019-03-26 at 11:02 -0700, stan via users wrote:
On Tue, 26 Mar 2019 16:38:13 -0000 "Doug Herr" fedoraproject.org@wombatz.com wrote:
After a dnf upgrade that included the new 5.x kernel I did my regular check to make sure that the nvidia driver got built via akmod- nvidia- 340xx-340.107-5.fc29.x86_64. It was not there, so I looked more closely at the output of the 'dnf upgrade' and found that:
dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.ReYjXp/initramfs -H --kerneldir /lib/modules/5.0.3- 200.fc29.x86_64/ -o -m =drivers/net/phy =drivers/ net/team =drivers/net/ethernet ecb arc4 bridge stp llc ipv6 bonding 8021q ipvlan macvlan af_packet virtio_net xennet
Full output is at: https://paste.fedoraproject.org/paste/qKIPdK4OB8JGmGH6g8LQEA
Line 234 is where it shows the issue.
I have not yet rebooted, but I tend to assume that a reboot into my current 4.20.16-200.fc29.x86_64 will still be fine but clearly it will have trouble trying to boot to 5.x
I think the new kernel version will require a new binary blob driver from nvidia. It probably just hasn't arrived yet, so you will have to use the previous kernel until it does. You could go to nvidia's website to see if it is there, and update it manually, but it is a lot easier to let the good folks at rpmfusion do the driving for you.
I think you got it right. I had considered switching over to the nouveau driver as a test but I was hesitant since the switch included a "dracut -f". Your reply gave me the courage. The switch worked fine, no issue for the dracut. I rebooted to the 4.20 kernel first and then did a "dnf reinstall kernel-5.0.3-200.fc29.x86_64". That had no issues and I have now rebooted into the 5.0.3 kernel and things look fine. I can run this way until the rpm fusion Nvidia is ready.
Thanks much.
Doug Herr wrote:
After a dnf upgrade that included the new 5.x kernel I did my regular check to make sure that the nvidia driver got built via akmod-nvidia- 340xx-340.107-5.fc29.x86_64. It was not there, so I looked more closely at the output of the 'dnf upgrade' and found that:
dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.ReYjXp/initramfs -H --kerneldir /lib/modules/5.0.3- 200.fc29.x86_64/ -o -m =drivers/net/phy =drivers/ net/team =drivers/net/ethernet ecb arc4 bridge stp llc ipv6 bonding 8021q ipvlan macvlan af_packet virtio_net xennet
Full output is at: https://paste.fedoraproject.org/paste/qKIPdK4OB8JGmGH6g8LQEA
Line 234 is where it shows the issue.
I have not yet rebooted, but I tend to assume that a reboot into my current 4.20.16-200.fc29.x86_64 will still be fine but clearly it will have trouble trying to boot to 5.x
I saw this reported in IRC a few times today as well. There's a dracut update pending which should fix it:
https://bodhi.fedoraproject.org/updates/FEDORA-2019-38c666fc03
-
Doug Herr -
stan -
Todd Zullinger