From owner-freebsd-questions@FreeBSD.ORG Wed Dec 31 03:48:52 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 3A62FBF7 for ; Wed, 31 Dec 2014 03:48:52 +0000 (UTC) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ECB4B1887 for ; Wed, 31 Dec 2014 03:48:51 +0000 (UTC) Received: from r56.edvax.de (port-92-195-39-170.dynamic.qsc.de [92.195.39.170]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx02.qsc.de (Postfix) with ESMTPS id 4F178276B7; Wed, 31 Dec 2014 04:48:50 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id sBV3mnVK002013; Wed, 31 Dec 2014 04:48:49 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Wed, 31 Dec 2014 04:48:49 +0100 From: Polytropon To: Christian Baer Subject: Re: FreeBSD with Win7 and UEFI Message-Id: <20141231044849.ebf531c1.freebsd@edvax.de> In-Reply-To: References: <20141226072950.GB13694@kontrol.kode5.net> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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: Wed, 31 Dec 2014 03:48:52 -0000 On Tue, 30 Dec 2014 16:03:22 +0100, Christian Baer wrote: > Am 28.12.2014 um 20:40 schrieb Warren Block: > > > 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. > > Yes, I've read about that and the fact that it has been quite hard. This > actually did surprise me a bit, considering that UEFI has been around > for a while now. AS/400 is around since the 1980's, and still I can't find a Linux or BSD that will run on it. ;-) The problem with UEFI seems to be that, even though there is documentation and attempts of standards, it's still a tricky black box, and manufacturers don't want to tell what goes on in their "micro OS" BIOS replacement. > In this case, I really went out of my way to make it overly clear, that > I was booting me computer in EFI mode and that the boot menu is from the > mainboard's firmware and offered before a single access to the SDD has > been made. I would get this boot loader (or boot menu) if I removed all > drives from my system and pressed F12 while starting the system. Using the traditional FreeBSD boot manager would surely be the more appealing option. Depending on if you can try to use MBR partitioning instead of GPT (and therefore, using the boot0 boot manager with MBR), this might be worth a try. UEFI seemed to support both MBR and GPT. But this is just a W.A.G., I don't have any UEFI hardware here to verify, and I'm not a "multi-booter" anymrore, sorry. > And it does offer a little something that I currently do not have: More > time. If I miss the right moment, I can't choose the OS, the computer > just boots up Windows as this is the default and I cannot set the > default to FreeBSD. This is the typical limitation by UEFI. If you can use FreeBSD's boot manager, a default will be available which will boot the desired FreeBSD if no action is taken at system startup. But as far as I understand, this will require MBR partitioning in combination with UEFI... -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...