Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 16 Sep 2014 07:51:21 +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:  <20140916075121.29989a53.ohartman@zedat.fu-berlin.de>
In-Reply-To: <541786BE.6010105@freebsd.org>
References:  <20140916020541.03c18d04.ohartman@zedat.fu-berlin.de> <54178607.1060305@freebsd.org> <541786BE.6010105@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help

[-- Attachment #1 --]
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 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:
> >>
> >>>> 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 (small
> > 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 above).

How to update bootcode on UEFI layout? I created a GPT partition with type efi (1 GB) as
well as a 512KB partition typed freebsd-boot.

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 with the old
console and 800x640 resolution. This might indicate some minor but very effective mistake
I made.

Oliver

[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBAgAGBQJUF8/fAAoJEOgBcD7A/5N8tmgH/1j2uaTJkwa8wognvF2yake9
mCG8Dg8YRD99yd0aue4oUZAxdkPas4Z6Nzyd0VMFbhZx4eXaU2cAfwKq1afj8tL/
41gozRDIU+nskQuIP4xO6QXnPU/4TjBuZINGuD99FHhmaWnv4Ow5wzXVw6dF5B1K
LyOXHeRQvlzuXkk/s2WVwK0YZeVacWE2v/H3zOMvJ3FIedS3iDV5mGCXJHoEVggz
N5Bqowvtxilq+I/BOXCrnA1A8fAlP9k1RXNBZaX5SshWmbjoCwE8VowFYwG53gRw
diBY7mxyM2zhLvMkHmhBASmK1dfT2O374cfsrPXTsRGo2Z/YrsKbdN51c9j/3W8=
=7pEr
-----END PGP SIGNATURE-----

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