Results 1 to 8 of 8

Thread: MODSIGN: EFI_NOT_FOUND

  1. #1

    MODSIGN: EFI_NOT_FOUND

    Hi

    There is a boot message "MODSIGN: Couldn't get UEFI db list: EFI_NOT_FOUND". What might be causing this problem? Should I care about it? Is there anything to be done?

    The boot process continues with some ACPI warnings concerning systemIO range conflicts with OpRegions ( \_SB_.PCI0.LPC_.PMIO and \_SB_.PCI0.LPC_.LPIO). SLED woks fine.

    The partitions /boot/efi, type vfat, and /boot/grub2/x86_64-efi, type btrfs, both look ok.

    Local environment: Lenovo T520, Type 4243F53, Architecture: x86_64, Kernel Version: 4.4.156-94.61-default, Last Updated Package: Do 18 Okt 2018 14:44:41 CEST.

    Thank you.

  2. Re: MODSIGN: EFI_NOT_FOUND

    Hi
    Is secure boot enabled in the BIOS? If so, perhaps you skipped an update by MokManager at boot (a blue screen asking for an update before grub)?

    Yes I see the same sort of ACPI/DSDT errors on an ASUS K88A and a HP dm4-3050us, if you check the output from dmesg or journalctl -b it maybe ignoring the calls. You can try adding to the grub boot kernel options acpi_osi=Linux and see if that helps, but to date I've not seen any issues with either of the two machines mentioned.
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  3. #3

    Re: MODSIGN: EFI_NOT_FOUND

    Hi

    BIOS Boot menu entries look like this
    UEFI/Legacy Boot [Both]
    UEFI/Legacy Boot Priority [UEFI First]

    BIOS Security menu
    Security Chip [Inactive]

    I changed the configuration to `active' and rebootet but nevertheless the message "MODSIGN: couldn't get ..." etc is fired. Extract from dmesg:
    MODSIGN: Couldn't get UEFI db list: EFI_NOT_FOUND
    MODSIGN: Couldn't get UEFI dbx list: EFI_NOT_FOUND

    So I don't understand if secure boot is enabled. As far as I remember I never saw a question for update before grub. Is it possible to initialize or test it manually? Where is the place to look for documentation of MManager?

    dmesg too contains these lines
    efi: EFI v2.00 by Lenovo
    efi: efi: ACPI=0xdaffe000 efi: ACPI 2.0=0xdaffe014 efi: SMBIOS=0xdae9e000 efi:
    SMBIOS 2.6 present.
    DMI: LENOVO 4243F53/4243F53, BIOS 8AET66WW (1.46 ) 09/20/2016

    Do these lines mean that EFI is used?

    Finally dmesg contains some lines which might relate to your suggested kernel option, especially the last one
    ACPI: Added _OSI(Module Device)
    ACPI: Added _OSI(Processor Device)
    ACPI: Added _OSI(3.0 _SCP Extensions)
    ACPI: Added _OSI(Processor Aggregator Device)
    ACPI : EC: EC description table is found, configuring boot EC
    ACPI : EC: EC started
    [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored

    Thank you.

  4. Re: MODSIGN: EFI_NOT_FOUND

    Hi
    TBH I would worry about it, maybe there is a BIOS update available?

    Did you add the acpi_osi=Linux? There are others to try eg \"!Windows 2012\" to see if can change that last line to not say "query ignore" and say "query honored via cmdline"
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  5. #5

    Re: MODSIGN: EFI_NOT_FOUND

    Hi
    adding acpi_osi= Linux to the grub boot kernel options changed nothing. Error resp. warning messages remain as before. Extracts from dmesg

    [ 0.303725] ACPI: Added _OSI(Module Device)
    [ 0.303731] ACPI: Added _OSI(Processor Device)
    [ 0.303735] ACPI: Added _OSI(3.0 _SCP Extensions)
    [ 0.303739] ACPI: Added _OSI(Processor Aggregator Device)
    [ 0.303744] ACPI: Added _OSI(Linux)
    [ 0.308234] ACPI : EC: EC description table is found, configuring boot EC
    [ 0.308263] ACPI : EC: EC started
    [ 0.327992] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query honored via cmdline
    ...
    [ 4.317367] MODSIGN: Couldn't get UEFI db list: EFI_NOT_FOUND
    [ 4.317679] MODSIGN: Couldn't get UEFI dbx list: EFI_NOT_FOUND
    ...
    [ 8.102392] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\_SB_.PCI0.LPC_.PMIO) (20150930/utaddress-254)
    [ 8.102393] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    and so on.

    The only OS installed and running on the machine is SLED.

    Thank you. Good-bye for now.

    Günter

  6. Re: MODSIGN: EFI_NOT_FOUND

    Hi
    I would check the system BIOS for being able to set UEFI to standard or off, I'm not familiar with the options. Else switch to secure efi booting...
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  7. #7

    Re: MODSIGN: EFI_NOT_FOUND

    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!

  8. Re: MODSIGN: EFI_NOT_FOUND

    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!


Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •