On Mon, 18 Oct 2004, Roe Peterson wrote:
> Yes. The hub seems to work just fine under 2.6.5.-1.358 (the stock
> fedora core 2 kernel).
> I think I'll try turning on some more debugging info and track down just
> exactly what
> is being sent to the hub to set it's address. Perhaps a length has
Alan Stern wrote:
On Thu, 14 Oct 2004, Roe Peterson wrote:
Here's what happens with ehci_hcd verbose debugging enabled:
Nothing stands out. Can you try using Linux 2.6 to see if that makes any
difference?
Yes. The hub seems to work just fine under 2.6.5.-1.358 (the stock
fedora core
Alan Stern wrote:
You can probably get more information if you turn on the USB debugging
option in the kernel configuration.
Here's what happens with ehci_hcd verbose debugging enabled:
Oct 14 14:55:52 tbolt kernel: ehci_hcd 00:1d.7: GetStatus port 1 status
001000 POWER sig=se0
Oct 14 14:55
On Thu, 14 Oct 2004, Roe Peterson wrote:
> Alan Stern wrote:
>
> >
> >
> >You can probably get more information if you turn on the USB debugging
> >option in the kernel configuration.
> >
> >
> Here's what happens with ehci_hcd verbose debugging enabled:
Nothing stands out. Can you try usi
Alan Stern wrote:
On Wed, 13 Oct 2004, Roe Peterson wrote:
This is a Dell Precision 650 running linux-2.4.28-pre3. It's got the
usb-uhci and echi-hcd modules loaded.
I've got a new error code showing up with this USB2 hub. On insertion,
I get:
Oct 13 15:35:55 tbolt kernel: hub.c: new USB dev
On Wed, 13 Oct 2004, Roe Peterson wrote:
>
> This is a Dell Precision 650 running linux-2.4.28-pre3. It's got the
> usb-uhci and echi-hcd modules loaded.
>
>
> I've got a new error code showing up with this USB2 hub. On insertion,
> I get:
>
> Oct 13 15:35:55 tbolt kernel: hub.c: new USB de
