On Thu, Feb 1, 2018, 3:52 PM AV wrote:
> On Thu, 2018-02-01 at 13:36 -0700, Chris Murphy wrote:
> > On Wed, Jan 31, 2018 at 9:53 AM, AV 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 de
On Thu, 2018-02-01 at 13:36 -0700, Chris Murphy wrote:
> On Wed, Jan 31, 2018 at 9:53 AM, AV 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 sh
On Wed, Jan 31, 2018 at 9:53 AM, AV 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.
On Thu, 01 Feb 2018 12:17:26 +0100
AV wrote:
> I very much doubt this. On a pc with secure boot you see:
>
> $ dmesg |grep -i secure
> [0.00] secureboot: Secure boot enabled
> [0.00] Kernel is locked down from EFI secure boot; see man
> kernel_lockdown.7
> [1.364686] Loaded U
On Wed, 2018-01-31 at 17:30 -0700, stan wrote:
> On Wed, 31 Jan 2018 17:53:22 +0100
> AV wrote:
>
> > However after install I find 'secure boot disabled'.
> > $ dmesg | grep -i secure
> > [0.00] secureboot: Secure boot disabled
> > [5.630671] Loaded UEFI:MokListRT cert 'Fedora Secure
On Wed, 31 Jan 2018 17:53:22 +0100
AV wrote:
> However after install I find 'secure boot disabled'.
> $ dmesg | grep -i secure
> [0.00] secureboot: Secure boot disabled
> [5.630671] Loaded UEFI:MokListRT cert 'Fedora Secure Boot CA:
> fde32599c2d61db1bf5807335d7b20e4cd963b42' linked t
