[Bug 1195118] some kernel modules cannot be loaded if secure boot is enabled
https://bugzilla.suse.com/show_bug.cgi?id=1195118 https://bugzilla.suse.com/show_bug.cgi?id=1195118#c9 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Installation Assignee|kernel-bugs@opensuse.org |yast2-maintainers@suse.de QA Contact|qa-bugs@suse.de |jsrain@suse.com --- Comment #9 from Takashi Iwai <tiwai@suse.com> --- Lukas, the comment 8 looks like a wrong analysis. This bug is in essentially two parts: the real bug that hinders the MOK cert deployment at installation, and the lack of intuitive usage. The package openSUSE-signkey-cert *is* installed as default, so the patterns or whatever choice of package itself works. The actual problem is that the end result is not what we expected due to the bug. The first item, the bug in the installation step, is described in comment 6, and it has to be evaluated by your team, I suppose. This isn't directly related with the kernel itself, but rather how mokutil gets executed at which state. The error indicates some insufficient installation at the mokutil execution time. The rest is rather about the documentation, or some instruction that could be shown in installer or something else. It's an enhancement, and you can take it as a sort of feature request in future products. Again, the kernel plays little role in this regard. So, please take a look at the first problem (comment 6). Once when this gets fixed, we can consider the rest (either more documentation or UI enhancement if really appropriate -- maybe it's better to continue in another bug, though). -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply@suse.com