From owner-freebsd-current Thu Feb 18 1:34:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id C0A88113F3; Thu, 18 Feb 1999 01:33:31 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.2/8.8.8) with ESMTP id JAA63665; Thu, 18 Feb 1999 09:32:39 GMT (envelope-from dfr@nlsystems.com) Date: Thu, 18 Feb 1999 09:32:39 +0000 (GMT) From: Doug Rabson To: Michael Reifenberger Cc: Benjamin Lewis , freebsd-current@freebsd.org, se@freebsd.org Subject: Re: Compaq built-in ncr & tl controllers with 4.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 18 Feb 1999, Michael Reifenberger wrote: > Hi, > On Wed, 17 Feb 1999, Benjamin Lewis wrote: > ... > > We then tried to boot with the 3.1 and the 4.0 boot floppies. Neither was > > able to find the SCSI controller or the ethernet device. Of course, we find > > it odd that 2.2.8 found the devices ok, but newer releases do not. As far > > as I can tell, the hardware is supported by CAM, etc. (I have a Tekram 390F > > 53c875-based card in another 4.0 machine that works great). The installs > > failed with the complaint that no disks could be found to install on. > > I have the same symptoms with an Compaq Proliant 1600. > The cause seems to be that these machines have more than one PCI-Busses which > lay behind on PCI-PCI-Bridges and only one gets probed/found under 3.*, 4.*. > > Furthermore under 2.2.7 the Busses seems to get probed but in an different order > than the BIOS does because the ncr for the internal disks (which gets probed > first by BIOS) is probed last by the Kernel and im my case the BIOS-drive C: > gets da2. Verry annoying if Disks get added into the cabinet... :-( > > Do the symptoms trigger some Ideas by someone? It may be that we aren't detecting the bridge properly in the 3.1 pci code. On the subject of probe ordering, I know about this. We probe the pci bus tree in breadth first order (i.e. we finish probing all the devices in the top bus before probing bridges attached to it). I guess most other systems (including your BIOS) use a depth first order which means that the contents of the bus behind the bridge is probed before it goes onto the next device at the top level. I may end up changing this so we probe in a depth first order due to some other changes I am making to the pci code. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message