Open dhoell opened 1 month ago
ManuaL46
commented
1 month ago Yes this issue popped up with 20240808 and 20240809 images, for some reason I have the 560 client driver version but the kernel module is still using the 555 driver version.
Has anyone else faced this issue, currently sticking with 20240807 fixes the issue.
castrojo
commented
1 month ago Please check again, we found the issue and corrected it. Builds just finished now.
castrojo
commented
1 month ago Oh sorry I misspoke, we were correcting the skew between this repo and akmod to fix having mixed 555/560 on the same image, stay pinned on your existing image for now.
Pryka
commented
1 month ago The current nvidia 560 drivers are still labeled "beta" (https://www.nvidia.com/en-us/drivers/unix/), thus are not available on flathub. Negativo17 however still packages them, causing all flatpaks to lose nvidia driver functionality, as they are stuck on 555.
Try updating image and rerunning flatpak upgrade flathub repo already have 560 beta drivers on it. There is a chance that was not downloaded due to mixed kernel module and drivers version in the image.
If this does not help, try enabling flathub beta repository.
dhoell
commented
1 month ago As far as I understand this is about a mismatch between Nagativo17 and Flathub repositories. Negativo17 publishes nvidia 560, which is still beta according to upstream. Which is why other repositories (like flathub) don't publish it in their release branch, which is IMO absolutely correct, and Negativo17 should not publish beta software in Fedora 40 release (rawhide, sure, but not in a stable release).
I'm sorry, I don't know about the reasons for the switch to Negativo17 repo, but if it was only speed of updates, I'd say that slower updates from RPMfusion are vastly preferable to fast, but premature and breaking updates.
Yes, this can be fixed by getting flatpak nvidia drivers from flathub-beta, but "we may use beta drivers at any random time, so switch so flathub-beta when that happens" does not seem like an appropriate solution.
Pryka
commented
1 month ago Yes, this can be fixed by getting flatpak nvidia drivers from flathub-beta, but "we may use beta drivers at any random time, so switch so flathub-beta when that happens" does not seem like an appropriate solution.
Enabling beta flatpak don't switch all apps to beta, you need to explicitly install them with flatpak install flathub-beta app/runtime name
It can be left enabled at all times.
PS. Also you can install stable and beta version of one app at the same time. They are not mutually exclusive.
ManuaL46
commented
2 weeks ago Hi this issue seems to have cropped up again, the system drivers and the flatpak drivers are different, and it seems that flathub stable still doesn't have this version
Pryka
commented
2 weeks ago Hi this issue seems to have cropped up again, the system drivers and the flatpak drivers are different, and it seems that flathub stable still doesn't have this version
Looks like NVIDIA flatpak package maintainers have some issues with building 32bit version - https://github.com/flathub/org.freedesktop.Platform.GL.nvidia/commit/c8df268595409665615fdf411de03c8a1d190951
seras42
commented
2 weeks ago Any solutions to @ManuaL46 problem? Rerolling does not seem to help. This shutdown a lot of flatpak apps who run on nvidia. I can not even run VLC.
ManuaL46
commented
2 weeks ago Any solutions to @ManuaL46 problem? Rerolling does not seem to help. This shutdown a lot of flatpak apps who run on nvidia. I can not even run VLC.
Rolling back to 2024.08.20 Fixed this for me the issue arises from 2024.08.21 onwards for me I think.
The current nvidia 560 drivers are still labeled "beta" (https://www.nvidia.com/en-us/drivers/unix/), thus are not available on flathub. Negativo17 however still packages them, causing all flatpaks to lose nvidia driver functionality, as they are stuck on 555.