On Fri 16 Nov 2018 06:04:01 PM CST, guennov wrote:


Hi
sorry about the delay. Meanwhile I had to add something to my 'personal
knowledge base'.

First a technician told me that the UEFI BIOS Version 8AET66WW (1.46) of
my machine doesn't support a secure boot option.

Second on ubuntu user forums I found that the message "MODSIGN: Couldn't
get UEFI db list: EFI_NOT_FOUND" sometimes is displayed because of a
(ubuntu) kernel bug, not because of a boot problem.

Finally on a user forum there was mentioned the command "efibootmgr -v".
When I tried it part of the response was
"Boot001A*
sled-secureboot
HD(2,GPT,195d3817-8d5f-464e-afba-117e7419d274,0x1c2800,0x82000)/File(\EFI\sled\shim.efi)"
so maybe the error message indeed is of no importance. Do you agree?

Thank you!


Hi
Yes, secure boot uses shim.efi, non-secure uses grubx64.efi. I would
manually remove the 001A entry via efibootmgr, or fire up YaST
bootloader and uncheck the secure boot option.

--
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.25-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below... Thanks!