according to kldstat -v, both "uhci/usbus" & "pci/uhci" were present in
my kernel but one or both of them was silently failing.
apparently something in my sources was corrupt because deleting all of
the USB related code from my CVS root, re-csuping it, and building a
fresh kernel solved the probl
On Monday, December 13, 2010 11:30:00 am Tom Uffner wrote:
> John Baldwin wrote:
> > On Friday, December 10, 2010 8:13:01 pm Tom Uffner wrote:
>
> >> no...@pci0:0:16:0: class=0x0c0300 card=0x80ed1043 chip=0x30381106
> >> rev=0x81 hdr=0x00
> >> vendor = 'VIA Technologies, Inc.'
> >>
John Baldwin wrote:
On Friday, December 10, 2010 8:13:01 pm Tom Uffner wrote:
no...@pci0:0:16:0: class=0x0c0300 card=0x80ed1043 chip=0x30381106
rev=0x81 hdr=0x00
vendor = 'VIA Technologies, Inc.'
device = 'VT82x UHCI USB 1.1 Controller (All VIA Chipsets)'
cla
On Friday, December 10, 2010 8:13:01 pm Tom Uffner wrote:
> John Baldwin wrote:
>
> >> pci0: at device 16.0 (no driver attached)
> >> pci0: at device 16.1 (no driver attached)
> >> pci0: at device 16.2 (no driver attached)
> >> pci0: at device 16.3 (no driver attached)
> >
> > Can you get pcic
John Baldwin wrote:
pci0: at device 16.0 (no driver attached)
pci0: at device 16.1 (no driver attached)
pci0: at device 16.2 (no driver attached)
pci0: at device 16.3 (no driver attached)
Can you get pciconf -lv output for these four devices?
no...@pci0:0:16:0: class=0x0c0300 card=
On Thursday, December 09, 2010 11:21:41 am Tom Uffner wrote:
> I have a fairly recent Current system running on an ASUS K8V SE Deluxe MB.
>
> It was a dual boot amd64/x86 system (until a few days ago when the drive
> w/ the amd64 partitions unexpectedly failed after only a week of use)
>
> When r
I have a fairly recent Current system running on an ASUS K8V SE Deluxe MB.
It was a dual boot amd64/x86 system (until a few days ago when the drive
w/ the amd64 partitions unexpectedly failed after only a week of use)
When running it as x86, USB 1.1 devices are not recognized by FreeBSD.
They wo
