lost wifi, ethernet, docking station with 16.04 kernel signing.

Tom H tomh0665 at gmail.com
Tue Apr 26 00:25:17 UTC 2016


On Tue, Apr 26, 2016 at 2:15 AM, Tom H <tomh0665 at gmail.com> wrote:
> On Tue, Apr 26, 2016 at 1:26 AM, Peter Silva <peter at bsqt.homeip.net> wrote:
>>
>> I boot 4.4.0-18 and all the modules insert just fine.
>> 4.4.0-19 and later I get the error message.
>
> Please bottom-post.
>
> My apologies. I always assumed that setting the MODULE_SIG* would
> force the kernel to check for signed modules in general as well as for
> signed modules in the SB case but I had some doubts.
>
> Given your problem, I had the rather silly idea of grepping through
> the 4.4.0-21 kernel config for "EFI" and I found
> "EFI_SECURE_BOOT_SIG_ENFORCE".
>
> I couldn't find it in my upstream 4.6-rc5 kconfig but I did find it in
> an Ubuntu patch, "linux_4.4.0-21.37.diff", and it means "Force module
> signing when UEFI Secure Boot is enabled".
>
> Check -18 and -19 for this. It's probably off or non-existent in -18.
>
> So Ubuntu's killed dkms-dependent packages (or otherwise
> locally-compiled modules) with SB active - unless you compile and sign
> your own stuff.

I've found the "EFI_SECURE_BOOT_SIG_ENFORCE" bug:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566221

You can use dkms modules after running "sudo mokutil
--disable-validation" so it might/should work for your
locally-compiled modules.



More information about the ubuntu-users mailing list