From owner-freebsd-sysinstall@freebsd.org Tue Aug 22 21:58:43 2017 Return-Path: Delivered-To: freebsd-sysinstall@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EA14ADE70F5 for ; Tue, 22 Aug 2017 21:58:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D804B76ECF for ; Tue, 22 Aug 2017 21:58:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7MLwhuu046896 for ; Tue, 22 Aug 2017 21:58:43 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-sysinstall@FreeBSD.org Subject: [Bug 221674] Installer can't back up when it finds MBR Date: Tue, 22 Aug 2017 21:58:43 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: conf X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: nwhitehorn@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-sysinstall@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Aug 2017 21:58:44 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221674 --- Comment #4 from Nathan Whitehorn --- (In reply to MMacD from comment #2) It's one installer, the issue is that it has no idea if the machine has CSM= or not. You can't know that unless you booted CSM. You can just boot the insta= ll disk that way by telling your BIOS that don't want to do an EFI boot if you don't want EFI boot. We could provide a "This *might* be bootable if you pr= ess OK" fallback, but I would prefer just modifying the warning to tell people = to disable EFI boot if they don't want EFI boot. (In reply to Ed Maste from comment #3) That's interesting. I don't see an obvious point in the history of the EFI loader where that changed (no disklabel support, for example). How have you= set up your disks on ARM? This situation is also a little dubious in that the firmware would probably either see the FreeBSD EFI partition and boot that, giving no opportunity to run any MBR-based boot manager (or Windows), or see the MBR-based boot mana= ger, which would not be able to start FreeBSD through the EFI loader. --=20 You are receiving this mail because: You are the assignee for the bug.=