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.
I am used to lilo with legacy bios and old way of doings things.
Need the latest kernel for hardware support and have to patch it also but patch has nothing to do with question.
Got a new to me laptop with uefi bios I went with elilo during install.
how do I get the new kernel installed. I see /boot/efi/EFI/Slackware/elilo.conf
Do I put my new kernel in /boot/efi/EFI/Slackware ?
Do I need run anything? tried running eliloconfig but it just wiped out elilo.conf with default settings.
Last edited by mrapathy; 07-12-2018 at 01:10 PM.
Reason: Solved
My system didnt like that. Just rebooted I just had to use dvd to switch it back to default kernel.
Hello,
Quite strange, this is how i do when upgrading my kernel on my laptop.
I also compile my own custom kernel.
It's a dual boot UEFI system, windows 10 for my work and Slackware 14.2 64 bits for me.
When you wrote "switch it back" it mean that you used the backup done before in /boot/efi/EFI/Slackware ?
elilo needs to have all needed stuff: the boot loader, elilo.conf, the kernel, case occurring the initramfs, in the same directory, which is /bot/efi/EFI/Slackware.
For this reason the script eliloconfig puts there elilo.conf and copy there the kernel /boot/vmlinuz (or whatever kernel it points to if it is a symlink) and /boot/initrd.gz it it exists.
But you can edit manually afterwards /boot/efi/EFI/Slint/elilo.conf as you see fit. Just bear in mind that all files it refers to should live in the same directory (symlink are not available because we are in a FAT file system).
The good thing is you don't have to change the bootloader itself (elilo.efi) as it reads elilo.conf at boot time, possibly edited.
For the same reason you don't need to change the boot entry in the firmware's menu if you accepted that eliloconfig write one in it when asked.
So, before running eliloconfig, make sure that /boot/vmlinuz is or links to the kernel you want, or put manually what you need in /boot/efi/EFI/Slint and make sure that /boot/efi/EFI/elilo.conf mentions the files there.
For this reason the script eliloconfig puts there elilo.conf and copy there the kernel /boot/vmlinuz (or whatever kernel it points to if it is a symlink) and /boot/initrd.gz it it exists.
Damn !!
As i don't use initrd anymore, i forgeted to speak about it >.<.
It can be the reason why you did not boot properly with new kernel.
It cant be corrupt files cause I just patched and recompile the kernel a bunch of times. I dont know what is going wrong.
whenever I try to boot a custom kernel the system reboots instantly.
Strange. You built for the correct architecture I'm assuming?
You did copy vmlinuz to /boot/efi/EFI/Slackware and not just symlink right? Did you run ls -l on both to ensure they are the same size?
Sounds like something is seriously wrong with the build. If it was a problem with your initrd missing, you'd be more likely to see the machine ATTEMPT to boot the kernel, but then give a no init found error or something like that.
Strange. You built for the correct architecture I'm assuming?
You did copy vmlinuz to /boot/efi/EFI/Slackware and not just symlink right? Did you run ls -l on both to ensure they are the same size?
Sounds like something is seriously wrong with the build. If it was a problem with your initrd missing, you'd be more likely to see the machine ATTEMPT to boot the kernel, but then give a no init found error or something like that.
I copied vmlinuz to /boot and to /boot/efi/EFI/Slackware/
as is I have 4 vmlinuz in /boot/efi/EFI/Slackware/
I have 3 different files trying to boot. first is stock kernel from install
next two are from custom kernel /usr/src/linuz/arch/x86/boot/bzImage and the other is from
/usr/src/linuxarch/x86_64/boot/bzImage
my custom kernels will not boot they just do a instant reboot to bios.
I have no initrd in /boot/ or /boot/efi/EFI/Slackware/ or anywhere else in the system.
I have no initrd in /boot/ or /boot/efi/EFI/Slackware/ or anywhere else in the system.
You may have tried this, but elilo gave me trouble when I used a full path to the kernel in my elilo.conf, even though the path was correct. So with the kernel in the same directory as elilo.conf, it's just image=vmlinuz... rather than image=/path/to/vmlinuz...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.