I am trying to access laptop's webcam from ubuntu 14.04 LTS.
I did lspci and found VGA compatible controller: Device 1234:1111
Can i assume that the webcam is installed? I was hoping for some device name or description.
I am not getting video0 when i did:
ls /dev/
Quite often, laptop webcams are controlled as USB devices, so you may attempt to search for them with lsusb:
From TLDP.org's Webcam-HOWTO:
5.1. Help, I have a USB webcam and don't know exactly what model it is and/or who the manufacturer is. What do I do?
Use lsusb; it can give you an idea of what other USB devices are available on your system, too:
$ lsusb
Bus 007 Device 001: ID 0000:0000
Bus 006 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 003: ID 0545:8080 Xirlink, Inc. IBM C-It WebCam
Bus 003 Device 002: ID 046d:0840 Logitech, Inc. QuickCam Express
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 003: ID 051d:0002 American Power Conversion Back-UPS Pro 500/1000/1500
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
The numbers after 'ID' are the Vendor and Product numbers, respectively. They can then be looked up in the Linux USB ID catalog. ...
Related
So, I made some high speed opencv camera detection code, got it running on my debian labtop, and bought some 720p60 chinese usb cam. All worked well. However I wanted to make it run on my TinkerBoard S (tinkerOS - debian).
Here the camera simply refused to get detected, as my lsusb output hinted (also tried guvcview & cheese, none worked):
Bus 001 Device 006: ID 05a3:9230 ARC International
Bus 001 Device 004: ID 1ea7:2001 *this is where i suspect the cam should be*
Bus 001 Device 005: ID 0458:003a KYE Systems Corp. (Mouse Systems) NetScroll+ Mini Traveler / Genius NetScroll 120
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0bda:481a Realtek Semiconductor Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
However I think I found the issue, just dont know the solution. When running dmesg, I found the following entries:
[ 94.277615] usb 1-1.4: new high-speed USB device number 6 using dwc2
[ 94.450592] usb 1-1.4: New USB device found, idVendor=05a3, idProduct=9230
[ 94.450611] usb 1-1.4: New USB device strings: Mfr=2, Product=1,
SerialNumber=0
[ 94.450625] usb 1-1.4: Product: USB 2.0 Camera
[ 94.450637] usb 1-1.4: Manufacturer: HD Camera Manufacturer
[ 94.454526] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (05a3:9230)
[ 94.496335] uvcvideo: auto-suspend is blacklisted for this device
EDIT: both outputs are from the tinker Board.
Sounds like whatever driver is installed on your laptop doesn't exisit on the TinkerOS board. Going by the second code block, this line looks like the camera:
Bus 001 Device 006: ID 05a3:9230 ARC International
It would be useful to have a comparison from the laptop to see what's different.
Maybe try these answers to obtain the driver (on the laptop with the webcam connected). Be sure to use the same physical ports when changing stuff over, to avoid numbers changing and causing confusion.
Searching the vendor / product code (05a3:9230) on google brings up some related results aswell although nothing I found to be conclusive.
Dead thread but still feel I should provide the solution.
Turns out that despite the cam being the only one connected, it was somewhere all the way at /dev/video4
whatever be the reason...
When I attach removable USB hard disk to my computer, I can distinguish it from others via the name of manufacture and device name. However, I can't exactly know what is the device file in /dev (e.g. sda, sdb, sdc...) corresponding to this USB storage device.
Is there a way to find out the device file according to the output of lsusb?
I always do like this:
If this USB device is the last one to remove/insert, you can get it from 'dmesg'. you can easy to see sdxxx in dmesg print out. that's what your need.
You can know exactly the /dev/path/to/your/device using lsusb.
Sample output:
Bus 002 Device 008: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
According to the previous example, you can locate the char device that corresponds to the Logitech USB receiver ( for wireless mouse and keyboard ) by examining the two numbers before the colon ( : ).
It would be /dev/bus/002/008
Notice the last two numbers ( last directory then the char device file itself ).
They are the same as the first two numbers in the line that says Logitech, Inc. Unifying Receiver.
So the path is always /dev/bus/[first number]/[second number].
NOTE: MY DEVICE is an xbox 360 kinect device NOT a kinect for windows.
I have tried different linux kernels and different compilations of libfreenect, but no cigar.
The light on the connection cord is solid green, the light on the kinect device blinks green (when its plugged into my running computer).
One pecularity that seemed suspicious is that the udev file designates ATTR{idProduct}=="02b0" to the xbox "Xbox NUI Motor". As one can see in my lsusb file linux is recocnizing the device with an idProduct of "02c2". The device has been purchased about a month ago, so could they have changed the idProduct?? Under this guess I modified my udev rules files restarted udev, no work, then restarted my computer, still no work.
I am compiling libfreenect from github and you can see the output below. I also tried the debian package (0.1.2). Since "Xbox NUI Audio" "Xbox NUI Camera" are detected I feel its not a usb power issue, but I could be wrong.
test program output:
$ ./bin/glview
Kinect camera test
Number of devices found: 1
Could not open device
debug info:
$ dmesg
[ 361.532077] usb 1-4: new high-speed USB device number 2 using ehci_hcd
[ 361.664408] usb 1-4: New USB device found, idVendor=045e, idProduct=02c2
[ 361.664416] usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 361.664875] hub 1-4:1.0: USB hub found
[ 361.665008] hub 1-4:1.0: 2 ports detected
[ 361.940144] usb 1-4.2: new high-speed USB device number 3 using ehci_hcd
[ 361.972410] hub 1-4:1.0: unable to enumerate USB device on port 2
[ 362.668134] usb 1-4.1: new high-speed USB device number 4 using ehci_hcd
[ 362.762514] usb 1-4.1: New USB device found, idVendor=045e, idProduct=02ad
[ 362.762522] usb 1-4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 362.762529] usb 1-4.1: Product: Xbox Kinect Audio, \xffffffc2\xffffffa9\xffffffa9 2011 Microsoft Corporation. All rights reserved.
[ 362.762535] usb 1-4.1: Manufacturer: Microsoft
[ 362.762540] usb 1-4.1: SerialNumber: A70774X04011232A
lsusb debug info:
$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 064e:a101 Suyin Corp. Acer CrystalEye Webcam
Bus 005 Device 003: ID 0c45:7403 Microdia
Bus 001 Device 002: ID 045e:02c2 Microsoft Corp.
Bus 001 Device 004: ID 045e:02ad Microsoft Corp. Xbox NUI Audio
Bus 001 Device 006: ID 045e:02ae Microsoft Corp. Xbox NUI Camera
Installed ROS (fuerto/groovy) + PCL and works fine with openni_launch package. I'm using XBOX kinect also. Use RVIZ for visualization!
I'm having a builddroot assembled busybox distribution running on my micro.
It all works well so far but I realized one thing. When I boot my box up and
I do an lsusb I see this:
# lsusb
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 001 Device 003: ID 12d1:14ac Huawei Technologies Co., Ltd.
Bus 001 Device 004: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x
Composite Device
and I have following links:
ttyUSB0 ttyUSB1 ttyUSB2 ttyUSB3
buyt none of those links seem to go to Device 0004 but if I replug the
CP210x device, I get this:
# lsusb
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 001 Device 003: ID 12d1:14ac Huawei Technologies Co., Ltd.
Bus 001 Device 005: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x
Composite Device
and these links:
ttyUSB0 ttyUSB1 ttyUSB2 ttyUSB3 ttyUSB4
and now ttyUSB4 is linking to my Device 005 why do I need to replug my
device in order to get a working symlink? That's not what I want? :(
How can I fix this? The cp210x module is compiled into the kernel (not
attached as a separate module) - any suggestions?
This for some reason just stop happening probably due to the fact that we're only using one usb device now. Inodes would have been a solution but got never implemented in our system.
I have car diagnostic device ELM327 with usb port connection, but Mint can't recognize it.
Here is the list of devices from terminal:
~ $ lsusb
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 09da:000e A4 Tech Co., Ltd
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 003: ID 7073:3037
Bus 003 Device 002: ID 046d:c215 Logitech, Inc. Extreme 3D Pro
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
That device is listed as "Bus 003 Device 003" and, as you can see, has no description.
Any suggestions? Does it have some further procedure to been recognized by auto-data software? Cant find this solved problem googleing.
Thanks!
I found other people who had the same problem as you by googling: Here and Here (in Polish).
"It says FTDI, manufacturer of the device, has a Linux driver to be able to use this interface as a serial port."
Knowing that you might try the FTDI site. EDIT: The FTDI site says that it is supported natively in kernel 2.6.31 and later. See also the FTDI driver sourceforge project.
Note that none of this tells you what protocol you speak to it.
lsusb merely translates the IDs (provided by the device) into text strings, using /usr/share/usb.ids. That does not say anything about the (un)availability of a driver.