Date: Mon, 18 Jul 2016 00:33:06 -0600 From: Warner Losh <imp@bsdimp.com> To: Naomichi Nonaka <nao@enuenu.org> Cc: freebsd-users-jp@freebsd.org Subject: [FreeBSD-users-jp 95882] Re: =?utf-8?b?VUVGSeODouODvOODieOBp+OCpOODs+OCueODiOODvOODqw==?= =?utf-8?b?44GX44Gf44GMSERE44GL44KJ6LW35YuV44Gn44GN44Gq44GE?= Message-ID: <CANCZdfrSTbYTOihWmvRFwkysTVb79Uj_uXwUKqgbjJEE2qkGew@mail.gmail.com> In-Reply-To: <b38b5e94-a0f6-2030-3e95-382d25ce7e99@enuenu.org> References: <17f7bf76-9c36-14bc-40e8-e6b04991d7d5@bcb.bai.ne.jp> <b38b5e94-a0f6-2030-3e95-382d25ce7e99@enuenu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
ワーナーです。 2016-07-17 17:11 GMT-06:00 Naomichi Nonaka <nao@enuenu.org>: > 原因は10.3のUEFIインストーラがUEFIのNVRAMにブートエントリを作成しない > ためで、対策としてはLinux等を用いて手動でブートエントリを作成すれば > ファームのドライブ選択リストからFreeBSD用のブートエントリを選択し、 > UEFIでのブートが行えます。 FreeBSD 10.3のUEFIはUEFIのブートマネージャプロトコルをしません。 もしかしたら FreeBSD 11.1がします。 ワーナー FreeBSD 10.3's UEFI doesn't implement the boot manager protocol. Perhaps FreeBSD 11.1 will do so. Warner P.S. I've been working on getting and setting variables after ExitBootServices() has been called, which is key to implementing the standard boot manager protocols. The workaround is to use the Linux tools to setup multi-boot, as has been pointed out here. (My Japanese skill is no good to translate this P.S. and google translate looks too weird for me to cut and paste :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfrSTbYTOihWmvRFwkysTVb79Uj_uXwUKqgbjJEE2qkGew>
