Am 03.10.20 um 22:23 schrieb Chris Murphy:
> .... after investigating the problem with not finding grub.cfg in the proprosed
bootpath /boot/ .. the solution was simple.
>
> The system died not use secure boot, as secure-boot was disabled for the
kernel-surface kernelseries. They are not signed, so no secure boot possible.
>
> Means: bios is loading "/boot/grub2/grub.cfg" but it can't find it,
because those are symlinks to "/boot/efi/fedora/grub.cfg" but that is not
accessible, because the partition it's linked to, is not mounted there when grub
starts.
A grub2-install based grubx64.efi expects to find the grub.cfg in
/boot/grub2/grub.cfg. This OSLoader is not signed.
The grub2-efi-x64-2.04-31.fc33.x86_64 based grubx64.efi expects to
find the grub.cfg on the EFI system partition inside EFI/fedora/ and
this OSLoader is signed.
Basically you've stepped through the Looking Glass by using
grub2-install on a UEFI computer.
I believe this due to the way the system got installed in the first
place, which was via a secure booted livedisc. Later, as the usual
kernel build for Fedora did not support touch on the pro4, Jake Day's
5.1 kernel was build on the system, but i needed to be started without
secure boot.
now, the efi stuff is installed, i accept a few "oh, theres efi, i do
efi" mistakes from time to time. But i don't have a clue, how the system
could boot with those symlinks before that grub-install destroyed it.
And still,we do not know why the f33 livedisc does not boot at all when
inserted early
AND
why grub-install /dev/USBDRIVE (correct devicename ofcourse ) is
overwriting the ssd boot setup, instead of the usbdrive bootconfig.
best regards,
Marius