lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Date:	Sat, 28 Jun 2014 02:31:23 -0400
From:	Fouldmother Finnishfucker <super.fmff@...dex.com>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: Problems booting kernel with UEFI bios 

Greetings

Two years ago I decided to ditch the shim and shams that come with booting in UEFI on the laptop. This was working fine. The last year someone had a suggestion to sign the kernel, and enable certificate checking, as describe here http://kroah.com/log/blog/2013/09/02/booting-a-self-signed-linux-kernel/, and this too was good.

Then along came version 3.15.0. The same config but now I see an EFI_MIXED option. I tried ignoring this, and I found that I could not boot. I enabled this and I still get the same result. So I waited for two versions to see if the problem is fixed and nothing. I have tried using early printks in EFI and the display is blank. I have no serial, but USB and I cannot get the traces out. So two questions: Has anyone else the same woes? and more importantly how does one debug this stuff? I tried qemu with tianocore and that barfs on the 3.14.8 kernel that is currently working.

Any suggestions would be apprecaited.

FM FF
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists