Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 16 Sep 2014 23:03:48 +0200
From:      "O. Hartmann" <ohartman@zedat.fu-berlin.de>
To:        Nathan Whitehorn <nwhitehorn@freebsd.org>
Cc:        freebsd-current@freebsd.org, Allan Jude <allanjude@freebsd.org>
Subject:   Re: CURRENT: EFI boot failure
Message-ID:  <20140916230348.189e80cd.ohartman@zedat.fu-berlin.de>
In-Reply-To: <5417E20D.8070607@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>

next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/lACDfITHnKiGm8K.pSJ3pYL
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Am Tue, 16 Sep 2014 00:09:01 -0700
Nathan Whitehorn <nwhitehorn@freebsd.org> schrieb:

>=20
> On 09/15/14 22:51, O. Hartmann wrote:
> > Am Mon, 15 Sep 2014 17:39:26 -0700
> > Nathan Whitehorn <nwhitehorn@freebsd.org> schrieb:
> >
> >> On 09/15/14 17:36, Allan Jude wrote:
> >>> On 2014-09-15 20:05, O. Hartmann wrote:
> >>>> Installing FreeBSD-11.0-CURRENT-amd64-20140903-r270990 on a Laptop w=
orks for UEFI
> >>>> fine. After I updated the sources to  r271649, recompiled world and =
kernel (as well
> >>>> as installed), now I get stuck with the screen message:
> >>>>
> >>>>>> FreeBSD EFI boot block
> >>>>      Loader path: /boot/loader.efi
> >>>>
> >>>> and nothing happens. After a couple of minutes, the system reboots.
> >>>>
> >>>> What happened and how can this problem be solved?
> >>>>
> >>> You might need to update the boot1.efi file on the UEFI partition (sm=
all
> >>> FAT partition on the disk)
> >>>
> >>> I am not sure how 'in sync' boot1.efi (on the fat partiton) and
> >>> loader.efi have to be.
> >>>
> >>> https://wiki.freebsd.org/UEFI
> >>>
> >> boot1.efi is designed never to need updating. (It also hasn't changed
> >> since April)
> >> -Nathan
> >
> > But it has changed bytesize when I recompiled world with recent sources=
 compared to
> > the boot.efi size from the USB image I installed from (revision see abo=
ve).
>=20
> Probably compiler updates or something? I really wouldn't worry about it=
=20
> too much. I'd worry more about loader, since we know boot1 could use the=
=20
> console but loader doesn't show up.

Well, I have to worry about because the system is stuck and completely unus=
able.

I installed the system from the very same USB drive image as mentioned abov=
e again. Then,
after the newtork issue has been fixed, I was able to update sources and bu=
ilt world. As
long as I do not attempt to use to use X, everything is fine.

>=20
> > How to update bootcode on UEFI layout? I created a GPT partition with t=
ype efi (1 GB)
> > as well as a 512KB partition typed freebsd-boot.
>=20
> How did you set it up in the first place? If you have a FreeBSD-only=20
> system partition (like the installer sets up), you just dd=20
> /boot/boot1.efifat to the EFI partition. Otherwise, it's FAT and you=20
> copy /boot/boot1.efi to somewhere your boot manager can find it.

The setup was plain and vanilla. I used the installer of the USB image (see=
 above).
Creating GPT partition scheme and two partitions of type "efi" and "freebsd=
-boot", first
1MB, latter 512KB. All other partitions are freebsd-ufs, exept freebsd-swap.

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
> > I'm new to EFI and the way the notebook now behaves is really strange. =
While the USB
> > drive image used to boot with new console enabled, it now boots again w=
ith the old
> > console and 800x640 resolution. This might indicate some minor but very=
 effective
> > mistake I made.
> >
>=20
> The EFI boot block finds the first UFS partition -- on any disk -- and=20
> tries to boot from it. If you have multiple FreeBSD disks connected,=20
> that will very likely result in madness.
> -Nathan

It is one disk, dedicated to FreeBSD (a laptop disk). Is there any document=
ation readable
for non-developer for that matter? I'm curious about how EFI works on FreeB=
SD.

Oliver

--Sig_/lACDfITHnKiGm8K.pSJ3pYL
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBAgAGBQJUGKW0AAoJEOgBcD7A/5N8XMUIAJfbI1Jps3JvtiY6wBjks1m4
4BPB7UU4g29hWTT0da1/z6akJ0dFk/CXQfIpieWGeDBsm9OfQzOJ2N5N1GA89B34
9/CppeByLASK8VMphOEOSO5lv4ijCDGA3Bzs/TvIbVZketqBJmNHZ3mGTt85vfh/
/isZZdx17jZvuMGJyoCE4g0pNjh5ybJGXmoQeYwLIuOMt9COmh3mOVZhLN3tFow7
cmsboAUEluE9YmNteFceV6X3doYSpQwRT7SvdyJUHNQBmMD/6nz+A3yGq78zsCWl
OxC7evQnIGUJAaILYosNxmw/q1+MOx5w/uOAk9Gx7KRgY5uaFk2SXEmHbdLjl1o=
=efCy
-----END PGP SIGNATURE-----

--Sig_/lACDfITHnKiGm8K.pSJ3pYL--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140916230348.189e80cd.ohartman>