Unprobed PCI bus on VXPro II chipset

Sean Welch welchsm at earthlink.net
Thu Dec 25 06:31:04 PST 2003

Thanks very much for the suggestion!  Unfortunately it didn't make any
difference at all to the probe.

Any other suggestions?

Anyone else?


-----Original Message-----
From: fbsd_user <fbsd_user at a1poweruser.com>
Sent: Dec 24, 2003 3:14 PM
To: Sean Welch <Sean_Welch at alum.wofford.org>, freebsd-questions at freebsd.org
Subject: RE: Unprobed PCI bus on VXPro II chipset

You did not have to do all that hacking, there is an simple fix for
old bio's and PCI cards.
Add device puc to your kernel source and recompile. Your next boot
review your boot log and you should see all the PCI devices found
except sound cards. You have to add device pcm to your kernel and
recompile to find PCI sound cards or built on the motherboard sound.
I know this works for the 4.x releases including 4.9.

-----Original Message-----
From: owner-freebsd-questions at freebsd.org
[mailto:owner-freebsd-questions at freebsd.org]On Behalf Of Sean Welch
Sent: Wednesday, December 24, 2003 5:55 PM
To: freebsd-questions at freebsd.org
Subject: Unprobed PCI bus on VXPro II chipset

As I'm not quite sure where I should be asking for help with this I
I'd try shooting the info over to freebsd-hackers (as it seemed the
match) and to freebsd-questions (as there seems to be a requirement
join the list for hackers mail).

I've got an oldish machine (EDO RAM and such) running a VXPro II
I have successfully configured FreeBSD from 2.2.8 up to 5-CURRENT to
on this thing but I've never managed to get it to probe and attach
on the PCI bus.  Here's what I've found and what I've tried.

I believe the motherboard was sold as PCChips kit.  Looking up the
I find that it was a rebrand of Hint Co. hardware.  The PCI IDs are
listed in /usr/share/misc/pci_vendors and look like this:

3388    Hint Corp.
        0021    HB1-SE33 PCI-to-PCI Bridge
        8011    VXPro II Chipset CPU to PCI Bridge
        8012    VXPro II Chipset PCI to ISA Bridge
        8013    VXPro II Chipset EIDE Controller

I found a commit notice online to the linux kernel that contained
same IDs so it looks like the complete string should be "33880020",
"33880021", etc.  I also managed to find this message from *long*


I'm currently running 4.9-RELEASE.  The uname -a output is:

FreeBSD  4.9-RELEASE FreeBSD 4.9-RELEASE #5: Tue Oct 14 11:51:28 CDT
root@:/usr/src/sys/compile/WARPPHYS  i386

Poking around I discovered that pcibus.c no longer contains the code
referenced in the above message (but that didn't stop me).  I found
it instead in pci_cfgreg.c and tried adding the explicit set of
oldval1 to
zero but no joy.  I ended up adding the PCI IDs to both
/usr/src/sys/i386/isa/pcibus.c and also
in the effort to get the chipset recognized.  No go.

When I boot verbose this is all I can get about the PCI bus:

pci_open(1):    mode 1 addr port (0x0cf8) is 0x0000ff00
pci_open(1a):   mode1res=0x00000000 (0x80000000)
pci_open(1b):   mode1res=0x00007020 (0xff000001)
pci_open(2):    mode 2 enable port (0x0cf8) is 0xff

Infuriatingly, the BIOS sees everything on the bus and labels the
with reasonable categories.  Likewise, scanpci (comes with XFree86)
identifies the chipsets and the devices without any trouble at
all -- that
at least explains why I've never had any trouble using the PCI video
under X.  The output of scanpci identifies the last three chipsets
that snipet I put above (from pci_vendors) with the last being
labeled as
IDE rather than EIDE (which is correct).

Based on this digging around I'm convinced that there must be some
ugly hack that is posible to get FreeBSD to probe and attach the bus
and devices on it.  I've only got this desktop and while I've been
to live without the PCI USB card, I need to test out a PCI WinTV
The whole machine is old enough that isn't feasible to just try
out the motherboard (the case isn't even ATX compatible) and I've
got the money to just buy something else.

Would anyone be willing to help me get this sorted out?  I'm out of
my depth here but to my inexperienced eyes this doesn't look to be
an insurmountable issue.


freebsd-questions at freebsd.org mailing list
To unsubscribe, send any mail to
"freebsd-questions-unsubscribe at freebsd.org"

More information about the freebsd-questions mailing list