Open haobinnan opened 2 years ago
@julian-klode
Hi,
The data in the figure is from UEFI boot**** Area 1 and area 2 are a boot entry record data of boot0000 (UEFI boot entry created by Windows)
Area 3 is boot0001 I created through the efibootmgr tool. Both boot0000 and boot0001 point to \EFI\Microsoft\Boot\Bootmgfw.efi (it is actually shimx64.efi) The difference between boot0000 and boot0001 is that the boot0000’s area 2 has additional data for the UEFI boot entry. boot0000 is generated by Windows.
Boot0001 created by efibootmgr does not have following messages, and it does not have this additional boot entry data (area 2). I suspect that the following error may be caused by the additional data of the additional boot entry boot0000.
{
Failed to open \EFI\Microsoft\Boot\S - Invalid Parameter
Failed to load image : Invalid Parameter
start_image() returned Invalid Parameter, falling back to default loader
}
@julian-klode
This question seems to be similar to the question of this link. https://github.com/rhboot/shim/issues/370
This question seems to be similar to the question of this link. #370
Yes
Hi, The shim I'm currently using is version 15.6 (https://github.com/rhboot/shim/releases/tag/15.6), I haven't added any other patches to it, but every time the computer boots, I get error messages. I remember that 15.4 has this problem too. Is it because I use it properly, or is there any other reason? shim and grub2 deployment paths: \EFI\Microsoft\Boot\bootmgfw.efi (it’s actually shim) \EFI\Microsoft\Boot\grubx64.efi(grub2)
Failed to open \EFI\Microsoft\Boot\S - Invalid Parameter Failed to load image : Invalid Parameter start_image() returned Invalid Parameter, falling back to default loader