From owner-freebsd-embedded@FreeBSD.ORG Mon Apr 20 13:55:27 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 9BD4D10656CD for ; Mon, 20 Apr 2009 13:55:27 +0000 (UTC) (envelope-from matthias-bsde@mteege.de) Received: from mail-in-01.arcor-online.net (mail-in-01.arcor-online.net [151.189.21.41]) by mx1.freebsd.org (Postfix) with ESMTP id 5A1D28FC0C for ; Mon, 20 Apr 2009 13:55:27 +0000 (UTC) (envelope-from matthias-bsde@mteege.de) Received: from mail-in-09-z2.arcor-online.net (mail-in-09-z2.arcor-online.net [151.189.8.21]) by mx.arcor.de (Postfix) with ESMTP id EB8A1332700; Mon, 20 Apr 2009 15:55:25 +0200 (CEST) Received: from mail-in-10.arcor-online.net (mail-in-10.arcor-online.net [151.189.21.50]) by mail-in-09-z2.arcor-online.net (Postfix) with ESMTP id D7E6E28EE08; Mon, 20 Apr 2009 15:55:25 +0200 (CEST) Received: from crn.mteege.de (six.mteege.de [88.79.143.204]) by mail-in-10.arcor-online.net (Postfix) with ESMTP id 8D38228F063; Mon, 20 Apr 2009 15:55:24 +0200 (CEST) X-DKIM: Sendmail DKIM Filter v2.8.2 mail-in-10.arcor-online.net 8D38228F063 Received: from cab.de ([192.168.153.14]) by crn; Mon Apr 20 13:55:24 GMT 2009 Message-ID: <4b925570b9c69698b6eb029454ed29fa@mteege.de> To: nick@van-laarhoven.org, freebsd-embedded@freebsd.org Date: Mon, 20 Apr 2009 15:55:23 +0200 From: Matthias Teege In-Reply-To: <200904201535.21191.nick@van-laarhoven.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Cc: Subject: Re: nanobsd boot slice selection does not work X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-embedded@freebsd.org List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Apr 2009 13:55:28 -0000 Moin, > I've seen this problem as well, but can't for the life of me remember what I I'm relieved to hear that. > did about it. Searching in our build environment does not yield an answer. I use fdisk to set the active slice as workaround. > Does changing boot image options change something? I don't think so. I've changed update/noupdate, packet/nopacket, setdrv/nosetdrv without any success. > Or change to boot0sio. perhaps the fact that there is no keyboard confuses > things. I use boot0sio all the time. I is the default in nanobsd. # grep boot0sio /usr/src/tools/tools/nanobsd/nanobsd.sh NANO_BOOTLOADER="boot/boot0sio" I can reproduce the problem under KVM Emulation so I think it isn't a soekris or CF problem. The problem is, that boot0cfg doesn't change the flag for the active slice. In my example slice 2 is always flagged as active. Many thanks Matthias