Date: Sun, 28 Dec 2014 16:49:56 +0100 From: Christian Baer <christian.baer@uni-dortmund.de> To: freebsd-questions@freebsd.org Subject: Re: FreeBSD with Win7 and UEFI Message-ID: <m7p8r5$jiv$1@ger.gmane.org> In-Reply-To: <20141226072950.GB13694@kontrol.kode5.net> References: <m7hfff$hno$1@ger.gmane.org> <20141226072950.GB13694@kontrol.kode5.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 26.12.2014 um 08:29 schrieb James Griffin: > As long as you have a part of the disk for FreeBSD, when you install > FreeBSD it will provide its own bootmanager. This is what works best. > I wouldn't bother trying to get Windows to do this. Well, technically, this isn't what happens. I installed Win7 first and FreeBSD after that. When I was finished, only Windows booted. The only way I could get FreeBSD to start, was to go into the setup of the motherboard (BIOS setup) and tell it to boot off another partition. What I wanted was the computer automatically starting the boot manager and letting me choose whether I wanted Windows or FreeBSD. That however didn't happen. 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? Best regards, Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m7p8r5$jiv$1>