Description of problem: Kernel (6.13.1-200) doesn't start, leaves a black screen saying "loading kernel 6.13 etc." and freezes there, in Huawei Matebook D15. Booting an old kernel works normally. Steps to Reproduce: 1.Install Fedora in Huawei Matebook D15 2.Update kernel to version 6.13 3.Try booting the system Actual results: System doesn't start. Expected results: System starting normally
I assume that you're not using systemd-boot and your report has nothing to do with systemd-boot. Do you mean 6.0.13? At least make a photo of the error and attach it here.
Created attachment 1946314 [details] Kernel not loading After booting from grub, this is what the frozen screen looks like.
(In reply to Zbigniew Jędrzejewski-Szmek from comment #1) > I assume that you're not using systemd-boot and your report has nothing to > do with systemd-boot. > > Do you mean 6.0.13? At least make a photo of the error and attach it here. Hi, I tried attaching the image of the bug. I'm new to Linux and this is the first time I report a bug, so I don't really now what to look for. The kernel is the one in the picture. If this is not systemd-boot related (I don't know, I read the label description and it seemed to me it could be that), can you please point me what the correct label is, so I can change it?
So it's 6.1.13-200.fc37.x86_64. The correct label in this case is generally 'kernel'. I already set to that now. Edit the grub command line to remove 'rhgb' and 'quiet'. (Press 'e' at the grub menu, and then do the edits and boot with ctrl-x. This is just a one-time modification that has no permanent effect.) Maybe you'll be able to see some more useful messages then. Please attach another photo in that case.
Created attachment 1946321 [details] output after removing rhgb and quiet
The interesting part is: VFS: Cannot open root device "nvme0n1p9" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) CPU: 3 PID: 1 Comm: swapper/0 Not tainted 6.1.13-200.fc37.x86_64 #1 Hardware name: HUAWEI BOHB-WAX9/BOBH-WAX9-PCB-B2, BIOS 1.42 03/25/2022 So this looks more more like a problem with the initrd rather than the kernel. Can you attach a) the kernel command line, b) the initrd ('ls /boot/*/6.1.13-200.fc37.x86_64/initrd' should show the path)
(In reply to Zbigniew Jędrzejewski-Szmek from comment #6) > The interesting part is: > VFS: Cannot open root device "nvme0n1p9" or unknown-block(0,0): error -6 > Please append a correct "root=" boot option; here are the available > partitions: > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(0,0) > CPU: 3 PID: 1 Comm: swapper/0 Not tainted 6.1.13-200.fc37.x86_64 #1 > Hardware name: HUAWEI BOHB-WAX9/BOBH-WAX9-PCB-B2, BIOS 1.42 03/25/2022 > > So this looks more more like a problem with the initrd rather than the > kernel. > Can you attach a) the kernel command line, > b) the initrd ('ls /boot/*/6.1.13-200.fc37.x86_64/initrd' should show the > path) I don't know how to do that. What should I do?
For the kernel command line: in the boot menu, press 'e' to edit, and then just take a picture of the text. For the initrd: boot into the working kernel, and attach the file /boot/*/6.1.13-200.fc37.x86_64/initrd. (The second component of the path should be a long hexadecimal number, e.g. it's /boot/64caa68cc47c42528071c0e1175bb34e/6.1.13-200.fc37.x86_64/initrd on my machine.)
Created attachment 1946335 [details] Kernel command line
(In reply to Zbigniew Jędrzejewski-Szmek from comment #8) > For the kernel command line: in the boot menu, press 'e' to edit, and then > just take a picture of the text. > For the initrd: boot into the working kernel, and attach the file > /boot/*/6.1.13-200.fc37.x86_64/initrd. > (The second component of the path should be a long hexadecimal number, e.g. > it's > /boot/64caa68cc47c42528071c0e1175bb34e/6.1.13-200.fc37.x86_64/initrd on my > machine.) I couldn't find any folder under /boot/ with an hexadecimal to use for the path /boot/*/; I found a hexadecimal number though, in the path /boot/loader/entries/; is that the number you're looking for? In /boot/loader/entries/346de757008a4818bd970ded9825aa02-6.1.13-200.fc37.x86_64.conf, I suppose 346de757008a4818bd970ded9825aa02 is the number(?)
Oh, oh. The kernel command line is OK, but the boot loader entry has no initrd! Please attach versions of packages: rpm -qa | grep -E 'grub2|systemd-udev|dracut'
(In reply to Zbigniew Jędrzejewski-Szmek from comment #11) > Oh, oh. The kernel command line is OK, but the boot loader entry has no > initrd! > > Please attach versions of packages: > rpm -qa | grep -E 'grub2|systemd-udev|dracut' This is the output from my terminal. dracut-057-5.fc37.x86_64 dracut-network-057-5.fc37.x86_64 dracut-live-057-5.fc37.x86_64 dracut-config-rescue-057-5.fc37.x86_64 dracut-squash-057-5.fc37.x86_64 systemd-udev-251.11-2.fc37.x86_64 grub2-common-2.06-88.fc37.noarch grub2-tools-minimal-2.06-88.fc37.x86_64 grub2-tools-2.06-88.fc37.x86_64 grub2-pc-modules-2.06-88.fc37.noarch grub2-pc-2.06-88.fc37.x86_64 grub2-efi-ia32-2.06-88.fc37.x86_64 grub2-efi-x64-2.06-88.fc37.x86_64 grub2-tools-extra-2.06-88.fc37.x86_64 grub2-efi-ia32-cdboot-2.06-88.fc37.x86_64 grub2-efi-x64-cdboot-2.06-88.fc37.x86_64 grub2-tools-efi-2.06-88.fc37.x86_64
It seems to be something on the interface between kernel-install and grub2 kernel-install plugin. Please attach 1) /boot/loader/entries/346de757008a4818bd970ded9825aa02-6.1.13-200.fc37.x86_64.conf 2) Run 'dnf history info kernel-core >/tmp/log.txt' and attach /tmp/log.txt
Created attachment 1947045 [details] /tmp/log.txt
Created attachment 1947046 [details] /boot/loader/entries/346de757008a4818bd970ded9825aa02-6.1.13-200.fc37.x86_64.conf
OK. So /boot/loader/entries/346de757008a4818bd970ded9825aa02-6.1.13-200.fc37.x86_64.conf has: linux /vmlinuz-6.1.13-200.fc37.x86_64 initrd /initramfs-6.1.13-200.fc37.x86_64.img This is what expect /usr/lib/kernel/install.d/20-grub.install to create. The installation log from dnf doesn't show anything out of place either. But as established in comment#9, the actual grub2 dynamic configuration created from this does not have an initrd line. In fact, it also has a different root= line. I'll reassign the bug to grub2, because the problem seems to be there, but I admit that I don't know what to make of this. One more question: please attach the output of 'sudo find /boot'.
Created attachment 1947273 [details] sudo find /boot
> /boot/initramfs-6.1.13-200.fc37.x86_64.img OK, so it really looks like grub2 makes up the invalid config entry out of thin air. ¯\_(ツ)_/¯
Hi, have you managed to resolve this, or are you still not able to boot this kernel? If you are still having problems, could you please paste the output of the commmands: lsblk -f and also grubby --info ALL (or alternately: cat /boot/loader/entries/*) thanks.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. 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 '37'. 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 37 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.
Fedora Linux 37 entered end-of-life (EOL) status on 2023-12-05. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.