-
Notifications
You must be signed in to change notification settings - Fork 751
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
Ubuntu 14.04 libusb error LIBUSB_ERROR_NO_DEVICE (-4) #216
Comments
Take a look to this issue #164. Maybe that helps for your problem as well. |
I reduced the MAX_ISO_BUFFER_LENGTH to 49152, but it did not help. I tried also the solution of #174, but still does not work. It is frustrating because any time I use the Protonect program all the usb ports stop to work and I have to restart the PC. |
Since you have not mentioned it, I have to ask: have you checked the USB autosuspend settings? Ubuntu 14.04 has power saving config by default. The OpenGL processor is basically using GPU but with overhead of abstraction several layers removed from the hardware. You should be able to do just fine with I have a JPEG decoding acceleration patch PR #210 for Intel. You might also want to try it out. |
I tried the autosuspend as you suggest in #174, but it did not work. On the NUC I tried with OpenCL and disabling the OpenGL and it works. I will try the JPEG decoding patch you suggest. Thank you! |
I think this is a kernel level issue. As you can see
LIBUSB_ERROR_NO_DEVICE came from here.
This is something between the ASMedia USB3 controller and its kernel driver. I don't know what more can be done within libusb or here. You can still try different versions of kernel, from 3.12 to 4.0. Further than that, I guess you have to assume this ASMedia controller is not supported. |
The same issue is me. I tried many combinations, e.g., disabling opencl, disabling opengl and none of them works. @xlz to reset the usb port, you can use the following command (usb3.0 port only)
My output is
|
@zhangtemplar |
I am getting the same LIBUSB_ERROR_NO_DEVICE error on Ubuntu 15.04 with kernel 3.19.0-21-generic. dmesg starts to show following errors right after protonect is started. After a while,device gets disconnected and program stops. Even tough I am not sure about the duration, I think,approx. after a hour, device gets disconnected. dmesg: [ 441.150310] xhci_hcd 0000:00:14.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 4 lsusb returns: Bus 003 Device 002: ID 8087:8001 Intel Corp. lspci returns: 00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09) ldd Protonect | grep usb returns:
I have disabled all autosuspends. |
AFAICT this controller hasn't yet been tested, this seems to be a pretty new one. The only ones we can confirm as working are those listed in the README; for any other controller, it may or may not work. Trying a different USB controller (either on a different machine or on an add-on card) will help to narrow it down. |
@xlz I have found the problem that my usb 3.0 controller in the mother board is Asmedia, which is obviously in non-compatible list of the Kinect 2.0. After switch to one suggested in the Kinect 2.0 support site, it works with no problem. |
@rastaxe @zhangtemplar @bellekci "ERROR Transfer event TRB DMA ptr not part of current TD" is the place the bug happens. What immediately follows is "HC is busted, give up!" and the rest is the fallout. This may have something to do with the XHCI_SPURIOUS_SUCCESS quirk. What is the hci version from your |
@xlz sorry for late return, somehow slipped from my attention.
|
I booted with kernel 4.3 and no additional quirk parameter and this is what get for
Thus, XHCI_SPURIOUS_SUCCESS quirk is added and I do not know if I still have the no-device problem as it takes some time until device gets disconnected. I will let you know. |
Yes, the problem is still there even with the XHCI_SPURIOUS_SUCCESS quirk. Before disconnection, dmesg issues following warnings:
I also got this error:
|
@bellekci Thanks for testing. I guess kernel's USB 3.0 maintenance has really gone down hill since Sarah Sharp. |
I am trying to run Kinect v2 on Ubuntu 14.04 (kernel 3.16)
When I run Protonect I got the -4 libusb error (LIBUSB_ERROR_NO_DEVICE).
The output of the program is
When I plug the kinect, I got from dmesg:
As soon as I start Protonect I got:
Protonect is using the patched version of libusb:
Listing the USB Controller gives:
Any ideas to solve this problem?
The text was updated successfully, but these errors were encountered: