Solus kernel location

Yav09

Solus is really great! 😀 But I have one problem: I dual boot. And every other OS stores it's kernel in the place it is installed, and thus, it is recognized by GRUB and added to the GRUB menu. But as Solus does not store it's kernel in it's partition, but in the EFI partition, GRUB recognizes it, but doesn't add it into the boot menu, because it doesn't know where the kernel is located. There is this post in the Manjaro forum: https://forum.manjaro.org/t/adding-solus-and-other-punk-linux-boot-sequence-in-grub-uefi-only/21405 , but I know this is kinda stupid, but if I use a theme, no icon shows up! Also, there probaly are people who just are not that good with computers to do this, and why not just start storing the Solus kernel in the disk Solus is installed for a more polished experience. It will also be nice to give users the option to install GRUB on a hard disk and use it as a bootloader.

(Sorry if the tag is not the right one, I just don't know which tag to put.)

just

Prefacing that my computers:

have only Linux(-es) installed
don't have WindOS
don't have EFI
don't have Grub 2

both kernel and initrd are stored in the regular Solus partition(s), where OS is installed, in the regular/boot folder. As in any other Linux:

$ dt && uname -a && ls -lh /boot/com* /boot/init*
Current datetime: 
2020-02-02 12:26:40

Linux alexsop.net 5.4.12-144.current #1 SMP PREEMPT Mon Jan 20 15:46:35 UTC 2020 x86_64 GNU/Linux
-rw-r--r-- 1 root root 11M Jan 26 08:19 /boot/com.solus-project.current.5.4.12-144
-rw-r--r-- 1 root root 29M Jan 26 08:19 /boot/initrd-com.solus-project.current.5.4.12-144
$

Kernel's location is probably different on computers, still infected by WindOS.

Yav09

just
I don't know... Unlike you, I have Windows installed and I have UEFI. The /boot folder is empty.

See how it is stored in the EFI partition (in my case, /dev/sda2):

¯＼(ツ)/¯
I think of creating a shortcut of the folder with Solus kernel and initrd to the partition Solus is installed. Will that work?

Justin

Sounds like you've installed your other OS in a legacy mode which uses GRUB. EFI is the current way to boot PCs.

I'd suggest backing up and re-installing the other OS in EFI mode, that way you can share Solus' EFI partition and boot either OS from there.

Yav09

Justin My PC comes with Windows pre-installed. I don't know how it was installed, but I really don't want to re-install Windows. I think all other operating systems are installed in UEFI mode.
I currently have these OSs installed.

Microsoft Windows 10 Home
Solus Fortitude Budgie
Debian 10 (Buster)
Linux Mint 19.3 (Tricia) Cinnammon

I also had installed FreeBSD (which couldn't boot, probaly because there wasn't enough space on the EFI partition, and GhostBSD (which made my Solus partition unallocated for some partitioning programs so Solus couldn't boot, it just hang on a black screen).

Justin

Yav09 /boot/ isn't mounted by default, only when an update takes place I believe. You can mount it manually if you want to look inside.

Yav09

Justin I know how to mount a partition, but I don't know how to mount a folder! How to do that?

Justin

Yav09 Well you mount a partition to a folder. For instance mine would be sudo mount /dev/nvme0n1p1 /boot/ yours will likely be different partition.

Yav09

Justin That would mount the EFI partition to /boot folder, and I think that must be pretty much useless...
Also, really, would creating a shortcut to the com.solus-project folder from the EFI partition (where Solus kernel and initrd are stored) and than placing it in the partition where Solus is installed (in my case: /dev/sda7) work?

Justin

A symlink between EFI partitions wouldn't work I imagine, it only looks at one at a time I believe.