We do not use debian signed EFI-bootloader so ignore this secure boot related messages.eriefisher wrote: ↑Tue Jun 11, 2019 8:08 pm Will do but I did see this blip on a reboot.Code: Select all
[ 5.642002] Loaded X.509 cert 'Debian Secure Boot CA: 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1' [ 5.642038] Loaded X.509 cert 'Debian Secure Boot Signer: 00a7468def' [ 5.642639] Loaded UEFI:db cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53' linked to secondary sys keyring [ 5.642685] Loaded UEFI:db cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4' linked to secondary sys keyring [ 5.642707] Loaded UEFI:db cert 'Acer Database: 84f00f5841571abd2cc11a8c26d5c9c8d2b6b0b5' linked to secondary sys keyring [ 5.642711] Problem loading UEFI:db X.509 certificate (-65) [ 5.642755] Problem loading UEFI:db X.509 certificate (-65)
In theory we could, but this would limit us to use only debian signed kernels, which prohibits also to load any other unsigned modules or dkms-created modules, e.g. needed for VirtualBox or Video driver etc .... But for now just ignore these lines.
