Skip to content
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

D415 Device Recognized on Power Up, Not on Reboot #1283

Closed
jallard-sr opened this issue Mar 5, 2018 · 6 comments
Closed

D415 Device Recognized on Power Up, Not on Reboot #1283

jallard-sr opened this issue Mar 5, 2018 · 6 comments

Comments

@jallard-sr
Copy link


Required Info
Camera Model D415
Firmware Version 05.08.15.00
Operating System & Version Ubuntu 16.04.4 LTS
Kernel Version (Linux Only) 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018
Platform NUC with dual Intel(R) Core(TM) i5-6260U CPU @ 1.80GHz cores
SDK Version librealsense tag 2.10.0

Issue Description

When rebooting this type of NUC computer with a D415 plugged in, the D415 does not register properly as a USB device, with the following error in dmesg output. However, when it is power cycled, the D415 registers fine.

[ 2.477775] usb 2-4: device not accepting address 2, error -71

I've attached the USB relevant bits of dmesg and the output of lsusb -t from a good start on power up, and from a bad start on reboot. Oddly enough, this does not occur with newer NUC models with dual Intel(R) Core(TM) i5-7260U CPU @ 2.20GHz cores, where the device registers fine on reboots.

dmesg-bad.txt
dmesg-good.txt
lsusb-t-bad.txt
lsusb-t-good.txt

@jallard-sr
Copy link
Author

Looks like dmesg output on failure didn't upload correctly. Here it is again.

dmesg-bad.txt

@RealSense-Customer-Engineering
Copy link
Collaborator

[Realsense Customer Engineering Team Comment]
@jallard-sr, in the BIOS settings try setting the xHCI mode to Enabled (not Auto or Smart Auto) under Devices/USB.

@ioreed
Copy link

ioreed commented Mar 20, 2018 via email

@RealSense-Customer-Engineering
Copy link
Collaborator

[Realsense Customer Engineering Team Comment]
Although I haven't seen this with the 415 it is similar to an issue with the 435 - except xHCl mode = enabled was a usable work-around (newer NUCs only have xHCI). For the f/w 5.9.2.0 fixed the problem for the 435 cameras so you can try that if you wish. https://downloadcenter.intel.com/download/27522/Latest-Firmware-for-Intel-RealSense-D400-Product-Family?v=t

@RealSense-Customer-Engineering
Copy link
Collaborator

[Realsense Customer Engineering Team Comment]
@jallard-sr did you try 5.9.2.0 f/w and/or do you still see the issue?

@tedtman
Copy link

tedtman commented Apr 25, 2018

@jallard-sr I assume that you are no longer having this issue and I will close this ticket. If you still have this or any other problem please feel free to open another issue.

Thanks.
Ted.
Intel RealSense Support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants