Unprobed PCI bus on VXPro II chipset

[Sean Welch]

I don't know about that.  I seem to recall that this motherboard
has a built-in USB controler but I read somewhere that it was
non-functional.  Regardless, I don't have any way to interface to
it (no cables etc from the the board).  I saw the two devices and
thought that maybe the onboard and pci slot USBs both were 
reporting the same chipset?

I suppose I should poke around in the bios to see if I can disable
the onboard USB (if it does exist).  Perhaps that would make the
USB attach...

                                                                           Sean

-----Original Message-----
From: Bernd Walter <ticso at cicely12.cicely.de>
Sent: Dec 26, 2003 6:34 PM
To: Sean Welch <Sean_Welch at alum.wofford.org>
Cc: John Baldwin <jhb at freebsd.org>, freebsd-hackers at freebsd.org
Subject: Re: Unprobed PCI bus on VXPro II chipset

On Fri, Dec 26, 2003 at 10:54:27AM -0800, Sean Welch wrote:
> That change seems to have done it!!
> 
> I left in the extra PCI IDs I had added to pcisupport.c
> and pci_cfgreg.c -- looks like that helps get things
> going.  I've got "options PCI_ENABLE_IO_MODES" in
> the kernel.  I've also got "device puc" due to a suggestion
> from fbsd_user on freebsd-questions.
> 
> The USB card doesn't seem to be attaching but I do see
> the WinTV card!
> 
> Any other suggestions based on what you see below?

Still very strange - you have many shadowed host-pci bridges.

> pcib4 at pci0:5:0: class=0x060000 card=0x80113388 chip=0x80113388 rev=0x00 hdr=0x00
> pcib5 at pci0:5:1: class=0x060100 card=0x80123388 chip=0x80123388 rev=0x00 hdr=0x00
> pcib6 at pci0:5:2: class=0x010100 card=0x80133388 chip=0x80133388 rev=0x00 hdr=0x00
> bktr0 at pci0:8:0: class=0x040000 card=0x13eb0070 chip=0x036e109e rev=0x02 hdr=0x00
> none0 at pci0:8:1: class=0x048000 card=0x13eb0070 chip=0x0878109e rev=0x02 hdr=0x00
> pcib7 at pci0:9:0: class=0x0c0300 card=0x12340925 chip=0x30381106 rev=0x04 hdr=0x00

This one (class=0x0c0300) is your USB (uhci) controller, but it's
already bogusly attached to pcib7.
Not surprising that uhci(4) didn't take care of it.

-- 
B.Walter                   BWCT                http://www.bwct.de
ticso at bwct.de                                  info at bwct.de