Installed the NVidia drivers with the akmod-nvidia package from RPMFusion.
Added the following kernel parameters to grub: rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1
Created /usr/lib/modprobe.d/blacklist-nouveau.conf with:
blacklist nouveau
options nouveau modeset=0
However, I do not seem to be able to load the nvidia module by default:
# modprobe nvidia
modprobe: FATAL: Module nvidia not found in directory /lib/modules/6.0.15-300.fc37.x86_64
# nvidia-smi
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.
However, if I insert the module manually, everything works correctly:
We need to check if the hardware is actually seen by the system.
Please use the preformatted text tags with the </> button on the toolbar to paste the screen text into your posts.
Please post the output of lspci -nnv | grep -A 12 -iE 'network|ethernet' so we may see the actual hardware details
This is probably the issue.
By default the nvidia module is not signed, so when secure boot is enabled the drivers cannot be loaded.
Very easy to fix, in one of 2 ways.
Disable secure boot in bios, which will allow the modules to load as-is
or
sign the modules so they can be loaded with secure boot enabled.
The modules signing can be enabled by following the steps in the file
‘/usr/share/doc/akmods/README.secureboot’.
Before the reboot at the end of those steps one must remove the current modules and rebuild the modules as signed with the following
a. dnf remove kmod-nvidia-* to remove the unsigned modules
b. akmods --force to rebuild the module with the signature key created above.
c. Finallly reboot and enroll the key as per the final step in the README above.
Now when you reboot the modules should load properly with secure boot enabled.
I got through all the steps, rebooted, and then there was supposed to be a MOK Management launched, but that did not happen. Confirmation of enrollment failed when I used the commands listed at the bottom of the README
Did bios show the blue screen for mok enrollment when you booted?
If not then go back to the README and carefully follow the steps. Note that all steps there must be done using sudo, both to run sudo kmodgenca -a and sudo mokutil --import /etc/pki/akmods/certs/public_key.der
The reboot following the import should bring up the mok blue screen with bios to complete the import of the signing key.
It did not bring up the blue screen for mok enrollment.
I used sudo for the steps. Will it cause a problem to go through the steps one more time? Or is there something I should do/remove before starting again?
The command mokutil --list-enrolled should show all keys already enrolled.
If the new key just generated is not shown then you can repeat the kmodgenca command using sudo kmodgenca -a -f to force building a new key pair, then repeat the import step to import that new key into bios.
Reboot after doing the import to ensure the key is enrolled into bios then repeat the steps above to remove and rebuild the modules with the newest keys before once again rebooting to load them.
Well something went way wrong because now after logging into the desktop it freezes within 5 seconds of login.
After about 5 reboots I was able to use my PC again.
[hal@localhost-live akmods]$ mokutil --list-enrolled | grep Issuer
Issuer: CN=Fedora Secure Boot CA
CA Issuers - URI:https://fedoraproject.org/wiki/Features/SecureBoot
So it’s not showing akmods as an issuer. I do see the public_key.der file generated from when I did the sudo kmodgenca command. I will try force building a new key pair.
