** Changed in: oem-priority
Status: Fix Committed => Fix Released
** Changed in: linux-oem-5.17 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
bug verified passed with linux-oem-22.04 5.17.0.1009.9 in jammy-proposed
** Changed in: oem-priority
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
** Description changed:
+ lp:1972802
+
Steps to reproduce:
1. enroll mok, and use the mok to sign dkms
2. make sure secure boot is on, and boots with kernel
3. load the kernel by either modprobe or insmod.
Expected:
the kernel module can be loaded.
Actually:
the kernel
** Changed in: oem-priority
Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1969432
Title:
5.17 kernel won't load
the fix is not in 5.17.0-1004-oem yet.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1969432
Title:
5.17 kernel won't load mok, so it refused to load dkms signed by mok
seems this just needs a config change? from the private bug:
"This is due to the patch "[patch] integrity: Do not load MOK and MOKx when
secure boot be disabled" was added to check if secureboot enabled for trusting
the MOK key,
is there a bug reported upstream yet?
** Also affects: linux-oem-5.17 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is
7 matches
Mail list logo
