Hi everyone,
Today I upgraded both my gaming PC and ThinkPad to Fedora 43, and encountered the same issue on both systems during the upgrade process.
Setup:
Gaming PC: NVIDIA GPU (primary)
ThinkPad: NVIDIA GPU (secondary, not primary)
Both systems using akmods
Issue:
The upgrade proceeded normally until after the kmod build tools completed their work. According to the systemd log, this step finished successfully. However, the upgrade then hung for ~30 minutes with no further progress.
On both machines, I had to switch to Ctrl+Alt+F3, log in as root, and manually execute reboot. After the manual reboot, both systems came up without issues on F43.
Note on gaming PC:
There was an initial issue with conflicting WINE packages that prevented the upgrade from starting. I resolved this by removing WINE before proceeding with the upgrade.
Has anyone else experienced the upgrade process hanging after the akmods step? Since this occurred identically on two different systems (both with NVIDIA hardware), I suspect there might be an issue with this last step.
Is this issue known, and I have a Homelab-Server that I want to upgrade too, so, is there a way I can prepare for it that this doesn’t occur when upgrading the Homelab-Server?
Aside from the upgrade-experience F43 works good
The akmods process was still active and compiling the nvidia kernel mods, so the reboot request failed. It would be better to queue the reboot request until the akmods build processes have finished.
You can remove the nvidia drivers and re-install after upgrade.
The listing for the laptop seems to be missing 2 packages that are installed on the PC.
The xorg libs.i686 and power.x86_64
Otherwise that seems normal.
I have never seen the hang of ~30 min as you said, but anything is possible.
After having that kind of hang it might be appropriate to run sudo dnf distro-sync --refresh to ensure that everything is fully in sync with the updates. Especially since the 6.17.5 kernel was just released.
Done that and kernel 6.17.5 was installed successfully, and so far F43 just works as it should. The only thing I could imagine, because this was an issue too, that after each kernel update with akmods building action, a restart often caused that fedora would go in the software rendering mode because it couldn’t find the driver which probably was a timing issue, that’s why I’m waiting most of the time 10-15 minutes if akmod is there to ensure somewhat that the driver was build. I could image that something like this also happend that a reboot request was maybe timed out and then nothing happend, the PC was in total idle mode.
Maybe it’s something to deal with (I’m just like 3 months switched from Windows to Linux aka Fedora, so there are some things still kinda scary if something like this happens).
Just to be sure, the previous issues were during a F42 → F43 release upgrade, right?
You can check the journal of the upgrade process session or check sudo dnf system-upgrade log --number=1 for clues.
Ah cool, I’ll remember this command, yesterday I tried to use the JournalId Browser or KSystemLog but couldn’t find this stuff directly.
That’s the log I’ve seen before the pc went idle and nothing happend on the screen anymore (some part’s are in German, since my system language is German)
Okt 28 15:19:13 MyHostName runuser[50342]: pam_unix(runuser:session): session closed for user akmods
Okt 28 15:19:13 MyHostName audit[50342]: AUDIT1106 pid=50342 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:unconfined_service_t:s0 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_unix acct="akmods" exe="/usr/bin/runuser" hostname=? addr=? terminal=? res=success'
Okt 28 15:19:13 MyHostName audit[50342]: AUDIT1104 pid=50342 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:unconfined_service_t:s0 msg='op=PAM:setcred grantors=pam_rootok acct="akmods" exe="/usr/bin/runuser" hostname=? addr=? terminal=? res=success'
Okt 28 15:19:14 MyHostName systemd-inhibit[50320]: [FAILED]
Okt 28 15:19:16 MyHostName dnf5[1243]: [7477/7477] Entferne libgcc-0:15.2.1-3. 100% | 0.0 B/s | 11.0 B | 01m00s
Okt 28 15:19:16 MyHostName dnf5[1243]: Warnung: ��bersprungene OpenPGP-Pr��fungen f��r 3771 Pakete aus den Repositories: copr:copr.fedorainfracloud.org:herzen:davinci-helper, fedora, fedora-cisco-openh264, rpmfusion-free, rpmfusion-free-updates, rpmfusion-nonfree, updates
Okt 28 15:19:16 MyHostName dnf5[1243]: Transaction complete! Cleaning up and rebooting...
Okt 28 15:19:16 MyHostName dnf5[1243]: [org.freedesktop.DBus.Error.AccessDenied] Access denied due to active block inhibitor
Okt 28 15:19:16 MyHostName systemd[1]: dnf5-offline-transaction.service: Main process exited, code=exited, status=1/FAILURE
Okt 28 15:19:16 MyHostName systemd[1]: dnf5-offline-transaction.service: Failed with result 'exit-code'.
Okt 28 15:19:16 MyHostName systemd[1]: Failed to start dnf5-offline-transaction.service - Offline upgrades/transactions using DNF 5.
Okt 28 15:19:16 MyHostName audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf5-offline-transaction comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Okt 28 15:19:16 MyHostName systemd[1]: dnf5-offline-transaction.service: Consumed 9min 32.565s CPU time, 28.8G memory peak.
Okt 28 15:19:16 MyHostName systemd[1]: dnf5-offline-transaction.service: Triggering OnFailure= dependencies.
Okt 28 15:19:16 MyHostName systemd[1]: Reached target system-update.target - Offline System Update.
Okt 28 15:19:16 MyHostName kernel: kauditd_printk_skb: 3786 callbacks suppressed
Okt 28 15:19:16 MyHostName kernel: audit: type=1130 audit(1761661156.831:4276): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf5-offline-transaction comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Okt 28 15:19:16 MyHostName systemd[1]: Starting dnf5-offline-transaction-cleanup.service - Offline upgrade/transaction using DNF 5 failed...
Okt 28 15:19:16 MyHostName systemd[1]: system-update-cleanup.service - Remove the Offline System Updates Symlink was skipped because no trigger condition checks were met.
Okt 28 15:19:16 MyHostName systemctl[60245]: Call to Reboot failed: Access denied
Okt 28 15:19:16 MyHostName systemd[1]: dnf5-offline-transaction-cleanup.service: Main process exited, code=exited, status=1/FAILURE
Okt 28 15:19:16 MyHostName systemd[1]: dnf5-offline-transaction-cleanup.service: Failed with result 'exit-code'.
Okt 28 15:19:16 MyHostName systemd[1]: Failed to start dnf5-offline-transaction-cleanup.service - Offline upgrade/transaction using DNF 5 failed.
Okt 28 15:19:16 MyHostName audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf5-offline-transaction-cleanup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Okt 28 15:19:16 MyHostName kernel: audit: type=1130 audit(1761661156.936:4277): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf5-offline-transaction-cleanup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Okt 28 15:19:19 MyHostName systemd-inhibit[50320]: Could not install newly built RPMs. You can find them and the logfile in:
Okt 28 15:19:19 MyHostName systemd-inhibit[50320]: /var/cache/akmods/nvidia/580.95.05-1-for-6.17.4-300.fc43.x86_64.failed.log
Okt 28 15:19:19 MyHostName systemd-inhibit[50320]: [FAILED]
Okt 28 15:19:19 MyHostName systemd[1]: Finished akmods@6.17.4-300.fc43.x86_64.service - Builds and install new kmods from akmod for a given kernel.
Okt 28 15:19:19 MyHostName systemd[1]: Startup finished in 20.324s (firmware) + 2.557s (loader) + 2.626s (kernel) + 2.838s (initrd) + 12min 44.301s (userspace) = 13min 12.649s.
And this is part of the nvidia.log described:
2025/10/28 15:19:13 akmodsbuild: + /usr/lib/rpm/brp-kmodsign /etc/pki/akmods/private/private_key.priv /etc/pki/akmods/certs/public_key.der /tmp/akmodsbuild.NZQJSryY/BUILD/nvidia-kmod-580.95.05-build/BUILDROOT/lib/modules/6.17.4-300.fc43.x86_64/extra/nvidia/ /usr/src/kernels/6.17.4-300.fc43.x86_64
2025/10/28 15:19:13 akmodsbuild: + '[' 0 -eq 1 ']'
2025/10/28 15:19:13 akmodsbuild: Reading /tmp/akmodsbuild.NZQJSryY/BUILD/nvidia-kmod-580.95.05-build/SPECPARTS/rpm-debuginfo.specpart
2025/10/28 15:19:13 akmodsbuild: Dateien werden verarbeitet: kmod-nvidia-6.17.4-300.fc43.x86_64-580.95.05-1.fc43.x86_64
2025/10/28 15:19:13 akmodsbuild: Provides: kernel-modules-for-kernel = 6.17.4-300.fc43.x86_64 kmod(nvidia-drm.ko) kmod(nvidia-modeset.ko) kmod(nvidia-peermem.ko) kmod(nvidia-uvm.ko) kmod(nvidia.ko) kmod-nvidia-6.17.4-300.fc43.x86_64 = 3:580.95.05-1.fc43 kmod-nvidia-6.17.4-300.fc43.x86_64(x86-64) = 3:580.95.05-1.fc43 kmod-nvidia-newest-6.17.4-300.fc43.x86_64 = 3:580.95.05-1.fc43 nvidia-kmod = 3:580.95.05-1.fc43
2025/10/28 15:19:13 akmodsbuild: Requires(interp): /bin/sh /bin/sh
2025/10/28 15:19:13 akmodsbuild: Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
2025/10/28 15:19:13 akmodsbuild: Requires(post): /bin/sh /usr/sbin/depmod
2025/10/28 15:19:13 akmodsbuild: Requires(postun): /bin/sh /usr/sbin/depmod
2025/10/28 15:19:13 akmodsbuild: Obsoletes: kmod-nvidia-newest-6.17.4-300.fc43.x86_64 < 3:580.95.05-1.fc43
2025/10/28 15:19:13 akmodsbuild: Auf nicht gepackte Datei(en) wird geprĂĽft: /usr/lib/rpm/check-files /tmp/akmodsbuild.NZQJSryY/BUILD/nvidia-kmod-580.95.05-build/BUILDROOT
2025/10/28 15:19:13 akmodsbuild: Erstellt: /tmp/akmodsbuild.NZQJSryY/RPMS/x86_64/kmod-nvidia-6.17.4-300.fc43.x86_64-580.95.05-1.fc43.x86_64.rpm
2025/10/28 15:19:13 akmodsbuild: AusfĂĽhrung(rmbuild): /bin/sh -e /var/tmp/rpm-tmp.ivvAaG
2025/10/28 15:19:13 akmodsbuild: + umask 022
2025/10/28 15:19:13 akmodsbuild: + cd /tmp/akmodsbuild.NZQJSryY//BUILD/nvidia-kmod-580.95.05-build
2025/10/28 15:19:13 akmodsbuild: + test -d /tmp/akmodsbuild.NZQJSryY//BUILD/nvidia-kmod-580.95.05-build
2025/10/28 15:19:13 akmodsbuild: + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w /tmp/akmodsbuild.NZQJSryY//BUILD/nvidia-kmod-580.95.05-build
2025/10/28 15:19:13 akmodsbuild: + rm -rf /tmp/akmodsbuild.NZQJSryY//BUILD/nvidia-kmod-580.95.05-build
2025/10/28 15:19:13 akmodsbuild: + RPM_EC=0
2025/10/28 15:19:13 akmodsbuild: ++ jobs -p
2025/10/28 15:19:13 akmodsbuild: + exit 0
2025/10/28 15:19:13 akmods: Installing newly built rpms
2025/10/28 15:19:14 akmods: DNF detected
Aktualisiere und lade Paketquellen:
Paketquellen geladen.
Paket Architektur Version Paketquelle Größe
Installiere:
kmod-nvidia-6.17.4-300.fc43.x86_64 x86_64 3:580.95.05-1.fc43 @commandline 35.3 MiB
Transaktionszusammenfasung:
Installiere: 1 Paket
Die vollständige Größe eingehender Pakete ist 8 MiB. Heruntergeladen werden müssen 0 B.
Nach dieser Operation werden 35 MiB mehr benötigt (installiere 35 MiB, entferne 0 B).
Transaktion wird ausgefĂĽhrt
Transaktion fehlgeschlagen: Rpm Transaktionssperre konnte nicht in Kraft gesetzt werden. Eine andere Transaktion wird bereits durchgefĂĽhrt.
Warnung: Ăśbersprungene OpenPGP-PrĂĽfungen fĂĽr 1 Paket aus dem Repository: @commandline
2025/10/28 15:19:19 akmods: Could not install newly built RPMs. You can find them and the logfile in:
2025/10/28 15:19:19 akmods: /var/cache/akmods/nvidia/580.95.05-1-for-6.17.4-300.fc43.x86_64.failed.log
Okt 28 15:19:16 MyHostName dnf5[1243]: [7477/7477] Entferne libgcc-0:15.2.1-3. 100% | 0.0 B/s | 11.0 B | 01m00s
Okt 28 15:19:16 MyHostName dnf5[1243]: Warnung: ��bersprungene OpenPGP-Pr��fungen f��r 3771 Pakete aus den Repositories: copr:copr.fedorainfracloud.org:herzen:davinci-helper, fedora, fedora-cisco-openh264, rpmfusion-free, rpmfusion-free-updates, rpmfusion-nonfree, updates
Okt 28 15:19:16 MyHostName dnf5[1243]: Transaction complete! Cleaning up and rebooting...
Okt 28 15:19:16 MyHostName dnf5[1243]: [org.freedesktop.DBus.Error.AccessDenied] Access denied due to active block inhibitor
Okt 28 15:19:16 MyHostName systemd[1]: dnf5-offline-transaction.service: Main process exited, code=exited, status=1/FAILURE
Okt 28 15:19:16 MyHostName systemd[1]: dnf5-offline-transaction.service: Failed with result 'exit-code'.
Okt 28 15:19:16 MyHostName systemd[1]: Failed to start dnf5-offline-transaction.service - Offline upgrades/transactions using DNF 5.
Okt 28 15:19:16 MyHostName audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf5-offline-transaction comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Okt 28 15:19:16 MyHostName systemd[1]: dnf5-offline-transaction.service: Consumed 9min 32.565s CPU time, 28.8G memory peak.
Okt 28 15:19:16 MyHostName systemd[1]: dnf5-offline-transaction.service: Triggering OnFailure= dependencies.
Okt 28 15:19:16 MyHostName systemd[1]: Reached target system-update.target - Offline System Update.
Okt 28 15:19:16 MyHostName kernel: kauditd_printk_skb: 3786 callbacks suppressed
Okt 28 15:19:16 MyHostName kernel: audit: type=1130 audit(1761661156.831:4276): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf5-offline-transaction comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Okt 28 15:19:16 MyHostName systemd[1]: Starting dnf5-offline-transaction-cleanup.service - Offline upgrade/transaction using DNF 5 failed...
Okt 28 15:19:16 MyHostName systemd[1]: system-update-cleanup.service - Remove the Offline System Updates Symlink was skipped because no trigger condition checks were met.
Okt 28 15:19:16 MyHostName systemctl[60245]: Call to Reboot failed: Access denied
There are still some issues to iron out with akmods in an offline transaction.
akmods can run during the next boot, so maybe it would be better to block akmods during offline updates. But this could then confuse users, because the first boot procedure would take much longer to display the login screen.
Ok, so as for now this is something to deal with?
Regarding the offline transaction this was recommended from the docs so I followed all the steps there:
# first step to update fedora
sudo dnf upgrade --refresh
# doing the system upgrade
sudo dnf system-upgrade download --releasever=43
# If you’re using DNF 5 (starting from Fedora 41+):
# Since I was on F42 I've done the offline reboot as said in the docs
sudo dnf5 offline reboot
If the akmod is not rebuilt during the initial upgrade it usually is done during the next reboot. I have seen this happen recently when I upgraded from kernel 6.17.4 to 6.17.5 (the nvidia driver was already installed) on a newly installed fedora 42 system. I waited a long time before the reboot since I was still running something else.
The reboot gave me notice on the spinner screen during boot that akmods was running its compile for the driver and the boot completed with the new driver already loaded.
The reboot displays the akmods reason for the delay on screen before reaching the login screen on my f42 system. See my comment above. Users may be irritated by the small delay, but not confused.
This was probably the f42-> f43 offline upgrade process. I saw similar issue, when I did the upgrade in Sep to F43 beta. The reboot would fail, (inhibitor active because of akmods building the kernel modules). The system resolved to transition into another target. Had to reset the system, because I forgot to unlock root account.
And weirdly enough after the reboot I could log in, which took a bit of time because somehow fedora seemed to have deactivated some services on the reboot (I have systemd logs activated instead of the loading screen), but I could login came to this SSDM or whatever this login screen is called, and everything loaded ok, then I did the distro-sync stuff, started the podman container “portainer”, visited the site, and then I was thrown back to the login screen, input my credentials again, but then the screen was black, I waited just a bit, and then, because I couldn’t input anything, forced the PC to shut down… For now it seems to work, my containers are running (especially AdGuard and NPM are important)…
Weird journey, this home server also had an nVidia card (but of an older generation, the 1080).
F42? That would be new, but may have been back ported to F42.
F43 yes, but only very briefly for 1-2 seconds max ( on my system) and can be easily missed. The next message appeared minutes later when build process finished and kernel modules were installed.
But I think the OP saw the issue updating the kernel with an offline upgrade.
I reproduced this with an upgrade to kernel 6.17.6. Akmods compiled and installed the kmods during the offline transaction( good) but unfortunately the session tries to reboot the system too early and gets stuck. Unlock root account if you want to reproduce. Boot w/o rhgb.
Agreed, but it happened.
During the boot with the spinner (reboot after the first update following the install) the message came up under the spinner that akmods was building the module. It then changed to installing, and when it disappeared the system finished booting with the driver loaded.
With the newer driver (580) it only takes a few seconds to completely build the driver, unlike the older proprietary driver which can take minutes.
