On Tue, Mar 29, 2016 at 11:13 AM, Eric Griffith <egriffith92@xxxxxxxxx> wrote: > On Tue, Mar 29, 2016 at 1:08 PM, Kevin Fenzi <kevin@xxxxxxxxx> wrote: >> >> On Tue, 29 Mar 2016 11:40:05 -0400 >> Eric Griffith <egriffith92@xxxxxxxxx> wrote: >> >> > >> > There was, once upon a time, but I'm having trouble tracking it down. >> > >> > What's more interesting is.. I've got a system in front of me, and I >> > just installed rawhide-nodebug on it. Recreated Grub, rebooted, >> > picked that entry from the boot menu.. And it booted. Secure boot is >> > enabled, those kernels aren't signed (according to the wiki), >> > shouldn't Grub be screaming its head off about the kernel not being >> > signed? >> >> No, but your firmware shouldn't allow it to boot. I'd double check that >> secure boot is enabled and that you are really booting a kernel from >> rawhide-nodebug repo. > > > uname -r says > > 4.6.0-0.rc1.git0.1.fc25.x86_64 > > dnf info kernel: > > Name : kernel > Arch : x86_64 > Epoch : 0 > Version : 4.6.0 > Release : 0.rc1.git0.1.fc25 > Size : 0.0 > Repo : @System > From repo : fedora-rawhide-kernel-nodebug > Summary : The Linux kernel > URL : http://www.kernel.org/ > License : GPLv2 and Redistributable, no modification permitted > Description : The kernel meta package > > > Asus UEFI says Secure Boot: Enabled. I'll play around with the firmware and > see if I can't get it to fail to boot. Really bizarre. # mokutil --sb-state # keyctl list %:.system_keyring -- Chris Murphy -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
