Nvidia version driver miss-match
Reasonably stumped, it appears that I'm running the Nvidia 555 akmods but the userspace tools are still on the 560 versions.
Someone in general mentioned they pinned the images to 555, but it appears that the user space tools are still the 560 version
https://github.com/iotku/atomic-tiles
GitHub
GitHub - iotku/atomic-tiles: i3wm/sway BlueBuild image
i3wm/sway BlueBuild image. Contribute to iotku/atomic-tiles development by creating an account on GitHub.
12 Replies
i think im having the same issue
I think that ublue folks should have pinned nvidia akmods to v555 too
hmm, did they revert nvidia images to get latest v560 now?
no idea, but nvidia drivers no longer work lol
Nvidia drivers or just akmods with them?
or both
idk which parts exactly but im currently getting software rendering on gnome
so i think that means akmods loads but drivers dont work cuz some of the stuff is still 555
what issues did 560 have
oh boy
they did not pin akmods to v555, so it's downloading v560 akmods
while they pinned nvidia images to v555
we default to latest tag for akmods
We need to pin akmods to
20240806 version it seems, this is how they pinned it:
https://github.com/ublue-os/hwe/commit/c0ffe44db571aa6cc8965136dc115fb1b2f0a6f6
I thought that logically, only other akmods should break, but not the nvidia akmod too, since it's pinned to v555
but it seems that's not the case
We need to see how to avoid issues like this in the future, while not needing to follow ublue-os/hwe or akmods repo 24/7so is this a ublue issue
Ublue folks seem to be figuring some stuff in dev channel about this
ah
hopefully they get it done before lots of people update lol
Looks like they noticed
https://discord.com/channels/1072614816579063828/1072617059265032342/1271307999641866333
Solution
looks like they fixed it