http://bugzilla.opensuse.org/show_bug.cgi?id=1198167 http://bugzilla.opensuse.org/show_bug.cgi?id=1198167#c4 --- Comment #4 from Kenneth Aaker <kenaaker@gmail.com> --- That's a useful suggestion. Thank you. I just tried it, and found a couple things. I couldn't find any package titled openSUSE-signing-certificate, but I did find one titled openSUSE-signkey-cert, so I installed that. Then when I rebooted, I did get the MOK prompt. So, that seemed promising. I still am not certain what "MOK" stands for. I was uncertain which "password" was being prompted for, so I used my general administrative password. That seemed to be Ok. Then the system rebooted again. And, I still get the same failure. I'll try it again. By the way, I'm generally running a Xen hypervisor (that showed the same failure), but I did try it with a non-Xen regular Linux kernel and got the same failure. So, in short it still fails whether running the Xen hypervisor, or a plain vmlinuz kernel. Regards, Ken Aaker(In reply to Marcus Meissner from comment #2)
actually when you first install opensUSE Leap 15.3 and reboot, you would be presented by the MOK Manager Dialog.
you can reenforce this by:
zypper in -f openSUSE-signing-cert reboot ... acknowledge the new key in the MOK dialog ...
This package will ask the MOK Manager to enroll the openSUSE signing key into the MOK.
After that you can do modprobe libafs.
(This should be happening during installation, but people might not see tzhe mok manager as it runs just once and has a 10 second timeout.)
That's a useful suggestion. Thank you. I just tried it, and found a couple things. I couldn't find any package titled openSUSE-signing-certificate, but I did find one titled openSUSE-signkey-cert, so I installed that. Then when I rebooted, I did get the MOK prompt. So, that seemed promising. I still am not certain what "MOK" stands for. I was uncertain which "password" was being prompted for, so I used my general administrative password. That seemed to be Ok. Then the system rebooted again. And, I still get the same failure. I'll try it again. By the way, I'm generally running a Xen hypervisor (that showed the same failure), but I did try it with a non-Xen regular Linux kernel and got the same failure. So, in short it still fails whether running the Xen hypervisor, or a plain vmlinuz kernel. Regards, Ken Aaker -- You are receiving this mail because: You are on the CC list for the bug.