From owner-freebsd-current@FreeBSD.ORG Tue Sep 16 22:25:31 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 539E952E; Tue, 16 Sep 2014 22:25:31 +0000 (UTC) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 D2C4C688; Tue, 16 Sep 2014 22:25:30 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.82) with esmtp (envelope-from ) id <1XU1Bh-003Rop-1s>; Wed, 17 Sep 2014 00:25:29 +0200 Received: from g226063043.adsl.alicedsl.de ([92.226.63.43] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.82) with esmtpsa (envelope-from ) id <1XU1Bg-002EAG-UG>; Wed, 17 Sep 2014 00:25:29 +0200 Date: Wed, 17 Sep 2014 00:25:24 +0200 From: "O. Hartmann" To: Ed Maste Subject: Re: CURRENT: EFI boot failure Message-ID: <20140917002524.5852fe14.ohartman@zedat.fu-berlin.de> In-Reply-To: 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> Organization: FU Berlin X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.22; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/NB7nN2b6/TDLSTOTibE4wYr"; protocol="application/pgp-signature" X-Originating-IP: 92.226.63.43 X-ZEDAT-Hint: A 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:25:31 -0000 --Sig_/NB7nN2b6/TDLSTOTibE4wYr Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Tue, 16 Sep 2014 17:32:12 -0400 Ed Maste schrieb: > On 16 September 2014 17:03, O. Hartmann wro= te: > > > > In that case, is it still /boot/boot1.efifat or is it /boot/boot1.efi? = What is the > > difference? Is the efi partition FAT? >=20 > 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. >=20 > 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. Thank you very much for the explanation. Well, since I never see the loader= screen as we are used to, were is that gone? There are no boot options anymore (like sin= gle user mode, ACPI off et cetera). Is this intended? Besides, checking both boot1.efi and loader.efi with file() shows something= like loader.efi: PE32+ executable (EFI application) x86-64 (stripped to external= PDB), for MS Windows. So both are PECOFF format files? >=20 > 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. All right, here you lost me ... sorry. The partition created by the install= es with type "efi" is then the /EFI/ partition, which then contains a folder BOOT and in= which the boot1.efi is located?=20 As I understand, I can manually mount this partition as FAT and copy boot1.= efi as BOOTX64.EFI into it? This knowledge could come in handy if something goes v= ery bad. >=20 > > It is one disk, dedicated to FreeBSD (a laptop disk). Is there any docu= mentation > > readable for non-developer for that matter? I'm curious about how EFI w= orks on > > FreeBSD. >=20 > Better user-facing documentation is in progress; for now the best > source is probably the wik. Thank you. --Sig_/NB7nN2b6/TDLSTOTibE4wYr Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJUGLjYAAoJEOgBcD7A/5N8iOcH/27MyNe3CXU/KKGJJaEwI3Ul dw8gDL67EGJ3WPDgfPevajjleRYJRSPDLXsfP1iX1y0KSHaChn88gQXqC4NicJpk nOq1IlrkKQAaq5UqyBs6Sx1En6xV1LqyiycBDdxLODCiXcycIMowcGVtham4dzLt HwaUXvn2dPJM3Wp660McIeJ10GlR/xvtRMeFK3+YG8XqJ3UNbOAP7BAUY7J4e/kM NDXlj/bj6YBe6fyDPzJumEK56v70leJHnnzz/IBE5UJQjE8L/zg/87giRcq9xgEM cZ1KX7HKXYcWpNIBfAGY2fiPgTHUfzNY3VE6LjEftCgxKvktFAWCa1NkxYKBM64= =qgGI -----END PGP SIGNATURE----- --Sig_/NB7nN2b6/TDLSTOTibE4wYr--