This issue is still valid in Ubuntu 23.04 with the virtualbox-dkms
package. See bug report
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1992673 marked
as a duplicate of this issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
I've done similar steps to install nvidia drivers on ubuntu 22.10 with
secure boot enabled but i didn't face mokutil
steps to reproduce
1-during installation i didn't install third party drivers
2-i updated the system then restart
3-i enabled the proposed repo and installed the updated "dkms"
This bug was fixed in the package dkms - 3.0.6-2ubuntu2
---
dkms (3.0.6-2ubuntu2) kinetic; urgency=medium
* Fix dkms signing regressions with cherry-picks from 3.0.7 upstream
git. LP: #1991725
- Reinstate enroll call, as it causes dpkg-trigger action during dpkg
@Gianfranco - this is why I added the verification-needed tags and was
poking Aaron on IRC because I wanted confirmation that this update is
verified. Previously I only got a written confirmation on IRC which I
wanted to have here as the papertrail (+ the other comments on the bug
were a bit
@sil2100, since this bug is already 13 days old (when the package was
really accepted), and its verified as working, can't we just promote it
to proposed pocket?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
Tested on my HP Elitebook 8570p, with Secure Boot and Broadcom WiFi,
following the current test plan. All operations went as expected, WiFi
is working properly.
** Tags removed: verification-needed verification-needed-kinetic
** Tags added: verification-done verification-done-kinetic
--
You
** Description changed:
[Impact]
With the current state of the DKMS package, if a user attempts to
install any package that includes a third-party driver (Broadcom WiFi,
VirtualBox, v4l2loobpack, etc.), the process of signing the newly built
driver with a MOK key will fail silently.
** Description changed:
[Impact]
With the current state of the DKMS package, if a user attempts to
install any package that includes a third-party driver (Broadcom WiFi,
VirtualBox, v4l2loobpack, etc.), the process of signing the newly built
driver with a MOK key will fail silently.
Hello Mike, or anyone else affected,
Accepted dkms into kinetic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/dkms/3.0.6-2ubuntu2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package dkms - 3.0.6-2ubuntu2
---
dkms (3.0.6-2ubuntu2) kinetic; urgency=medium
* Fix dkms signing regressions with cherry-picks from 3.0.7 upstream
git. LP: #1991725
- Reinstate enroll call, as it causes dpkg-trigger action during dpkg
** Description changed:
+ [Impact]
+
+ With the current state of the DKMS package, if a user attempts to
+ install any package that includes a third-party driver (Broadcom WiFi,
+ VirtualBox, v4l2loobpack, etc.), the process of signing the newly built
+ driver with a MOK key will fail silently.
BTW for those that don't have it, this is a solution:
https://discourse.ubuntu.com/t/dkms-package-support-extra-drivers-does-
not-work-in-ubuntu-22-10-install-media/31655
There's a typo, though. The command should be:
sudo kmodsign sha512 /var/lib/shim-signed/mok/MOK.priv /var/lib/shim-
When will the ISOs be correct?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1991725
Title:
fails to sign kernel modules
Status in Release Notes for Ubuntu:
Fix Released
Status in
Ubuntu-SRU please release this one if possible, it is tested and
working, and preventing people from building kernel modules.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1991725
Title:
At the time of this writing, this fix is still stuck in -proposed. This
makes the Lubuntu release notes wrong, as it makes it so that updating
the system prior to installing WiFi drivers is not enough, even though
it is documented as being enough. Considering that this fix very nearly
was hotfixed
** Changed in: ubuntu-release-notes
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1991725
Title:
fails to sign kernel modules
Status in Release Notes
** Changed in: dkms (Ubuntu)
Status: Triaged => Fix Committed
** Description changed:
Expected on kinetic: dkms will sign built modules with MOK key if
requested.
What happens:
dkms outputs "Binary kmod-sign not found, modules won't be signed"
Fix:
update dkms to 3.0.7:
** Changed in: dkms (Ubuntu)
Importance: Undecided => High
** Changed in: dkms (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1991725
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1991725
Title:
fails to sign kernel modules
Status in
I tried the new version and worked perfectly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1991725
Title:
fails to sign kernel modules
Status in dkms package in Ubuntu:
Confirmed
To workaround the issue by rebuilding and signing the driver manually:
1: Run "sudo dpkg-reconfigure bcmwl-kernel-source" to rebuild the driver.
2: Run "sudo kmodsign sha512 /var/lib/shim-signed/mok/MOK.priv
/var/lib/shim-signed/mok/MOK.der
/lib/modules/5.19.0-21-generic/updated/dkms/wl.ko" to
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/1991725
** Tags added: iso-testing
--
You received this bug notification because you are a member of Kernel
Packages,
Worthy of note, to get the driver to build so I could sign it, I had to
do "sudo dpkg-reconfigure bcmwl-kernel-source", then sign the resulting
wl.ko file. So it looks like the driver isn't even building in the first
place.
--
You received this bug notification because you are a member of Kernel
Also, I was able to manually sign the Broadcom kernel module with
kmodsign and now it's accepted.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1991725
Title:
fails to sign kernel
Installing the Kinetic Final image on a Secure Boot enabled laptop with
Broadcom WiFi resulted in the WiFi adapter not being able to be turned
on in the newly installed system. Doing "sudo modprobe wl" tells me "Key
was rejected by service".
--
You received this bug notification because you are
The attachment "dkms.diff" seems to be a patch. If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for
If you don't want to update the dkms package version, you can apply this
patch to fix the problem
** Patch added: "dkms.diff"
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1991725/+attachment/5624265/+files/dkms.diff
--
You received this bug notification because you are a member of
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dkms (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1991725
28 matches
Mail list logo
