From owner-freebsd-current@FreeBSD.ORG Fri Sep 19 13:22:41 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 30DBC67B; Fri, 19 Sep 2014 13:22:41 +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 D8B331F2; Fri, 19 Sep 2014 13:22:40 +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 <1XUy91-002YeH-5p>; Fri, 19 Sep 2014 15:22:39 +0200 Received: from [141.89.176.137] (helo=hermann.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.82) with esmtpsa (envelope-from ) id <1XUy91-000nrr-3M>; Fri, 19 Sep 2014 15:22:39 +0200 Date: Fri, 19 Sep 2014 15:22:07 +0200 From: "O. Hartmann" To: Andriy Gapon Subject: Re: CURRENT: EFI boot failure Message-ID: <20140919152207.0473e213.ohartman@zedat.fu-berlin.de> In-Reply-To: <5418B8C3.7040406@FreeBSD.org> 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> <5418B8C3.7040406@FreeBSD.org> 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_/.e/tjG/Ym/n3CLqOLR+iM1N"; protocol="application/pgp-signature" X-Originating-IP: 141.89.176.137 X-ZEDAT-Hint: A Cc: FreeBSD Current , Ed Maste , 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: Fri, 19 Sep 2014 13:22:41 -0000 --Sig_/.e/tjG/Ym/n3CLqOLR+iM1N Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Wed, 17 Sep 2014 01:25:07 +0300 Andriy Gapon schrieb: > On 17/09/2014 00:32, Ed Maste wrote: > > On 16 September 2014 17:03, O. Hartmann w= rote: > >> > >> 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 > A very useful read about how EFI boot process works and how different OSe= s boot > on top of it: > http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/efi-boot-process= .html >=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. > >=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. > >=20 > >> It is one disk, dedicated to FreeBSD (a laptop disk). Is there any doc= umentation > >> readable for non-developer for that matter? I'm curious about how EFI = works on > >> FreeBSD. > >=20 > > 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.o= rg" > >=20 >=20 >=20 The problem I reported about in the first place is triggered by a faulty lo= ader.efi that arises, when optimisation level is -O3. -O2 works fine. I also realized that there is a kind of inconsistency in how COPTFLAGS and = CFLAGS are handled in reality compared to that what the manpage of make.conf states. S= etting COPTFLAGS=3D-O2 for compiling kernel stuff only ALWAYS incorporates CFLAGS,= which is set to CFLAGS=3D-O3 in make.conf in my case. loader.efi is, in my opinion, kernel = stuff only as well as kernel modules, which also gets compiled with CFLAGS. --Sig_/.e/tjG/Ym/n3CLqOLR+iM1N Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJUHC3/AAoJEOgBcD7A/5N8w5YH/3sLuzZ+GJh1Nd9FpBupdvrZ 3H8t/8m4SFx+HR2oikHIfFPfPfQ5sM9m5iJ960OzDWGDo7Hrc7nebBmFo6NCb8pG 9HLjqVuRh1UJAIgCalzbM8IAL/Qt3NfIzRx++tt3TqY9X7aZjvg7sqHWcaFBPwgB 3IV/DvWvlX5xIQyfa1gtnbRhkKBpObuDRoY56bC5BcyDBqcAFwZFiJMQMvs4lUfX 9ZgSdUNvEjaN7XMuqa1+DPemnYMBec95ScEvAU44sofTW263G1OtSmp+5buBLGb1 4eG5LUKfQqKGFMr3E19w3tfGzhfaFYptPfPoV9EgDOeF/iGyMHeXTty1uudBWXg= =q03c -----END PGP SIGNATURE----- --Sig_/.e/tjG/Ym/n3CLqOLR+iM1N--