From owner-freebsd-sparc64@FreeBSD.ORG Sat Jun 12 17:52:34 2004 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D42916A4D0 for ; Sat, 12 Jun 2004 17:52:34 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id B416743D41 for ; Sat, 12 Jun 2004 17:52:33 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from freebsd.org (junior-wifi.samsco.home [192.168.0.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i5CHsPCh015608; Sat, 12 Jun 2004 11:54:25 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40CB4289.5070709@freebsd.org> Date: Sat, 12 Jun 2004 11:51:05 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040304 X-Accept-Language: en-us, en MIME-Version: 1.0 To: jml References: <20040612170533.GA12295@static.protection.cx> In-Reply-To: <20040612170533.GA12295@static.protection.cx> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-sparc64@freebsd.org Subject: Re: E450 installation problems X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jun 2004 17:52:34 -0000 jml wrote: > Hi, > > I'm trying to install 5.2.1 on an E450 from CDROM (generated from > 5.2.1-RELEASE-sparc64-bootonly.iso). > > Unfortunately, after finishing partitioning I get: > > Unable to find device node for /dev/da0b in /dev! > The creation of filesystems will be aborted. > > I tried jumping to a shell to run mknod but mknod doesn't seem to be > anywhere. > > Did I do something wrong / is this a known issue? Not sure what to say about this, maybe others do. > > Also, the raid controller doesn't appear to be in the dmesg, even as an > unconfigured device (I believe it is handled by the asr driver). > I don't know why it wouldn't show up as an unconfigured device. What does 'pciconf -lv' show? In any case, the asr driver has absolutely no chance of working on sparc64 or any other non-i386 architecture. It is neither 64-bit clean nor endian clean, and it is missing the code needed to work with 64-bit s/g lists. Scott