From owner-freebsd-hackers@FreeBSD.ORG Tue May 12 18:29:38 2015 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 44848252 for ; Tue, 12 May 2015 18:29:38 +0000 (UTC) Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D25411389 for ; Tue, 12 May 2015 18:29:37 +0000 (UTC) Received: by wicmc15 with SMTP id mc15so60705400wic.1 for ; Tue, 12 May 2015 11:29:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=nDyNlUyLwxOF9wo7bmYKlPYMgmwzJ0BW0e/2of/NKy8=; b=CZv9W2GqyXfEzm9sX+m+3PqIwzIFIQnRQDA5HJAUCsSeYB7/fggGBWwTsO0hBiatyy LSrU2ZoQc6z8oxWUw3InCw7XJ/U5b/P3bXF4ijLsCLZ1L3V9tlZlZPar5Tx0ctVM1aWC kvv6vZhgPBfjekTDO3bISmTTkbz7JTl9OGOx5BvHsEbeUtem6fO4sCc9ogvLYcaITuis SGmy52Gp2zoBwSzHKwi0Y+UoM/4k5T01sb+ksoeSEaK3NUHb21RFig7xBFJee03iVG71 o8OsPjOqcnVQg3aR9Gc92BYvweRq1+2gCz0Gir5cYhNNA9qB0w10iAQdHzMWIerLmyHb jEqg== MIME-Version: 1.0 X-Received: by 10.180.186.5 with SMTP id fg5mr7534030wic.60.1431455376412; Tue, 12 May 2015 11:29:36 -0700 (PDT) Received: by 10.194.38.104 with HTTP; Tue, 12 May 2015 11:29:36 -0700 (PDT) In-Reply-To: <554F9DBB.6020202@metricspace.net> References: <553A8CE4.9030204@metricspace.net> <554F9DBB.6020202@metricspace.net> Date: Tue, 12 May 2015 21:29:36 +0300 Message-ID: Subject: Re: EFI boot loader regression? From: Andrey Fesenko To: Eric McCorkle Cc: "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 May 2015 18:29:38 -0000 On Sun, May 10, 2015 at 9:04 PM, Eric McCorkle wrote: > Sorry for the delay in posting this. Attached is my latest work on the > boot block. It includes numerous debugging messages. You should be > able to tell if it gets all the way through the first stage, or where it > stops if it doesn't. > > > > For everyone else, these are the outstanding issues I still need to address: > > * I'm currently (ab)using the UEFI pool allocator as a malloc-like > mechanism. > > * The partition scan completely ignores the GPT labels, and tries to > probe every single partition for every single filesystem. > > * Need to work out argv-style options for the UEFI loader, and have the > boot block construct and pass in an argv array. > > Any other comments are welcome. > > On 04/24/2015 02:35 PM, Eric McCorkle wrote: >> What kind of laptop are you using, and did you update your BIOS in there >> anywhere? >> >> I'm actively working on the UEFI boot block. I will post a patch with >> extra debugging messages added, which will hopefully help track down the >> problem. >> >> On 04/24/2015 12:50 PM, Andrey Fesenko wrote: >>> Hello, >>> >>> I'm use system with EFI boot loader on Lenovo X220. >>> >>> Old EFI loader work fine if BIOS set any boot priority UEFI or Legacy first. >>> >>> Starting around December last year, system not boot if set UEFI boot first. >>> >>> http://bsdnir.info/files/efi/ screenshots and working version boot loader >>> >>> For the cleanliness of experiment, as a new loader I downloaded and >>> test FreeBSD-11.0-CURRENT-amd64-20150421-r281832-memstick.img Hello, I'm test this patch with r281381 build sucess. Now work boot priority Legacy first, with UEFI first loader not found. There diagnostic messages, but unfortunately, they take more than two screens and almost unreal to see even at 50fps video recording After https://svnweb.freebsd.org/base/head/sys/boot/efi/boot1/Makefile?r1=282474&r2=282727 seems to need additional changes, I corrected reloc.c to self_reloc.c but the image obtained is not loaded, though and with diagnostic messages.