On Sunday 11 April 2004 11:49pm, tj wrote:
> If you have time.I'll walk you through what I do and what system
> messages are. Oh, I might mention I have a Belkin USB serial adapter and
> it works just fine.
>
> Ok I boot the system and modprobe input; modprobe input; modprobe input;
> modprobe joydev.
Huh? You don't mean to say that you're doing 'modprobe input' 3 times, do you?
If so, why?
> A lsmod shows.
>
> hid 15496 0 (unused)
> joydev 6048 0 (unused)
> input 3232 0 [hid joydev]
> uhci 25616 0 (unused)
> ehci-hcd 17544 0 (unused)
> usbcore 62016 1 [hid uhci ehci-hcd]
OK, I'm assuming you've adjusted your setup (per Sergey Vlasov's email) to
avoid having to load 'keybdev' and 'mousedev' with the 'hid' module.
> A dmesg responds:
> usb.c: registered new driver hid
> hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <[EMAIL PROTECTED]>
> hid-core.c: USB HID support drivers
> At the bottom.
> T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0
> D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
> P: Vendor=06a3 ProdID=0006 Rev= 0.01
> C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
> I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=(none)
> E: Ad=81(I) Atr=03(Int.) MxPS= 7 Ivl=10ms
>
> Notice that it does not show a manufacturer string. But now look at dmesg:
> usb.c: USB device 2 (vend/prod 0x6a3/0x6) is not claimed by any active
> driver.
> usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -110
> usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -110
> usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -110
> usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -110
>
> With the last line repeating over and over again.
Well, a quick perusal of the Slackware 9.1 kernel 2.4.22 USB source code shows
that 'devio.c' is trying to send a USB device request which apparently is
failing, yielding the repeated messages.
I'm no USB expert by any means, but a peek through the USB 1.1 specification
document shows that a USB device request with a 'Request Type' of 128 ('rqt
128') and a 'Request' of 6 ('rq 6') correlates to a USB 'Get Descriptor'
request. The 'ret -110' is a 'Connection timed out' error. Unfortunately,
that error message leaves out the 'Value' field of the USB device request, so
I cannot tell what specific type of Descriptor is being requested from the
joystick. Anyway, I'm guessing that your joystick is not replying to that
request, thereby causing the failure.
Since I'm no expert at this stuff, I strongly recommend you gather all the
facts (including whatever portion of my analysis and speculation that you
feel is relevant) and re-submit this query to the Linux USB Developers'
mailing list ([EMAIL PROTECTED]). Someone on that list is
likely to be able to intelligently address this.
I was wondering if you had any evidence that anyone has successfully used this
'Saitek Cyborg 3D' joystick under Linux, then I checked the USB 'Working
Devices' list (http://www.qbik.ch/usb/devices/) and there is an entry (circa
Dec 2000) for this particular joystick showing success, so it must have
worked for someone back then! :^)
Sorry I can't help more with this, but I'll keep my eyes and ears open to
future replies.
Regardless of what happens, please keep the list(s) posted on whatever
successes or failures you have so that future readers of the archives can
benefit.
Good luck and holler if I can be of any further help....
Bill Marr
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
