From owner-freebsd-embedded@FreeBSD.ORG Fri Nov 6 20:33:04 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 1DFB810656A3 for ; Fri, 6 Nov 2009 20:33:04 +0000 (UTC) (envelope-from sven@hazejager.nl) Received: from mail-yx0-f171.google.com (mail-yx0-f171.google.com [209.85.210.171]) by mx1.freebsd.org (Postfix) with ESMTP id DBBFB8FC29 for ; Fri, 6 Nov 2009 20:33:03 +0000 (UTC) Received: by yxe1 with SMTP id 1so1290909yxe.3 for ; Fri, 06 Nov 2009 12:33:03 -0800 (PST) MIME-Version: 1.0 Received: by 10.101.149.3 with SMTP id b3mr5154764ano.115.1257537608193; Fri, 06 Nov 2009 12:00:08 -0800 (PST) X-Originating-IP: [83.160.136.100] Date: Fri, 6 Nov 2009 21:00:08 +0100 Message-ID: <8ffccde70911061200t6788ca9bo67a094122f18b6ab@mail.gmail.com> From: Sven Hazejager To: freebsd-embedded@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Problem booting nanoBSD 7.2-p4 on Alix 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: Fri, 06 Nov 2009 20:33:04 -0000 All, I'm having some challenging issues booting nanoBSD 7.2-p4 on CF on an Alix serial-only system. Symptom: I'm seeing boot0sio fine, I can get into the loader etc. boot after typing "boot" or letting it timeout, I see "Booting [/boot/kernel/kernel]..." and I get one "/" character on the next line but then everything stops. The loader prompt allows me to do an "ls" and I can see the files on the first slice just fine. This happens both with GENERIC and with my own kernel. GENERIC and my own kernel boot fine over PXE. Things I already tried: - Using both CHS and LBA geometry of the CF card as reported by Alix tinybios in nanoBSD - Set tinybios both to CHS and LBA mode - Changed nanoBSD boot0config to include "-o nopacket" Possibly I have NOT tested all combinations of above options to be honest, but I'm not sure if the problem lies with geometry or not...? At the very least I'm staring myself blind :-) By the way, the nanoBSD disk image works fine (with heads=16 and sectors=63) in VMware (in that case I do not call the cust_comconsole function in nanoBSD)! Cheers, Sven