From owner-freebsd-current@freebsd.org Wed May 23 11:49:18 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2E85FEFB0F1 for ; Wed, 23 May 2018 11:49:18 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp001.me.com (st13p35im-asmtp001.me.com [17.164.199.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C51E686D98 for ; Wed, 23 May 2018 11:49:17 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp001.me.com by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) id <0P9600H00GM1AU00@st13p35im-asmtp001.me.com> for freebsd-current@freebsd.org; Wed, 23 May 2018 10:49:03 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017; t=1527072543; bh=G8FZpYf4gy0n4BBCKI17wuuV1h7nd/BTscYmzHxh4gk=; h=Content-type:MIME-version:Subject:From:Date:Message-id:To; b=NV+nr/B8f/AirSaaNPsmp7osW5f+ljIVtfrl7JtgIvhG2zfIXlnuAe0LJI8BQWciJ 8JFXBZZTpawOgIytzH1bLfRC2y7Nm5DilGhVzDgoBrFRoKwDf74h+EkzxV5CTmogCt rC72m5OQA7JYuU6TtBHVL04lt2CcQnMzl4iEUBnfihKoAf2j1ptAg6PfXxluxmOqt4 VsuR0tE/nbB0qOuJMUlhzMiuqC1qOlUgbKUTGpYg2kC9w87U7R8Gl+zmC0LJgzJDlL 0LpgAUhvv4IOmKw1gdHwKilCWBDa+zYj+cvUO3VWIHooT6x1Am+4v4LnHr3j322cpE vO9uUSnJuFxxg== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) with ESMTPSA id <0P9600BWFGPNY550@st13p35im-asmtp001.me.com>; Wed, 23 May 2018 10:49:02 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-05-23_05:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 suspectscore=1 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1805230109 Content-type: text/plain; charset=utf-8 MIME-version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: UEFI equivalent of boot.config? (Was: Re: [RFC] Deprecation and removal of the drm2 driver) From: Toomas Soome In-reply-to: <20180523.122921.74726348.sthaug@nethelp.no> Date: Wed, 23 May 2018 13:48:58 +0300 Cc: freebsd-current@freebsd.org Content-transfer-encoding: quoted-printable Message-id: <22882C48-69E4-4571-9C6A-F25D6E9CC7B3@me.com> References: <201805222212.w4MMCdA9031937@pdx.rh.CN85.dnsmgr.net> <20180523.122921.74726348.sthaug@nethelp.no> To: sthaug@nethelp.no X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2018 11:49:18 -0000 > On 23 May 2018, at 13:29, sthaug@nethelp.no wrote: >=20 > Hijacking a thread here, >=20 >> Turns out, you can't install FreeBSD using a USB stick image because = the >> BIOS only support MBR. No idea why MBR support was dropped for the = USB images. >>=20 >> In the end I had to find a CD burner, and after a couple of tries = managed to >> install from CD. >=20 > On a somewhat related note - I recently installed 11.1-STABLE on a box > with support for both UEFI and "good old fashioned BIOS". I initially > used UEFI and GPT, but ended up switching to BIOS and MBR because I > needed boot.config to enable booting from an alternate partition. >=20 > Despite lots of Googling I couldn't find a simple way to do this using > config stored on the disk itself (e.g. having "0:ad(0,f)/boot/loader" > in /boot.config) with UEFI. >=20 > Does anybody know if this can be done using UEFI? >=20 > Steinar Haug, Nethelp consulting, sthaug@nethelp.no it can but it a bit different situation there. you can not start bios = boot loader from UEFI loader or vice versa, you only can use the same = platform binaries. for UEFI case, the boot1.efi does not process boot.config, so you have = total 3 options - you switch boot disk in UEFI boot manager, or you use = chain command to load either bootx64.efi from target disk ESP partition = or you use chain command to load /boot/loader.efi from target disk = freebsd root file system. You also can set currdev to point to new root, = but usually you want a bit more (read in the configuration etc) so the = chainload may be a bit easier. Once you have figured out the proper file name to use with chain = command, you can set chain_disk to have it as value and you will have = chain menu entry=E2=80=A6 like = chain_disk=3Dzfs:zroot/ROOT/default:/boot/loader.efi rgds, toomas