https://blue-build.org/ logo
error installing nvidia akmods
# questions
h
I was testing the creation of an image using the official Fedora image (
Copy code
quay.io/fedora-ostree-desktops/base-atomic
) instead of the images provided by ublue, and when installing akmod nivida it gives an error because it assumes that the ublue copr repo is installed https://github.com/Heus-Sueh/hyprland/actions/runs/12508667508/job/34897084114#step:2:2437 Is this behavior correct or is it a bug?
a
message has been deleted
g
You'll want to set
nvidia: true
on the module as well (it's not well documented and no idea if the schema currently allows that)
There was a reason for not having it enabled yet, but I can't remember. @fiftydinar ?
h
like this?
Copy code
yaml
type: akmods
base: main # if not specified, classic "main" base is used by default
install:
  - nvidia: true
x
lift it out of install: next to base: main
it didn't work
x
oh yeah
it's not in the schema
i guess it's back to this then
maybe there's a good reason, maybe there's not
g
Yeah, I took a look through the code for akmods and it seems like we're not even using the RPM packages that get mounted during that module.
I know there were some changes that were going to be happening to support different Nvidia driver types, but I don't know where that's gone yet.
m
If you just want a quick solution that works but is ugly as hell, look at secureblue nvidia images (both open and closed)
f
It wasn't enabled because it wasn't tested enough & Ublue was in transition period regarding Nvidia iirc
but I see that there is more demand for Nvidia akmod, so I think we can turn that on