From owner-freebsd-current  Sat Nov 23 05:02:45 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id FAA23829
          for current-outgoing; Sat, 23 Nov 1996 05:02:45 -0800 (PST)
Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA23821;
          Sat, 23 Nov 1996 05:02:40 -0800 (PST)
Received: from x14.mi.uni-koeln.de (annexr2-42.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA06797
  (5.67b/IDA-1.5); Sat, 23 Nov 1996 14:02:36 +0100
Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.3/8.6.9) id OAA17983; Sat, 23 Nov 1996 14:01:51 +0100 (CET)
Message-Id: <199611231301.OAA17983@x14.mi.uni-koeln.de>
Date: Sat, 23 Nov 1996 14:00:30 +0100
From: se@FreeBSD.org (Stefan Esser)
To: dawes@rf900.physics.usyd.edu.au (David Dawes)
Cc: se@FreeBSD.org (Stefan Esser), thyerm@satech.net.au, current@FreeBSD.org
Subject: Re: Four problems that really bug me with CURRENT
References: <199611221253.NAA07064@x14.mi.uni-koeln.de> <199611230422.PAA03075@rf900.physics.usyd.edu.au>
X-Mailer: Mutt 0.49-PL10
Mime-Version: 1.0
In-Reply-To: <199611230422.PAA03075@rf900.physics.usyd.edu.au>; from David Dawes on Nov 23, 1996 15:22:18 +1100
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> >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

There is PCI code in XFree86 ???

> 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.

Well, but how do you think I'm going to fix this,
if I have no idea what actually fails. Send me the
information I asked for (verbose boot messages and
the information about the chip set, CPU and BIOS
you can easily get at), and I'll make it work.

The current code already deals with many chip sets
that fail to conform to the PCI specs., and I've got
to add specific code for each new such chip set :(

Regards, STefan