03:16 <zzUzz> So I was able to get void running on a btrfs volume using GRUB!! but I would rather use systemd/gummi-boot (or rEFInd or something else! Im open to suggestions). I tried simply using bootctl install, which gave me ```Failed to write 'LoaderSystemToken' EFI variable: Read-only filesystem```

03:18 <tpw_rules> systemd-boot works fine but you have to give it a flag to say not to write to efi variables

03:18 <tpw_rules> uboot doesn't support that

03:24 <zzUzz> Is that flag "--graceful"? Using it returns ```Failed to create EFI Boot variable entry: Read-only file system```

03:25 <zzUzz> Wait I think I found it

03:28 <zzUzz> I tried --no-variables, and while it appeared to succeed, It ended up the same as ```bootctl install``` with no flags

03:30 <tpw_rules> i'm not sure, i use systemd-boot on nixos just fine

03:31 <tpw_rules> what files is it installing?

03:37 <zzUzz> ``Copied "/usr/lib/systemd/boot/efi/systemd-bootaa64efi" to "/boot/efi/EFI/systemd-bootaa64.efi"```

03:37 <zzUzz> ```Copied "/usr/lib/systemd/boot/efi/systemd-bootaa64.efi" to "/boot/efi/EFI/BOOT/BOOTAA64.EFI"```

03:37 <tpw_rules> that looks about right

04:14 <zzUzz> The error I get from the U-Boot side is: basically "Booting: nvme 0 \ No loader found. Configuration files in \loader\entries\*.conf are needed." and then "Booting /\EFI\BOOT\BOOTAA64.EFI \ No Loader found. Configuration files in \loader\entries\*.conf are needed"