Re: USB detection problems
On Mon, Mar 08, 2004 at 08:42:57PM -0500, Joey Hess wrote:
> Santiago Garcia Mantinan wrote:
> > I've been doing more tests now, the problem is that this machine has a intel
> > 82801EB usb controller, and no driver is loaded for it, it could have been
> > uhci, usb-uhci or ehci-hcd, but none is loaded, thus none of the devices
> > atached to it work at all :-(
> >
> > This is what the devices look like for lspci -n:
> >
> > 00:1d.0 Class 0c03: 8086:24d2 (rev 02)
> > Subsystem: 147b:1028
> > Flags: bus master, medium devsel, latency 0, IRQ 16
> > I/O ports at bc00 [size=32]
> >
> > 00:1d.1 Class 0c03: 8086:24d4 (rev 02)
> > Subsystem: 147b:1028
> > Flags: bus master, medium devsel, latency 0, IRQ 19
> > I/O ports at b000 [size=32]
> >
> > 00:1d.2 Class 0c03: 8086:24d7 (rev 02)
> > Subsystem: 147b:1028
> > Flags: bus master, medium devsel, latency 0, IRQ 18
> > I/O ports at b400 [size=32]
> >
> > 00:1d.3 Class 0c03: 8086:24de (rev 02)
> > Subsystem: 147b:1028
> > Flags: bus master, medium devsel, latency 0, IRQ 16
> > I/O ports at b800 [size=32]
>
> Looks like we need to add these to discover-data and to usb-discover.
> I've added it for usb-discover, at least, which should be enough to make
> the memory stick work.
I've added these to discover-data, all using usb-uhci, since that seems
to be the precedent at least within the file. As a side note, I've been
unable to commit any changes to our alioth CVS repo since the move, so
if someone who knows how to fix this would mind contacting me off-list,
it'd be much appreciated.
> > 00:1d.7 Class 0c03: 8086:24dd (rev 02) (prog-if 20)
> > Subsystem: 147b:1028
> > Flags: bus master, medium devsel, latency 0, IRQ 23
> > Memory at fa100000 (32-bit, non-prefetchable) [size=1K]
> > Capabilities: [50] Power Management version 2
> > Capabilities: [58] #0a [20a0]
> >
> > Last one is the USB2 thing, the others the USB ones.
> What is the proper module for the usb2 device?
I'll patch this too when the answer appears.
- David Nusinow
Note: I'm only patching discover1's discover-data right now, this has to
be done for discover2 as well.
Reply to: