Date: Wed, 2 Apr 1997 02:41:05 -0800 (PST) From: asami@vader.cs.berkeley.edu (Satoshi Asami) To: stesin@gu.net Cc: hackers@freebsd.org, scsi@freebsd.org Subject: Re: 2 PCI busses, 2 AIC chips, 2.2.1. Howto ? Message-ID: <199704021041.CAA03124@silvia.HIP.Berkeley.EDU> In-Reply-To: <Pine.BSF.3.95q.970402122302.283F-100000@trifork.gu.net> (message from Andrew Stesin on Wed, 2 Apr 1997 13:03:25 %2B0300 (EEST))
next in thread | previous in thread | raw e-mail | index | archive | help
* 1. neither of the 2 SCSI busses has anything attached yet (disk drives will * come in a day or two, they ordered drives separately, and no Wide * drives here to try). This shouldn't matter. * 2. SCSI BIOSes for 2 chips aren't configured correctly (just now * it has "BIOS enabled" in SCSIconfig for the first chip and * "BIOS disabled" for the second, should be Ok?) This shouldn't matter either. You will never have to enable BIOS unless you plan to boot from a disk on that bus. * 3. 2.2.1 has some problem with two PCI busses? (while both AICs are * on the second bus??? or on EISA???) What I see at boot * after the "Probing devices on the pci:0 bus" message: It might be that it can't recognize the PCI-PCI bridge. What do the markings on the chip say? I know FreeBSD can deal with DEC and IBM chips. * chip0 <generic PCI bridge (vendor=8086 device=1225 subclass=0)> \ * rev 2 on pci0:0 * chip1 <Intel 82375EB PCI-EISA bridge> rev 5 on pci0:14 * pci0:15:0: Intel Corporation device=0x0008, class=0xff, subclass=0x00 \ * [no driver assigned] Boot with "-v" and send the output to se@freebsd.org. You may want to hack /sys/pci/pcisupport.c by yourself (grep for "IBM") to see if you can get it to work. * ....^^^^.... * This last message is repeated exactly for all pci0:15:[0-7] * values. This is quite weird though. Sounds like a multi-function chip misprobed. Satoshi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704021041.CAA03124>