Date: Tue, 22 Aug 2017 21:58:43 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-sysinstall@FreeBSD.org Subject: [Bug 221674] Installer can't back up when it finds MBR Message-ID: <bug-221674-2920-eA9r8UBOKx@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-221674-2920@https.bugs.freebsd.org/bugzilla/> References: <bug-221674-2920@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221674 --- Comment #4 from Nathan Whitehorn <nwhitehorn@FreeBSD.org> --- (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 install 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 press 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 manager, which would not be able to start FreeBSD through the EFI loader. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-221674-2920-eA9r8UBOKx>