Date: Wed, 17 Sep 2014 00:25:24 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Ed Maste <emaste@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org>, Nathan Whitehorn <nwhitehorn@freebsd.org>, Allan Jude <allanjude@freebsd.org> Subject: Re: CURRENT: EFI boot failure Message-ID: <20140917002524.5852fe14.ohartman@zedat.fu-berlin.de> In-Reply-To: <CAPyFy2AicKf-PWGDnq80Zmm8ukwTkURZm8RRUFxdfHK=Xd7XAQ@mail.gmail.com> 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> <CAPyFy2AicKf-PWGDnq80Zmm8ukwTkURZm8RRUFxdfHK=Xd7XAQ@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Am Tue, 16 Sep 2014 17:32:12 -0400 Ed Maste <emaste@freebsd.org> schrieb: > On 16 September 2014 17:03, O. Hartmann <ohartman@zedat.fu-berlin.de> 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. > > 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 single 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? > > 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 installes with type "efi" is then the /EFI/ partition, which then contains a folder BOOT and in which the boot1.efi is located? 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 very bad. > > > 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. Thank you. [-- Attachment #2 --] -----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-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140917002524.5852fe14.ohartman>