Good morning everyone.

I have used Arch Linux and Slackware (current) in dual boot for about a year. I like these two distributions very much, for several reasons.
Until a few days ago I used them in Legacy (MBR) mode and made the decision to migrate to EFI (UEFI) mode, as my computer supports it. Before, I installed Arch first, completely, and then I installed Slackware (without Lilo, without Grub). Restarted the computer, entered the "arch-chroot / mnt", mounted the Arch partitions (/ and / home, for example) and asked him to find Slackware with the command grub-mkconfig -o / boot / grub / grub. cfg), after I reinstalled Grub ("grub-install /dev/sdx.... and maybe I didn't even need this reinstallation of GRUB).
Everything was fine, I did it. The only times I had problems with my dual boot was because of current updates (which sometimes gives some problems, for those who are not experts, as is my case) I simply reinstalled Slackware, again without Lilo and without Grub), and repeated the procedure of asking Arch to find Slackware with the command "grub-mkconfig -o /boot/grub/grub.cfg". Well, as I said at the beginning of my help request, I decided to switch my SSD to GPT and installed Arch creating the EFI partition [/ boot / efi] is required to install GRUB on it.
After this complete installation, I started to install Slackware (current) thinking about using the Arch Linux EFI partition. I noticed that during the installation of Slackware "automatically" the EFI partition (native to Arch) was detected and it was added to Slackware's FSTAB (I didn't add it). I followed the same procedure that I did when using Legacy / MBR and completed the installation of Slackware without installing either LILO or GRUB, as I was going to let Arch Linux GRUB manage the dual boot, as I always did. Restarting the computer, I asked Arch (arch-chroot ....) to locate Slackware to include it in GRUB. This time, using EFI, this process took a lot longer than it did before, maybe 5 minutes, but Arch found Slackware and added it to the GRUB boot. Finally the problem, which did not occur before: When updating Slackware, including the kernel, when I restarted the computer I saw that GRUB disappeared.
It was as if there was no distribution installed on the disc. I had to boot the pendrive with the Arch Linux ISO, go to arch-chroot, mount the Arch partitions and reinstall the complete GRUB. With that, I was able to find Slackware again. I certainly shouldn't be doing something that I should have done, to have this problem, after the first Slackware update. Before (Legacy / MBR) there was no such problem that occurred with having a / boot / efi partition, remembering that the only times I had a problem with current updates (when I updated the kernel, without problems) was something related the graphical interface (which had nothing to do with boot / GRUB).
I would really like to know what to do or how to do it, in order to have the same functionality, without major problems, in my dual boot of Arch with Slackware current (in UEFI / EFI).

I take this opportunity to ask you to reveal my imperfect English.

probably there are two ways to go if i were in your shoes ; either grub2 with efi from Arch or Elilo from slackware.

First pre-requisit to use uefi , you can disable the secure boot element but you need a gpt table partition on your HD and a circa 100 Mb partition using file type EF00 .

probably first to help even experts on here can you take a graphic of your HD using maybe gparted i,e a snapshot.

What I can tell you is that is that https://sourceforge.net/projects/ref...0.zip/download when put on a usb stick is an excellent tool that i found would boot my wifes Windows 10 64 bit PC with UEFI firmware and also my Slackware.

I don't know if I was clear enough. The SSD is in GPT. Secure boot is disabled. I had no problems installing either Arch or Slackware on EFI, having created a 512 mb EFi partition (as stated on the Arch Wiki). It seems to me that the problem is that when I install Slackware it automatically recognizes that there is an EFI partition (which already has Arch's GRUB) and adds it to FSTAB. I will go to the end, like this, without any problems (it is not recommended to install Elilo in this case, and I go straight through). Everything works, dual boot, I can use both systems. The problem, I believe, was when I updated Slackware (kernel), I probably should be forgetting to do something. When using dual boot with both in Legacy, everything was very smooth (neither installed Lilo nor Grub on Slackware, let Arch manage the boot). I want to find out how to have this dual boot, with this EFI partition, and be able to update everything normally in Slackware, without Grub disappearing.

Anyway, thanks for listening.

I have only two working, in dual boot. Grub 2 is on the EFI partition (512 nb) that is mounted on the Linux arch. Slackware was installed in second (without Lilo, without Elilo, without Grub, of course). I managed to redo Grub, after updating Slackware current (the kernel), calmly. The Slackware Fstab contains the "EFI" partition that at first belongs to Arch Linux (as I explained in the initial psotagem, this is done automatically when installing Slackware, it detects), but there is no initiator in Slackware, only in Arch. I'm using it here. I want to find out what remains to be done, configure it, so that when I go to update the Slackware kernel again (something I did without problems when the dual boot was on the Legacy / MBR machine), GRUB will not disappear again. There must be a way, and it is probably not complicated, but that only I ignore how to do it.

Here is an image.

The image

Attached Thumbnails

 

I know it's not really a newbie issue. But, I think I found the solution, after doing some tests here:

just comment (#) the "EFI partition" (which is on Arch Linux) and that Slackware automatically adds its FSTAB. When installing Slackware, after Arch, neither Lilo nor Elilo nor Grub. The solution was to let Arch's Grub manage the startup, commenting on Slackware's FSTAB "efi" before any updates.

\o/

After a kernel update in Slackware you can copy the vmlinuz and initrd.gz to . That way you don't overwrite the boot loader and don't need to edit Slackware's fstab. Also you can change boot loader with efibootmgr if you need to. slackpkg is updated in Current so you can't accidently run lilo after updating the kernel.

1 members found this post helpful.

I could only read your post now, thank you very much RadicalDreamer
Is noted here, your orientation \ o /

Hi,

For your future information look at Slackware Doc Project Maybe the project will help you with future Slackware work.
Hope this helps.
Have fun & enjoy Slackware!