On Wed, 2023-04-12 at 06:54 -0400, Genes Lists wrote:
> Maybe post the actual fatal kernel error exactly - is it possible the
> error you printed was non-fatal and something else kiilled boot?
Hi,
yes, it is something else.
$ grep -i module_sig
/lib/modules/4.19.277-rt122-0.300-securityink/bui
On 12-04-2023 09:55, Ralf Mardorf wrote:
Hi,
some kernels that do boot on my old UEFI computer with legacy boot
enabled, don't boot on my new UEFI computer were the Intel processor
graphics doesn't allow to enable legacy boot, but at least _secure boot_
is _disabled_.
What can I do to get rid
On 4/12/23 07:54, Ralf Mardorf wrote:
I don't understand it. If it should be a signing issue, then it does
matter when using one mobo and doesn't matter, if the same SSD holding
the Arch Linux install is connected to another mobo? It only matters
when UEFI booting (with secure boot disabled), bu
sible. At the moment I've got 4 Arch Linux kernels that fail
to boot. 3 were build by me, 1 is from an official Arch repo.
[rocketmouse@archlinux ~]$ grep -ePKCS -eunknown
/mnt/m1.xubu20.04/boot/grub/grub.cfg
menuentry "Arch Linux Rt Cornflower, PKCS#7 signature not signed with
On 4/12/23 03:55, Ralf Mardorf wrote:
Hi,
Bit hard to say from above - clearly these need 2 different keys
(right?) also you dont say what CONFIG_MODULE_COMPRESS_xx are set to
either since you have 2 different module compressions as well as keys
being different.
Maybe post the actual fatal
parameter "module.sig_enforce=1" is _never_ used.
A kernel that fails to boot with "PKCS#7 signature not signed with a
trusted key":
[rocketmouse@archlinux ~]$ ls -hl
/lib/modules/4.19.271-rt120-0.300-cornflower/updates/dkms/
.rw-r--r-- root root 65 KB Sun Apr 2 15:42:39 2023 r8
