From owner-freebsd-bugs@FreeBSD.ORG Thu Oct 9 20:52:59 2014 Return-Path: Delivered-To: freebsd-bugs@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 D4024986 for ; Thu, 9 Oct 2014 20:52:59 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 A1737983 for ; Thu, 9 Oct 2014 20:52:59 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s99KqxkK050373 for ; Thu, 9 Oct 2014 20:52:59 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, 09 Oct 2014 20:52:59 +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: uefi X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: bugs@odac.co 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: cc Message-ID: In-Reply-To: References: 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-1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Oct 2014 20:52:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192184 Pablo Olmos de Aguilera C. changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugs@odac.co --- Comment #14 from Pablo Olmos de Aguilera C. --- >> 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 > here. 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. I'm finding a similar issue, but loading boot1.efi just get me: >> FreeBSD EFI boot block Loader path: /boot/loader.efi panic: No bootable partition found I guess that's because my system doesn't have any UFS partition, because I have a freebsd-boot partition, and my root is on zfs. I tried to load.efi, but it says the kernel is wrong and drop me into a loader console that works very weird (characters get added, if I write "show", sometimes say "sh" not found, or inserts random characters "shkokw". I tried to copy loader.4th over there, but still nothing happens... even worse, it seems that after adding .4th not even the `set` command is being recognized. -- You are receiving this mail because: You are the assignee for the bug.