-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
call op_detach_kernel_driver(linux_usbfs.c) failed, return -1, and errno= 113 #1400
Comments
The detailed logs is below:
|
I can not find errno = 113 for libusb. Maybe it is from the lower level. And it seems to me you are not using an official version of libusb. Please use libusb-1.0.26 release or libusb-1.0.27-rc1 (recommended) or git and try again. What is the Android device you are testing with? Is it rooted? Do you have the right permission if you use official version of libusb release (1.026 or 1.0.27-rc1) or libusb git. Or better you may want to give PR #1164 a try to see if that helps. |
@mcuee The libusb library I used is forked with this github 4 years ago. |
I see. In that case, the error codes may come from Android. Please check. Unfortunately I can not help you much here as I have zero experiences with Android. I feel it is a problematic platform to support especially since the libusb main line is not working well and people have to use a fork. Reference: there are multiple open issues for Android. |
when I call op_detach_kernel_driver on Android, It‘s failed, and logs :
12-22 16:26:11.091 15259 15790 E libusb : [10.626199] [00003dae] libusb: error [op_detach_kernel_driver] detach failed error -1 errno 113
and later ,I call submit_control_transfer also failed. error is alose 113.
what does 113 errno means?
The text was updated successfully, but these errors were encountered: