Bug 497134 – Kernel image in /boot must start with kernel-

• Status: RESOLVED FIXED
• Product: [OLD] Docs on www.gentoo.org

[Description Sven Vermeulen (RETIRED) 2014-01-05 13:27:37 UTC]

Received e-mail on [e-mail]:

I never saw this in the Gentoo handbook - that the symlink name (mine happened to be 'linux-3.10.17-gentoo') is not always compatible with 
GRUB2's default settings for detecting the filename in /boot. When I copied my compiled bzImage to /boot, I simply used the
'linux-3.10.17-gentoo' tag as the filename, when it _needs_ to start with 'kernel' in order for `grub2-mkconfig` to detect it. Can you please
update this change into the docs, to make it apparent of this misleading flaw? Thank you. 

Reproducible: Always

[Comment 1 Graham Murray 2014-01-06 10:01:29 UTC]

Is this actually correct? The files in by /boot are of the form 'vmlinuz-xxxx' with the latest symlinked to vmlinuz (as created by 'make install' when building the kernel) and grub2-mkconfig finds them just fine.

[Comment 2 Sven Vermeulen (RETIRED) 2014-01-10 20:01:26 UTC]

The logic I found in GRUB:

case "x$machine" in
    xi?86 | xx86_64)
        list=`for i in /boot/vmlinuz-* /vmlinuz-* /boot/kernel-* ; do
                  if grub_file_is_not_garbage "$i" ; then echo -n "$i " ; fi
              done` ;;
    *)
        list=`for i in /boot/vmlinuz-* /boot/vmlinux-* /vmlinuz-* /vmlinux-* /boot/kernel-* ; do
                  if grub_file_is_not_garbage "$i" ; then echo -n "$i " ; fi
             done` ;;
esac

So for x86 and x86_64 systems, the file should be starting with "vmlinuz" or "kernel".

[Comment 3 Sven Vermeulen (RETIRED) 2014-04-12 06:13:59 UTC]

Paragraph updated in CVS for x86 and amd64.