Hi again,
I didn't attract much attention with my first post :(, so I've been working
through the 2.6.10 USB code, following the error messages that get produced
when I attach a device (an unpowered hub), to my Armada 7400. I get as far as
core/message.c::usb_start_wait_urb(). It seems that after
wait_for_completion(), urb->status is set to -ECONNRESET, which is what one
would expec after a timeout, given the notes that precede
core/urb.c::usb_unlink_urb().
Hoping that my problems stem from my laptop being old and slow, I
(experimentally) amended the value assigned to timer.expires to jiffies +
timeout * 5, but still got a timeout failure ("khubd timed out on ep0in"),
followed by the message "unable to read config index 0 descriptor/start" from
core/config.c::usb_get_configuration().
Could anyone offer advice as to where I should now start looking. I've built
and booted with 2.4.29 and my hub (and other devices) just plain and simple
work, so I know it must be possible. Unless of course, there is a hardware
bug here that the 2.6 ohci design just can't work around. As I said before, I
can attach devices via a cardbus USB2 adapter, but I just hate it when things
that should work don't.
I'm willing to do the hard yards, experimenting with various settings, but I
really need some advice on where to start.
By the way, I'm building all the usb stuff as modules, with the intention that
after a rebuild I could just unload and reload the modules. But, usbcore is
reported as being in use and will not unload. Is there any way to force the
loading of a new version of usbcore without rebooting?
Thanks in advance.
Chris
On Wednesday 26 Jan 2005 15:55, Chris Clayton wrote:
> Hi,
>
> I have already posted to the linux-usb-user mail list about this, but
> had no success in finding a resolution.
>
> I'm having trouble getting on on-board USB port working on my Compaq
> Aramada 7400. Well. I should qualify that and say that I can't get it to
> wotk with a 2.6 kernel - devices that I plug in when running a
> 2.4.{26,28} kernel or, for that matter, Windows ME, work fine. In fact
> they work fine with 2.6.10 (haven't tried others) if I attach them
> through a cardbus USB2 adapater. The devices I am referring to are a
> Belkin F5D6050 wireless adapter, a STIR4200 IrDA adapter, a plain
> (unpowered) hub and a CF Card adapter. The 2.6 kernels I have tried are
> 2.6.5 and 2.6.10.
>
> I can get the usb hub to attach occasionally by unloading and then
> reloading the ohci-hcd driver, but this is a hit-and-miss affair. Even
> when I do get it to attach, things break down again as soon as I plug
> something into the hub - I have been using the IrDA adapter for this
> experiment.
>
> I attach the outputs from lspci, lsusb and three "dmesg logs". The first
> dmesg log shows a simple boot of my system. The second shows a couple of
> unsuccessful attempts to get the hub to attach by unloading and
> reloading the driver. I did. after many goes at bouncing the driver, get
> the hub to attach and the third log shows what happens after I plug the
> IrDA adapter into the hub.. The filenames indicate which is which log.
>
> I am more than happy to provide additional diagnostics, test things,
> whatever.
>
> Thanks in anticipation
>
> Chris
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
