Re: weekly patches crippled my display.

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

 



On 11/23/23 12:52, home user wrote:
On 11/23/23 1:43 PM, Samuel Sieb wrote:
On 11/23/23 12:02, home user wrote:
(f38; home workstation; dual monitor;
using nvidia 4xx kmod and akmod from rpmfusion)

A short while ago, I did my weekly patches.  After rebooting, only one monitor is displaying anything, and then with a large, wide font.  I saw no indication of trouble during the "dnf upgrade". The boot messages go by fast, but I think I saw something about a missing module, and nouveau being used.

I'm not a sys.admin., and the display is very limited.  What's the cause of these problems, and how do I fix things?

Try running "sudo akmods" and see if there are any errors.
--
I've rebooted to the previous kernel.  Does that matter?  Running under that older kernel, I get this:
-----
-bash.1[~]: akmods
Checking kmods exist for 6.5.10-200.fc38.x86_64            [  OK  ]
Building and installing nvidia-470xx-kmod                  [FAILED]
Building rpms failed; see /var/cache/akmods/nvidia-470xx/470.223.02-1-for-6.5.10-200.fc38.x86_64.failed.log for details

Hint: Some kmods were ignored or failed to build or install.
You can try to rebuild and install them by by calling
'/usr/sbin/akmods --force' as root.

Checking kmods exist for 6.5.12-200.fc38.x86_64            [  OK  ]
Building and installing nvidia-470xx-kmod                  [FAILED]
Building rpms failed; see /var/cache/akmods/nvidia-470xx/470.223.02-1-for-6.5.12-200.fc38.x86_64.failed.log for details

Hint: Some kmods were ignored or failed to build or install.
You can try to rebuild and install them by by calling
'/usr/sbin/akmods --force' as root.

-bash.2[~]:
-----
1. Do I need to re-do this under the new kernel?

I think it will compile against any kernels that need it. Which kernel are you running and which one do you need?

2. Should I do what the output above says?

Check the log to see why it's failing. It might be a kernel change that breaks the module. You could try forcing it and see what happens.
--
_______________________________________________
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, report it: https://pagure.io/fedora-infrastructure/new_issue



[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