Re: urgent major problem after f39 to f40 upgrade.

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

 



On 10/12/24 3:58 PM, Samuel Sieb wrote:
[snip]
I might be treading on old ground here, but the above output is showing that you have nouveau blacklisted so it will not start. If you are booting to a console because your nvidia drivers aren't working yet allowing nouveau to be used may get you to a graphic login. To remove the multiple occurrences of rd.driver.blacklist=nouveau, modprobe.blacklist=nouveau you may want to remove them from the kernel line in /etc/default/grub and rebooting.
If that gets you a graphic interface, to get the nvidia drivers working via akmods you may have to redo the uefi signing signing processes if you are booting via uefi. I had to do that resigning when I upgraded from F39 to F40.

I don't recall how to determine whether this workstation boots bois or uefi or something else.  I don't recall hwo to determine this.  It;s 11 years old; I'm thinking it's bios.

Samuel later says to leave blacklist part in the BOOT_IMAGE line.

I'll come back to the digital signing later.

If it's BIOS, then you don't need that.  But even if you do have UEFI, you must have secure boot turned off because the modules are loading, so there's no problem there.

If you have UEFI, then there will be a line from running "mount" that looks like this:
/dev/nvme0n1p1 on /boot/efi type vfat ...
(different drive of course, but most likely p1 anyway)


-bash.4[~]: mount | grep p1
-bash.5[~]:

For years, I've been seeing lines like these during boot:

-bash.5[~]: journalctl -b | grep taint
Oct 12 12:31:47 coyote kernel: nvidia: loading out-of-tree module taints kernel.
Oct 12 12:31:47 coyote kernel: nvidia: module license 'NVIDIA' taints kernel.
Oct 12 12:31:47 coyote kernel: Disabling lock debugging due to kernel taint
Oct 12 12:31:47 coyote kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
Oct 12 12:31:47 coyote kernel: nvidia: module license taints kernel.
Oct 12 12:31:51 coyote kernel: nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
-bash.6[~]:

But I'm not aware of any problems relating to this.  Is this somehow related to the absence of "digital signing"?

I do not know what this "digital signing" is or how to do it, but I gather from what Samuel says, I don't need it.

--
_______________________________________________
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