Re: Akmod Built Nvidia Module Tainting the Kernel at Boot Time

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

 



On Tue, Jul 5, 2022 at 7:55 PM Stephen Morris <samorris@xxxxxxxxxxxxxxx> wrote:
Hi,
    I believe I am using akmod to build the nvidia kernel module when the kernel version changes and that built module is tainting the kernel because of missing signature or keys, which I am assuming are secure boot keys, but I also followed some instructions I found on the net to get nvidia keys into secure boot when I first installed the nvidia modules. I don't know whether I was getting the following messages at that time or not, as I found these when I was looking for something else.
     Is the issue with the following messages that the secure boot keys have to be rebuilt every time the nvidia modules are updated?

It is the nvidia proprietary code that kernel developers can't examine -- nothing to do with the secure boot keys: https://ask.fedoraproject.org/t/nvidia-taints-kernel/12753 
 
    Just as a follow on from this, I've read that nvidia have open sourced their linux drivers, how long will it take for those to be incorporated into the distribution to remove the requirement for the Rpm Fusion versions?

[   13.973631] nvidia: loading out-of-tree module taints kernel.
[   13.973636] nvidia: module license 'NVIDIA' taints kernel.
[   13.978637] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[   13.988926] nvidia-nvlink: Nvlink Core is being initialized, major device number 511
[   13.989619] nvidia 0000:09:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
[   14.040430] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  510.68.02  Wed Apr 20 21:10:34 UTC 2022
[   14.677665] caller _nv000651rm+0x1ad/0x200 [nvidia] mapping multiple BARs
[   14.928567] nvidia_uvm: module uses symbols from proprietary module nvidia, inheriting taint. 




--
George N. White III

_______________________________________________
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