Akmods failing on 6.8.5, 5XX Nvidia Drivers

System Specs

Operating System: Fedora Linux 39
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12
Kernel Version: 6.7.11-200.fc39.x86_64 (64-bit)
Graphics Platform: Wayland
GPU Nvidia 3050
Nvidia Driver: 535.129.03

Ever since 6.8.X kernel, akmods has failed to build the Nvidia driver. Predictably nvidia-smi fails stating that it cannot communicate with the Nvidia driver.

I have no issues from 6.7.X kernels.
I am using 535 drivers because 540 and 550 drivers cause flickering on XWayland apps.

sudo akmods --force fails producing the following error log - Part 1 Part 2 (split into 2 due to length limits)

I have seen Akmods fails to compile 470xx module on kernel 6.8.4-200, however I’m on 535 and not 470XX drivers.

I have also seen Nvidia Drivers Fail to Install
Secure boot is disabled for me, and I’m coming from a prior stable and working config.

I didn’t manage to find a topic with similar config to mine, hence this post. Any help is welcome, thank you.

1 Like

As I understand it the 470 is for old hardware and the 500 series is for the newer hardware.

I think people are waiting for NVidia to fix there drivers so that they can be built for the 6.8 kernels.

In other words as a workaround use older kernel.

It can be resolved by downloading the latest nvidia 470 driver from the nvidia website.
The driver also asks whether to install in the dkms for automatic recompilation with future kernels.

The only annoyance I had was to, is download drivers first, blacklist nouveau, reboot, and install from console (and ignore the messages about the absence of the X configuration file).

Would you happen to have a link to an issue tracker? I’m finding more posts about the same thing happening to 470XX drivers, but not on 5XX drivers.

Yup already doing so. Seeing 6.8.5 release without a fix or other posts about this makes my worried though. Not sure if this is an issue unique to my system, I am on 535 as opposed to 550 drivers afterall, or this is more widespread.

Kindly re-read what I posted again, I’m on different hardware and drivers!

I was not clear.

I was responding to the reference to the compilation problems on the 470 for the 6.8 kernel, already solved by nvidia but not yet included in akmod.

And I implicitly suggested trying the latest drivers available on the nvidia website, and not waiting for akmod.

@rideandrain @giusdbg
Please note that the very small number of users that require the 470xx drivers has seemed to make updates there a lower priority for resolution than the 5XX drivers which are required for anyone with the newer GPUs and intending to use wayland.

I would anticipate the updates at rpmfusion will happen soon, but it is hardly a reason to become disgruntled with the delay. (frustrated certainly, but workarounds do exist).

It is, after all, up to the user whether they choose to remain on the much older hardware with newer kernels or to upgrade the hardware as the great majority do. When remaining in the minority that way certain inconsistencies in support are – Well: certain!

1 Like

Personally I have no problems, I abandoned akmod, and currently I have the same results, everyone is happy :slightly_smiling_face:.

1 Like

In my case, I have gtx 1050 4gb, so I remove akmod-nvidia, install new 6.9 kernel update then again install nvidia driver. It’s getting very annoying for me, luckily, I’ve enabled keepcache since I’m using 128gb ssd so I don’t need to download nvidia drivers again

Installing a new kernel will do that automatically.
But you do need to wait for the background build to complete.

Why is it not sufficient to run sudo akmods --force if that does not happen auromatically?

In my experience this is a bad choice. It seems to frequently cause problems with fedora since the .run file from nvidia is generalized for all linux distros. It has not had the tweaks and testing done by rpmfusion to confirm that the drivers compile and function without issue on fedora.

In the past the .run file had to be reinstalled with every kernel upgrade.

When installed from rpmfusion the command sudo akmods --force --rebuild should remove the existing module and rebuild it new whenever there is an issue.

2 Likes

Yes, but it’s OT.

The argument was that akmod-nvidia no longer worked and was abandoned, hence the suggestion not to wait.

Then the project was taken over again.

P.S. Personally for a few weeks I used the nvidia driver, then I went back to using akmod-nvidia.
In those weeks I prepared a boot choice that allows me to select noveau, nvidia, purely in text, to be ready for any eventuality (including having to forcefully use only wayland).

akmod-nvidia-390xx and akmod-nvidia-470xx were orphans for a while and failed to build, akmod-nvidia in updates repo hasn’t been fail to build for years.

1 Like

I don’t fix old nvidia releases, rpmfusion 535 ended on the 28/11/23.
If users want to continue to use old versions they will need to use old kernel.

https://bugzilla.rpmfusion.org/show_bug.cgi?id=6860
https://bugzilla.rpmfusion.org/show_bug.cgi?id=6862

2 Likes

I am not able to test the 5x.

As I wrote, I reported my experience on the 470, and suggested trying the same route.
My experience with 470 is excellent, just a few weeks of malfunction and abandonment.