BuzzPCSOS edora went in like a perfect install but then no boot 🙁
I took a look at the Fedora partition layout while installing Spiral OS and the two were significantly different. Spiral seems to have only one Btrfs partition whereas Fedora had two small unidentified partitions in front of the main Btrfs partition. I'm guessing Boot and Swap.
there is some big distro (Fedora) that makes like a 1MB [Mandatory Grub Boot] even if you did sysd uefi bootloader so maybe both are boots? but you would see that in gparted so weird.
BuzzPCSOS make Solus bootable by avoiding the boot partition and just making a single Ext4 partition and setting it's flag as boot with a mount of / (think that was what I did). Solus booted after the install but could not survive updates probably because new kernels would have been written to/expected to be in the non-existant boot partition.
that is either creative as heck or you have everything going to a single EFI bootloader used by other distro? does that work?
What a conundrum. I don't see a navigable way to do things here. Spiral not bad but not Solus. If this is a goof off laptop I'd even find and up and comer in Distrowatchs unapproved/waiting list. that's always fun to, if not temporary. might be a way to get a better feel for whats acceptable/unacceptable for the toshiba. crikey.
