Comment 4 for bug 2066945

Hmm I see, thanks for the details. I'm not sure, but you may indeed be right about enabling Secure Boot causing complications with device drivers / kernel modules.

Are you by any chance using the official Canonical-provided kernel on your Ubuntu installation, or are you perhaps using a third-party/unofficial kernel? I was looking at https://wiki.ubuntu.com/UEFI/SecureBoot and noticed this sentence:

> In the case of unofficial kernels, or kernels built by users, additional steps need to be taken if users wish to load such kernels while retaining the full capabilities of UEFI Secure Boot.

And this:

> Unsigned modules are simply refused by the kernel. Any attempt to insert them with insmod or modprobe will fail with an error message.

Which made wonder if you may be running into this with a custom/unofficial kernel.