From owner-freebsd-questions@FreeBSD.ORG Sun Dec 28 19:40:12 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 33A85149 for ; Sun, 28 Dec 2014 19:40:12 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B9FEF647F5 for ; Sun, 28 Dec 2014 19:40:11 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.9/8.14.9) with ESMTP id sBSJe3BN096923 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 28 Dec 2014 12:40:03 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id sBSJe3c0096920; Sun, 28 Dec 2014 12:40:03 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Sun, 28 Dec 2014 12:40:03 -0700 (MST) From: Warren Block To: Christian Baer Subject: Re: FreeBSD with Win7 and UEFI In-Reply-To: Message-ID: References: <20141226072950.GB13694@kontrol.kode5.net> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sun, 28 Dec 2014 12:40:04 -0700 (MST) Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Dec 2014 19:40:12 -0000 On Sun, 28 Dec 2014, Christian Baer wrote: > > This is a little redundant, but I really want to make this clear... > > My motherboard is a Supermicro X10SAT. When the system starts, I can press > F12 which lets me choose the boot device (basicly like in the BIOS setup, but > an a temporary basis). This is a *motherboard* function, this is not a boot > manager from any OS. The motherboard recognises both Windows (list item: > "Windows boot manager") and FreeBSD (list item: "EFI OS"). > > I have seen no other boot manager after the installation nor did I see any > chance to choose/configure/check one during the installation of FreeBSD. The > handbook in rather silent about this subject too, which is quite a surprise > to me. When I started out with Linux, everything was about being able to > coexist with Windows on a single machine. I switched to FreeBSD a little > later. My first FreeBSD CDs were of v3.3 (that was 1999 and I am feeling very > old right about now). The FreeBSD boot manager of back then wasn't as pretty > as the one supplied with SuSE at the time but it did the same thing. > > Is this an EFI thing or have the priorities shifted? UEFI is a whole new game, utterly different from what came before. And FreeBSD's UEFI support is new. As far as I know, it has no provision for multibooting in UEFI. Code to do that would be welcome, it's been difficult just to get the current UEFI support. Your boot menu suggests that Windows 7 is installed for standard BIOS booting. The easiest way to deal with this is to reinstall FreeBSD for standard BIOS booting also, with an MBR format. Then you can install the boot0 multiboot program, but it really doesn't offer anything that the BIOS boot menu does not already have. Please also consider running FreeBSD as a VM with one of the many virtualization options. That has many advantages over multiboot setups.