Wishlist item only. It would be nice if akmods was run inside the dnf process or as part of it so that users can see that something is still happening. To use the new modules the user is likely going to need to reboot anyway and will likely sit there contemplating why their computer is waiting to reboot and may force reboot. I am usually updating via the terminal so I see the systemd-inhibit message, but how long the akmod process will take is unknown. Having it in or part of the dnf process would make it visible to the end-user that something is still happening and when it finishes.
Hi, we have 2 different phases to build new kmods, one is on kernel updated, other is on akmod-foo updated, when is on akmod-foo update maybe we can do something . The problem is on an dnf transaction we can do new rpms but we can't install it ...
Indeed, we need to release the dnf/rpm transaction in order to install our new packages, so that's not the way we can hold the transaction. The way forward is probably to conflict with shutdown until the package is installed, but then users may force poweroff their devices... which lead to another can of worms.
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle. Changing version to 36.
The best way would be to have an akmods-wait command that just wait for akmods to end and display any error if any (or use --verbose to connect to any WIP logs)
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
I don't believe this has been fixed so I'm moving it to F38.
Reworded the request to be more general. (not to assume the solution) I can expect an easy way to fix that for akmods.service when running as boot time with plymouth, but it looks like more difficult when running as kernel post-installation Maybe we could use an option for end-users to opt-in for desktop notification with notify-send...
I also add up to the issue : for me most of the time spent on my laptop is around 3 minutes longer than regular startup, probably due to the nvidia module compiling (afaik this time is correct), however I also find it disturbing and I even once hard rebooted my PC during akmods.service running... and resulted in breaking my system. My feeling here is the major issue is that users are not able to understand what's going on. Maybe just displaying a plymouth message (even without progress percentage) would be enough. "Kernel modules are updating, do not turn off your computer..." I don't know if such message can appear only when akmods service is starting to take a long time though (to prevent it displaying unnecessarily when it's short-lived)