yes thats true colorpurple21859, I was just saying if you did want persistence, you know
I noticed too that some distros use syslinux in the efi/boot folder, not grub...have you tried throwing the contents of /boot/syslinux folder into EFI/BOOT folder?

No you have to use the syslinux.efi which is similar to the grub.efi but works with syslinux setup

https://wiki.syslinux.org/wiki/index.php?title=Install

ok I'll check that out thanks a bunch

The thing I was wondering, should I chroot into the newly copied over system in order to install eLilo ? Or do it from the system booted from the USB, also I'm not really sure of where I should have my boot set at since it is NVMe+UEFI, my bet would be to have the kernel alongside the boot files in the UEFI partition in the EFI/Slackware folder, but I'm sure of nothing and had no success so far.

I'm working on new iso today with uefi/efi support I hope...
If running from live usb/dvd did you try installing grub/lilo/elilo?
did you open a terminal and type in "pkgtool" and choose rerun slackware scripts then choose lilo/elilo install?
I believe you can also use the slackware dvd current to do same in setup menu
have you made the /etc/lilo.conf as in readme? and /etc/fstab?
thanks for trying it out and helping me too

Imma try this, and filling Lilo won't do anything as only eLilo is needed.

Also I filled the fstab and I dunno if I should also include the boot partition in it.

oh when I install linux distros I give each distro it's own partition, no seperate /home /boot etc partitions.
do efi systems make a seperate /boot partition?
if so, copy the boot and EFI folders there and kernel, then do mkinitrd command as in readme to make a hard drive initrd in /boot or EFI/BOOT/
colorpurple21859 has a efi system too so he knows more than me about it...

hopefully I'm helping you lol

The thing is, UEFI hardware needs a separate UEFI booting partition, to install the bootloader on, since I already have a big one that contains my Win10 installation, it becomes obligatory to use this one in order to properly install the loader, so yeah, a separate /boot is needed on EFI installations, I'm totes new to this too but I know it works that way...

It just tells me no EFI system partition is mounted on /boot/efi, which brings me to the fact I should chroot into the installed system and add the UEFI partiton to the fstab as /boot/efi

On efi systems I do the same thing, no seperate /home /boot etc partitions.
The efi partition can either be mounted manually to /boot/efi before running grub-install, elilo.confg. or have an entry in your fstab to mount the efi partition at boot time to /boot/efi. Elilo requires the elilo.config, kernel and initrd be in the same folder as the elilo.efi bootloader file on the efi partition. Grub just needs the grubx64.64 bootloader file to be on the efi partition. Not sure how syslinux.efi needs to be setup

Note This isn't written in stone as other distros may setup grub-efi differently, fedora based distros are one in that they set up grub efi differently and requires the grub.cfg to be on the efi partition also.

1 members found this post helpful.

Now though, is the version of GRUB2 shipped with Slackware_Current compatible with NVMe drives ?

I think it is but can't be for sure as I don't have any systems with NVMe drives.

So, correct me if I'm wrong, I mount the new installation path like this


mount /dev/nvme0n1p5 /mnt
mount -o bind /dev /mnt/dev
mount -o bind /proc /mnt/proc
mount -o bind /sys /mnt/sys

chroot in it with

chroot /mnt

and then

mount /dev/nvme0n1p1 /boot/efi

And then eliloconfig/grub-install ?

That should work

mount /dev/nvme0n1p5 /mnt
mount -o bind /dev /mnt/dev
mount -o bind /proc /mnt/proc
mount -o bind /sys /mnt/sys

chroot in it with

chroot /mnt /bin/bash
. /etc/profile

I did that, installed grub but the system won't boot.
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=grub
grub-mkconfig -o /boot/grub/grub.cfg
____________________________________________

Imma try with eLilo

1 members found this post helpful.

are you getting a grub prompt?
in chroot need to run grub-mkconfig -o /boot/grub/grub.cfg

edit try running grub-install like this grub-install --target=x86_64-efi