Re: Updating F32 (with Nvidia drivers) and startup hangs.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 01/01/2022 17:52, Fulko Hew wrote:
I'm not sure where the problem lies, so I'll start out with where I'm coming from...

I built a machine 2 years ago to support the Folding@Home project
using F32 and an Nvidia 2060 card.

It's been running non-stop ever since.
But I want to update the system to the latest and greatest release and drivers
(since it appears that my old? CUDA drivers have stopped working with F@H)

So first I updated all my packages using dnf and attempted a reboot
(into the new kernel) and that's where the first problem appeared.
The boot process hangs with the last message on the screen being
"Notify NFS peers of a restart"

(I don't have any NFS configured on this machine.)

So I rebooted with my old working kernel and examined /var/log/messages
and I see:
Jan  1 12:36:10 localhost sh[972]: (bad exit status: 2)
Jan  1 12:36:10 localhost sh[4378]: Error! Bad return status for module build on kernel: 5.11.22-100.fc32.x86_64 (x86_64) Jan  1 12:36:10 localhost sh[4378]: Consult /var/lib/dkms/nvidia/440.82/build/make.log for more information.

Looking at that file, I see a variety of errors basically telling me there's
incompatibilities between the stuff Nvidia uses to get itself 'linked in' at boot
time, and what the kernel is now providing.

If I can't get to a GUI screen to be able to fetch and install newer NVIDIA drivers
how can I get my system updated?

Suggestions welcome.
TIA
Fulko


There have been several posts in the last few days arising from the shift of some nvidia cards to 'legacy' status. Cards supported by the 470 series driver but not by 495 now have to add the 470xx tag to the rpmfusion package name.

The GTX2060 is listed as supported by 495, but there won't be F32 packages for it. It would probably be best to upgrade to F35 (or F34) to get them; that process now seems to be straightforward and reliable.

I found that the rpmfusion cuda package was not installed by the default akmod build process; "dnf install xorg-x11-drv-nvidia-cuda" should work for you.

HTH

John P
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux