[SOLVED] Install elilo after you have installed slacware.

NaboHipersonico · 09-29-2022, 02:51 PM

Okay, now I've understood, if it's a text that I copied from you, it's where it should be, I've already done everything you've told me, I'm going to restart and see.

khronosschoty · 09-29-2022, 03:01 PM

I caught a slight error that might be in your refind.conf . See my last post for context. I think you got confused and might of added that later.

https://www.linuxquestions.org/quest...ml#post6383473

enorbet · 09-29-2022, 03:40 PM

Above all, my friend, don't get too discouraged. Manually configuring EFI boot is a fairly steep learning curve as you've noticed., At least it was for me because I had no way of understanding what exactly can be "seen" by the various bootloaders once /boot is no longer sacrosanct and /boot/efi/EFI is king.

Because I have several bootable systems it even took me an inordinate amount of time to discover the size limitations of whatever partitions the bootloader could see so that I had enough room for several kernels, configs and System.maps. I'm still not certain it needs anything more than to see the kernel image, only that having them (kernel specific config and System.map) works and the kernel takes up the most space.

In the interest of clarity I have /boot/efi/EFI include other directories. One is refind (/boot/efi/EFI/refind) which the refind-install script creates by default and I manually add /boot/efi/EFI/Slackware, /boot/efi/EFI/Suse, and /boot/efi/EFI/Windows. That way I keep them organized but it requires entering their full paths in /boot/efi/EFI/refind/refind.conf to get a working menu.

This is why my main entry for Slackware in refind.conf looks like this

Code:

 
###
menuentry "*SLACKWARE*-1564" {
  icon /EFI/refind/icons/slackware.png
    loader  /EFI/Slackware//vmlinuz-5.16.12
    options "root=/dev/nvme1n1p3 ro video=normal"
    #disabled
}
###

Note: I build a custom kernel and I don't use encryption so I don't need an initrd. The only step I need is to hardwire in kernrel config my root file system support for ext4. If you don't custom build you have only 2 choices - Huge, with no need for initrd.gz, or Generic, with an initrd.gz. Because I don't use initrd I am a bit confused why people running 15.0 are still using "mkinitrd" instead of "geninitrd" but maybe they can guide you in that if you wish to use the Generic kernel. Whichever you choose rEFInd needs to be told where they are. and wherever you choose must be somewhere in /boot/efi/EFI if I understand correctly/ Why in Hell EFI can't see into /boot is beyond me, but I suspect it is a Microsoft thing since Windows automatically installs reserved partitions and pays zero attention to what anyone else needs.

NaboHipersonico · 09-29-2022, 03:53 PM

Quote:

Originally Posted by khronosschoty

The entry in refind.conf that you said you copied and pasted to the end of your refind.conf... that refind.conf should be in /boot/efi/EFI/refind/ (if we're following the example I set)... much of this is just preference. You can define it, how you like, in the refind.conf.

also the initrd should be copied to the same location

Code:

 cp /boot/initrd.gz /boot/efi/EFI/

You'll need to update the kernel and make a new initrd and copy those each time to that location... whenever you change kernels e.g. you upgrade the kernel.

From the example you added to your refind.conf
the efi partition (the partition that has or the menuentry expects to have) will later be mounted to /boot/efi it contains a folder EFI... so in this example EFI folder sits in the root of the partition. That menuentry defines for refind the kernel to use and the intitrd (their names and locations).

BUT note your error here, "initrd -o /boot/initrd.gz" should be: initrd EFI/initrd.gz

At the moment it still doesn't work, tomorrow I'll check to see if I've done something wrong and we'll continue, today I'm going to sleep. Thanks for everything.

colorpurple21859 · 09-29-2022, 07:33 PM

This should work if you have copied a kernel to /boot/efi/EFI/vmlinuz.efi and /boot/initrd.gz to /boot/efi/EFI/initrd.gz

Code:

menuentry Slackware {
icon /EFI/refind/icons/os_slackware.png
loader /EFI/vmlinuz.efi
initrd /EFI/initrd.gz
options "root=/dev/sda7 ro video=normal"
}

NaboHipersonico · 09-30-2022, 03:04 AM

Hello everyone, I've been here for a while now and I think we're making progress.

One thing like I know if the generic kernel has loaded me?

if I do uname -r

I always get 5.15.63, it doesn't put anything generic

But it is that now, as a result of putting this file of @ colorpurple21859 and modifying a line, when I start it I get starting vmlinuz-generic-5.15.63, but I would say that the hugue keeps loading me, now I will tell you more things than I I have been aware.

I have realized that when putting what @colorpurple21859 comments:

menuentry Slackware {
icon /EFI/refind/icons/os_slackware.png
loader /EFI/vmlinuz.efi
initrd /EFI/initrd.gz
options "root=/dev/sda7 ro video=normal"
}

When putting this above, a new entry appeared in the menu, because I have realized that whatever I put in refind.conf, everything was always the same and the icon that the kernel panic gave, is a dead icon, although not put nothing in refind.conf, the icon is still there, so it's a fake kernel panic, it's from something that got caught there.

When I put the @ colorpurple21859, I saw that, a new icon appeared and when I hit enter, starting vmlinuz exited and the hugue kernel was loaded, so I changed a line:

menuentry Slackware {
icon /EFI/refind/icons/os_slackware.png
loader /EFI/vmlinuz-generic-5.15.63
initrd /EFI/initrd.gz
options "root=/dev/sda7 ro video=normal"
}

Changing that line, now it says starting vmlinuz-generic-5.15.63, but doing uname -r gives me 5.15.63, nothing generic.

I'm still investigating, now I'll put a picture of what I say.

I mean, in the menu I get the new option, I hit enter and the image comes out and then all the letters come out, passing quickly as always to the desktop, but I insist uname -r or uname -a, it always says 5.15.63 only.

hazel · 09-30-2022, 04:23 AM

Quote:

Originally Posted by NaboHipersonico

if I do uname -r

I always get 5.15.63, it doesn't put anything generic
.....
Changing that line, now it says starting vmlinuz-generic-5.15.63, but doing u[]name -r gives me 5.15.63, nothing generic.

I'm still investigating, now I'll put a picture of what I say.

I mean, in the menu I get the new option, I hit enter and the image comes out and then all the letters come out, passing quickly as always to the desktop, but I insist un[]ame -r or un[]ame -a, it always says 5.15.63 only.

The number given by un[]ame is the kernel's internal version number. If you build your own kernel, there's an option to add a suffix to it, otherwise it's just -X.Y.Z. X is the major version number, Y is the minor version and Z the latest patch.

However what you call the file the kernel code is loaded from is up to you (or up to the distro developer in practice). Slackware has two differently configured kernels for each version: -generic is a standard distro kernel with all its drivers compiled separately (kernel-modules package) and -huge is an integrated kernel with everything on board. In theory you can have any number of differently configured kernels all built out of the same source. u[]name won't care which one is loaded. If they were all built out of the same source code, they will all have the same version number.

PS: sorry for the weird spelling of a certain command but Cloudflare wouldn't let me post this answer without this.

NaboHipersonico · 09-30-2022, 04:35 AM

Quote:

Originally Posted by hazel

The number given by un[]ame is the kernel's internal version number. If you build your own kernel, there's an option to add a suffix to it, otherwise it's just -X.Y.Z. X is the major version number, Y is the minor version and Z the latest patch.

However what you call the file the kernel code is loaded from is up to you (or up to the distro developer in practice). Slackware has two differently configured kernels for each version: -generic is a standard distro kernel with all its drivers compiled separately (kernel-modules package) and -huge is an integrated kernel with everything on board. In theory you can have any number of differently configured kernels all built out of the same source. u[]name won't care which one is loaded. If they were all built out of the same source code, they will all have the same version number.

PS: sorry for the weird spelling of a certain command but Cloudflare wouldn't let me post this answer without this.

Hello. Thanks for the explanation, I already know all that. But as in other distributions if you do uname -r if you get named as generic, that's why.

So how do I know if I'm using the generic or the hugue if the terminal doesn't specify it?

marav · 09-30-2022, 04:56 AM

Quote:

Originally Posted by NaboHipersonico

Hello. Thanks for the explanation, I already know all that. But as in other distributions if you do uname -r if you get named as generic, that's why.

So how do I know if I'm using the generic or the hugue if the terminal doesn't specify it?

I for one, I know it because I chose it during the boot process
Otherwise

Code:

# dmesg | grep BOOT_IMAGE | cut -d- -f2 | head -1

NaboHipersonico · 09-30-2022, 05:06 AM

Quote:

Originally Posted by marav

I for one, I know it because I chose it during the boot process
Otherwise

Code:

# dmesg | grep BOOT_IMAGE | cut -d- -f2 | head -1

Hello. I enter the command in the console and nothing comes out:

bash-5.1$ su
Contraseña:
bash-5.1# dmesg | grep BOOT_IMAGE | cut -d- -f2 | head -1
bash-5.1#

In refind I get drawings and it doesn't put anything about kernel, that's why I don't know what I'm really choosing as it happens with grub.

NaboHipersonico · 09-30-2022, 05:19 AM

I have found these commands on the internet:

bash-5.1# cat /proc/cmdline
root=/dev/sda7 ro video=normal initrd=\EFI\initrd.gz
bash-5.1# dmesg | grep "Command line"
[ 0.000000] Command line: root=/dev/sda7 ro video=normal initrd=\EFI\initrd.gz
bash-5.1#

https://www.cyberciti.biz/faq/displa...rs-for-booted/

marav · 09-30-2022, 05:28 AM

Quote:

Originally Posted by NaboHipersonico

Hello. I enter the command in the console and nothing comes out:

bash-5.1$ su
Contraseña:
bash-5.1# dmesg | grep BOOT_IMAGE | cut -d- -f2 | head -1
bash-5.1#

In refind I get drawings and it doesn't put anything about kernel, that's why I don't know what I'm really choosing as it happens with grub.

You have to adapt regarding to the bootloader
The dmesg output for lilo is different from grub, same for elilo.

NaboHipersonico · 09-30-2022, 05:32 AM

Quote:

Originally Posted by marav

You have to adapt regarding to the bootloader
The dmesg output for lilo is different from grub, same for elilo.

The bootloader I am using is refind.

NaboHipersonico · 09-30-2022, 05:33 AM

More things I've discovered, I have an entry in refind that loads hugue, but it seems to be somewhere else:

As you can see in the image it says: EFI\Slackware\vmlinuz I think this is refind, not me and even if I delete the file that I put at the end of refind, this continues to appear and load the operating system.

A raiz de poner este archivo:

menuentry Slackware {
icon /EFI/refind/icons/os_slackware.png
loader /EFI/vmlinuz-generic-5.15.63
initrd /EFI/initrd.gz
options "root=/dev/sda7 ro video=normal"
}

It is when another icon appears like the one in the image, but it puts another route and it is the one that when starting it says starting vmlinuz-generic-5.15.63

If I delete the file, this icon disappears, but the one in the image is still there and working and, as you can see, it is in another path.

Nothing, in the end I got mixed up and since the posts cannot be deleted, I mean that there are entries with different addresses, but if the content of this one changes, that of the image, then it makes me panic kernel.

hazel · 09-30-2022, 05:33 AM

Try sudo dmesg|more and just scroll through. Near the top, you should find a line saying what file was loaded.

Your picture suggests that refind loaded the kernel via a symbolic link, so see what that link points to.