safe installation fails to setup bootloader

[skinkie]

If it is booted in non-efi mode, it installs syslinux on an extra partition
If it is booted in efi mode, it is not executing bootctl install --esp-path=/mnt/clearlinux/boot hence uefi does not pick it up

Average user has no idea what to do after an installation.

Given #3141 will basically present any succesful boot, this should be a showstopper.

[bwarden]

Can you give us more detail on the platform you're installing on and the steps you're taking? If it's an esoteric hardware situation like in #3141 (hardware serial port issues), there may not be much we can do systemically.

[skinkie]

@bwarden I have experienced this on two laptops, an older HP one, and a Thinkpad T470. Both inhibit the exact same issues: the console must be removed at boot, and the EFI installation must be finished manually. So what do I do? I take the live distribution and just install.

[bwarden]

clr-boot-manager creates the UEFI boot entries by calling underlying APIs (not bootctl). Unfortunately, it's probably a quirk in HP's BIOS for those systems that it doesn't work as expected -- especially if they were originally shipped legacy-booting Windows. I would definitely check for BIOS updates, keeping in mind that the T470 is about 7 years old now.

Just to be clear, you were able to complete installation by running bootctl yourself, right?

[skinkie]

I was able to create a booting system after running bootctl manually. I was only able to succesfully boot clear-linux on both systems after removing console=ttyS0,115200n8.