Everyone:
The worst problem I have so far discovered about Fedora 42 is that the DNF updater does not work as it once did. The "updates ready" icon no longer shows, and one attempt I made to update packages with it, ended with a kernel entry in the boot loader (GRUB?) that causes a panic when I try to load it. This is Kernal Build 6:14.4 for the x86_64 architecture.
If I didn't retain two known good kernels with every upgrade, I would have "bricked" this computer. Happily, I have Build 6.14.3 available to use. But because it's not at the top of the list, I must consciously select it every time.
What I want to do is to install 6.14.4 in a working version. I'm guessing that I need to remove the corrupt 6.14.4 installation I have, then run, say, "sudu dnf upgrade --refresh" again and have that routine install the kernel "fresh." But I'm afraid to try to work out the commands, because I might remove all kernels and then my system would really be "bricked."
So: could someone tell me what commands to issue, in their proper order, to get Kernel build 6.14.3 working again?
Two outputs follow below.
Temlakos
____________________________________________________
[T******s@localhost ~]$ dnf list kernel.x86_64* Updating and loading repositories: Repositories loaded. Installed packages kernel.x86_64 6.14.2-300.fc42 updates kernel.x86_64 6.14.3-300.fc42 updates kernel.x86_64 6.14.4-300.fc42 <unknown> [T******s@localhost ~]$ dnf list --installed kernel* Installed packages kernel.x86_64 6.14.2-300.fc42 updates kernel.x86_64 6.14.3-300.fc42 updates kernel.x86_64 6.14.4-300.fc42 <unknown> kernel-core.x86_64 6.14.2-300.fc42 updates kernel-core.x86_64 6.14.3-300.fc42 updates kernel-core.x86_64 6.14.4-300.fc42 <unknown> kernel-devel.x86_64 6.14.2-300.fc42 updates kernel-devel.x86_64 6.14.3-300.fc42 updates kernel-devel.x86_64 6.14.4-300.fc42 <unknown> kernel-headers.x86_64 6.14.3-300.fc42 updates kernel-modules.x86_64 6.14.2-300.fc42 updates kernel-modules.x86_64 6.14.3-300.fc42 updates kernel-modules.x86_64 6.14.4-300.fc42 <unknown> kernel-modules-core.x86_64 6.14.2-300.fc42 updates kernel-modules-core.x86_64 6.14.3-300.fc42 updates kernel-modules-core.x86_64 6.14.4-300.fc42 <unknown> kernel-modules-extra.x86_64 6.14.2-300.fc42 updates kernel-modules-extra.x86_64 6.14.3-300.fc42 updates kernel-modules-extra.x86_64 6.14.4-300.fc42 <unknown> kernel-srpm-macros.noarch 1.0-25.fc42 fedora kernel-tools.x86_64 6.14.4-300.fc42 <unknown> kernel-tools-libs.x86_64 6.14.4-300.fc42 <unknown> [T******s@localhost ~]$
On 5/2/25 3:58 PM, Terry Hurlbut wrote:
The worst problem I have so far discovered about Fedora 42 is that the DNF updater does not work as it once did. The "updates ready" icon no longer shows, and one attempt I made to update packages with it, ended with a kernel entry in the boot loader (GRUB?) that causes a panic when I try to load it. This is Kernal Build 6:14.4 for the x86_64 architecture.
What "DNF updater" are you using?
If I didn't retain two known good kernels with every upgrade, I would have "bricked" this computer. Happily, I have Build 6.14.3 available to use. But because it's not at the top of the list, I must consciously select it every time.
There's a reason that previous kernel packages are kept.
What I want to do is to install 6.14.4 in a working version. I'm guessing that I need to remove the corrupt 6.14.4 installation I have, then run, say, "sudu dnf upgrade --refresh" again and have that routine install the kernel "fresh." But I'm afraid to try to work out the commands, because I might remove all kernels and then my system would really be "bricked."
You can't remove the running kernel.
So: could someone tell me what commands to issue, in their proper order, to get Kernel build 6.14.3 working again?
dnf remove kernel-core-6.14.4-300.fc42 dnf upgrade kernel
On Fri, May 2, 2025 at 6:58 PM Terry Hurlbut temlakos@gmail.com wrote:
Everyone:
The worst problem I have so far discovered about Fedora 42 is that the DNF updater does not work as it once did. The "updates ready" icon no longer shows, and one attempt I made to update packages with it, ended with a kernel entry in the boot loader (GRUB?) that causes a panic when I try to load it. This is Kernal Build 6:14.4 for the x86_64 architecture.
If I didn't retain two known good kernels with every upgrade, I would have "bricked" this computer. Happily, I have Build 6.14.3 available to use. But because it's not at the top of the list, I must consciously select it every time.
What I want to do is to install 6.14.4 in a working version. I'm guessing that I need to remove the corrupt 6.14.4 installation I have, then run, say, "sudu dnf upgrade --refresh" again and have that routine install the kernel "fresh." But I'm afraid to try to work out the commands, because I might remove all kernels and then my system would really be "bricked."
So: could someone tell me what commands to issue, in their proper order, to get Kernel build 6.14.3 working again?
Two outputs follow below.
Temlakos
[T******s@localhost ~]$ dnf list kernel.x86_64* Updating and loading repositories: Repositories loaded. Installed packages kernel.x86_64 6.14.2-300.fc42 updates kernel.x86_64 6.14.3-300.fc42 updates kernel.x86_64 6.14.4-300.fc42 <unknown> [T******s@localhost ~]$ dnf list --installed kernel* Installed packages kernel.x86_64 6.14.2-300.fc42 updates kernel.x86_64 6.14.3-300.fc42 updates kernel.x86_64 6.14.4-300.fc42 <unknown> kernel-core.x86_64 6.14.2-300.fc42 updates kernel-core.x86_64 6.14.3-300.fc42 updates kernel-core.x86_64 6.14.4-300.fc42 <unknown> kernel-devel.x86_64 6.14.2-300.fc42 updates kernel-devel.x86_64 6.14.3-300.fc42 updates kernel-devel.x86_64 6.14.4-300.fc42 <unknown> kernel-headers.x86_64 6.14.3-300.fc42 updates kernel-modules.x86_64 6.14.2-300.fc42 updates kernel-modules.x86_64 6.14.3-300.fc42 updates kernel-modules.x86_64 6.14.4-300.fc42 <unknown> kernel-modules-core.x86_64 6.14.2-300.fc42 updates kernel-modules-core.x86_64 6.14.3-300.fc42 updates kernel-modules-core.x86_64 6.14.4-300.fc42 <unknown> kernel-modules-extra.x86_64 6.14.2-300.fc42 updates kernel-modules-extra.x86_64 6.14.3-300.fc42 updates kernel-modules-extra.x86_64 6.14.4-300.fc42 <unknown> kernel-srpm-macros.noarch 1.0-25.fc42 fedora kernel-tools.x86_64 6.14.4-300.fc42 <unknown> kernel-tools-libs.x86_64 6.14.4-300.fc42 <unknown> [T******s@localhost ~]$
Reinstall the latest kernel:
sudo dnf update sudo dnf reinstall kernel kernel-core kernel-modules kernel-modules-core kernel-modules-extra
Be sure to include kernel-modules-extra. That's where your NIC adapter drivers likely reside.
Jeff
On Fri, May 2, 2025 at 4:58 PM Terry Hurlbut temlakos@gmail.com wrote:
one attempt I made to update packages with it, ended
with a kernel entry in the boot loader (GRUB?) that causes a panic
when I try to load it.
I have run into this. For some reason, the package files are installed, but it fails to build the initramfs file. This has happened on multiple machines of mine.
I fixed it this way:
# cd /boot # dracut initramfs-6.13.11-200.fc41.x86_64.img 6.13.11-200.fc41.x86_64
(change the kernel version in the dracut command to match the one you need to fix)
After that you should be able to reboot and select the kernel you just fixed.
But we shouldn't normally have to do this; something is clearly wrong here.
--Greg
Greg Woods composed on 2025-05-02 20:58 (UTC-0600):
Terry Hurlbut wrote:
one attempt I made to update packages with it, ended
with a kernel entry in the boot loader (GRUB?) that causes a panic
when I try to load it.
I have run into this. For some reason, the package files are installed, but it fails to build the initramfs file. This has happened on multiple machines of mine.
I have 41 & 42 on most of my PCs. On one of my Intel Kaby Lakes last month, 6.13.11 on 41 wouldn't get as far as Grub, and the initrd seemed normally built. Instead of getting stuck in Grub, it exited directly into BIOS setup, which I'd never heard of happening before, much less experienced. Instead of rerunning dracut, I removed all 6.13.11 packages and installed them again with same result. Instead of trying yet again, I removed 6.13.11 and installed 6.12.24, which worked normally. On 42, 6.13.11 gave me no such trouble, so I suspected 41 didn't like the 20250410 linux-firmware or intel-gpu-firmware for 6.13.11. Next time I use that PC it should get its first 6.14 kernels.....
-
Felix Miata -
Greg Woods -
Jeffrey Walton -
Samuel Sieb -
Terry Hurlbut