From owner-freebsd-embedded@FreeBSD.ORG Thu Apr 23 22:01:38 2009 Return-Path: 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 20E6A106564A for ; Thu, 23 Apr 2009 22:01:38 +0000 (UTC) (envelope-from rickvanderzwet@gmail.com) Received: from mail-fx0-f162.google.com (mail-fx0-f162.google.com [209.85.220.162]) by mx1.freebsd.org (Postfix) with ESMTP id 786458FC17 for ; Thu, 23 Apr 2009 22:01:37 +0000 (UTC) (envelope-from rickvanderzwet@gmail.com) Received: by fxm6 with SMTP id 6so448984fxm.43 for ; Thu, 23 Apr 2009 15:01:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=hHGOEoqNI3Spo0UCyiWHF7QZF594AGQOYLCfzxcIctw=; b=pHVQTGA36ixBXVzfO3P76tjbR9ZGI8nTFY3YiOvIXiJ21+zr840pxzh2nK7MkPucVn zSd9cajnMACYvXTOrRnkwfbYPh01RLNsvborOtnKFpPN5/5JBBaSITM3D0r4Fkv3lDPX 3cXU3HstLAs1CI9UJXf5jHkQptM6KQVJt5wB0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; b=jBrpIdm1WhIixckB5U98FnaWuf17iobyMRc21Ole2ecH/smAY7pu9rHIyGzFC3eiov qTMYwaz4nTCe7kkwbofGx7EHRkNOBhm8NJ3jaDUaZHLqAr3UoNdDheh6iZVIJAWWZaPM 3Bc+REMjQNj239xVq2rfARV2bLSV+T6aB12LU= MIME-Version: 1.0 Sender: rickvanderzwet@gmail.com Received: by 10.223.108.74 with SMTP id e10mr482171fap.35.1240522720687; Thu, 23 Apr 2009 14:38:40 -0700 (PDT) Date: Thu, 23 Apr 2009 23:38:40 +0200 X-Google-Sender-Auth: c313f4fc20d1f675 Message-ID: <5aaae08a0904231438v5b655056g8852dc11f1e83987@mail.gmail.com> From: Rick van der Zwet To: freebsd-embedded@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: nanobsd image boot issues X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Apr 2009 22:01:38 -0000 Boot delay and fail issues on various hardware using nanobsd generated RELENG_7_1 images on a sandisk 2gb CF (SDCFH2-002G). For example while trying to run a image on a soekris net4521 (bios 1.33) it seems to take ages (up to a minute) to start booting. Same image supplied to a PC (intel Pentium 1 & award bios) using a CF->IDE converter does not seems to boot at all, neither does a net4801 (bios 1.33). Just seems trying to find a boot loader. The net4801 even bails out after a while. Output of fdisk of image list as follows: Disk: /dev/disk3 geometry: 992/64/63 [4001760 sectors] Signature: 0xAA55 Starting Ending #: id cyl hd sec - cyl hd sec [ start - size] ------------------------------------------------------------------------ *1: A5 0 1 1 - 491 15 63 [ 63 - 495873] FreeBSD 2: A5 492 1 1 - 983 15 63 [ 495999 - 495873] FreeBSD 3: A5 984 0 1 - 992 15 63 [ 991872 - 9072] FreeBSD 4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused A reference pfSense image put on the same CF card is boot perfectly fine under the net4521 & PC (untested net4801): Disk: /dev/rdisk3 geometry: 992/64/63 [4001760 sectors] Signature: 0xAA55 Starting Ending #: id cyl hd sec - cyl hd sec [ start - size] ------------------------------------------------------------------------ 1: 00 0 0 0 - 0 0 0 [ 0 - 0] unused 2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused 3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused *4: A5 0 0 1 - 1023 254 63 [ 0 - 50000] FreeBSD Which makes me wonder about the sector start, why does nanobsd not start at sector 0, but uses sector 63 as a start instead. Could that be the explanation or is something else going on? /Rick -- http://rickvanderzwet.nl