Am 16.03.19 um 15:04 schrieb Neil Rickert:
Tumbleweed (64-bit) at 20190314:
The following lines are from "dmesg" output:
[ 1.774479] Couldn't get size: 0x800000000000000e [ 1.774490] fbcon: Taking over console [ 1.774491] MODSIGN: Couldn't get UEFI db list [ 1.774513] Couldn't get size: 0x800000000000000e [ 1.774515] Couldn't get UEFI MokListRT [ 1.774535] Couldn't get size: 0x800000000000000e [ 1.774536] Couldn't get UEFI dbx list
I am seeing 4 of those lines on the screen in early boot (before prompted for LUKS passphrase. The lines on the boot screen are the three "Couldn't get size" lines and the "MODSIGN" line.
It is not causing problems, and I am ignoring for now. But I'm posting this in case they matter.
I see these only with the 5.0 kernel. I did not see them with the previous 4.20 kernels.
I do not see this with a legacy BIOS. I do not see this with a 64-bit UEFI BIOS. I only see it with a 32-bit UEFI BIOS ("ia32").
I should add that this is on a KVM virtual machine, with the OVMF UEFI firmware. I do not have a physical machine with ia32 firmware.
My best guess is that the kernel sees that this is a UEFI system but fails to recognize that it is using 32-bit UEFI rather than 64-bit UEFI.
I see other messages in the same area since kernel 5.0, with 64-bit UEFI on hardware. Might be related: ... [ 3.008497] integrity: Loading X.509 certificate: UEFI:db [ 3.008501] integrity: Problem loading X.509 certificate -65 [ 3.008505] Error adding keys to platform keyring UEFI:db ... https://bugzilla.opensuse.org/show_bug.cgi?id=1129471 Hendrik -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org