Usb System Totally Non-functional Kernel 2.6.24

[Allelectrix]

Hi All,

Does anyone know how to get the USB sub-system running on an Akita with the following OS's ? :

Angstrom-x11-image-glibc-ipk-2007.12-r13-akita-installkit.tgz

and

Angstrom-x11-image-glibc-ipk-2007.12-r9-akita-installkit.tgz.gz


All of the main kernel modules are present, for example:

the kernel module:

usbmouse.ko

is present , but when the mouse is attached, no go.
same for USB storage, and probably, just about everything else.

Capn_Fish kindly compiled a Module for me which modprobe loads happily, but when my RT73 Radio Card
is plugged in, same as all the other USB devices, no operation, and the system is not recognizing it at all
except for :

lsusb -v

which shows the manufacturers data for each USB device correctly, at least, the USB system is reading this
data from each device, so thats a good start.

Modprobe picks up and loads all Modules properly and normally.

lsusb list them after modprobe has loaded them.

Any suggestions anyone ?

If not, do you have an Angstrom Kernel 2.6.24 OS file we can all try that is not the same as the 2 OS's above ?

[utx]

lsusb -v

Did you check the current requirements? If it is more than 150mA, you are going out of power budget (and dmesg shows proper error).

[Jon_J]

I have 5 devices that no longer work because of the electrical restriction of the 2.6 kernels.
Using a device that is under 150mA, you still have to use the commandline to get USB host devices to work.
Not like Cacko, or pdaxii13, where most all USB host devices are plug-n-play.

There is a "hack" in this thread that "bypasses" the power limitation.
https://www.oesf.org/forum/index.php?showtopic=20739

[utx]

I have 5 devices that no longer work because of the electrical restriction of the 2.6 kernels.
Using a device that is under 150mA, you still have to use the commandline to get USB host devices to work.
Not like Cacko, or pdaxii13, where most all USB host devices are plug-n-play.

There is a "hack" in this thread that "bypasses" the power limitation.
https://www.oesf.org/forum/index.php?showtopic=20739

No kernel is not the problem. The real problem are devices programmed to lie about their needs.

I have one device, which tells true (WL54USB-A) and does not work with 180mA, and another one, which lies (A-Data 2G SD Flash Duo with USB), wanting 500mA, running with 180mA.

In such case you need my OHCI Power Budget Hack. You need to recompile kernel, even if USB driver is in module (power budget is stored in platform description of kernel, which is in the kernel itself). Replace the number 680 by anything you need.

[Allelectrix]

I have 5 devices that no longer work because of the electrical restriction of the 2.6 kernels.
Using a device that is under 150mA, you still have to use the commandline to get USB host devices to work.
Not like Cacko, or pdaxii13, where most all USB host devices are plug-n-play.

There is a "hack" in this thread that "bypasses" the power limitation.
https://www.oesf.org/forum/index.php?showtopic=20739

Hi Jon_J , many thanks for your reply, yeh, seen that thread already mate, done that and did not work for me unfortuantely, any more ideas ?
there is nothing wrong with the hardware either as Cacko and PdaX fire up the USB with total ease, - everything works including my RT73
Radio Card (courtesy Capn_Fish and evilJazz) - just in case you might be wondering if there is anything wrong with the Hardware.

[Allelectrix]

I have 5 devices that no longer work because of the electrical restriction of the 2.6 kernels.
Using a device that is under 150mA, you still have to use the commandline to get USB host devices to work.
Not like Cacko, or pdaxii13, where most all USB host devices are plug-n-play.

There is a "hack" in this thread that "bypasses" the power limitation.
https://www.oesf.org/forum/index.php?showtopic=20739

No kernel is not the problem. The real problem are devices programmed to lie about their needs.

I have one device, which tells true (WL54USB-A) and does not work with 180mA, and another one, which lies (A-Data 2G SD Flash Duo with USB), wanting 500mA, running with 180mA.

In such case you need my OHCI Power Budget Hack. You need to recompile kernel, even if USB driver is in module (power budget is stored in platform description of kernel, which is in the kernel itself). Replace the number 680 by anything you need.

Hi there utx, this looks like a good solution, as my system is rather limited in resources at the mo, would you be so good as to post the recompiled
kernel here to the forum (the zImage file) like you did the patch file , with the patch you have kindly provided already added  so everyone can share
your good work on this issue ?

That would be fantastic !  

I presume this is Kernel 2.6.24 for Angstrom ?

Many thanks ! We await your 2nd post,  Allelectrix

[Allelectrix]

lsusb -v

Did you check the current requirements? If it is more than 150mA, you are going out of power budget (and dmesg shows proper error).

Oh yes, even with this issue, I connected all devices via a powered 2.0 Hub, and they all still did not work, just like they all still did not
work when I connected them up to the Computer by themselves.

[Allelectrix]

As of the end of Janurary 2009, I am still looking for a solutiuon to this issue, I am happy to send my SL-C1000 to anyone
who can resolve this USB Start issue. Many thanks to you all !  

[Allelectrix]

as of end of April 2009, this issue is still unresolved. does anyone know if USB using kernel 2.6.24 Angstrom can be used on the other machine versions ?

that is, all machines issued after the SL-C1000 which feature the same ARM Processor ?

thanks all !

[Allelectrix]

June 1st 2009, issue still unresolved. anyone want to exchange this C1000 for a OQO x86 ? - contact me at my email address.

[sdjf]

USB is really tricky.  I have different kernel and module...Sharp ROM on sl6000 and the problem for me has been that if I change which CF card I plug in to my USB CF reader, the zaurus assigns it a different device number.

I found it quite annoying as I need to change and it has nothing to do with power requirements.

Have you watched dmesg to see what device names have been assigned each time?  That could be your problem, I don't know how to fix it.  For me, rebooting does it, but I'd rather not have to reboot every time I change what's plugged into USB.

Just some thoughts in case you haven't noticed this.

sdjf

[koen]

June 1st 2009, issue still unresolved. anyone want to exchange this C1000 for a OQO x86 ? - contact me at my email address.

Why don't you read http://www.angstrom-distribution.org/contact and follow the instructions there?

[craigtyson]

Did they work in Angstrom before?

I have / still use several USB devices on my C1000 on Angstrom.  The default however is that the Z is in slave mode and so has to be put into Master mode to host the USB devices.

As Koen says, the instructions how to do so are in the FAQ

Q: How can I get the USB Host working (on machines with USB Host HW)?

    * A: The ohci-hcd module is mandatory for USB connections; load it with "modprobe ohci-hcd". To have it loaded at boot time, create a file called "/etc/modutils/ohci-hcd", with the single line "ohci-hcd", and run "update-modules". Don't forget that some machines (Zaurus, for example) can't deliver much power to usb devices (disks, network adapters, ...); you may need a powered usb hub.

[semen]

Is there a reason why you only want this working on Angstrom and not looking at any other options?

If the full kernel source is available, I don't see why this isn't working right now. When my C1000 arrives, I'll look into this for you.