nvidia drivers fail to install
Hello. I'm using the
silverblue-nvidia base image, which already included nvidia akmods. However, after the last reboot, I get prompted by Gnome Software to enroll MOK for some other NVIDIA drivers. But when I enter my password to do that, I get the error Failed to call 'kmodgenca', because that command is not available on the system.9 Replies
sounds like something that secureblue has as well, and it's recommended to be ignored: https://secureblue.dev/post-install#secureboot
and btw, *-nvidia base images would be deprecated soon, see https://github.com/ublue-os/main/issues/927
they already removed other images other than base, silverblue and kinoite
So I should switch to the main image + the akmods module?
I read this and I'm not sure if it says nvidia images will be deprecated? There's some discussion about it but it seems like no conclusion
I've been around in ublue space, they've agreed on that part but not sure when it will happen. not to mention that copilot pr they have about documenting an integration of nvidia on your own...
you can try using bluebuild's base image instead, they're basically replicating ublue older base images for base, silverblue, kinoite and cosmic https://github.com/blue-build/base-images
they'll probably add more systems but not sure about that
GitHub
GitHub - blue-build/base-images: Reference implementation and base ...
Reference implementation and base images for BlueBuild - blue-build/base-images
We have Nvidia base images. The only thing is, the kernel is not signed by UBlue anymore, it's signed by us. I still have to add a justfile to make enrolling easier
That's what I'm using for now while we get those nice just files from @gmpinder 🙃
Regarding gnome-software, that's a known issue. Fedora added a kmod signing module, which is what you saw there. The ublue people used to build their own version of gnome-software to avoid this, but stopped doing it around v47.
Personally, I just remove it from my image and use gnome-firmware + bazaar instead to avoid those messages
oh cool! Is that still experimental? Because the docs still recommend the ublue images
Fedora added a kmod signing module, which is what you saw there.Why can't ublue/bluebuild use that instead of a custom solution then?
Afaik that plugin is meant to be used in regular fedora, where you install the akmod. That akmod is then used to build the proper rpm and, then, sign it before installing.
The problem with that is, if you use it (which you can), it will have to do layer that on top of the base system.
Imho that's one of the drawbacks of this model, that you would need as many images as combinations of kmods like this one. Or let the user build their own images either installing precompiled modules (ublue kmods), or like blue build is doing right now with Nvidia doing the build+install step while the image is being built
Yes, they're expiremental for now
They are based off of what I could gleam from the code in Ublue's main repo and from what I got working for my own personal base images