Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 18 Sep 2014 22:13:12 +0200
From:      "O. Hartmann" <ohartman@zedat.fu-berlin.de>
To:        FreeBSD CURRENT <freebsd-current@freebsd.org>
Subject:   Re: CURRENT: EFI boot failure
Message-ID:  <20140918221312.3811e382.ohartman@zedat.fu-berlin.de>
In-Reply-To: <20140916020541.03c18d04.ohartman@zedat.fu-berlin.de>
References:  <20140916020541.03c18d04.ohartman@zedat.fu-berlin.de>

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

Am Tue, 16 Sep 2014 02:05:41 +0200
"O. Hartmann" <ohartman@zedat.fu-berlin.de> schrieb:

>=20
> Installing FreeBSD-11.0-CURRENT-amd64-20140903-r270990 on a Laptop works =
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:
>=20
> >> FreeBSD EFI boot block
>    Loader path: /boot/loader.efi
>=20
> and nothing happens. After a couple of minutes, the system reboots.
>=20
> What happened and how can this problem be solved?


after today's "make world" (revision 271800) and two days of normal operati=
on, I run into
the same situation as described above! This is more than annoying! The scre=
en show simply


>> FreeBSD EFI boot block
   Loader path: /boot/loader.efi

and nothing happens forever. Usually, the loader/console shows up. This tim=
e the system
gets stuck as I reported earlier.

I can not afford another two days of installing the laptop again. How can I=
 get rid of
this immature EFI and run the system in the traditional way? It seems two i=
mmature
systems meet each other, vt() and EFI and this ends up in a desaster.

What is the fallback procedure? How to save the system and circumvent this =
problem? Is
there a way to interrupt the boot process and drop out into some kind of em=
ergency
screen/console?

BTW, I temporarily fixed this issu by copying the USB drive image's loader.=
efi into boot.
This seems to be a bug in the compiler/compiling loader.efi.

--Sig_/WfQo.9SgOOH6_G34tw8wFgv
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

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

iQEcBAEBAgAGBQJUGzzdAAoJEOgBcD7A/5N8Fx8H/j1qHObMSIeepXqj3LQHosyn
03kdo2PIEghpkrxir0k11ZO5YUzvzJsFlh2y2jHBdN3B0NAEDubekFBmiUfFu9qc
6RG7gfsKCc9c1Dd9u9fDajdH/nb/7O3wkO9u9JmAL6FokbFX1OTQEHJSsIP5G/0J
+Q6lE/MdaVQDtDo9s/yBQEV5B7bihZ43vFUfDaer3OnV/qaBg0A+XMVJtYZ84pvD
V/czf7BJBoOA4H8DOAevrL+TgAGUwCZ1Vl89zngC/HhlDHbt668wCZ0dfGEDc1Lv
M+U8gTw+ULq4vWmpWkYB2A1djTuLZzA+jknb2xU21LuYHxLjbfwKXNZxfv3A2yk=
=WHwy
-----END PGP SIGNATURE-----

--Sig_/WfQo.9SgOOH6_G34tw8wFgv--



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