From owner-freebsd-current@FreeBSD.ORG Sun Oct 9 11:10:59 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24E80106564A; Sun, 9 Oct 2011 11:10:59 +0000 (UTC) (envelope-from matt.thyer@gmail.com) Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by mx1.freebsd.org (Postfix) with ESMTP id 46D448FC0A; Sun, 9 Oct 2011 11:10:57 +0000 (UTC) Received: by wwn22 with SMTP id 22so2674253wwn.1 for ; Sun, 09 Oct 2011 04:10:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+dfhJcgkwZUE2WoiWrRij+Xa7s0WufAefZwBkGXUH38=; b=U7JltWoN5ybrNdRAbRwuJboVyHjPJYGCxWR8G1+Rb3TVDc/Mxw3fQXI6GULADf7+bP VtRBXd1JEbRBrGoQIFEDP6VX/sDV5hwHyWFNkdXU3eqK1O/P4Fm4kN81gWSxc0ka/3HO aiXz25PL4+nFLO9LMoQ4OCT1enbq7IOnGLPmk= MIME-Version: 1.0 Received: by 10.216.25.196 with SMTP id z46mr4900640wez.16.1318158653123; Sun, 09 Oct 2011 04:10:53 -0700 (PDT) Received: by 10.216.36.18 with HTTP; Sun, 9 Oct 2011 04:10:53 -0700 (PDT) In-Reply-To: <20111009025047.GB13517@vs2.gothschlampen.com> References: <20111008155252.GA24223.edited@vs2.gothschlampen.com> <4E90B4B1.7000009@FreeBSD.org> <4E90C801.4060108@FreeBSD.org> <4E90EBF5.4090101@freebsd.org> <20111009025047.GB13517@vs2.gothschlampen.com> Date: Sun, 9 Oct 2011 21:40:53 +1030 Message-ID: From: Matt Thyer To: "Thomas K." Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Warren Block , Glen Barber , freebsd-current@freebsd.org, Garrett Cooper , Nathan Whitehorn Subject: Re: Memstick image differences between 8.x and 9.x X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Oct 2011 11:10:59 -0000 On 9 October 2011 13:20, Thomas K. wrote: > On Sat, Oct 08, 2011 at 07:28:55PM -0600, Warren Block wrote: > > On Sun, 9 Oct 2011, Matt Thyer wrote: > > >On Oct 9, 2011 11:04 AM, "Nathan Whitehorn" > wrote: > > >> > > >> On 10/08/11 19:25, Matt Thyer wrote: > > >>> > > >> > > >There is also the interesting question of actually installing to GPT on > the hard disk, which is the default in 9.0. Does this not work on some > systems? If so, do we want to blacklist > > >them and use a different default partition scheme? Can we identify > systems that violate regular PC boot standards and reject GPT? Any data on > any of these points would be appreciated. > > >> > > >I don't think there have been any reports of failure to boot properly > formatted GPT yet. > > > > Lenovo T420S and T520, from the links above. Install GPT on the > > hard drive, try to boot. > > > > http://forums.freebsd.org/showthread.php?t=26304 > > http://forums.freebsd.org/showthread.php?t=26759 > > http://forum.thinkpads.com/viewtopic.php?f=9&t=98078 > > As I used parted from Linux to fix the alternate GPT, i.e. put it not at > the > end of the image data but on the end of the disk, and it still did not > appear > in the boot device list, the Acer AX3960 should probably be on the list > as well. > > Being a Core i7 2600k system maybe 6 months old, it's rather recent > hardware, > but doesn't boot from the memstick image. > > > Regards, > Thomas > Failure to boot the FreeBSD 9.0-BETA{2|3} memstick images does not indicate a problem with a PCs BIOS/UEFI as these images are not properly formatted. If we were able to come up with examples of BIOS/UEFI that cannot boot from GPT partitioned volumes there would not be a problem as long as bsdinstall still supports partitioning volumes with MSDOS/MBR partitioning schemes. The big problem is being able to launch the installation process to start with which is yet another reason to have the memstick image non-GPT even if you could work out a script/kludge etc to be able to write a properly formatted GPT memstick. The solution to this issue is obvious.