From owner-freebsd-current@FreeBSD.ORG Tue Sep 16 22:26:08 2014 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 00BA27A9; Tue, 16 Sep 2014 22:26:07 +0000 (UTC) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 9894669C; Tue, 16 Sep 2014 22:26:06 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id BAA16697; Wed, 17 Sep 2014 01:26:04 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1XU1CF-0005GM-Oz; Wed, 17 Sep 2014 01:26:03 +0300 Message-ID: <5418B8C3.7040406@FreeBSD.org> Date: Wed, 17 Sep 2014 01:25:07 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 MIME-Version: 1.0 To: Ed Maste , "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> <5417E20D.8070607@freebsd.org> <20140916230348.189e80cd.ohartman@zedat.fu-berlin.de> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: FreeBSD Current , Nathan Whitehorn , 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 22:26:08 -0000 On 17/09/2014 00:32, Ed Maste wrote: > On 16 September 2014 17:03, O. Hartmann wrote: >> >> In that case, is it still /boot/boot1.efifat or is it /boot/boot1.efi? What is the >> difference? Is the efi partition FAT? > > An EFI system partition (ESP) is a FAT-formatted partition with a > specific GPT or MBR identifier and file system hierarchy; EFI firmware > will try to load /EFI/BOOT/BOOTX64.EFI from the ESP. A very useful read about how EFI boot process works and how different OSes boot on top of it: http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/efi-boot-process.html > boot1.efi is an EFI application - that is, a PECOFF format binary. It > searches for a UFS filesystem and loads loader.efi from that. It is > intended to simplify the UEFI boot process, so that loader.efi, the > .4th files, loader.conf etc. do not all need to be installed in the > ESP. > > boot1.efifat is a FAT filesystem image that contains a copy of > boot1.efi as /EFI/BOOT/BOOTX64.EFI. It exists so that the installer > can treat it as opaque bootcode, like other boot schemes. It's > certainly possible to create a partition, use newfs_msdos to format > it, and copy in boot1.efi instead. > >> It is one disk, dedicated to FreeBSD (a laptop disk). Is there any documentation readable >> for non-developer for that matter? I'm curious about how EFI works on FreeBSD. > > Better user-facing documentation is in progress; for now the best > source is probably the wik. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- Andriy Gapon