I installed Solus 4.3 and it doesn't handle setting up the bootloader correctly for me. I have 2 hard disks, one with Windows 10 Pro and the other with Solus 4.3. I had to disconnect the Windows 10 hard disk before installing Solus 4.3 because with the Windows 10 hard disk connected the Solus installer wouldn't create a 512mb EFI boot partition nor set up a bootloader. There was also no room after updating to update the kernel if I tried to install Solus with the Windows 10 hard disk connected.
Can someone help me fix this and get a bootloader working so I don't have to select from the BIOS/UEFI menu?
Note that I had to create a Solus boot file manually from within the BIOS/UEFI menu settings with trial and error. Had to do it manually to even be able to boot into Solus. Still no GRUB bootloader though.
I can't upload .txt files so I'll just post the structure below:
FS0: (Solus hard disk)
EFI
----Boot
--------BOOTX64.EFI
----systemd
--------systemd-bootx64.efi
----com.solus -project
--------kernel-com.solus-project.current.5.13.1-187
--------initrd-com.solus-project.current.5.13.1-187
loader
----loader.conf
----entries
--------Solus-current-5.13.1-187.conf
FS1: (Windows 10 hard disk)
EFI
----Microsoft
--------Boot
------------BCD
------------BCD.LOG
------------KDSTUB.DLL
------------MEMTEST.EFI
------------kd_02_10df.dll
------------kd_02_10ec.dll
------------kd_02_1137.dll
------------kd_02_14e4.dll
------------kd_02_15b3.dll
------------kd_02_1969.dll
------------kd_02_19a2.dll
------------KDB882~1.DLL
------------kd_07_1415.dll
------------kd_0C_8086.dll
------------winsipolicy.p7b
------------BOOTSTAT.DAT
------------BCD.LOG1
------------BCD.LOG2
------------BOOT.STL
------------BOOTMGFW.EFI
------------BOOTMGR.EFI
------------kdnet_uart16550.dll
------------bg-BG (Localization language directories)
------------" "
------------Fonts
----------------(Font files)
------------Resources
----------------BOOTRES.DLL
--------------------en-US
------------------------bootres.dll.mui
--------Recovery
------------BCD
------------BCD.LOG
------------BCD.LOG1
------------BCD.LOG2
----Boot
--------bootx64.efi
----systemd
--------systemd-bootx64.efi
----com.solus -project
--------kernel-com.solus-project.current.5.13.1-187
--------initrd-com.solus-project.current.5.13.1-187
loader
----loader.conf
----entries
--------Solus-current-5.13.1-187.conf
(BIOS/UEFI Images)
From this structure it looks like Solus put its boot files on both hard disks. I don't know if it's supposed to do that or not. For reference: https://discuss.getsol.us/d/1732-installing-solus-didn-t-create-bootloader-entry-in-bios/18 and https://discuss.getsol.us/d/5246-clr-boot-manager-insists-on-doing-things-in-boot-instead-of-on-esp-partition
Sorry for the many threads, my brain is just fried and Solus is by far my favorite GNU/Linux OS.
