From owner-freebsd-current@freebsd.org Fri Mar 18 23:55:57 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 79700AD5A18 for ; Fri, 18 Mar 2016 23:55:57 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from dec.sakura.ne.jp (dec.sakura.ne.jp [210.188.226.8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2E6CB1281 for ; Fri, 18 Mar 2016 23:55:56 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from fortune.joker.local (123-48-23-227.dz.commufa.jp [123.48.23.227]) (authenticated bits=0) by dec.sakura.ne.jp (8.15.2/8.15.2/[SAKURA-WEB]/20080708) with ESMTPA id u2INtnSA009425 for ; Sat, 19 Mar 2016 08:55:49 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Sat, 19 Mar 2016 08:55:48 +0900 From: Tomoaki AOKI To: freebsd-current@freebsd.org Subject: Re: UEFI Booting on a Thinkpad Yoga 11e w/ Security Chip Message-Id: <20160319085548.0dbbf31ac1b7414931058473@dec.sakura.ne.jp> In-Reply-To: References: Organization: Junchoon corps X-Mailer: Sylpheed 3.5.0 (GTK+ 2.24.29; amd64-portbld-freebsd10.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Mar 2016 23:55:57 -0000 Hi. Is there any setting about"Secure Boot"? *Maybe all Windoze7 (or later) generation ThinkPads would have it. If so, disable it INSTEAD OF "Security Chip" and try. On Fri, 18 Mar 2016 15:54:46 -0500 Kyle Evans wrote: > Hello! > > I recently purchased an older Thinkpad Yoga 11e and now I've installed > 10.3RC2 to it. It appears that the Security Chip feature causes > problems in attempting to boot 10.3RC2 (and a slightly older -CURRENT, > as well, but re-tested with 10.3RC2 just for the sake of > verification). The following output is written when attempting to boot > from the `amd64-uefi-memstick.img`: > > == > > >> FreeBSD EFI boot block > Loader path: /boot/loader.efi > LoadImage failed with error 2 > HandleProtocol failed with error 2 > StartImage failed with error 2 > panic: Load failed > > == > > Rebooting and disabling the security chip fixes this, and everything > runs along nicely. Re-enabling the Security Chip after 10.3RC2 is > installed and attempting a boot yields the slightly different (while > slightly expected, given the above, but I'm adding this anyways): > > == > > >> FreeBSD EFI boot block > Loader Path: /boot/loader.efi > > Initializing modules: ZFS UFS > Probing 4 block devices. . . . . .* done > ZFS found the following pools: zroot > UFS found no partitions > Failed to load image provided by ZFS, size: 2033504512, (2) > panic: No bootable partitions found! > > == > > Is this expected behavior? I was under the impression that the > "Security Chip" was largely unrelated to anything in the boot process. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- Tomoaki AOKI junchoon@dec.sakura.ne.jp