-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libusb_set_configuration error -6 #15
Comments
I have no direct idea what to do. Maybe unload the usbhid module before. |
Try to check if the following udev rules has been installed: ATTR{idVendor}=="6688", ATTR{idProduct}=="6850", MODE="664", GROUP="plugdev" And your user must be in plugdev group |
I've the same issue about :
Even if I copy the 20-rwrfid.rules in /dev/udev/rules.d and restart it... The "dmesg" related output is :
EDIT : The previous tests are done on my Ubuntu 14.04 desktop, but this morning, I did the same tests on an OrangePiPCPlus with Armbian Stetch Linux 5.1.0-rc7, and the results were exactly the same ... |
Same here. Dmesg:
Related with #14 but tried three different USB ports Tried this #3 (comment)
idrw_linux command returns:
Windows application works as expected. Link http://download.5yoa.com/IDW02.zip |
Hi, I'm having exactly the same issue, using Kali linux. Does anyone know how to disable the lock that hid puts on the device? |
Try commenting out the libusb_claim_interface call in the code. |
Hi, When I uncomment the libusb_claim_interface call (the whole section), I get the same error:
If I do what has been mentioned by Mark-81, which is the following: SUBSYSTEM=="usb", DRIVERS=="usbhid", ACTION=="add", ATTR{authorized}="0" without removing the libusb_claim_interface call, I would get the error:
This is expected. When removing the libusb_claim_interface call, I get the follwing error:
I have to say that the compiled binary now waits for the USB device to read the tag, but one the tag is read, it displays the error shown. Any ideas? |
I'm trying to read/write a chinese "203-ID-RW" device. The
lsusb -v
output is the same of what reported in the idrw_linux.c file.This is the
dmesg
output:Here the output of your program:
and here some further output in
dmesg
;[ 608.765459] usb 1-1.3: usbfs: interface 0 claimed by usbhid while 'idrw_linux' sets config #1
Even issuying
lsusb -v
does nothing. I tried also as a root.Is there something I could try to do?
UPDATE:
Just to be sure, I tried to exclude usbhid using this rule:
SUBSYSTEMS=="usb", DRIVERS=="usbhid", ACTION=="add", ATTR{authorized}="0"
now the error is different:
The text was updated successfully, but these errors were encountered: