From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 23 12:08:04 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 941FC106566B for ; Fri, 23 Mar 2012 12:08:04 +0000 (UTC) (envelope-from scdbackup@gmx.net) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by mx1.freebsd.org (Postfix) with SMTP id E36738FC0A for ; Fri, 23 Mar 2012 12:08:03 +0000 (UTC) Received: (qmail invoked by alias); 23 Mar 2012 12:07:57 -0000 Received: from 165.126.46.212.adsl.ncore.de (HELO 192.168.2.69) [212.46.126.165] by mail.gmx.net (mp016) with SMTP; 23 Mar 2012 13:07:57 +0100 X-Authenticated: #2145628 X-Provags-ID: V01U2FsdGVkX19pBoQS4LVpgqOakoHfzcKckTy7sTip8UMgqqdeVB 6MT1ExKl8pctN9 Date: Fri, 23 Mar 2012 13:08:33 +0100 From: "Thomas Schmitt" To: freebsd-hackers@freebsd.org References: <4F6C5E33.7000506@herveybayaustralia.com.au> In-Reply-To: <4F6C5E33.7000506@herveybayaustralia.com.au> Message-Id: <10030481899038@192.168.2.69> X-Y-GMX-Trusted: 0 Subject: Re: iso2flash img X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2012 12:08:04 -0000 Hi, > Thats the whole point of this exercise - I can't, no cdrom: its a netbook. I hoped that you had a USB attachable optical drive in reach for development. > My disk worked in VBox, so I'm sure it is just a netbook thing. I > also use that disk as my "install" disk, so I'm not sure exactly what > partitions been on it now, it has been used for FreeBSD, PC-BSD, Linux > distros, etc. After copying the ISO image to the base device (/dev/da0 rather than /dev/da0s1), it now carries the isohybrid MBR which marks a single DOS partition and leaves the rest of the disk unclaimed. A partition editor should be able to push the end of the partition to the next 1 MiB boundary, without altering the partition content. But as said, it is unlikely that this misalignement of the partition end is the cause. The observable state of ISOLINUX rather points to a problem between hardware, firmware, and the SYSLINUX programs. Have a nice day :) Thomas