*BSD News Article 42337


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!agate!news.mindlink.net!giant!a09878
From: a09878@giant.rsoft.bc.ca (Curt Sampson)
Newsgroups: comp.os.386bsd.bugs
Subject: FreeBSD 2.0 and the ASUS PCI Motherboard
Date: 11 Feb 1995 06:24:27 GMT
Organization: MIND LINK! Communications Corp., Langley, BC, Canada
Lines: 39
Message-ID: <3hhl6r$q66@deep.rsoft.bc.ca>
NNTP-Posting-Host: giant.mindlink.net
Summary: Doesn't work!

I went into the shop to pick up my new system today and discovered,
somewhat to my horror, that FreeBSD doesn't seem to boot on it. I'd
started with a boot disk made from the "January 1994" [sic] Walnut
Creek CD-ROM, but upon encountering the errors described below, went
and downloaded the boot disk from the 2.0-021092 snapshot and got the
exact same results. I then went and downloaded the NetBSD 1.0 boot
disks and found that the system booted just fine. (NetBSD seems to get
through its autoconfig about six or eight times as fast as FreeBSD,
BTW, though the messages aren't as informative.) 

Now this isn't that big a deal for me, as I was going to run NetBSD
anyway. (My NetBSD CD-ROM hasn't arrived yet, so I thought the FreeBSD
CD-ROM would do for testing.) However, I thought that the FreeBSD
folks would want to know about this.

I've got a 486/66 on an ASUS PVI-486 SP3 motherboard, which is a
PCI-bus motherboard using an SiS chipset. One of the PCI slots has an
ATI Graphics Pro, the other has the PCI-SC200 SCSI controller (NCR
53C810-based) that optionally accompanies the system board.

What happens is that FreeBSD configures the graphics card and the SCSI
controller just fine, and then goes on to find a second, identical
graphics card and SCSI controller on the same interrupts. After it
waits for the SCSI bus to settle on the "phantom" SCSI card (about
twenty seconds) it tries to probe the SCSI bus for devices at which
point the system hangs with the hard disk light on. FreeBSD claims to
find the graphics card and SCSI controler at pci0:11 and pci0:12
respectively, and the phantom ones at pci0:23 and pci0:24, I believe.

That's about all I have on the problem. If someone wants an exact copy
of those hardware messages, I can boot it up again, copy them out and
type them in.

cjs
--
Curt Sampson  a09878@giant.rsoft.bc.ca		Opinions are mine,
Fluor Daniel Wright, Ltd. 604 488 2226		not Fluor Daniel's.
1075 W. Georgia Street
Vancouver, B.C., V6E 4M7	 	De gustibus, aut bene aut nihil.