From owner-freebsd-stable@FreeBSD.ORG Thu Oct 9 15:23:40 2014 Return-Path: Delivered-To: freebsd-stable@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 7249A1CD; Thu, 9 Oct 2014 15:23:40 +0000 (UTC) Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D82D2DA9; Thu, 9 Oct 2014 15:23:39 +0000 (UTC) Received: by mail-wg0-f49.google.com with SMTP id x12so1591989wgg.20 for ; Thu, 09 Oct 2014 08:23:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=5GVxhhjMS1KkGcMg9/iQOhXftDY0i6mNGo5q4w5plPI=; b=EyFQkwuN9A6Z61JkLRRUqo8UJbdM0ZHuyQq20HeQRN0KBSebZicRsri+LqfrkWc1lx kxZPTz76qQLtyU4r8ma265Y5ZlyTe99ycrn2y3xoXUN2I5+XMXdYTY8yjgL38ISM4Tr2 bLDdYNf08t0iRRWeH8QFijyX94vIuHdxBymEYN/bvdAxkB48lL/NlE6bFiNQTHqQbP7S yBODytxniN22p7dVtHlwc14RjTHkb7UnVJ9Bzqv2I49xj52VAHg4jr/JagqYO5SBZksA Zywv/ObQOGR7bEp+O8EeDPF15LOH9dt5l+HDiwT8mcokFrqjDzpH7/T/DWicFsPQuHwd zxYQ== MIME-Version: 1.0 X-Received: by 10.180.187.83 with SMTP id fq19mr40183327wic.59.1412868218050; Thu, 09 Oct 2014 08:23:38 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.106.136 with HTTP; Thu, 9 Oct 2014 08:23:37 -0700 (PDT) In-Reply-To: <54369687.5020807@beastielabs.net> References: <201410011358.s91DwOXJ033137@fire.js.berklix.net> <88376822.lFZdKxbhSR@ralph.baldwin.cx> <54333019.9010304@egr.msu.edu> <54369687.5020807@beastielabs.net> Date: Thu, 9 Oct 2014 08:23:37 -0700 X-Google-Sender-Auth: wOJbYYDHuF1Cht6WinBKmT5Ahqs Message-ID: Subject: Re: Media image names - Document & rationalise. From: Adrian Chadd To: Hans Ottevanger Content-Type: text/plain; charset=UTF-8 Cc: Glen Barber , Adam McDougall , FreeBSD Stable Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Oct 2014 15:23:40 -0000 Hi! Can you bug this? http://bugs.freebsd.org/submit/ ? This is likely not the only board with this behaviour and having it in the bug system with the motherboard vendor/type will be really helpful. Thanks! -a On 9 October 2014 07:07, Hans Ottevanger wrote: > On 10/07/14 02:13, Adam McDougall wrote: >> >> On 10/06/2014 16:34, John Baldwin wrote: >>> >>> I believe the issue here as I discussed with Marcel last year is that the >>> x86 >>> installer needs to tell gpart to set the active flag on the dummy MBR >>> slice in >>> the PMBR if GPT is being used without EFI (the installer knows if it is >>> booted >>> via EFI or not). >> >> >> I ran into this today too with 10.1-RC1 (and recent 11 I think) on a >> BIOS based desktop freshly liberated from windows. It would not boot. >> I got it going with gpart but as a new user I'd be in trouble. >> > > This is exactly what I see with my oldish Intel DP965LT main board. > Installation went perfect up to 9.2, but for later releases I have to issue > > /sbin/gpart set -a active ada0 > > either from a shell before rebooting the fresh installation or after > rebooting single user from the install media. > > I also hear from several acquaintances (potential "switchers"), often with > similar Intel (or Foxconn) boards that their fresh install of FreeBSD "does > not even boot". On the other hand my even older Asus NL4VM-DH board does not > have this issue (It does complain about being unable to read the backup GPT > header, but that is another issue.) > > If it is not possible to have the installer set the active flag when a BIOS > is detected, the remedy using gpart could at least be documented in the > installation notes, maybe even in the handbook. > >>> >>> In 9.2 and older, the flag was always set, but that violated the EFI spec >>> and >>> broke several systems, so in 9.3 and later, gpart was changed to not set >>> the >>> flag by default. However, we should still set it for non-EFI booting via >>> GPT >>> to cater to broken BIOSes (such as yours). >>> > > Kind regards, > > Hans > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"