From owner-freebsd-current@FreeBSD.ORG Tue Sep 16 07:09:05 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2A6FECDC; Tue, 16 Sep 2014 07:09:05 +0000 (UTC) Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) (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 0E13BE4C; Tue, 16 Sep 2014 07:09:04 +0000 (UTC) Received: from comporellon.tachypleus.net (polaris.tachypleus.net [75.101.50.44]) (authenticated bits=0) by d.mail.sonic.net (8.14.9/8.14.9) with ESMTP id s8G7918M008574 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 16 Sep 2014 00:09:02 -0700 Message-ID: <5417E20D.8070607@freebsd.org> Date: Tue, 16 Sep 2014 00:09:01 -0700 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 MIME-Version: 1.0 To: "O. Hartmann" Subject: Re: CURRENT: EFI boot failure References: <20140916020541.03c18d04.ohartman@zedat.fu-berlin.de> <54178607.1060305@freebsd.org> <541786BE.6010105@freebsd.org> <20140916075121.29989a53.ohartman@zedat.fu-berlin.de> In-Reply-To: <20140916075121.29989a53.ohartman@zedat.fu-berlin.de> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Sonic-CAuth: UmFuZG9tSVYsUThMiSvR6Bir7qXtYsuE9uBkg8fRop1TGzY5d4z5InvjJm8yOHJO7o4OFOQNwntAMCfXD/ofZ9Ubg//U1s+Ts3ZLjou3+Pc= X-Sonic-ID: C;MrsZVnA95BGPzgDu5Qupew== M;rntzVnA95BGPzgDu5Qupew== X-Spam-Flag: No X-Sonic-Spam-Details: 2.4/5.0 by cerberusd Cc: freebsd-current@freebsd.org, Allan Jude X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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: Tue, 16 Sep 2014 07:09:05 -0000 On 09/15/14 22:51, O. Hartmann wrote: > Am Mon, 15 Sep 2014 17:39:26 -0700 > Nathan Whitehorn schrieb: > >> On 09/15/14 17:36, Allan Jude wrote: >>> On 2014-09-15 20:05, O. Hartmann wrote: >>>> Installing FreeBSD-11.0-CURRENT-amd64-20140903-r270990 on a Laptop works for UEFI >>>> fine. After I updated the sources to r271649, recompiled world and kernel (as well >>>> as installed), now I get stuck with the screen message: >>>> >>>>>> FreeBSD EFI boot block >>>> Loader path: /boot/loader.efi >>>> >>>> and nothing happens. After a couple of minutes, the system reboots. >>>> >>>> What happened and how can this problem be solved? >>>> >>> You might need to update the boot1.efi file on the UEFI partition (small >>> FAT partition on the disk) >>> >>> I am not sure how 'in sync' boot1.efi (on the fat partiton) and >>> loader.efi have to be. >>> >>> https://wiki.freebsd.org/UEFI >>> >> boot1.efi is designed never to need updating. (It also hasn't changed >> since April) >> -Nathan > > But it has changed bytesize when I recompiled world with recent sources compared to the > boot.efi size from the USB image I installed from (revision see above). Probably compiler updates or something? I really wouldn't worry about it too much. I'd worry more about loader, since we know boot1 could use the console but loader doesn't show up. > How to update bootcode on UEFI layout? I created a GPT partition with type efi (1 GB) as > well as a 512KB partition typed freebsd-boot. How did you set it up in the first place? If you have a FreeBSD-only system partition (like the installer sets up), you just dd /boot/boot1.efifat to the EFI partition. Otherwise, it's FAT and you copy /boot/boot1.efi to somewhere your boot manager can find it. > I'm new to EFI and the way the notebook now behaves is really strange. While the USB > drive image used to boot with new console enabled, it now boots again with the old > console and 800x640 resolution. This might indicate some minor but very effective mistake > I made. > The EFI boot block finds the first UFS partition -- on any disk -- and tries to boot from it. If you have multiple FreeBSD disks connected, that will very likely result in madness. -Nathan