Date: Sun, 19 May 2024 09:45:32 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 279154] loader.efi shows wrong kernel name, but boots correct kernel Message-ID: <bug-279154-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D279154 Bug ID: 279154 Summary: loader.efi shows wrong kernel name, but boots correct kernel Product: Base System Version: Unspecified Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: freebsd@kumba.dev NOTE: This is with FreeBSD 14.1-BETA2 I am not 100% on this yet, but I think I am seeing a bit of a visual bug in loader.efi. On an Intel NUC8i5BEH, I build and use a custom kernel that is installed to /boot/kernel.custom. In /boot, I create two symlinks: - "GENERIC" which points at /boot/kernel - "CUSTOM" which points at /boot/kernel.custom In /boot/loader.conf, I set these three variables: > kernels=3D"CUSTOM GENERIC" > kernel=3D"CUSTOM" > bootfile=3D"/boot/kernel.custom/kernel" Under 14.0-RELEASE, the boot menu would show for Item #6, this text: > 6. Kernel: default/CUSTOM (X of Y) But under 14.1-BETA2, I see this: > 6. Kernel: default/GENERIC (X of Y) Which shouldn't happen, because the default kernel is the first element in = the 'kernels' variable. However, despite what the menu shows, the correct kern= el, pointed at by "CUSTOM", is what is booted (likely because of the setting of= the 'kernel' variable or the bootfile variable). So I think this could be just a visual bug, but I am not 100% certain at the moment. I haven't updated a system using the classic BIOS loader yet to se= e if it's got the same bug. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-279154-227>