From owner-freebsd-current Fri Nov 22 20:22:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA08067 for current-outgoing; Fri, 22 Nov 1996 20:22:43 -0800 (PST) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA08059; Fri, 22 Nov 1996 20:22:24 -0800 (PST) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.2/8.8.2) id PAA03075; Sat, 23 Nov 1996 15:22:18 +1100 (EST) From: David Dawes Message-Id: <199611230422.PAA03075@rf900.physics.usyd.edu.au> Subject: Re: Four problems that really bug me with CURRENT In-Reply-To: <199611221253.NAA07064@x14.mi.uni-koeln.de> from Stefan Esser at "Nov 22, 96 01:53:40 pm" To: se@FreeBSD.org (Stefan Esser) Date: Sat, 23 Nov 1996 15:22:18 +1100 (EST) Cc: thyerm@satech.net.au, current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >On Nov 20, thyerm@satech.net.au (Matthew Thyer) wrote: >> - Fix PCI bus probing >> - The first time I boot FreeBSD it fails to detect my >> PCI bus and hence my NCR SCSI card and hence my >> SCSI HDDs. On the second boot (which I have put >> into /etc/rc) it probes the PCI bus ALWAYS ! > >PCI bus probing seems not to be a general problem. >Please send more details about your system (chip set, >peripherals, ...). The most important information is >the VERBOSE boot message log. (Boot with "-v" and send >me the output of "dmesg", or cut the messages out of the >"/var/log/messages" file ...) The recent XFree86 release uses PCI code that is very closely based on that in 2.2-current from about two months ago, and I know of some cases where the PCI bus probe seems to fail. The common factor is that they are PCs made by HP, and at least some are PPro machines. David