When using akmods without specifying a kernel, the check_default_kernel function is not called because the init function initializes the kernels variable to the current kernel beforehand. Related lines in akmods: 185:init () 197: # fall back to current kernel if user didn't provide one 198: if [[ ! -n "${kernels}" ]] ; then 199: kernels="$(uname -r)" 200: fi 681:init 683:# only check for default_kernel if no value have been parsed 684:if [ -z "${kernels}" ] ; then 685: check_default_kernel 686:fi In addition, the calls to check_kernel_devel are wrong: 315: if [[ $(check_kernel_devel "${_kernel}" == 0) ]] ; then 602: if [[ $(check_kernel_devel "${1}" != 0) ]] ; then they should be: 315: if check_kernel_devel "${_kernel}" ; then 602: if ! check_kernel_devel "${1}" ; then Version used: https://kojipkgs.fedoraproject.org//packages/akmods/0.6.0/13.fc43/noarch/akmods-0.6.0-13.fc43.noarch.rpm The attached patch fixes that I think. Reproducible: Always
Created attachment 2096096 [details] akmods-fix-default-kernel.patch
Thanks for the patches, I've finally had room for tests (actually I haven't but hey! ) I've added the change you have suggested. make sense. I've also spotted another issue where grubby can be a symlink on upgraded system f42+ with unmerged-bin taint (in systemctl status) There is also the rhbz#2379766 that is little different, I will check this situation... Hopefully I will push the changes real soon.
Hi (In reply to Nicolas Chauvet (kwizart) from comment #2) > Thanks for the patches, > I've added the change you have suggested. make sense. Thanks. > I've also spotted another issue where grubby can be a symlink on upgraded system f42+ with unmerged-bin > taint (in systemctl status) Oups. Sorry, I missed that you found that also before commenting in rhbz#2379766
FEDORA-2025-37e985b13a (akmods-0.6.1-2.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2025-37e985b13a
FEDORA-2025-37e985b13a (akmods-0.6.1-2.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2025-33ea68b80b (akmods-0.6.1-2.el10_2) has been submitted as an update to Fedora EPEL 10.2. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-33ea68b80b
FEDORA-EPEL-2025-08996c0ee3 (akmods-0.6.1-2.el10_1) has been submitted as an update to Fedora EPEL 10.1. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-08996c0ee3
FEDORA-EPEL-2025-b5c526537e (akmods-0.6.1-2.el10_0) has been submitted as an update to Fedora EPEL 10.0. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-b5c526537e
FEDORA-2025-d5be7c00c4 (akmods-0.6.1-2.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-d5be7c00c4
FEDORA-2025-d5be7c00c4 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-d5be7c00c4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-d5be7c00c4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-08996c0ee3 has been pushed to the Fedora EPEL 10.1 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-08996c0ee3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-33ea68b80b has been pushed to the Fedora EPEL 10.2 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-33ea68b80b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-b5c526537e has been pushed to the Fedora EPEL 10.0 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-b5c526537e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-b18a85b925 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-b18a85b925` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-b18a85b925 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-d5be7c00c4 (akmods-0.6.1-2.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-b18a85b925 (akmods-0.6.1-2.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2025-33ea68b80b (akmods-0.6.1-2.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2025-08996c0ee3 (akmods-0.6.1-2.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2025-b5c526537e (akmods-0.6.1-2.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository. If problem still persists, please make note of it in this bug report.