Bug 197021 - MODSIGN: Couldn't get UEFI db list
Summary: MODSIGN: Couldn't get UEFI db list
Status: NEW
Alias: None
Product: EFI
Classification: Unclassified
Component: Boot (show other bugs)
Hardware: Intel Linux
: P1 normal
Assignee: EFI Virtual User
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-21 20:47 UTC by paviluf
Modified: 2020-01-10 07:36 UTC (History)
5 users (show)

See Also:
Kernel Version: 4.12
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description paviluf 2017-09-21 20:47:11 UTC
Hello,

As well as other people on different hardware and distro, I have these messages on boot (Fedora 26) with kernel 4.12 and up with my Chromebook HP 14 (Falco) with MattDevo firmware (UEFI).

sept. 12 00:56:17 hp kernel: Couldn't get size: 0x800000000000000e
sept. 12 00:56:17 hp kernel: MODSIGN: Couldn't get UEFI db list
sept. 12 00:56:17 hp kernel: Couldn't get size: 0x800000000000000e

https://bugzilla.redhat.com/show_bug.cgi?id=1470995
https://forum.level1techs.com/t/fedora-26-kernel-4-12/118296/18
https://forums.fedoraforum.org/showthread.php?t=315207
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779

Can it be fixed please ?

Thanks !
Comment 1 horizonbrave 2017-10-17 04:34:51 UTC
same problem here for me on a Dell 6520 Latitude laptop with UEFI enabled (secure boot is not available):
https://forums.fedoraforum.org/showthread.php?t=315800

Thanks :)
Comment 2 Soeren Grunewald 2018-01-04 12:39:38 UTC
I see the same issue on my Lenovo Yoga 2 pro.

> [    1.127519] Loaded X.509 cert 'Fedora kernel signing key:
> a04b55b15c4372646f782c962d4a11665b6d0cb6'
> [    1.128077] Couldn't get size: 0x800000000000000e
> [    1.128099] MODSIGN: Couldn't get UEFI db list
> [    1.128834] Loaded UEFI:MokListRT cert 'Fedora Secure Boot CA:
> fde32599c2d61db1bf5807335d7b20e4cd963b42' linked to secondary sys keyring
Comment 3 Lee, Chun-Yi 2020-01-10 07:36:42 UTC
The message just mentions kernel did not find db. I have sent cosmetic patches and waiting patch be merged:

https://lkml.org/lkml/2019/12/12/194

Note You need to log in before you can comment on or make changes to this bug.