LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   14.2: new to elilo, checking procedure for kernel upgrades (https://www.linuxquestions.org/questions/slackware-14/14-2-new-to-elilo-checking-procedure-for-kernel-upgrades-4175639321/)

rshepard 09-27-2018 04:51 PM

14.2: new to elilo, checking procedure for kernel upgrades
 
This is the first motherboard that supports elilo. I see that in /boot/efi/EFI/Slackware/ are three files: elilo.conf, elilo.efi, and vmlinuz.

Am I correct in assuming that when I upgrade the stock 4.4.14 kernel to the latest 4.4.157 I do the following:

1) in /boot, run mkinitrd
2) cp (mv?) initrd.gz to /boot/efi/EFI/Slackware/
3) in /boot, re-link vmlinuz to vmlinuz-generic-4.4.157
4) cp vmlinuz to /boot/efi/EFI/Slackware
5) edit elilo.conf to add both image=initrd.gz and add a second stanzq pointing to /boot/vmlinuz-huge-4.4.157

franzen 09-28-2018 02:47 AM

Quote:

Originally Posted by rshepard (Post 5908619)
This is the first motherboard that supports elilo. I see that in /boot/efi/EFI/Slackware/ are three files: elilo.conf, elilo.efi, and vmlinuz.

Am I correct in assuming that when I upgrade the stock 4.4.14 kernel to the latest 4.4.157 I do the following:

1) in /boot, run mkinitrd
2) cp (mv?) initrd.gz to /boot/efi/EFI/Slackware/
3) in /boot, re-link vmlinuz to vmlinuz-generic-4.4.157
4) cp vmlinuz to /boot/efi/EFI/Slackware
5) edit elilo.conf to add both image=initrd.gz and add a second stanzq pointing to /boot/vmlinuz-huge-4.4.157

EDIT: I did that on -current, don't know what that does on 14.2

No.
I was using efi also the first time this week on two laptops. On the one machine that has a proper efi firmware, on a kernel update i did:
Code:

/usr/share/mkinitrd/mkinitrd_command_generator.sh -k NEWKERNELVERSION | /bin/bash
eliloconfig

and all went fine.

This uses the kernel where /boot/vmlinuz points to, which in my case is kernel-generic.

rshepard 09-28-2018 10:34 AM

Quote:

Originally Posted by franzen (Post 5908745)
EDIT: I did that on -current, don't know what that does on 14.2

No.
I was using efi also the first time this week on two laptops. On the one machine that has a proper efi firmware, on a kernel update i did:
Code:

/usr/share/mkinitrd/mkinitrd_command_generator.sh -k NEWKERNELVERSION | /bin/bash
eliloconfig

and all went fine.

This uses the kernel where /boot/vmlinuz points to, which in my case is kernel-generic.

Franzen,

I'm unclear on what you're telling me. You wrote that you used the four steps I listed on -current, then you write "no' to my applying them to 14.2?

When I asked a SBo package maintainer about running the mkinitrd shell script he told me to just use the regular command sequence; that's worked for him on his EFI-enabled systems.

This motherboard, and Asus Prime X470-Pro is designed to support UEFI and that's what Slackware is using when it boots.

Thanks,

Rich

bassmadrigal 09-28-2018 10:42 AM

Quote:

Originally Posted by rshepard (Post 5908619)
This is the first motherboard that supports elilo. I see that in /boot/efi/EFI/Slackware/ are three files: elilo.conf, elilo.efi, and vmlinuz.

Am I correct in assuming that when I upgrade the stock 4.4.14 kernel to the latest 4.4.157 I do the following:

1) in /boot, run mkinitrd
2) cp (mv?) initrd.gz to /boot/efi/EFI/Slackware/
3) in /boot, re-link vmlinuz to vmlinuz-generic-4.4.157
4) cp vmlinuz to /boot/efi/EFI/Slackware
5) edit elilo.conf to add both image=initrd.gz and add a second stanzq pointing to /boot/vmlinuz-huge-4.4.157

There is no need to relink vmlinuz in your /boot directory. That was used previously to keep your lilo.conf simple (it would just point to the symlink, which would then point to the main file and would be automatically updated when new kernels were installed).

Basically, you'll need to make sure that your initrd and kernel are both in the /boot/efi/EFI/Slackware directory (can be a cp or an mv -- I always do a cp to keep the original files in /boot/ for historical reasons... AFAIK, there's no technical reason to keep them there), then make sure your elilo.conf references the correct filenames. There's no equivalent of running lilo for elilo since the UEFI firmware can read the config file when booting.

If you do have two entries, elilo does not display a prompt like lilo did. You can press enter or wait for the timeout to select the default/first entry. You would need to press tab to view the other entries and then, I believe, you need to type the label you want and press enter to boot it.

rshepard 10-03-2018 09:10 AM

Thanks, both of you. Once I went through the upgrade from the distribution's 4.4.14 to the most current 4.4.157 the process became (ahem!) "intuitive."


All times are GMT -5. The time now is 05:11 PM.