elilo-c(line 77): Kernel file not found umlinuz-huge-5.15.154
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
elilo-c(line 77): Kernel file not found umlinuz-huge-5.15.154
Hello All ,
A Very frustrating issue here , the item that is being complained about IS there and IS a bzImage file ...
the one hint the 'elilo.c(line 77):Kernel file' could either be a line in the original elilo.c file or it thinks there is a line 77 in lilo.conf and the rest of the file name is being stripped off ...
More info comeing in a bit . Enabling the serial console .
I'll also look into the elilo.c file , to hopefully garner some insight .
The vmlinuz-huge-5.15.154 is a locally complied kernel .
Please see what I have below & the attched elilo.conf file .
Below is hand typed in from a photo ...
Code:
read_config=Success
selected chooser simple
command list (must be first character):
=:print device list, %:print variable list, &:print paths, ?:help
TAB:print label infrmation
default file path: scsi0:\EFI\Slackware\
config file: \EFI\Slackware\elilo.conf
ELILO boot: ..........
kernel is 'vmlinuz-huge-5.15.154'
arguments are ' root=PARTUUID=4856b1c5-xxxx-yyyy-zzzz-xyzxyzxyzxyz vg...
sbcore-autosuspend=-1 ro ipu6.disable=1 ro'
initrd is 'vmlinuz-huge-5.15.154-initrd-gz'
elilo.c(line 77):Kernel file not found vmlinuz-huge-5.15.154
First one is visible to the one time boot menu in elilo ...
Next one says Not Found from above ...
Code:
# file /boot/efi/EFI/Slackware/vmlinuz-huge-5.15.145
/boot/efi/EFI/Slackware/vmlinuz-huge-5.15.145: Linux kernel x86 boot executable bzImage, version 5.15.145 (root@z-mp.slackware.lan) #1 SMP PREEMPT Sun Dec 24 00:07:06 CST 2023, RO-rootFS, swap_dev 0XB, Normal VGA
# file /boot/efi/EFI/Slackware/vmlinuz-huge-5.15.154
/boot/efi/EFI/Slackware/vmlinuz-huge-5.15.154: Linux kernel x86 boot executable bzImage, version 5.15.154 (root@replaceme.baby-dragons.com) #1 SMP PREEMPT Fri Apr 12 18:02:35 AKDT 2024, RO-rootFS, swap_dev 0XB, Normal VGA
# file /boot/efi/EFI/Slackware/vmlinuz-huge-5.15.145-initrd.gz
/boot/efi/EFI/Slackware/vmlinuz-huge-5.15.145-initrd.gz: gzip compressed data, max compression, from Unix, original size modulo 2^32 33037824
# file /boot/efi/EFI/Slackware/vmlinuz-huge-5.15.154-initrd.gz
/boot/efi/EFI/Slackware/vmlinuz-huge-5.15.154-initrd.gz: gzip compressed data, max compression, from Unix, original size modulo 2^32 29868544
If you are booting huge kernels, you do not need an initrd.
Since you are booting x86, both kernels should be huge-smp, or generic-smp with appropriate initrd. "kernel not found" can also mean "no suitable kernel found" and not that the file is missing. There may have been changes to 5.15.154 that now require you to use smp kernel - especially if you are on a x86_64 CPU.
Where did you get 5.15.154? I do not see it in the Official Slackware ChangeLog. Did you compile it yourself?
Yes this is locally built kernel , I did mention that in the original post .
download of sources from www.kernel.org &
I copied the config-huge-5.15.145.x64 from /boot/ ...
Code:
cd /usr/src/linux
make mrproper
cp /boot/config-huge-5.15.145.x64 .config
make olddefconfig
make V=1 KBUILD_VERBOSE=1 prepare
make -j 3 V=1 KBUILD_VERBOSE=1 all
make -j 3 V=1 KBUILD_VERBOSE=1 modules_install
# since /usr/src/linux/arch/x86_64/boot/bzImage is a link to ../../x86/boot/bzImage
cp /usr/src/linux/arch/x86/boot/bzImage /boot/efi/EFI/Slackware/vmlinuz-huge-5.15.154
mkinitrd ...
Had a brain fart & thought I might have used a differant /dev/disk/by-uuid , in the mkinitrd .
It seems I did not ...
This is the reason for my confusion .
That there is nothing substantially odd between the two .
1) I don't use initrd. Problem persists if you have two-three "long" vmlinuz names. I noticed this some time ago as I have only custom kernels (all without initrd by the way) at least three at a time.
You can have one longer name though that is why users following default Slackare kernel don't see the problem. The issue is not related to elilo per se as I never upgraded elilo since 2021. The problem was gone for some time but recently reappeared. I never mentioned it because elilo is dying so I doubt that there is an interest in fixing the issue.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.