Today the 580.142 update came out.
A computer of mine was set to “install updates after restart”.
AKMODS was keeping on failing to build, each and every single time it was booting up, so I swapped to the iGPU (I am lucky this one has it)[1] and now I ran the almighty
sudo akmods --rebuild --force
Using the GUI to update Nvidia drivers seems dangerous, which shouldn’t be.
You can technically use Ctrl + Alt + F3 to log in without graphics, but this one computer had a different username compared to my other ones because the way Fedora gets installed changed and I didn’t notice that iclarke became isaac on this one alone. ↩︎
This journal seems to include logs from 2 machines: fedora and DESKTOP-L9HGLLK.
Am I right ? Have you setup journald to centralise the logs ?
On DESKTOP-L9HGLLK the akmods service has been killed 3 times by I guess a reboot.
The listing of /var/cache/akmods/nvidia/ only shows one log for today: the last
successful one. I’m working to modify akmods to keep all the logs.
Do you know how “install updates after restart” is implemented on this machine ?
I guess it should be a systemd service. It should be then safer to make akmods.service
start after it.
I have no idea how Linux works in the background.
I updated from the user one[2] because I was there, doing things, and when I restarted the PC I got the message “building stuff” with the MOBO’s and Fedora’s Logos; then I got to Login, and after that the KDE screen didn’t show up, but I could move the mouse, alt-tab (with nothing open) and Meta+Esc shower that System Monitor tried to start, but didn’t.
tl;dr I’ve already seen things like this in the 2+ years I’ve been with Fedora KDE, so I knew what to do.
It’s ok, but it’s not about VLC.
The user said —>
—> without giving me the correct command to get the logs, and another user’s command gave me logs as old as 1 month if not more.
I need a way to fish out that data from the log, if you can help with it, please.
I deleted the User account because I was having other problems which are not related to this one. ↩︎
Which has the default setting of “update once restarted”, since I didn’t change it yet, because it should not be a problem.↩︎
If you want to restrict the output of journalctl to recent logs and not see all the older stuff, a few ways are:
Use -b to specify a boot index. So journalctl -b 0 gives logs only from the current boot, journalctl -b -1 only from the previous one, journalctl -b -2 only from the one before that, etc.
Use --since with a relative timestamp, like the journalctl --since 1d that @francismontagnac showed earlier
Use --since with an absolute timestamp, for example journalctl --since "2026-04-18 12:00:00"
Ok: it was thus a manual update, not an automatic one as I thought.
Seeing an update of nvidia or of the kernel, you should wait a few minutes to give
time to akmods to build and install the nvidia driver. That’s sad yes: still work in
progress to fix that …
Rebooting too early may effectively make akmods fail repeatedly to properly build the
nvidia driver, and the fix is as you said: sudo akmods --rebuild --force (another
fix to come).
PS: Beware, I forgot to use sudo in my journalctl command. It worked for you
probably because your account is in the wheel group (as mine is).
This applies also to the logs you want to see in the other “Vulcan video ..” topic.
Indeed.
There’s no loading screen, or to better say it, it shouldn’t allow to reach Login IF AKMODS didn’t finishing to build… which should happen alongside all the other updates between the 0% and 100%…
That’s the thing, I didn’t “restart too early”, I restarted it when the PC told me to.
The account was set as “download first, update when booting”, as default, with 800+ things (grouped in a blob called “system updates”).
No, I just added Sudo afterwards.
Btw, I updated the Nvidia drivers TODAY, when the new ones came out.
Why is there anything AKMODS-related from yesterday?
:~$ journalctl --since 8d
Failed to parse timestamp: 8d
:~$ journalctl --since 1d
Failed to parse timestamp: 1d
:~$ journalctl --since 8g
Failed to parse timestamp: 8g
(The g is for giorni, because I’m italian and I tried just in case some setting were in italian, just to not have to try later.)
Doesn’t seem to work? ,':-/
I tried 8 days because It’s x+1 from when I needed the message for.
journalctl --since "2026-04-12 00:00:00" worked, but there are 50k lines for just 17 hours or logs.
Is there a way to filter the results for words like avcodec decoder?
I see now what means “install updates after restart”. This is also called “offline updates”.
I guess that you setup that with the plasma-discover GUI.
This is a known bug of akmods: when using offline updates, the automatic reboot at the end of the updates may happen too early. There is also a work in progress to correct that.
I think thus that it’s not worth to dig deeper for this case,
FWIW, there will be a somehow related change in plasma-discover with Fedora 44:
My bad: it would have been better to specify --since 00:00 instead of --since -1d
Ah, sorry. The akmods service is started at every boot. Its goal is to check that
every automatic kmod (akmod-*) has a corresponding kernel module
(kmod-KMOD-KERNEL_VERSION) installed for the current and default kernel, otherwise
attempt to build and install them.
Those logs show thus that you rebooted your machine around Apr 19 16:21 the day before
(on Sunday).
