On Thu, Feb 1, 2018, 3:52 PM AV <volov...@ziggo.nl> wrote:
> On Thu, 2018-02-01 at 13:36 -0700, Chris Murphy wrote:
> > On Wed, Jan 31, 2018 at 9:53 AM, AV <volov...@ziggo.nl> wrote:
> > > I installed Fed 27 on a Dell XPS 13 9370 using Fed 27 Live
> > > on a usb stick after deleting Ubuntu 16.04 LTS that came
> > > installed on the device.
> > It's possible the kernel version that shipped with Fedora 27 had a
> > bug
> > related to secure boot notification. I forget exactly what kernel
> > versions were affected. Anyway anything in the 4.14 series should
> > work. You can check Secure Boot status with mokutil.
> > $ mokutil --sb-state
> > SecureBoot enabled
> Ah, thanks. I was looking for something like this but did not
> find mokutil. And indeed SecureBoot is enabled:
> $ mokutil --sb-state
> SecureBoot enabled
> The Fed 27 Live version which I used for the install contains
> a 4.13 kernel. So the bug with notification is related to 4.13.
> But the following update to the 4.14.14-300 kernel did not correct
I suggest filing a Red Hat Bugzilla bug against the kernel. Include
complete dmesg. Include mokutil --sb-state, and if you see the very early
message about Secure Boot right after the GRUB menu goes away but before
the Plymouth boot splash, mention it.
Weirdly, Secure Boot support is not in the mainline kernel. Every distro is
carrying their own patches including Fedora.
users mailing list -- firstname.lastname@example.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org