Date: Tue, 4 Jun 2019 08:16:29 -0600 From: Warner Losh <imp@bsdimp.com> To: Tomoaki AOKI <junchoon@dec.sakura.ne.jp> Cc: FreeBSD Current <freebsd-current@freebsd.org>, Johannes Lundberg <johalun@freebsd.org>, Warner Losh <imp@freebsd.org> Subject: Re: UEFI boot broken in 13? Message-ID: <CANCZdfrh4XP0WJK65w2RjmvV4VLsZswYKR-EoJ-suvdLc4LaPg@mail.gmail.com> In-Reply-To: <20190604212831.360fd1a0c34c9f329e3084fc@dec.sakura.ne.jp> References: <71a0c9f7-0b1f-3757-fc04-4c0d0a1e1085@FreeBSD.org> <20190604212831.360fd1a0c34c9f329e3084fc@dec.sakura.ne.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 4, 2019 at 7:11 AM Tomoaki AOKI <junchoon@dec.sakura.ne.jp> wrote: > Hi. > > Try attached patch for stand/efi/boot1/boot1.c. > This partially reverts r347193 and works at least for me. > > Without this, boot1.efi (bootx64.efi) forcibly boot from > first physical HDD/SSD, even if forcibly booted from other > physical drive via BIOS (UEFI firmware) menu. > > Remaining parts of r347193 and following some commits does not > affect. > > *Hand-crafted reverse patch from commit mail [1]. > Reverting whole r347193 is fine, too. > > [1] > https://lists.freebsd.org/pipermail/svn-src-head/2019-May/124677.html I'll take a look. My experience is that even prior to this patch, forcibly booting also failed though due to ordering issues... Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfrh4XP0WJK65w2RjmvV4VLsZswYKR-EoJ-suvdLc4LaPg>