Public bug reported: I'm running a surface 6 pro with a customized kernel which is MOK signed for secure boot.
The system ran a customized MOK signed 5.8.16 kernel when I upgraded from 20.10 to 21.04. The upgrade worked smooth without errors. The system also started well on reboot booting the ubuntu shipped 5.11.0-17-generic kernel. To have full advantages of the system I use surface kernel patches from github: https://github.com/linux-surface/linux-surface on vanilla kernel. So once and a while I compile a fresh surface-patched kernel to stay up-to-date. For secure boot I followed the MOK shim signing process described here: https://gloveboxes.github.io/Ubuntu-for-Azure-Developers/docs/signing-kernel-for-secure-boot.html This worked out so far, but not after upgrade to 21.04. Already signed kernel which have worked before and also newly signed kernel cannot boot due to "invalid signature" error. I found shim-signed related bugs: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1925010 https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1928434 But I think this issue isn't covered by them. Any help is appreciated. Cheers Roman ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928917 Title: 21.04 - MOK signed custom kernel not booting "invalid signature" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1928917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
