Just uploaded new packages to the repos.

Thank you Didier. I will definitely take a close look.

That is nice.

During the last days, I've seen that Salix 15.0, with the default 5.15 kernel, fails to even boot some new hardware. It looks like we need an updated release with a newer kernel.

I have no idea how nordvpn works, what the software does and I don't have a nordvpn account.

Some ideas:
* Did you follow the instructions in the README? https://slackbuilds.org/repository/15.0/network/nordvpn/
* Does the service actually start? Try running the rc file manually:
sudo /etc/rc.d/rc ...

Ah, so you're not using a /boot partition for Salix as you're doing for the other OS. In that case, I believe just updating grub from the other OS will pick Salix up.

It is indeed a good idea. However, I'm not sure how what we will do for the next release. I've been playing with the idea of having only a live iso and either using djemos's installer, creating a new one, or trying to adapt one of the existing solutions for Salix (e.g. calamares)

You posted the same fdisk output twice. This should be the same from both installations anyway. Can you post the /etc/fstab from salix?

I wasn't expecting that. It seems that you're not using UEFI and using the legacy BIOS mode. In that case, you can skip those instructions about the EFI partition.

But you'll need to make sure that the /boot partition is common between the two distributions. If that output you provided is from the ...

Which EFI directories? There are no such folders in the /boot, nor the Salix one, nor the other one.
Edit: In the other OS, there is a /boot/efi directory, but it is empty.
From the other OS, you need to mount the EFI partition to the /boot/efi directory. What is the output of
sudo fdisk -l
and ...

I'm writing these from memory as I don't have grub here. You still need to copy the new kernel and initrd to the EFI directories. Only at the last step, you should run
sudo update-grub
instead.

Also make sure the initrd.gz file is mentioned in the /boot/grub/grub.cfg file.

Oh, and since you ...