System won't boot after installing kernel-core-6.12.5-200.fc41.x86_64

himanshudodiya0 · December 21, 2024, 8:56am

Just downloaded the new kernel but system is not booting after installing it.

There are 3 versions of kernel is installed on my laptop

kernel-6.11.10-200.fc40.x86_64
kernel-6.12.4-200.fc41.x86_64
kernel-6.12.5-200.fc41.x86_64

And currently booted into 6.12.4.

Here is my system info :

# System Details Report
---

## Report details
- **Date generated:**                              2024-12-21 14:24:31

## Hardware Information:
- **Hardware Model:**                              Dell Inc. Latitude 7400
- **Memory:**                                      16.0 GiB
- **Processor:**                                   Intel® Core™ i5-8365U × 8
- **Graphics:**                                    Intel® UHD Graphics 620 (WHL GT2)
- **Disk Capacity:**                               (null)

## Software Information:
- **Firmware Version:**                            1.36.0
- **OS Name:**                                     Fedora Linux 41 (Workstation Edition)
- **OS Build:**                                    (null)
- **OS Type:**                                     64-bit
- **GNOME Version:**                               47
- **Windowing System:**                            Wayland
- **Kernel Version:**                              Linux 6.12.4-200.fc41.x86_64

Will happy to troubleshoot this if anyone have any idea how to resolve this? I won’t to try new kernel version as current kernel version 6.12.4 causing frequent disconnect of wifi and bluetooth.

jeree · December 21, 2024, 11:25am

Boot to old kernel and run:
sudo dracut --kver 6.12.5-200.fc41.x86_64

I have had the same problem with the last two updates, I hope they will fix it soon. I don’t want to run this for every future update.

barryascott · December 21, 2024, 11:28am

Are you seeing the problem with 3rd party dkms software not building against the new kernel?

himanshudodiya0 · December 22, 2024, 9:14am

Yup currently booted on 6.12.4 with selecting option on grub bootloader directly. Waiting for team fixes it.

Just to confirm are you facing issue with bluetooth and wifi too? As when I try to change wifi network it basically won’t connect (It just shows connecting) to any network and that’s the same for bluetooth as well.

inandegress1 · December 22, 2024, 9:45am

Same issue. Having to run dracut --regenerate-all -p after every kernel update

barryascott · December 22, 2024, 5:57pm

I could not find an existing bug report.
Raised 2333757 – initrd is not create if a dkms build fails leaving system boot to fail

captaintrips · December 22, 2024, 10:03pm

Had the same issue coming from 6.11.(something) to 6.12.5-200.x86_64. Had a kernel panic on the 6.12.5-200 after reboot, threw a fit about initramfs.

Rebooted into prior kernel, ran the suggested dracut command:
dracut --kver 6.12.5-200.fc41.x86_64

Rebooted and the new kernel did throw a “dkms.service failed to start” but booted successfully after a few moments.

After login, I checked “systemctl status dkms.service”, was in failed state and wouldn’t restart…log output from status showed that “anbox-binder” and “anbox-ashmem” were the cause.

Took the following steps to fully resolve:

Reinstalled the relevant to make sure nothing was missed or corrupt
sudo dnf reinstall kernel-devel kernel-headers

(to confirm the packages matched the kernel)
uname -r
rpm -q kernel-devel kernel-headers

get bad dkms modules all cleaned up, again in this case looks like it was Anbox modules
sudo dkms remove anbox-binder/1 --all
sudo dkms remove anbox-ashmem/1 --all
sudo dkms autoinstall --verbose

make sure dkms was all updated
sudo dnf update dkms

restart and verify the dkms unit was successfully started
sudo systemctl restart dkms.service
sudo systemctl status dkms.service

voila… resolved. After reboot, dkms no longer complains when booting into 6.12.5-200.x86_64.

captaintrips · December 22, 2024, 10:23pm

I would personally advise not regenerating against all installed kernels (could potentially bust working prior kernels… unlikely, but just cautionary), and only the latest affected one.

So instead of:
dracut --regenerate-all -p

Do that only the latest kernel having the issue:
dracut --kver 6.12.5-200.fc41.x86_64

again, thats just personal suggestion for safety. Don’t regenerate for what’s already working is a bit safer.

himanshudodiya0 · December 25, 2024, 7:39am

Tried dracut for 6.12.5-200.fc41.x86_64 but not worked showing same kernel panic screen.

Verified if it generated new img file, and yes it does

root@fedora:/boot# ls -lrth
total 343M
drwx------. 6 root root 4.0K Jan  1  1970 efi
drwx------. 2 root root  16K Jul 28 00:03 lost+found
drwxr-xr-x. 3 root root 4.0K Jul 28 00:05 loader
-rwxr-xr-x. 1 root root  15M Jul 28 00:06 vmlinuz-0-rescue-05048653076d4700992ea5f2ce7ebf08
-rw-------. 1 root root 155M Jul 28 00:06 initramfs-0-rescue-05048653076d4700992ea5f2ce7ebf08.img
-rwxr-xr-x. 1 root root  16M Nov 22 05:30 vmlinuz-6.11.10-200.fc40.x86_64
-rw-r--r--. 1 root root 9.6M Nov 22 05:30 System.map-6.11.10-200.fc40.x86_64
-rw-r--r--. 1 root root 272K Nov 22 05:30 config-6.11.10-200.fc40.x86_64
-rw-------. 1 root root  36M Dec  8 15:15 initramfs-6.11.10-200.fc40.x86_64.img
-rw-r--r--. 1 root root 179K Dec  8 15:15 symvers-6.11.10-200.fc40.x86_64.xz
-rwxr-xr-x. 1 root root  16M Dec  9 05:30 vmlinuz-6.12.4-200.fc41.x86_64
-rw-r--r--. 1 root root  11M Dec  9 05:30 System.map-6.12.4-200.fc41.x86_64
-rw-r--r--. 1 root root 274K Dec  9 05:30 config-6.12.4-200.fc41.x86_64
-rwxr-xr-x. 1 root root  16M Dec 15 05:30 vmlinuz-6.12.5-200.fc41.x86_64
-rw-r--r--. 1 root root  11M Dec 15 05:30 System.map-6.12.5-200.fc41.x86_64
-rw-r--r--. 1 root root 274K Dec 15 05:30 config-6.12.5-200.fc41.x86_64
-rw-------. 1 root root  30M Dec 20 00:10 initramfs-6.12.4-200.fc41.x86_64.img
-rw-r--r--. 1 root root 179K Dec 20 00:10 symvers-6.12.4-200.fc41.x86_64.xz
-rw-r--r--. 1 root root 179K Dec 21 13:57 symvers-6.12.5-200.fc41.x86_64.xz
-rw-------. 1 root root  30M Dec 25 12:57 initramfs-6.12.5-200.fc41.x86_64.img
drwx------. 4 root root 4.0K Dec 25 13:03 grub2
root@fedora:/boot# date
Wednesday 25 December 2024 01:03:47 PM IST

Also checked dkms service status, it is exited:

Service status :

root@fedora:~# systemctl status dkms
● dkms.service - Builds and install new kernel modules through DKMS
     Loaded: loaded (/usr/lib/systemd/system/dkms.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf, 50-keep-warm.conf
     Active: active (exited) since Wed 2024-12-25 13:00:26 IST; 5min ago
 Invocation: e2d749d0846a4e8f9941d0069d73ab5a
       Docs: man:dkms(8)
    Process: 1042 ExecStart=/usr/sbin/dkms autoinstall --verbose --kernelver 6.12.4-200.fc41.x86_64 (code=exited, status=0/SU>
   Main PID: 1042 (code=exited, status=0/SUCCESS)
   Mem peak: 27.8M
        CPU: 162ms

Dec 25 13:00:25 fedora systemd[1]: Starting dkms.service - Builds and install new kernel modules through DKMS...
Dec 25 13:00:26 fedora systemd[1]: Finished dkms.service - Builds and install new kernel modules through DKMS.

Below are the journalctl logs:

-- Boot ba1d368151164cf5be1e7a69acd78998 --
Dec 25 12:56:36 fedora systemd[1]: Starting dkms.service - Builds and install new kernel modules through DKMS...
Dec 25 12:56:37 fedora systemd[1]: Finished dkms.service - Builds and install new kernel modules through DKMS.
Dec 25 12:59:10 fedora systemd[1]: dkms.service: Deactivated successfully.
Dec 25 12:59:10 fedora systemd[1]: Stopped dkms.service - Builds and install new kernel modules through DKMS.
-- Boot f9efa4bdad054b9ba13e9c45dd76beef --
Dec 25 13:00:25 fedora systemd[1]: Starting dkms.service - Builds and install new kernel modules through DKMS...
Dec 25 13:00:26 fedora systemd[1]: Finished dkms.service - Builds and install new kernel modules through DKMS.

Anything I can check further to resolve this?

hendrik-s · December 25, 2024, 7:14pm

I had the same problem. Issuing a ˋsystemctl restart dkmsˋ showed for me that 3 modules, all unrelated to each other, caused the error.

displaylink-driver (evdi from GitHub - displaylink-rpm/displaylink-rpm: RPM sources for the DisplayLink USB display adapters). Uninstalled it, as I don’t really use it.
oscdriver from Open Super Clone. Same approach, uninstalled the package.
rts5229 driver (from GitHub - Zibri/Realtek-rts5229-linux-driver: Realtek card reader driver for kernel >4.4.x (ubuntu 16.04-17.10 have broken driver and all kernels up to 4.15.0-041500rc1)) for the internal sd card slot in my NUC. Removed that as well, but haven’t found time yet to reboot and see if the sd card reader still works with newer kernel version (was broken in older ones).

Do more a matter unrelated to Fedora or the kernel, more other modules that were not updated.

Merry Christmas all!
*

himanshudodiya0 · January 5, 2025, 8:03am

Just an update:

I installed 6.12.7 kernel version and it showed the same kernel panic error so tried dracut and it worked

root@fedora:~# uname -r
6.12.7-200.fc41.x86_64

After all this wifi option is not showing though…

hendrik-s · January 5, 2025, 11:40am

Doesn’t dracut warn you that you may have to manually enable or include wifi and bluetooth? I believe my laptop had that warning, although there everything worked.
May still be worthwhile for you to figure out what kills the creation of the initfs (see my last post before yours) and sort that problem out. Likely some non-stnadard module that needs updated source, may not be needed anymore or simply is not maintained and does not compile anymore.

himanshudodiya0 · January 5, 2025, 1:58pm

Nope, I didn’t see any warnings but bluetooth is working fine after upgrade to kernel 6.12.7 unlike wifi.

gnwiii · January 5, 2025, 2:20pm

This Dell Latitude 7480 with 1.40.0 firmware gave the error you show for all installed kernels and also USB installer keys. Using the Dell BIOS configuration, I used the option to add a boot entry, which filled in the fields and gave Boot0003 (Fedora2) that works:

% efibootmgr  
BootCurrent: 0003
Timeout: 0 seconds
BootOrder: 0003,0002,0001
Boot0001* Fedora	HD(1,GPT,a9b8f5c8-95d9-4899-a355-e9fbeb547be8,0x800,0xfa000)/\EFI\fedora\shimx64.efi
Boot0002* Linux Firmware Updater	HD(1,GPT,a9b8f5c8-95d9-4899-a355-e9fbeb547be8,0x800,0xfa000)/\EFI\fedora\fwupdx64.efi
Boot0003* Fedora2	PciRoot(0x0)/Pci(0x1d,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-25-38-5A-01-9E-5A-56)/HD(1,GPT,a9b8f5c8-95d9-4899-a355-e9fbeb547be8,0x800,0xfa000)/\EFI\fedora\shimx64.efi

Some documents indicate that the grub2 HD() format is not universally supported, but haven’t had time to fully investigate.

himanshudodiya0 · January 5, 2025, 2:34pm

Thanks for the reply. After upgrading to 6.12.7, I was able to boot. And regarding grub2 not supporting HD(), maybe it is because of efi systems.

Topic		Replies	Views
Kernel 6.9.x won't boot after upgrade Ask Fedora wayland , gnome , intel , silverblue	3	720	June 22, 2024
Last 3 kernel update i have error initramfs not generated Ask Fedora wayland , gnome , nvidia , f41	3	93	January 5, 2025
New kernel - Fedora don't start - ASUS S5602ZA Ask Fedora f38	3	350	June 17, 2023
Kernel issues with fedora 39 with higher version than 6.9.8-100.fc39 Ask Fedora	2	65	November 28, 2024
Fedora not booting after kernel update Ask Fedora f38 , amd , kernel	3	578	October 23, 2023

System won't boot after installing kernel-core-6.12.5-200.fc41.x86_64

Related topics