From owner-freebsd-alpha@FreeBSD.ORG Sun Feb 20 23:51:21 2005 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8483C16A4CF for ; Sun, 20 Feb 2005 23:51:21 +0000 (GMT) Received: from smtp4.sea.theriver.com (smtp4.sea.theriver.com [216.39.128.19]) by mx1.FreeBSD.org (Postfix) with SMTP id 2D50E43D1D for ; Sun, 20 Feb 2005 23:51:21 +0000 (GMT) (envelope-from tponsford@theriver.com) Received: (qmail 10571 invoked from network); 20 Feb 2005 23:51:18 -0000 Received: from 207-207-75-40.ip.theriver.com (HELO theriver.com) (tponsford@207.207.75.40) by 216.39.128.7 with SMTP; Sun, 20 Feb 2005 23:51:18 +0000 Message-ID: <42190EB0.9060502@theriver.com> Date: Sun, 20 Feb 2005 15:26:56 -0700 From: Tom Ponsford User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7b) Gecko/20040429 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-alpha@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: re: kernel panic on AS1000a X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Feb 2005 23:51:21 -0000 Hi All, Well I had a chance to play with the AS1000 this weekend. Before playing with the hints before booting the cdrom, I tried two things, I changed the boot_osflag from 0 to blank AND I took out a floppy that was in the floppy drive. The result was no panic and I was able to get to the install menu. I kept the same 64MB of mem as it should install under that, which is all I'm trying to do just now. The floppy in question was the configuration program as200rcu.exe used to configure the raid controller under the arc console.. I haven't tried another floppy to see if that was the cause, we can check that out later, but my next problem is also a show stopper. When booting, the software sees and correctly identifies the disks in the dmesg. And when the install menu appears, going into into the disklabel menu, the install program correctly identifies the the disks, ie., cd0, mlx0 mlx1. But when entering the disklabel menu, there is no disk size defined at the top of the menu. It seems the disklabel menu doesn't yet see the disk geometry. I suspect I need to do something to the disks. Maybe I missed a step, pilot error? a bug? The two disk attached to the DAC960 raid controller are defined as JBOD, not RAID. I think I tried the install with the disks formatted, and .or unformatted (DOS) by the raid config utility. But either way it made no difference, the disklabel menu does not see the size of the disk! Any more hints! Thanks tom -- --- Please do not read this sig. If you have read this far, please unread back to the beginning.