From owner-freebsd-bugs@FreeBSD.ORG  Thu Jul 31 21:10:00 2014
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@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 C73BE140
 for <freebsd-bugs@FreeBSD.org>; Thu, 31 Jul 2014 21:10:00 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id ACE362804
 for <freebsd-bugs@FreeBSD.org>; Thu, 31 Jul 2014 21:10:00 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s6VLA0KJ029760
 for <freebsd-bugs@FreeBSD.org>; Thu, 31 Jul 2014 21:10:00 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 192184] [uefi] fresh install of 2014-07-14 11.0-CURRENT amd64
 snapshot doesn't boot
Date: Thu, 31 Jul 2014 21:10:00 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: emaste@freebsd.org
X-Bugzilla-Status: Issue Resolved
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-192184-8-UtuD1Ifr7n@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-192184-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-192184-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Jul 2014 21:10:00 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192184

--- Comment #9 from Ed Maste <emaste@freebsd.org> ---
> An older FreeBSD boot .img had been dd'd to another disk partition.
> It turns out that UEFI code will pick up the first available image
> it recognises and boots from that, and not the loader.efi and
> loader.conf etc in the same EFI location at boot1.efi or similar.
> This would be worth addressing.

Ahh, yes.  Sorry this tripped you up.

boot1.efi finds the first available UFS filesystem and loads loader.efi from
there.  You can skip boot1.efi altogether if you like, and just but loader.efi
and the .4th and config files in your EFI system partition, but you'll then
need to explicitly set currdev to load the kernel.

-- 
You are receiving this mail because:
You are the assignee for the bug.