Tiny Core Linux
Tiny Core Base => TCB Bugs => Topic started by: Tuftec on May 02, 2011, 03:41:13 AM
-
Hi All,
I am trying to get TC to run on an eBox 3300MX PC with a Vortex SOC h/w core.
I frequently get errors for USB connections similar to the following
generic-usb: probe of 0003:0EEF:0001.0004 failed with error -32
What does this mean?
I think it might be a latent kernel bug that shows up with the non standard x86 core.
Peter.
-
You could try posting a question to the mailing list at http://www.linux-usb.org/
-
It could be a bug in linux code, or in your usb hardware (the chipset, or the stick).
-
A quick google search seems to indicate the 2.6.29 kernel changed in a way that exposed bugs in some drivers (http://kerneltrap.com/mailarchive/linux-usb/2009/3/16/5175814/thread). If you are knowledgeable enough, you can try to patch and recompile the affected module, using the example for the Saitek Cyborg Gold Joystick (http://lxr.free-electrons.com/source/drivers/usb/core/quirks.c?v=2.6.33#L57).
-
Thanks guys.
I am not experienced enough to be able to patch.
I have tried the same configuration on other h/w platforms and I get the same error message.
There must be a list somewhere that tells me what an error 32 means.
Peter.
-
Is this for a particular device or for any device? If it's a particular device, then load the usb-utils extension, execute lsusb, and post the results. I expect that particular error could be caused by one of many different problems, but with additional information we may be able to see something.
-
Here is an lsusb -v output.
The error occurs repeatedly with my touch screen (which I have not been able to get to work. It does work fine under MS Windows).
-
Here is the dmesg output also. I thought it may help.
Peter.
-
I can't offer ony suggestion yet, but when looking at USB related stuff I always find the output of lsusb -t quite helpful, plus the output of lsmod to know what kernel modules have been loaded. You might want to add those few lines here as well.
-
files as requested.