From owner-freebsd-alpha  Tue Jul 18 12: 4: 6 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id E756637BADB; Tue, 18 Jul 2000 12:03:58 -0700 (PDT)
	(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id PAA03978;
	Tue, 18 Jul 2000 15:03:57 -0400 (EDT)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.9.3/8.9.1) id PAA45540;
	Tue, 18 Jul 2000 15:03:57 -0400 (EDT)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Tue, 18 Jul 2000 15:03:57 -0400 (EDT)
To: wilko@freebsd.org
Cc: FreeBSD-alpha mailing list <freebsd-alpha@freebsd.org>
Subject: Re: test results for Lynx (AS2100A)
In-Reply-To: <20000718203813.B2834@freebie.demon.nl>
References: <20000718193708.A2031@freebie.demon.nl>
	<14708.41311.494517.133622@grasshopper.cs.duke.edu>
	<20000718203813.B2834@freebie.demon.nl>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <14708.43258.138626.9497@grasshopper.cs.duke.edu>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


Wilko Bulte writes:
 > On Tue, Jul 18, 2000 at 02:29:17PM -0400, Andrew Gallatin wrote:
 > > 
 > > Wilko Bulte writes:
 > >  > Below the results of booting 4.1-RC on a Lynx (AS2100A).
 > >  > Works reasonably well, but locks up/waits forever after printing
 > >  > 'waiting 15 secs for SCSI devices to settle'.
 > >  > 
 > >  > Any ideas? Maybe interrupts don't get thru? (wild guess).
 > >  > 
 > >  > Test boot floppies can be pulled over for test, I have the Lynx wednesday &
 > >  > thursday available..
 > > 
 > > Yes, the IRQs are almost certainly wrong. I'll try to look into this
 > > tonight or tomorrow (I just had a slew of hardware arrive that we've
 > > been waiting for for quite some time, so I'm pretty busy today).
 > 
 > I notices NetBSD is also quite involved with AS2100[a] these days

It would be very cool if you could try to boot NetBSD on your 2100A &
see what happens.