From owner-freebsd-embedded@FreeBSD.ORG  Mon Aug 15 14:16:59 2011
Return-Path: <owner-freebsd-embedded@FreeBSD.ORG>
Delivered-To: freebsd-embedded@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 6385E1065672;
	Mon, 15 Aug 2011 14:16:59 +0000 (UTC)
	(envelope-from espartano.mail@gmail.com)
Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com
	[209.85.220.182])
	by mx1.freebsd.org (Postfix) with ESMTP id 0434E8FC2C;
	Mon, 15 Aug 2011 14:16:58 +0000 (UTC)
Received: by vxh11 with SMTP id 11so5135333vxh.13
	for <multiple recipients>; Mon, 15 Aug 2011 07:16:58 -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:content-transfer-encoding;
	bh=osa4NE4avLgtsXH8ECINWGykcxVEBBEnyGHlmU9CE9M=;
	b=pRexNSjINJ+YvXeZj1DtAsRR6sUhCwro/fmIRvyTL6cUxPBs5nuEJcjs1HyQAnt/rO
	Q5MFM5KkHbS/m8qYetsl062RqHgLFzfiXl/XM/qqER7rART+Djwrfork+9+xUd/ELtde
	JQj7YDM+mcYc5dfNeK5pxoQyF0+8WpMTcFmZc=
MIME-Version: 1.0
Received: by 10.52.111.72 with SMTP id ig8mr3735153vdb.38.1313416427002; Mon,
	15 Aug 2011 06:53:47 -0700 (PDT)
Received: by 10.52.183.39 with HTTP; Mon, 15 Aug 2011 06:53:46 -0700 (PDT)
In-Reply-To: <B03DCB85-A9C1-4AF4-8D10-ABC390BD9B35@develooper.com>
References: <BANLkTikZx=uxokXcpQUi2jksgdMaUp4_+Q@mail.gmail.com>
	<E18BA1D4-C2A7-4FE7-A1A4-0C5B6FDD60DB@bsdimp.com>
	<81D83998-D920-4A69-ACF8-519527D3BC7F@FreeBSD.org>
	<B03DCB85-A9C1-4AF4-8D10-ABC390BD9B35@develooper.com>
Date: Mon, 15 Aug 2011 08:53:46 -0500
Message-ID: <CAJaC6KZsGV9HW8Nz+2nwRYyePSkm-0XNsEoq66N2VzjKSFfU4w@mail.gmail.com>
From: Espartano <espartano.mail@gmail.com>
To: =?ISO-8859-1?Q?Ask_Bj=F8rn_Hansen?= <ask@develooper.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: freebsd-embedded@freebsd.org
Subject: Re: Problem with NanoBSD And Alix Board not device boot
X-BeenThere: freebsd-embedded@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Dedicated and Embedded Systems <freebsd-embedded.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-embedded>, 
	<mailto:freebsd-embedded-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-embedded>
List-Post: <mailto:freebsd-embedded@freebsd.org>
List-Help: <mailto:freebsd-embedded-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-embedded>, 
	<mailto:freebsd-embedded-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2011 14:16:59 -0000

On Mon, Aug 15, 2011 at 1:35 AM, Ask Bj=F8rn Hansen <ask@develooper.com> wr=
ote:
>
> On Jun 5, 2011, at 10:10, Henrik Brix Andersen wrote:
>
>>> nopacket mode is the hardest of all modes to use. =A0Your CF's reported=
 geometry *MUST* be encoded properly in the nano config file. =A0This isn't=
 the geometry that the CF card reader reports, but what the CF card reports=
 in true IDE mode. =A0This will vary from card to card (even cards with exa=
ctly the same label). Unless your boot loader doesn't support packet mode p=
roperly, I'd strongly urge you to use packet mode.
>>
>> Last time I checked, the TinyBIOS used in the Alix boards does not suppo=
rt packet mode properly (but according to http://blog.brixandersen.dk/?p=3D=
94 this was 3 years ago, I'll try to find time to retest against a newer ve=
rsion of TinyBIOS).
>
> One of the 0.99x firmware updates fixed that I believe (sometime in 2007 =
or 2008). =A0 (I use packet mode on Alix boards for what it's worth).
>
>
> =A0- ask
>

Thanks for the answer, my problem was with the CF writer, it had one
pin cuted and that caused a bad written nanobsd image and not boot.