Date: Wed, 2 Apr 1997 17:29:42 +0300 (EEST) From: Andrew Stesin <stesin@gu.net> To: Satoshi Asami <asami@vader.cs.berkeley.edu> Cc: hackers@freebsd.org, scsi@freebsd.org Subject: Re: 2 PCI busses, 2 AIC chips, 2.2.1. Howto ? Message-ID: <Pine.BSF.3.95q.970402171956.283L-100000@trifork.gu.net> In-Reply-To: <199704021041.CAA03124@silvia.HIP.Berkeley.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, thanks for comments. On Wed, 2 Apr 1997, Satoshi Asami wrote: > * 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. Unfortunately (or vice versa? ;) I have no access to the box' internals, I'm not authorized to open the case and look inside. But: the box is "genuine Intel", the model is Magellan W/15", base board (kinda of backplane) is XXpress 15" Rel 2, with 1 P166 CPU module. I'll try to find what the bridge chip is. But what is the chance that _both_ AIC chips are "on the other side of the bridge", anyway? > * 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. Yep, I got the idea. > * ....^^^^.... > * 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. Gmmm... > > Satoshi > Best regards, Andrew Stesin nic-hdl: ST73-RIPE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95q.970402171956.283L-100000>