-
Notifications
You must be signed in to change notification settings - Fork 38
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
ps4eye under Ubuntu 16.04 #27
Comments
I've got same error with my MacBook Air + Ubuntu 16.04 LTS kernel 4.4.0-38-generic. |
Would you please say what kernel / OS will support it for sure? I am considering to setup older platform. |
I tried multiple kernels including 3.17.3 and 3.19.0 as recommended, but the outcome is always the same. Thanks, |
I have just received my Jetson TK1 and tried on it - PS4 Camera works like a charm there. |
Thank you for reporting! |
Ubuntu 16.04 LTS kernel 4.4.0-38-generic
eugene@EBUB:~/ps4eye/script$ guvcview
GUVCVIEW: version 2.0.2
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
GUVCVIEW: couldn't get a valid audio context for the selected api - disabling audio
libv4l2: error turning on stream: No space left on device
V4L2_CORE: (VIDIOC_STREAMON) Unable to start stream: No space left on device
V4L2_CORE: (get_v4l2_frame) video stream must be started first
V4L2_CORE: (get_v4l2_frame) video stream must be started first
V4L2_CORE: (get_v4l2_frame) video stream must be started first
V4L2_CORE: (get_v4l2_frame) video stream must be started first
Thank you in advance!
Eugene
The text was updated successfully, but these errors were encountered: