Why do I get the option to update to the 565 nvidia driver although it’s still in beta according to nvidia’s website? I don’t have any updates-testing repos activated.
You might have the rpmfusion-nonfree-updates-testing repository enabled, which should be disabled by default.
I’ve checked locally and am also seeing this against rpmfusion-nonfree-updates
Maybe the driver has now been released but the website hasn’t yet been updated? Not sure
as I said I have no testing repos active
1 Like
Interesting. I’m on aarch64 system (so different packages), but this is my output:
$ dnf list xorg-x11-drv-nvidia
Updating and loading repositories:
Repositories loaded.
Available packages
xorg-x11-drv-nvidia.aarch64 3:560.35.03-5.fc41 rpmfusion-nonfree
xorg-x11-drv-nvidia.aarch64 3:560.35.03-5.fc41 rpmfusion-nonfree-nvidia-driver
$ dnf list xorg-x11-drv-nvidia --repo=rpmfusion-nonfree-updates-testing
Updating and loading repositories:
Repositories loaded.
Available packages
xorg-x11-drv-nvidia.aarch64 3:565.57.01-3.fc41 rpmfusion-nonfree-updates-testing
According to this page, the 565 version should still be in updatest-testing. Maybe a glitch?
The package maintainer might see this thread and reply to you.
ohh something seems to be broken with dnf
dnf list akmod-nvidia
Updating and loading repositories:
corrupted size vs. prev_size
the update for the nvidia driver got displayed in discover
I’m going to assume is the exact same reason that Arch updated the nvidia 565 beta drivers to their stable branch as well, which is a serious CVE that the beta fixed, so they updated immediately.
As per their post, "The latest NVIDIA Beta driver is now available in the stable extra repository. Normally on archlinux we do not push the beta driver into the stable repository, but the current 560 branch does have a CVE rated with 8.2 .
NVIDIA did not intend to do another 560 driver to fix the CVE, and therefor we decided to push the 565 driver."
As seen on these two relevant links:
555.xx and 560.xx both have unfixed CVE’s and 550.xx doesn’t have good enough wayland support.
1 Like
Also when Fedora 41 was still beta the testing repo’s were enabled.When Fedora 41 was released the testing repo’s were disabled so somewhere in between the driver may have been pushed into updates.I am pretty sure my driver updated to 565 several days ago while Fedora 41 was still in beta.
I installed that driver and it made external monitor unusable. I’m guessing that is one of the reasons that we’re not seeing it yet in F41 repo.
Run the following, to rebuild the kmods and update the boot image, and see if it fixes it
sudo akmods --rebuild --force
sudo dracut --force
It was mentioned in the links I provided:
Known Issues with the 565 Driver:
- Displays connected via DVI may not function on certain graphics cards.
Thanks Colin, I tried several things to no avail. I just removed it and went back to the 560 driver. I even tried it on a fresh install, same issue.
I tried every cable I had, HDMI, USB, USB-C, thunderbolt to display port, thinking it might fix the issue but nothing worked. I have the 4090 card, not sure if that is part of the problem. I also tried disabling hybrid graphics, and that made the system unbootable.
maybe try the nvidia-open driver. (Howto/NVIDIA - RPM Fusion)
sounds reasonable, thank you 
I should have mentioned, using the laptop monitor, I had no issues. Everything seemed to work fine. The only problem was external monitor, wouldn’t come on at all.
I’m no expert but that may be the same issue as with desktops having black screens with DVI (maybe due to how the I/O ports are connected internally in the laptop).
To my knowledge, thunderbolt does not use DVI. This is a new alienware 18 laptop, and I would be surprised if it used DVI at all, but I could be mistaken. I am no expert on it either.
I suggest if anyone has issues with 565 they post it to
1 Like