From owner-freebsd-alpha  Thu Nov 16 11:13:30 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
	by hub.freebsd.org (Postfix) with ESMTP id 051E337B479
	for <alpha@freebsd.org>; Thu, 16 Nov 2000 11:13:28 -0800 (PST)
Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71])
	by feral.com (8.9.3/8.9.3) with ESMTP id LAA11035;
	Thu, 16 Nov 2000 11:13:27 -0800
Date: Thu, 16 Nov 2000 11:13:25 -0800 (PST)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: John Polstra <jdp@polstra.com>
Cc: alpha@freebsd.org
Subject: Re: 4.2-RC1 failure on 164LX
In-Reply-To: <200011161904.eAGJ4Mf48976@vashon.polstra.com>
Message-ID: <Pine.LNX.4.21.0011161112480.9657-100000@zeppo.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


> In article <Pine.LNX.4.21.0011161059350.9657-100000@zeppo.feral.com>,
> Matthew Jacob  <mjacob@feral.com> wrote:
> > > 
> > > A question: if the floppy had read errors, would they be detected
> > > and reported?  I.e., is it worthwhile to try a different diskette?
> > 
> > No, SRM does complain about bad diskettes. At least the Multia one does all
> > the time.
> 
> But does /boot/loader complain about read errors after it gets
> control?

No- but it calls back into SRM, and SRM should complain to the console.

> 
> > What I had been thinking of is taking boot.flp and copying all 3MB
> > to the head of a SCSI or IDE disk and booting that on your 164LX.
> 
> Hrm, I'd love to help but I don't think I can take it quite that far.
> :-(

Okay. Whatever you can do. We suck right now.

-matt




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message