[06:21] <alkisg> (03:57:03 PM) sforshee: alkisg: the first time you install a dkms module while booted under secure boot you should get prompted about creating a MOK and given further instructions
[06:21] <alkisg> ==> https://termbin.com/p82v ==> I'm supposed to be seeing a whiptail menu but I don't! I guess some stdio descriptor has been redirected and it only works when updating from GUI?!
[06:38] <alkisg> It did show up later on with `dpkg --configure -a`... dunno, maybe `apt --yes` breaks stdin :/
[06:44] <alkisg> Meh, failed not open \efi\boot\max64.efi: not found => won't boot
[06:46] <alkisg> It should be looking in ubuntu\mmx64.efi instead, copying the file...
[06:54] <alkisg> OK that worked. I wonder if these 2 bugs affect everyone, or just my installation.
[07:05] <tomreyn> hmm, "max64.efi" sounds like a typo to me.
[07:08] <tomreyn> also ubuntu uefi boot code is usually installed to /efi/ubuntu/ rather than /efi/BOOT/, i think
[07:49] <alkisg> tomreyn: true, my first line there was my own typo; but the fact that it looks in boot rather than ubuntu wasn't a typo
[07:55] <tomreyn> thanks for clarifying.
[11:59] <sforshee> cyphermox: ^ alkisg is seeing some issues with setting up the MOK for dkms
[12:01] <cyphermox> alkisg: no; it's expected; we largerly install in both locations because some systems are busted and don't record the BootEntry for ubuntu
[12:02] <cyphermox> as for the upgrade issue, that's a known bug that someone is working on. headers redirect output for dkms
[12:29] <alkisg> cyphermox: thank you; I only had mmx64 in one location; I had to manually use cp; maybe it's been resolved after I installed that system
[13:16] <tomreyn> are there some rough plans on a 5.x kernel backport (HWE) to 18.04?
[13:16] <tomreyn> i know there's one in proposed, but it's been there for a while
[13:17] <tomreyn> i was hoping to see it on hwe-edge at least