Date: Mon, 22 Sep 1997 12:43:59 +0930 From: Greg Lehey <grog@lemis.com> To: dfinley@netgate.compaq.com Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Installation problems Message-ID: <19970922124359.10054@lemis.com> In-Reply-To: <vines.qod5%2BjKR7oA@netgate.compaq.com>; from dfinley@netgate.compaq.com on Sun, Sep 21, 1997 at 09:19:28PM -0600 References: <vines.qod5%2BjKR7oA@netgate.compaq.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Sep 21, 1997 at 09:19:28PM -0600, dfinley@netgate.compaq.com wrote:
> To whom it may concern:
>
> I am having trouble installing FreeBSD on my personal system. I have a
> Pentium Pro 200 with three 2GB SCSI drives, a 2GB SCSI Archive Python DAT
> drive, an NEC 4X SCSI cdrom drive, a Western Digital 1.2GB EIDE drive, and
> a Conner 540MB IDE drive. My SCSI controller is an Adaptec 1522A ISA card.
> Everytime I boot my machine with the bootdisk I get the following message
> after BSD waits for SCSI devices to settle:
>
> Aic at line 2561:unexpected busfree phase
> Debuger ("aic 6360") called
> Panic:panic for historical reasons
>
> What the hell does this mean?
The "historical reasons" turn out to be a little silly. In fact, it
will panic unless you have the kernel debugger installed. In other
words, it's a bit of remnant debug code.
The real problem is deeper in the driver. I've forwarded your message
to somebody who may be able to help.
> I can't seem to get past it! I've tried
> changing the SCSI ID's of all the SCSI devices, I've tried removing all of
> the SCSI drives from the machine except for my external ZIP drive, cdrom,
> and the DAT drive. Nothing works.
>
> I don't know what else to do except.........install Win95. OH PLEASE DON'T
> MAKE ME DO THAT! PLEASE TELL ME WHAT MIGHT BE WRONG!!! Heeeeeeeeeeeeeeeelp
> meeeeeeeeeeeeeeee!!!!
Well, how about removing everything from the SCSI chain except the
CD-ROM drive? Also, check the configuration of the controller. I
don't know this one, but the 1542 has lots of jumpers that need
setting. It's possible that one of these is harmless to Microsoft,
but causes the FreeBSD driver to become confused.
Greg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970922124359.10054>