From owner-freebsd-scsi Wed Apr 9 04:28:27 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA13558 for freebsd-scsi-outgoing; Wed, 9 Apr 1997 04:28:27 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id EAA13551; Wed, 9 Apr 1997 04:28:19 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-8.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA12295 (5.67b/IDA-1.5); Wed, 9 Apr 1997 13:28:16 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id NAA02904; Wed, 9 Apr 1997 13:02:00 +0200 (CEST) Message-Id: <19970409130200.12143@x14.mi.uni-koeln.de> Date: Wed, 9 Apr 1997 13:02:00 +0200 From: Stefan Esser To: stesin@gu.net Cc: hackers@freebsd.org, scsi@freebsd.org Subject: Re: 2 PCI busses, 2 AIC chips, 2.2.1. Howto ? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.68 In-Reply-To: ; from Andrew Stesin on Wed, Apr 02, 1997 at 01:03:25PM +0300 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Apr 2, Andrew Stesin wrote: Sorry for the late reply, I just returned from a vacation ... > The box: Intel XXpress-, 2 AIC7870 chips onboard, EISA bus present. Is this a Pentium or PPro system ? > neither of AICs are recognized at boot. ??? I have the following guesses: > > 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). Should not cause any trouble ... > 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: > > chip0 \ > rev 2 on pci0:0 > chip1 rev 5 on pci0:14 > pci0:15:0: Intel Corporation device=0x0008, class=0xff, subclass=0x00 \ > [no driver assigned] > .....^^^^.... > This last message is repeated exactly for all pci0:15:[0-7] > values. This may be caused by (incorrectly) assuming, that chip was a multi-function device. This does not cause any problems, though ... > What I am missing? Any comments and explanations are appreciated! Seems you have some way of obtaining the boot message log. Could you please provide me with VERBOSE boot messages ? (Eenter "-v" at the "Boot: " prompt.) The problem you are facing comes from the fact, that PCI specifies a single bus directly attached to the CPU, and a tree structure of seconfary buses connected to it. Since this limits the number of low-latency slots to at most 5, server machines often come with more than one bus directly attached to the CPU. But there is no standard way of telling, how many buses are actually connected to a CPU (1 is assumed), and while the bus numbers behing PCI to PCI bridges can be determined in a chip-independent way, this is not possible in the case of multiple CPU to PCI chips. Device specific code has to be added for each of them. (The information on the number of buses can be queried by calling the PCI BIOS, but I'd prefer, if I not have to, for a number of reasons ...) I need more information on the chip set used on that mother board. The Orion should be supported out of the box, but if this is a system with multiple PCI buses directly attached to the CPU based on some other chip set, a small addition to the PCI probe code will be required. Regards, STefan