* adding a udev entry for a camera
@ 2013-10-30 20:51 Edward Vidal
2013-10-30 23:58 ` Khem Raj
0 siblings, 1 reply; 17+ messages in thread
From: Edward Vidal @ 2013-10-30 20:51 UTC (permalink / raw)
To: yocto@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]
Hello,
I am trying to add a c920 camera to my systems. I am not getting a
/dev/video0.
lsusb --verbose shows the HD Pro Webcam C920
Bus 001 Device 007: ID 046d:082d Logitech, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 239 Miscellaneous Device
bDeviceSubClass 2 ?
bDeviceProtocol 1 Interface Association
bMaxPacketSize0 64
idVendor 0x046d Logitech, Inc.
idProduct 0x082d
bcdDevice 0.11
iManufacturer 0
iProduct 2 HD Pro Webcam C920
iSerial 1 211EF9AF
bNumConfigurations 1
plus much more information
I created /etc/udev/rules.d/10-c920.rules
SUBSYSTEM=="video4linux", BUS=="usb", ATTRS{idvendor}=="0x046d",
ATTRS{idProduct}=="0x082d", NAME="video0", MODE:="0660"
mknod /dev/video0 c 81 0
when I v4l2-ctl --all error no /dev/video0
Any and all help will be appreciated.
Thanks
[-- Attachment #2: Type: text/html, Size: 1238 bytes --]
^ permalink raw reply [flat|nested] 17+ messages in thread* Re: adding a udev entry for a camera 2013-10-30 20:51 adding a udev entry for a camera Edward Vidal @ 2013-10-30 23:58 ` Khem Raj 2013-10-31 1:12 ` Edward Vidal 0 siblings, 1 reply; 17+ messages in thread From: Khem Raj @ 2013-10-30 23:58 UTC (permalink / raw) To: Edward Vidal; +Cc: yocto@yoctoproject.org On Wed, Oct 30, 2013 at 1:51 PM, Edward Vidal <vidal.develone@gmail.com> wrote: > Hello, > I am trying to add a c920 camera to my systems. I am not getting a > /dev/video0. > lsusb --verbose shows the HD Pro Webcam C920 > Bus 001 Device 007: ID 046d:082d Logitech, Inc. > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass 239 Miscellaneous Device > bDeviceSubClass 2 ? > bDeviceProtocol 1 Interface Association > bMaxPacketSize0 64 > idVendor 0x046d Logitech, Inc. > idProduct 0x082d > bcdDevice 0.11 > iManufacturer 0 > iProduct 2 HD Pro Webcam C920 > iSerial 1 211EF9AF > bNumConfigurations 1 > plus much more information > > I created /etc/udev/rules.d/10-c920.rules > SUBSYSTEM=="video4linux", BUS=="usb", ATTRS{idvendor}=="0x046d", > ATTRS{idProduct}=="0x082d", NAME="video0", MODE:="0660" > > mknod /dev/video0 c 81 0 > > when I v4l2-ctl --all error no /dev/video0 > Any and all help will be appreciated. you can check if udev rule is infact kicking in. use udevadm monitor/test > Thanks > > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: adding a udev entry for a camera 2013-10-30 23:58 ` Khem Raj @ 2013-10-31 1:12 ` Edward Vidal 2013-10-31 10:27 ` Gary Thomas 2013-10-31 14:41 ` Khem Raj 0 siblings, 2 replies; 17+ messages in thread From: Edward Vidal @ 2013-10-31 1:12 UTC (permalink / raw) To: Khem Raj; +Cc: yocto@yoctoproject.org [-- Attachment #1: Type: text/plain, Size: 6095 bytes --] Hello, This is when I connect the camera udevadm monitor test monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[803.263336] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 (usb) KERNEL[803.267456] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 (usb) KERNEL[803.269287] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 (usb) KERNEL[803.269958] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 (usb) KERNEL[803.270721] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 (usb) KERNEL[803.276214] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.15 (usb_device)********** UDEV [803.277191] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 (usb) UDEV [803.306091] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.15 (usb_device) UDEV [803.318603] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 (usb) UDEV [803.324249] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 (usb) UDEV [803.329712] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 (usb) UDEV [803.333160] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 (usb) still no /dev/video0 ls -la /dev/v* crw-rw---- 1 root tty 7, 0 Jan 1 2000 /dev/vcs crw-rw---- 1 root tty 7, 1 Jan 1 2000 /dev/vcs1 crw-rw---- 1 root tty 7, 2 Jan 1 2000 /dev/vcs2 crw-rw---- 1 root tty 7, 3 Oct 29 13:51 /dev/vcs3 crw-rw---- 1 root tty 7, 128 Jan 1 2000 /dev/vcsa crw-rw---- 1 root tty 7, 129 Jan 1 2000 /dev/vcsa1 crw-rw---- 1 root tty 7, 130 Jan 1 2000 /dev/vcsa2 crw-rw---- 1 root tty 7, 131 Oct 29 13:51 /dev/vcsa3 root@beagleboard:~# lsusb Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. Bus 001 Device 004: ID 0409:0059 NEC Corp. HighSpeed Hub Bus 001 Device 005: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard Bus 001 Device 006: ID 046d:c001 Logitech, Inc. N48/M-BB48 [FirstMouse Plus] Bus 001 Device 015: ID 046d:082d Logitech, Inc. *********************************************************************************** udevadm monitor --udev monitor will print the received events for: UDEV - the event which udev sends out after rule processing camera removed***************************************************** UDEV [1325.916811] remove /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 (usb) UDEV [1325.918489] remove /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 (usb) UDEV [1325.919282] remove /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 (usb) UDEV [1325.923005] remove /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 (usb) UDEV [1325.928437] remove /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.15 (usb_device) UDEV [1325.932709] remove /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 (usb) camera added *************************************************************************** UDEV [1329.344727] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 (usb) UDEV [1329.376313] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.16 (usb_device) UDEV [1329.389008] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 (usb) UDEV [1329.396241] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 (usb) UDEV [1329.401795] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 (usb) UDEV [1329.406739] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 (usb) This is what I get in /var/log/messages Oct 29 14:17:28 beagleboard user.info kernel: usb 1-2.3.4: USB disconnect, device number 16 Oct 29 14:17:31 beagleboard user.info kernel: usb 1-2.3.4: new high-speed USB device number 17 using ehci-omap Is there anything else that I can test / provide Thanks On Wed, Oct 30, 2013 at 5:58 PM, Khem Raj <raj.khem@gmail.com> wrote: > On Wed, Oct 30, 2013 at 1:51 PM, Edward Vidal <vidal.develone@gmail.com> > wrote: > > Hello, > > I am trying to add a c920 camera to my systems. I am not getting a > > /dev/video0. > > lsusb --verbose shows the HD Pro Webcam C920 > > Bus 001 Device 007: ID 046d:082d Logitech, Inc. > > Device Descriptor: > > bLength 18 > > bDescriptorType 1 > > bcdUSB 2.00 > > bDeviceClass 239 Miscellaneous Device > > bDeviceSubClass 2 ? > > bDeviceProtocol 1 Interface Association > > bMaxPacketSize0 64 > > idVendor 0x046d Logitech, Inc. > > idProduct 0x082d > > bcdDevice 0.11 > > iManufacturer 0 > > iProduct 2 HD Pro Webcam C920 > > iSerial 1 211EF9AF > > bNumConfigurations 1 > > plus much more information > > > > I created /etc/udev/rules.d/10-c920.rules > > SUBSYSTEM=="video4linux", BUS=="usb", ATTRS{idvendor}=="0x046d", > > ATTRS{idProduct}=="0x082d", NAME="video0", MODE:="0660" > > > > mknod /dev/video0 c 81 0 > > > > when I v4l2-ctl --all error no /dev/video0 > > Any and all help will be appreciated. > > you can check if udev rule is infact kicking in. use udevadm monitor/test > > > Thanks > > > > > > _______________________________________________ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > > > [-- Attachment #2: Type: text/html, Size: 7255 bytes --] ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: adding a udev entry for a camera 2013-10-31 1:12 ` Edward Vidal @ 2013-10-31 10:27 ` Gary Thomas 2013-10-31 10:58 ` Diego Sueiro 2013-10-31 14:41 ` Khem Raj 1 sibling, 1 reply; 17+ messages in thread From: Gary Thomas @ 2013-10-31 10:27 UTC (permalink / raw) To: yocto On 2013-10-30 19:12, Edward Vidal wrote: > Hello, > This is when I connect the camera > udevadm monitor test > monitor will print the received events for: > UDEV - the event which udev sends out after rule processing > KERNEL - the kernel uevent > > KERNEL[803.263336] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 (usb) > KERNEL[803.267456] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 (usb) > KERNEL[803.269287] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 (usb) > KERNEL[803.269958] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 (usb) > KERNEL[803.270721] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 (usb) > KERNEL[803.276214] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.15 (usb_device)********** > UDEV [803.277191] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 (usb) > UDEV [803.306091] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.15 (usb_device) > UDEV [803.318603] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 (usb) > UDEV [803.324249] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 (usb) > UDEV [803.329712] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 (usb) > UDEV [803.333160] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 (usb) > > still no /dev/video0 > ls -la /dev/v* > crw-rw---- 1 root tty 7, 0 Jan 1 2000 /dev/vcs > crw-rw---- 1 root tty 7, 1 Jan 1 2000 /dev/vcs1 > crw-rw---- 1 root tty 7, 2 Jan 1 2000 /dev/vcs2 > crw-rw---- 1 root tty 7, 3 Oct 29 13:51 /dev/vcs3 > crw-rw---- 1 root tty 7, 128 Jan 1 2000 /dev/vcsa > crw-rw---- 1 root tty 7, 129 Jan 1 2000 /dev/vcsa1 > crw-rw---- 1 root tty 7, 130 Jan 1 2000 /dev/vcsa2 > crw-rw---- 1 root tty 7, 131 Oct 29 13:51 /dev/vcsa3 > root@beagleboard:~# lsusb > Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. > Bus 001 Device 004: ID 0409:0059 NEC Corp. HighSpeed Hub > Bus 001 Device 005: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard > Bus 001 Device 006: ID 046d:c001 Logitech, Inc. N48/M-BB48 [FirstMouse Plus] > Bus 001 Device 015: ID 046d:082d Logitech, Inc. *********************************************************************************** > > > udevadm monitor --udev > monitor will print the received events for: > UDEV - the event which udev sends out after rule processing > camera removed***************************************************** > UDEV [1325.916811] remove /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 (usb) > UDEV [1325.918489] remove /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 (usb) > UDEV [1325.919282] remove /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 (usb) > UDEV [1325.923005] remove /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 (usb) > UDEV [1325.928437] remove /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.15 (usb_device) > UDEV [1325.932709] remove /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 (usb) > camera added *************************************************************************** > UDEV [1329.344727] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 (usb) > UDEV [1329.376313] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.16 (usb_device) > UDEV [1329.389008] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 (usb) > UDEV [1329.396241] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 (usb) > UDEV [1329.401795] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 (usb) > UDEV [1329.406739] add /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 (usb) > > This is what I get in /var/log/messages > Oct 29 14:17:28 beagleboard user.info <http://user.info> kernel: usb 1-2.3.4: USB disconnect, device number 16 > Oct 29 14:17:31 beagleboard user.info <http://user.info> kernel: usb 1-2.3.4: new high-speed USB device number 17 using ehci-omap > Is there anything else that I can test / provide What version of the Linux kernel are you using? Are you sure that there is a driver available for this camera? Does it work in your laptop/desktop? n.b. This question is probably better suited elsewhere as it is not really a Yocto issue. Maybe try: linux-media@vger.kernel.org > Thanks > > > On Wed, Oct 30, 2013 at 5:58 PM, Khem Raj <raj.khem@gmail.com <mailto:raj.khem@gmail.com>> wrote: > > On Wed, Oct 30, 2013 at 1:51 PM, Edward Vidal <vidal.develone@gmail.com <mailto:vidal.develone@gmail.com>> wrote: > > Hello, > > I am trying to add a c920 camera to my systems. I am not getting a > > /dev/video0. > > lsusb --verbose shows the HD Pro Webcam C920 > > Bus 001 Device 007: ID 046d:082d Logitech, Inc. > > Device Descriptor: > > bLength 18 > > bDescriptorType 1 > > bcdUSB 2.00 > > bDeviceClass 239 Miscellaneous Device > > bDeviceSubClass 2 ? > > bDeviceProtocol 1 Interface Association > > bMaxPacketSize0 64 > > idVendor 0x046d Logitech, Inc. > > idProduct 0x082d > > bcdDevice 0.11 > > iManufacturer 0 > > iProduct 2 HD Pro Webcam C920 > > iSerial 1 211EF9AF > > bNumConfigurations 1 > > plus much more information > > > > I created /etc/udev/rules.d/10-c920.rules > > SUBSYSTEM=="video4linux", BUS=="usb", ATTRS{idvendor}=="0x046d", > > ATTRS{idProduct}=="0x082d", NAME="video0", MODE:="0660" > > > > mknod /dev/video0 c 81 0 > > > > when I v4l2-ctl --all error no /dev/video0 > > Any and all help will be appreciated. > > you can check if udev rule is infact kicking in. use udevadm monitor/test > > > Thanks > > > > > > _______________________________________________ > > yocto mailing list > >yocto@yoctoproject.org <mailto:yocto@yoctoproject.org> > >https://lists.yoctoproject.org/listinfo/yocto > > > > > > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: adding a udev entry for a camera 2013-10-31 10:27 ` Gary Thomas @ 2013-10-31 10:58 ` Diego Sueiro 0 siblings, 0 replies; 17+ messages in thread From: Diego Sueiro @ 2013-10-31 10:58 UTC (permalink / raw) To: Gary Thomas; +Cc: yocto@yoctoproject.org [-- Attachment #1: Type: text/plain, Size: 8346 bytes --] Is it enabled on kernel config? Some references: http://linuxtv.org/wiki/index.php/Webcam_Devices http://tldp.org/HOWTO/Webcam-HOWTO/hardware.html Regards, -- *dS Diego Sueiro /*long live rock 'n roll*/ 2013/10/31 Gary Thomas <gary@mlbassoc.com> > On 2013-10-30 19:12, Edward Vidal wrote: > >> Hello, >> This is when I connect the camera >> udevadm monitor test >> monitor will print the received events for: >> UDEV - the event which udev sends out after rule processing >> KERNEL - the kernel uevent >> >> KERNEL[803.263336] add /devices/platform/usbhs_omap/** >> ehci-omap.0/usb1/1-2/1-2.3/1-**2.3.4 (usb) >> KERNEL[803.267456] add /devices/platform/usbhs_omap/** >> ehci-omap.0/usb1/1-2/1-2.3/1-**2.3.4/1-2.3.4:1.0 (usb) >> KERNEL[803.269287] add /devices/platform/usbhs_omap/** >> ehci-omap.0/usb1/1-2/1-2.3/1-**2.3.4/1-2.3.4:1.1 (usb) >> KERNEL[803.269958] add /devices/platform/usbhs_omap/** >> ehci-omap.0/usb1/1-2/1-2.3/1-**2.3.4/1-2.3.4:1.2 (usb) >> KERNEL[803.270721] add /devices/platform/usbhs_omap/** >> ehci-omap.0/usb1/1-2/1-2.3/1-**2.3.4/1-2.3.4:1.3 (usb) >> KERNEL[803.276214] add /devices/platform/usbhs_omap/** >> ehci-omap.0/usb1/1-2/1-2.3/1-**2.3.4/usb_device/usbdev1.15 >> (usb_device)********** >> UDEV [803.277191] add /devices/platform/usbhs_omap/** >> ehci-omap.0/usb1/1-2/1-2.3/1-**2.3.4 (usb) >> UDEV [803.306091] add /devices/platform/usbhs_omap/** >> ehci-omap.0/usb1/1-2/1-2.3/1-**2.3.4/usb_device/usbdev1.15 (usb_device) >> UDEV [803.318603] add /devices/platform/usbhs_omap/** >> ehci-omap.0/usb1/1-2/1-2.3/1-**2.3.4/1-2.3.4:1.2 (usb) >> UDEV [803.324249] add /devices/platform/usbhs_omap/** >> ehci-omap.0/usb1/1-2/1-2.3/1-**2.3.4/1-2.3.4:1.1 (usb) >> UDEV [803.329712] add /devices/platform/usbhs_omap/** >> ehci-omap.0/usb1/1-2/1-2.3/1-**2.3.4/1-2.3.4:1.0 (usb) >> UDEV [803.333160] add /devices/platform/usbhs_omap/** >> ehci-omap.0/usb1/1-2/1-2.3/1-**2.3.4/1-2.3.4:1.3 (usb) >> >> still no /dev/video0 >> ls -la /dev/v* >> crw-rw---- 1 root tty 7, 0 Jan 1 2000 /dev/vcs >> crw-rw---- 1 root tty 7, 1 Jan 1 2000 /dev/vcs1 >> crw-rw---- 1 root tty 7, 2 Jan 1 2000 /dev/vcs2 >> crw-rw---- 1 root tty 7, 3 Oct 29 13:51 /dev/vcs3 >> crw-rw---- 1 root tty 7, 128 Jan 1 2000 /dev/vcsa >> crw-rw---- 1 root tty 7, 129 Jan 1 2000 /dev/vcsa1 >> crw-rw---- 1 root tty 7, 130 Jan 1 2000 /dev/vcsa2 >> crw-rw---- 1 root tty 7, 131 Oct 29 13:51 /dev/vcsa3 >> root@beagleboard:~# lsusb >> Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. >> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >> Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. >> Bus 001 Device 004: ID 0409:0059 NEC Corp. HighSpeed Hub >> Bus 001 Device 005: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard >> Bus 001 Device 006: ID 046d:c001 Logitech, Inc. N48/M-BB48 [FirstMouse >> Plus] >> Bus 001 Device 015: ID 046d:082d Logitech, Inc. >> **************************************************************** >> *********************** >> >> >> udevadm monitor --udev >> monitor will print the received events for: >> UDEV - the event which udev sends out after rule processing >> camera removed******************************************************* >> UDEV [1325.916811] remove /devices/platform/usbhs_omap/** >> ehci-omap.0/usb1/1-2/1-2.3/1-**2.3.4/1-2.3.4:1.1 (usb) >> UDEV [1325.918489] remove /devices/platform/usbhs_omap/** >> ehci-omap.0/usb1/1-2/1-2.3/1-**2.3.4/1-2.3.4:1.0 (usb) >> UDEV [1325.919282] remove /devices/platform/usbhs_omap/** >> ehci-omap.0/usb1/1-2/1-2.3/1-**2.3.4/1-2.3.4:1.2 (usb) >> UDEV [1325.923005] remove /devices/platform/usbhs_omap/** >> ehci-omap.0/usb1/1-2/1-2.3/1-**2.3.4/1-2.3.4:1.3 (usb) >> UDEV [1325.928437] remove /devices/platform/usbhs_omap/** >> ehci-omap.0/usb1/1-2/1-2.3/1-**2.3.4/usb_device/usbdev1.15 (usb_device) >> UDEV [1325.932709] remove /devices/platform/usbhs_omap/** >> ehci-omap.0/usb1/1-2/1-2.3/1-**2.3.4 (usb) >> camera added ******************************** >> *********************************************** >> UDEV [1329.344727] add /devices/platform/usbhs_omap/** >> ehci-omap.0/usb1/1-2/1-2.3/1-**2.3.4 (usb) >> UDEV [1329.376313] add /devices/platform/usbhs_omap/** >> ehci-omap.0/usb1/1-2/1-2.3/1-**2.3.4/usb_device/usbdev1.16 (usb_device) >> UDEV [1329.389008] add /devices/platform/usbhs_omap/** >> ehci-omap.0/usb1/1-2/1-2.3/1-**2.3.4/1-2.3.4:1.2 (usb) >> UDEV [1329.396241] add /devices/platform/usbhs_omap/** >> ehci-omap.0/usb1/1-2/1-2.3/1-**2.3.4/1-2.3.4:1.1 (usb) >> UDEV [1329.401795] add /devices/platform/usbhs_omap/** >> ehci-omap.0/usb1/1-2/1-2.3/1-**2.3.4/1-2.3.4:1.0 (usb) >> UDEV [1329.406739] add /devices/platform/usbhs_omap/** >> ehci-omap.0/usb1/1-2/1-2.3/1-**2.3.4/1-2.3.4:1.3 (usb) >> >> This is what I get in /var/log/messages >> Oct 29 14:17:28 beagleboard user.info <http://user.info> kernel: usb >> 1-2.3.4: USB disconnect, device number 16 >> Oct 29 14:17:31 beagleboard user.info <http://user.info> kernel: usb >> 1-2.3.4: new high-speed USB device number 17 using ehci-omap >> >> Is there anything else that I can test / provide >> > > What version of the Linux kernel are you using? > > Are you sure that there is a driver available for this camera? Does it > work in your laptop/desktop? > > n.b. This question is probably better suited elsewhere as it is not really > a Yocto issue. Maybe try: > linux-media@vger.kernel.org > > Thanks >> >> >> On Wed, Oct 30, 2013 at 5:58 PM, Khem Raj <raj.khem@gmail.com <mailto: >> raj.khem@gmail.com>> wrote: >> >> >> On Wed, Oct 30, 2013 at 1:51 PM, Edward Vidal < >> vidal.develone@gmail.com <mailto:vidal.develone@gmail.**com<vidal.develone@gmail.com>>> >> wrote: >> > Hello, >> > I am trying to add a c920 camera to my systems. I am not getting a >> > /dev/video0. >> > lsusb --verbose shows the HD Pro Webcam C920 >> > Bus 001 Device 007: ID 046d:082d Logitech, Inc. >> > Device Descriptor: >> > bLength 18 >> > bDescriptorType 1 >> > bcdUSB 2.00 >> > bDeviceClass 239 Miscellaneous Device >> > bDeviceSubClass 2 ? >> > bDeviceProtocol 1 Interface Association >> > bMaxPacketSize0 64 >> > idVendor 0x046d Logitech, Inc. >> > idProduct 0x082d >> > bcdDevice 0.11 >> > iManufacturer 0 >> > iProduct 2 HD Pro Webcam C920 >> > iSerial 1 211EF9AF >> > bNumConfigurations 1 >> > plus much more information >> > >> > I created /etc/udev/rules.d/10-c920.**rules >> > SUBSYSTEM=="video4linux", BUS=="usb", ATTRS{idvendor}=="0x046d", >> > ATTRS{idProduct}=="0x082d", NAME="video0", MODE:="0660" >> > >> > mknod /dev/video0 c 81 0 >> > >> > when I v4l2-ctl --all error no /dev/video0 >> > Any and all help will be appreciated. >> >> you can check if udev rule is infact kicking in. use udevadm >> monitor/test >> >> > Thanks >> > >> > >> > ______________________________**_________________ >> > yocto mailing list >> >yocto@yoctoproject.org <mailto:yocto@yoctoproject.org**> >> >https://lists.yoctoproject.**org/listinfo/yocto<https://lists.yoctoproject.org/listinfo/yocto> >> >> > >> >> >> >> >> ______________________________**_________________ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.**org/listinfo/yocto<https://lists.yoctoproject.org/listinfo/yocto> >> >> > -- > ------------------------------**------------------------------ > Gary Thomas | Consulting for the > MLB Associates | Embedded world > ------------------------------**------------------------------ > > ______________________________**_________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.**org/listinfo/yocto<https://lists.yoctoproject.org/listinfo/yocto> > [-- Attachment #2: Type: text/html, Size: 10743 bytes --] ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: adding a udev entry for a camera 2013-10-31 1:12 ` Edward Vidal 2013-10-31 10:27 ` Gary Thomas @ 2013-10-31 14:41 ` Khem Raj 2013-10-31 15:45 ` Edward Vidal 1 sibling, 1 reply; 17+ messages in thread From: Khem Raj @ 2013-10-31 14:41 UTC (permalink / raw) To: Edward Vidal; +Cc: yocto@yoctoproject.org On Wed, Oct 30, 2013 at 6:12 PM, Edward Vidal <vidal.develone@gmail.com> wrote: > Hello, > This is when I connect the camera > udevadm monitor test > monitor will print the received events for: > UDEV - the event which udev sends out after rule processing > KERNEL - the kernel uevent > > KERNEL[803.263336] add > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 (usb) > KERNEL[803.267456] add > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 > (usb) > KERNEL[803.269287] add > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 > (usb) > KERNEL[803.269958] add > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 > (usb) > KERNEL[803.270721] add > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 > (usb) > KERNEL[803.276214] add > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.15 > (usb_device)********** > UDEV [803.277191] add > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 (usb) > UDEV [803.306091] add > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.15 > (usb_device) > UDEV [803.318603] add > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 > (usb) > UDEV [803.324249] add > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 > (usb) > UDEV [803.329712] add > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 > (usb) > UDEV [803.333160] add > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 > (usb) > > still no /dev/video0 > ls -la /dev/v* > crw-rw---- 1 root tty 7, 0 Jan 1 2000 /dev/vcs > crw-rw---- 1 root tty 7, 1 Jan 1 2000 /dev/vcs1 > crw-rw---- 1 root tty 7, 2 Jan 1 2000 /dev/vcs2 > crw-rw---- 1 root tty 7, 3 Oct 29 13:51 /dev/vcs3 > crw-rw---- 1 root tty 7, 128 Jan 1 2000 /dev/vcsa > crw-rw---- 1 root tty 7, 129 Jan 1 2000 /dev/vcsa1 > crw-rw---- 1 root tty 7, 130 Jan 1 2000 /dev/vcsa2 > crw-rw---- 1 root tty 7, 131 Oct 29 13:51 /dev/vcsa3 > root@beagleboard:~# lsusb > Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. > Bus 001 Device 004: ID 0409:0059 NEC Corp. HighSpeed Hub > Bus 001 Device 005: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard > Bus 001 Device 006: ID 046d:c001 Logitech, Inc. N48/M-BB48 [FirstMouse Plus] > Bus 001 Device 015: ID 046d:082d Logitech, Inc. > *********************************************************************************** > > > udevadm monitor --udev > monitor will print the received events for: > UDEV - the event which udev sends out after rule processing > camera removed***************************************************** > UDEV [1325.916811] remove > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 > (usb) > UDEV [1325.918489] remove > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 > (usb) > UDEV [1325.919282] remove > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 > (usb) > UDEV [1325.923005] remove > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 > (usb) > UDEV [1325.928437] remove > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.15 > (usb_device) > UDEV [1325.932709] remove > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 (usb) > camera added > *************************************************************************** > UDEV [1329.344727] add > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 (usb) > UDEV [1329.376313] add > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.16 > (usb_device) > UDEV [1329.389008] add > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 > (usb) > UDEV [1329.396241] add > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 > (usb) > UDEV [1329.401795] add > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 > (usb) > UDEV [1329.406739] add > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 > (usb) > > This is what I get in /var/log/messages > Oct 29 14:17:28 beagleboard user.info kernel: usb 1-2.3.4: USB disconnect, > device number 16 > Oct 29 14:17:31 beagleboard user.info kernel: usb 1-2.3.4: new high-speed > USB device number 17 using ehci-omap > Is there anything else that I can test / provide OK another thing to try is udevadm test --action=add /sys/.... where /sys/... is path to your device in sysfs this should give enough reason to what udev is doing when its getting an add event for this device. Secondly in your udev rule refer mknod with absolute path like /sbin/mknod or /bin/mknod where ever it is ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: adding a udev entry for a camera 2013-10-31 14:41 ` Khem Raj @ 2013-10-31 15:45 ` Edward Vidal 2013-10-31 15:55 ` Gary Thomas 2013-10-31 16:23 ` Khem Raj 0 siblings, 2 replies; 17+ messages in thread From: Edward Vidal @ 2013-10-31 15:45 UTC (permalink / raw) To: Khem Raj; +Cc: yocto@yoctoproject.org [-- Attachment #1: Type: text/plain, Size: 7921 bytes --] Hello all, less /etc/udev/rules.d/10-c920.rules WARNING: terminal is not fully functional SUBSYSTEM=="video4linux", BUS=="usb", ATTRS{idvendor}=="0x046d", ATTRS{idProduct }=="0x082d", NAME="video0", MODE:="0660" It appears the key BUS is not correct based on the tests below. My mknod is /bin/mknod. find / -name sysfs /usr/include/sysfs /usr/src/kernel/fs/sysfs udevadm test --action=add /usr/include/sysfs or udevadm test --action=add /usr/src/kernel/fs/sysfs unable to open device '/sys/usr/src/kernel/fs/sysfs' run_command: calling: test adm_test: version 182 This program is for debugging only, it does not run any program, specified by a RUN key. It may show incorrect results, because some values may be different, or not available at a simulation run. builtin_kmod_init: load module index add_matching_files: unable to open '/var/run/udev/rules.d': No such file or directory parse_file: reading '/etc/udev/rules.d/10-c920.rules' as rules file add_rule: unknown key 'BUS' in /etc/udev/rules.d/10-c920.rules:1 add_rule: invalid rule '/etc/udev/rules.d/10-c920.rules:1' lots of output udev_rules_new: rules use 18408 bytes tokens (1534 * 12 bytes), 12756 bytes buffer udev_rules_new: temporary index used 12800 bytes (640 * 20 bytes) unable to open device '/sys/usr/include/sysfs' builtin_kmod_exit: unload module index Do I add RUN+="/bin/mknod /dev/video0 c 81 0" see below new version of 1--c920.rules cat 10-c920.rules SUBSYSTEM=="video4linux", BUS=="usb", ATTRS{idvendor}=="0x046d", ATTRS{idProduct}=="0x082d", NAME="video0", MODE:="0660", RUN+="/bin/mknod /dev/video0 c 81 0" udevadm test --action=add /usr/src/kernel/fs/sysfs run_command: calling: test adm_test: version 182 This program is for debugging only, it does not run any program, specified by a RUN key. It may show incorrect results, because some values may be different, or not available at a simulation run. builtin_kmod_init: load module index add_matching_files: unable to open '/var/run/udev/rules.d': No such file or directory parse_file: reading '/etc/udev/rules.d/10-c920.rules' as rules file add_rule: unknown key 'BUS' in /etc/udev/rules.d/10-c920.rules:1 add_rule: invalid rule '/etc/udev/rules.d/10-c920.rules:1' Where do you find information for working with rules other than just some examples? Thanks On Thu, Oct 31, 2013 at 8:41 AM, Khem Raj <raj.khem@gmail.com> wrote: > On Wed, Oct 30, 2013 at 6:12 PM, Edward Vidal <vidal.develone@gmail.com> > wrote: > > Hello, > > This is when I connect the camera > > udevadm monitor test > > monitor will print the received events for: > > UDEV - the event which udev sends out after rule processing > > KERNEL - the kernel uevent > > > > KERNEL[803.263336] add > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 (usb) > > KERNEL[803.267456] add > > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 > > (usb) > > KERNEL[803.269287] add > > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 > > (usb) > > KERNEL[803.269958] add > > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 > > (usb) > > KERNEL[803.270721] add > > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 > > (usb) > > KERNEL[803.276214] add > > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.15 > > (usb_device)********** > > UDEV [803.277191] add > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 (usb) > > UDEV [803.306091] add > > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.15 > > (usb_device) > > UDEV [803.318603] add > > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 > > (usb) > > UDEV [803.324249] add > > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 > > (usb) > > UDEV [803.329712] add > > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 > > (usb) > > UDEV [803.333160] add > > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 > > (usb) > > > > still no /dev/video0 > > ls -la /dev/v* > > crw-rw---- 1 root tty 7, 0 Jan 1 2000 /dev/vcs > > crw-rw---- 1 root tty 7, 1 Jan 1 2000 /dev/vcs1 > > crw-rw---- 1 root tty 7, 2 Jan 1 2000 /dev/vcs2 > > crw-rw---- 1 root tty 7, 3 Oct 29 13:51 /dev/vcs3 > > crw-rw---- 1 root tty 7, 128 Jan 1 2000 /dev/vcsa > > crw-rw---- 1 root tty 7, 129 Jan 1 2000 /dev/vcsa1 > > crw-rw---- 1 root tty 7, 130 Jan 1 2000 /dev/vcsa2 > > crw-rw---- 1 root tty 7, 131 Oct 29 13:51 /dev/vcsa3 > > root@beagleboard:~# lsusb > > Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. > > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. > > Bus 001 Device 004: ID 0409:0059 NEC Corp. HighSpeed Hub > > Bus 001 Device 005: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard > > Bus 001 Device 006: ID 046d:c001 Logitech, Inc. N48/M-BB48 [FirstMouse > Plus] > > Bus 001 Device 015: ID 046d:082d Logitech, Inc. > > > *********************************************************************************** > > > > > > udevadm monitor --udev > > monitor will print the received events for: > > UDEV - the event which udev sends out after rule processing > > camera removed***************************************************** > > UDEV [1325.916811] remove > > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 > > (usb) > > UDEV [1325.918489] remove > > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 > > (usb) > > UDEV [1325.919282] remove > > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 > > (usb) > > UDEV [1325.923005] remove > > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 > > (usb) > > UDEV [1325.928437] remove > > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.15 > > (usb_device) > > UDEV [1325.932709] remove > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 (usb) > > camera added > > > *************************************************************************** > > UDEV [1329.344727] add > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 (usb) > > UDEV [1329.376313] add > > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.16 > > (usb_device) > > UDEV [1329.389008] add > > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 > > (usb) > > UDEV [1329.396241] add > > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 > > (usb) > > UDEV [1329.401795] add > > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 > > (usb) > > UDEV [1329.406739] add > > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 > > (usb) > > > > This is what I get in /var/log/messages > > Oct 29 14:17:28 beagleboard user.info kernel: usb 1-2.3.4: USB > disconnect, > > device number 16 > > Oct 29 14:17:31 beagleboard user.info kernel: usb 1-2.3.4: new > high-speed > > USB device number 17 using ehci-omap > > Is there anything else that I can test / provide > > OK another thing to try is > > udevadm test --action=add /sys/.... > > where /sys/... is path to your device in sysfs > > this should give enough reason to what udev is doing when its getting an > add > event for this device. > > Secondly in your udev rule refer mknod with absolute path like > /sbin/mknod or /bin/mknod where ever it is > [-- Attachment #2: Type: text/html, Size: 9284 bytes --] ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: adding a udev entry for a camera 2013-10-31 15:45 ` Edward Vidal @ 2013-10-31 15:55 ` Gary Thomas 2013-10-31 16:20 ` Khem Raj 2013-10-31 16:23 ` Khem Raj 1 sibling, 1 reply; 17+ messages in thread From: Gary Thomas @ 2013-10-31 15:55 UTC (permalink / raw) To: yocto On 2013-10-31 09:45, Edward Vidal wrote: > Hello all, > less /etc/udev/rules.d/10-c920.rules > WARNING: terminal is not fully functional > SUBSYSTEM=="video4linux", BUS=="usb", ATTRS{idvendor}=="0x046d", ATTRS{idProduct > }=="0x082d", NAME="video0", MODE:="0660" > It appears the key BUS is not correct based on the tests below. > My mknod is /bin/mknod. > find / -name sysfs > /usr/include/sysfs > /usr/src/kernel/fs/sysfs Note: chasing this udev behaviour is a waste of time if the kernel doesn't recognize and support your device. Have you even looked to see if this camera is supported in your kernel? I could not find a driver for it when I looked, even in the latest mainline kernel. What kernel are you trying to use? > > udevadm test --action=add /usr/include/sysfs or udevadm test --action=add /usr/src/kernel/fs/sysfs unable to open device '/sys/usr/src/kernel/fs/sysfs' > run_command: calling: test > adm_test: version 182 > This program is for debugging only, it does not run any program, > specified by a RUN key. It may show incorrect results, because > some values may be different, or not available at a simulation run. > > builtin_kmod_init: load module index > add_matching_files: unable to open '/var/run/udev/rules.d': No such file or directory > parse_file: reading '/etc/udev/rules.d/10-c920.rules' as rules file > add_rule: unknown key 'BUS' in /etc/udev/rules.d/10-c920.rules:1 > add_rule: invalid rule '/etc/udev/rules.d/10-c920.rules:1' > > lots of output > > udev_rules_new: rules use 18408 bytes tokens (1534 * 12 bytes), 12756 bytes buffer > udev_rules_new: temporary index used 12800 bytes (640 * 20 bytes) > unable to open device '/sys/usr/include/sysfs' > builtin_kmod_exit: unload module index > > Do I add RUN+="/bin/mknod /dev/video0 c 81 0" see below new version of 1--c920.rules > cat 10-c920.rules > SUBSYSTEM=="video4linux", BUS=="usb", ATTRS{idvendor}=="0x046d", ATTRS{idProduct}=="0x082d", NAME="video0", MODE:="0660", RUN+="/bin/mknod /dev/video0 c 81 0" > udevadm test --action=add /usr/src/kernel/fs/sysfs > run_command: calling: test > adm_test: version 182 > This program is for debugging only, it does not run any program, > specified by a RUN key. It may show incorrect results, because > some values may be different, or not available at a simulation run. > > builtin_kmod_init: load module index > add_matching_files: unable to open '/var/run/udev/rules.d': No such file or directory > parse_file: reading '/etc/udev/rules.d/10-c920.rules' as rules file > add_rule: unknown key 'BUS' in /etc/udev/rules.d/10-c920.rules:1 > add_rule: invalid rule '/etc/udev/rules.d/10-c920.rules:1' > > Where do you find information for working with rules other than just some examples? > > Thanks > > > On Thu, Oct 31, 2013 at 8:41 AM, Khem Raj <raj.khem@gmail.com <mailto:raj.khem@gmail.com>> wrote: > > On Wed, Oct 30, 2013 at 6:12 PM, Edward Vidal <vidal.develone@gmail.com <mailto:vidal.develone@gmail.com>> wrote: > > Hello, > > This is when I connect the camera > > udevadm monitor test > > monitor will print the received events for: > > UDEV - the event which udev sends out after rule processing > > KERNEL - the kernel uevent > > > > KERNEL[803.263336] add > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 (usb) > > KERNEL[803.267456] add > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 > > (usb) > > KERNEL[803.269287] add > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 > > (usb) > > KERNEL[803.269958] add > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 > > (usb) > > KERNEL[803.270721] add > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 > > (usb) > > KERNEL[803.276214] add > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.15 > > (usb_device)********** > > UDEV [803.277191] add > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 (usb) > > UDEV [803.306091] add > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.15 > > (usb_device) > > UDEV [803.318603] add > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 > > (usb) > > UDEV [803.324249] add > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 > > (usb) > > UDEV [803.329712] add > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 > > (usb) > > UDEV [803.333160] add > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 > > (usb) > > > > still no /dev/video0 > > ls -la /dev/v* > > crw-rw---- 1 root tty 7, 0 Jan 1 2000 /dev/vcs > > crw-rw---- 1 root tty 7, 1 Jan 1 2000 /dev/vcs1 > > crw-rw---- 1 root tty 7, 2 Jan 1 2000 /dev/vcs2 > > crw-rw---- 1 root tty 7, 3 Oct 29 13:51 /dev/vcs3 > > crw-rw---- 1 root tty 7, 128 Jan 1 2000 /dev/vcsa > > crw-rw---- 1 root tty 7, 129 Jan 1 2000 /dev/vcsa1 > > crw-rw---- 1 root tty 7, 130 Jan 1 2000 /dev/vcsa2 > > crw-rw---- 1 root tty 7, 131 Oct 29 13:51 /dev/vcsa3 > > root@beagleboard:~# lsusb > > Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. > > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. > > Bus 001 Device 004: ID 0409:0059 NEC Corp. HighSpeed Hub > > Bus 001 Device 005: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard > > Bus 001 Device 006: ID 046d:c001 Logitech, Inc. N48/M-BB48 [FirstMouse Plus] > > Bus 001 Device 015: ID 046d:082d Logitech, Inc. > > *********************************************************************************** > > > > > > udevadm monitor --udev > > monitor will print the received events for: > > UDEV - the event which udev sends out after rule processing > > camera removed***************************************************** > > UDEV [1325.916811] remove > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 > > (usb) > > UDEV [1325.918489] remove > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 > > (usb) > > UDEV [1325.919282] remove > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 > > (usb) > > UDEV [1325.923005] remove > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 > > (usb) > > UDEV [1325.928437] remove > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.15 > > (usb_device) > > UDEV [1325.932709] remove > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 (usb) > > camera added > > *************************************************************************** > > UDEV [1329.344727] add > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 (usb) > > UDEV [1329.376313] add > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.16 > > (usb_device) > > UDEV [1329.389008] add > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 > > (usb) > > UDEV [1329.396241] add > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 > > (usb) > > UDEV [1329.401795] add > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 > > (usb) > > UDEV [1329.406739] add > > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 > > (usb) > > > > This is what I get in /var/log/messages > > Oct 29 14:17:28 beagleboarduser.info <http://user.info> kernel: usb 1-2.3.4: USB disconnect, > > device number 16 > > Oct 29 14:17:31 beagleboarduser.info <http://user.info> kernel: usb 1-2.3.4: new high-speed > > USB device number 17 using ehci-omap > > Is there anything else that I can test / provide > > OK another thing to try is > > udevadm test --action=add /sys/.... > > where /sys/... is path to your device in sysfs > > this should give enough reason to what udev is doing when its getting an add > event for this device. > > Secondly in your udev rule refer mknod with absolute path like > /sbin/mknod or /bin/mknod where ever it is > > > > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: adding a udev entry for a camera 2013-10-31 15:55 ` Gary Thomas @ 2013-10-31 16:20 ` Khem Raj 2013-10-31 16:34 ` Gary Thomas 0 siblings, 1 reply; 17+ messages in thread From: Khem Raj @ 2013-10-31 16:20 UTC (permalink / raw) To: Gary Thomas; +Cc: yocto@yoctoproject.org On Thu, Oct 31, 2013 at 8:55 AM, Gary Thomas <gary@mlbassoc.com> wrote: > On 2013-10-31 09:45, Edward Vidal wrote: >> >> Hello all, >> less /etc/udev/rules.d/10-c920.rules >> WARNING: terminal is not fully functional >> SUBSYSTEM=="video4linux", BUS=="usb", ATTRS{idvendor}=="0x046d", >> ATTRS{idProduct >> }=="0x082d", NAME="video0", MODE:="0660" >> It appears the key BUS is not correct based on the tests below. >> My mknod is /bin/mknod. >> find / -name sysfs >> /usr/include/sysfs >> /usr/src/kernel/fs/sysfs > > > Note: chasing this udev behaviour is a waste of time if the kernel doesn't > recognize > and support your device. Look at the first post. Its recognised and displayed ok with lsusb. > > Have you even looked to see if this camera is supported in your kernel? I > could > not find a driver for it when I looked, even in the latest mainline kernel. > > What kernel are you trying to use? > >> >> udevadm test --action=add /usr/include/sysfs or udevadm test --action=add >> /usr/src/kernel/fs/sysfs unable to open device >> '/sys/usr/src/kernel/fs/sysfs' >> run_command: calling: test >> adm_test: version 182 >> This program is for debugging only, it does not run any program, >> specified by a RUN key. It may show incorrect results, because >> some values may be different, or not available at a simulation run. >> >> builtin_kmod_init: load module index >> add_matching_files: unable to open '/var/run/udev/rules.d': No such file >> or directory >> parse_file: reading '/etc/udev/rules.d/10-c920.rules' as rules file >> add_rule: unknown key 'BUS' in /etc/udev/rules.d/10-c920.rules:1 >> add_rule: invalid rule '/etc/udev/rules.d/10-c920.rules:1' >> >> lots of output >> >> udev_rules_new: rules use 18408 bytes tokens (1534 * 12 bytes), 12756 >> bytes buffer >> udev_rules_new: temporary index used 12800 bytes (640 * 20 bytes) >> unable to open device '/sys/usr/include/sysfs' >> builtin_kmod_exit: unload module index >> >> Do I add RUN+="/bin/mknod /dev/video0 c 81 0" see below new version of >> 1--c920.rules >> cat 10-c920.rules >> SUBSYSTEM=="video4linux", BUS=="usb", ATTRS{idvendor}=="0x046d", >> ATTRS{idProduct}=="0x082d", NAME="video0", MODE:="0660", RUN+="/bin/mknod >> /dev/video0 c 81 0" >> udevadm test --action=add /usr/src/kernel/fs/sysfs >> run_command: calling: test >> adm_test: version 182 >> This program is for debugging only, it does not run any program, >> specified by a RUN key. It may show incorrect results, because >> some values may be different, or not available at a simulation run. >> >> builtin_kmod_init: load module index >> add_matching_files: unable to open '/var/run/udev/rules.d': No such file >> or directory >> parse_file: reading '/etc/udev/rules.d/10-c920.rules' as rules file >> add_rule: unknown key 'BUS' in /etc/udev/rules.d/10-c920.rules:1 >> add_rule: invalid rule '/etc/udev/rules.d/10-c920.rules:1' >> >> Where do you find information for working with rules other than just some >> examples? >> >> Thanks >> >> >> On Thu, Oct 31, 2013 at 8:41 AM, Khem Raj <raj.khem@gmail.com >> <mailto:raj.khem@gmail.com>> wrote: >> >> >> On Wed, Oct 30, 2013 at 6:12 PM, Edward Vidal >> <vidal.develone@gmail.com <mailto:vidal.develone@gmail.com>> wrote: >> > Hello, >> > This is when I connect the camera >> > udevadm monitor test >> > monitor will print the received events for: >> > UDEV - the event which udev sends out after rule processing >> > KERNEL - the kernel uevent >> > >> > KERNEL[803.263336] add >> > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 >> (usb) >> > KERNEL[803.267456] add >> > >> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 >> > (usb) >> > KERNEL[803.269287] add >> > >> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 >> > (usb) >> > KERNEL[803.269958] add >> > >> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 >> > (usb) >> > KERNEL[803.270721] add >> > >> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 >> > (usb) >> > KERNEL[803.276214] add >> > >> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.15 >> > (usb_device)********** >> > UDEV [803.277191] add >> > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 >> (usb) >> > UDEV [803.306091] add >> > >> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.15 >> > (usb_device) >> > UDEV [803.318603] add >> > >> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 >> > (usb) >> > UDEV [803.324249] add >> > >> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 >> > (usb) >> > UDEV [803.329712] add >> > >> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 >> > (usb) >> > UDEV [803.333160] add >> > >> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 >> > (usb) >> > >> > still no /dev/video0 >> > ls -la /dev/v* >> > crw-rw---- 1 root tty 7, 0 Jan 1 2000 /dev/vcs >> > crw-rw---- 1 root tty 7, 1 Jan 1 2000 /dev/vcs1 >> > crw-rw---- 1 root tty 7, 2 Jan 1 2000 /dev/vcs2 >> > crw-rw---- 1 root tty 7, 3 Oct 29 13:51 /dev/vcs3 >> > crw-rw---- 1 root tty 7, 128 Jan 1 2000 /dev/vcsa >> > crw-rw---- 1 root tty 7, 129 Jan 1 2000 /dev/vcsa1 >> > crw-rw---- 1 root tty 7, 130 Jan 1 2000 /dev/vcsa2 >> > crw-rw---- 1 root tty 7, 131 Oct 29 13:51 /dev/vcsa3 >> > root@beagleboard:~# lsusb >> > Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. >> > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >> > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >> > Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. >> > Bus 001 Device 004: ID 0409:0059 NEC Corp. HighSpeed Hub >> > Bus 001 Device 005: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard >> > Bus 001 Device 006: ID 046d:c001 Logitech, Inc. N48/M-BB48 >> [FirstMouse Plus] >> > Bus 001 Device 015: ID 046d:082d Logitech, Inc. >> > >> *********************************************************************************** >> > >> > >> > udevadm monitor --udev >> > monitor will print the received events for: >> > UDEV - the event which udev sends out after rule processing >> > camera removed***************************************************** >> > UDEV [1325.916811] remove >> > >> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 >> > (usb) >> > UDEV [1325.918489] remove >> > >> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 >> > (usb) >> > UDEV [1325.919282] remove >> > >> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 >> > (usb) >> > UDEV [1325.923005] remove >> > >> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 >> > (usb) >> > UDEV [1325.928437] remove >> > >> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.15 >> > (usb_device) >> > UDEV [1325.932709] remove >> > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 >> (usb) >> > camera added >> > >> *************************************************************************** >> > UDEV [1329.344727] add >> > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 >> (usb) >> > UDEV [1329.376313] add >> > >> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.16 >> > (usb_device) >> > UDEV [1329.389008] add >> > >> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 >> > (usb) >> > UDEV [1329.396241] add >> > >> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 >> > (usb) >> > UDEV [1329.401795] add >> > >> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 >> > (usb) >> > UDEV [1329.406739] add >> > >> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 >> > (usb) >> > >> > This is what I get in /var/log/messages >> > Oct 29 14:17:28 beagleboarduser.info <http://user.info> kernel: usb >> 1-2.3.4: USB disconnect, >> > device number 16 >> > Oct 29 14:17:31 beagleboarduser.info <http://user.info> kernel: usb >> 1-2.3.4: new high-speed >> >> > USB device number 17 using ehci-omap >> > Is there anything else that I can test / provide >> >> OK another thing to try is >> >> udevadm test --action=add /sys/.... >> >> where /sys/... is path to your device in sysfs >> >> this should give enough reason to what udev is doing when its getting >> an add >> event for this device. >> >> Secondly in your udev rule refer mknod with absolute path like >> /sbin/mknod or /bin/mknod where ever it is >> >> >> >> >> _______________________________________________ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto >> > > -- > ------------------------------------------------------------ > Gary Thomas | Consulting for the > MLB Associates | Embedded world > ------------------------------------------------------------ > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: adding a udev entry for a camera 2013-10-31 16:20 ` Khem Raj @ 2013-10-31 16:34 ` Gary Thomas 0 siblings, 0 replies; 17+ messages in thread From: Gary Thomas @ 2013-10-31 16:34 UTC (permalink / raw) To: Khem Raj; +Cc: yocto@yoctoproject.org On 2013-10-31 10:20, Khem Raj wrote: > On Thu, Oct 31, 2013 at 8:55 AM, Gary Thomas <gary@mlbassoc.com> wrote: >> On 2013-10-31 09:45, Edward Vidal wrote: >>> >>> Hello all, >>> less /etc/udev/rules.d/10-c920.rules >>> WARNING: terminal is not fully functional >>> SUBSYSTEM=="video4linux", BUS=="usb", ATTRS{idvendor}=="0x046d", >>> ATTRS{idProduct >>> }=="0x082d", NAME="video0", MODE:="0660" >>> It appears the key BUS is not correct based on the tests below. >>> My mknod is /bin/mknod. >>> find / -name sysfs >>> /usr/include/sysfs >>> /usr/src/kernel/fs/sysfs >> >> >> Note: chasing this udev behaviour is a waste of time if the kernel doesn't >> recognize >> and support your device. > > Look at the first post. Its recognised and displayed ok with lsusb. That doesn't mean it has a driver which hooks it into the video subsystem (which is what will evoke the creation of /dev/video*) > >> >> Have you even looked to see if this camera is supported in your kernel? I >> could >> not find a driver for it when I looked, even in the latest mainline kernel. >> >> What kernel are you trying to use? >> >>> >>> udevadm test --action=add /usr/include/sysfs or udevadm test --action=add >>> /usr/src/kernel/fs/sysfs unable to open device >>> '/sys/usr/src/kernel/fs/sysfs' >>> run_command: calling: test >>> adm_test: version 182 >>> This program is for debugging only, it does not run any program, >>> specified by a RUN key. It may show incorrect results, because >>> some values may be different, or not available at a simulation run. >>> >>> builtin_kmod_init: load module index >>> add_matching_files: unable to open '/var/run/udev/rules.d': No such file >>> or directory >>> parse_file: reading '/etc/udev/rules.d/10-c920.rules' as rules file >>> add_rule: unknown key 'BUS' in /etc/udev/rules.d/10-c920.rules:1 >>> add_rule: invalid rule '/etc/udev/rules.d/10-c920.rules:1' >>> >>> lots of output >>> >>> udev_rules_new: rules use 18408 bytes tokens (1534 * 12 bytes), 12756 >>> bytes buffer >>> udev_rules_new: temporary index used 12800 bytes (640 * 20 bytes) >>> unable to open device '/sys/usr/include/sysfs' >>> builtin_kmod_exit: unload module index >>> >>> Do I add RUN+="/bin/mknod /dev/video0 c 81 0" see below new version of >>> 1--c920.rules >>> cat 10-c920.rules >>> SUBSYSTEM=="video4linux", BUS=="usb", ATTRS{idvendor}=="0x046d", >>> ATTRS{idProduct}=="0x082d", NAME="video0", MODE:="0660", RUN+="/bin/mknod >>> /dev/video0 c 81 0" >>> udevadm test --action=add /usr/src/kernel/fs/sysfs >>> run_command: calling: test >>> adm_test: version 182 >>> This program is for debugging only, it does not run any program, >>> specified by a RUN key. It may show incorrect results, because >>> some values may be different, or not available at a simulation run. >>> >>> builtin_kmod_init: load module index >>> add_matching_files: unable to open '/var/run/udev/rules.d': No such file >>> or directory >>> parse_file: reading '/etc/udev/rules.d/10-c920.rules' as rules file >>> add_rule: unknown key 'BUS' in /etc/udev/rules.d/10-c920.rules:1 >>> add_rule: invalid rule '/etc/udev/rules.d/10-c920.rules:1' >>> >>> Where do you find information for working with rules other than just some >>> examples? >>> >>> Thanks >>> >>> >>> On Thu, Oct 31, 2013 at 8:41 AM, Khem Raj <raj.khem@gmail.com >>> <mailto:raj.khem@gmail.com>> wrote: >>> >>> >>> On Wed, Oct 30, 2013 at 6:12 PM, Edward Vidal >>> <vidal.develone@gmail.com <mailto:vidal.develone@gmail.com>> wrote: >>> > Hello, >>> > This is when I connect the camera >>> > udevadm monitor test >>> > monitor will print the received events for: >>> > UDEV - the event which udev sends out after rule processing >>> > KERNEL - the kernel uevent >>> > >>> > KERNEL[803.263336] add >>> > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 >>> (usb) >>> > KERNEL[803.267456] add >>> > >>> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 >>> > (usb) >>> > KERNEL[803.269287] add >>> > >>> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 >>> > (usb) >>> > KERNEL[803.269958] add >>> > >>> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 >>> > (usb) >>> > KERNEL[803.270721] add >>> > >>> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 >>> > (usb) >>> > KERNEL[803.276214] add >>> > >>> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.15 >>> > (usb_device)********** >>> > UDEV [803.277191] add >>> > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 >>> (usb) >>> > UDEV [803.306091] add >>> > >>> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.15 >>> > (usb_device) >>> > UDEV [803.318603] add >>> > >>> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 >>> > (usb) >>> > UDEV [803.324249] add >>> > >>> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 >>> > (usb) >>> > UDEV [803.329712] add >>> > >>> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 >>> > (usb) >>> > UDEV [803.333160] add >>> > >>> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 >>> > (usb) >>> > >>> > still no /dev/video0 >>> > ls -la /dev/v* >>> > crw-rw---- 1 root tty 7, 0 Jan 1 2000 /dev/vcs >>> > crw-rw---- 1 root tty 7, 1 Jan 1 2000 /dev/vcs1 >>> > crw-rw---- 1 root tty 7, 2 Jan 1 2000 /dev/vcs2 >>> > crw-rw---- 1 root tty 7, 3 Oct 29 13:51 /dev/vcs3 >>> > crw-rw---- 1 root tty 7, 128 Jan 1 2000 /dev/vcsa >>> > crw-rw---- 1 root tty 7, 129 Jan 1 2000 /dev/vcsa1 >>> > crw-rw---- 1 root tty 7, 130 Jan 1 2000 /dev/vcsa2 >>> > crw-rw---- 1 root tty 7, 131 Oct 29 13:51 /dev/vcsa3 >>> > root@beagleboard:~# lsusb >>> > Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. >>> > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >>> > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >>> > Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. >>> > Bus 001 Device 004: ID 0409:0059 NEC Corp. HighSpeed Hub >>> > Bus 001 Device 005: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard >>> > Bus 001 Device 006: ID 046d:c001 Logitech, Inc. N48/M-BB48 >>> [FirstMouse Plus] >>> > Bus 001 Device 015: ID 046d:082d Logitech, Inc. >>> > >>> *********************************************************************************** >>> > >>> > >>> > udevadm monitor --udev >>> > monitor will print the received events for: >>> > UDEV - the event which udev sends out after rule processing >>> > camera removed***************************************************** >>> > UDEV [1325.916811] remove >>> > >>> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 >>> > (usb) >>> > UDEV [1325.918489] remove >>> > >>> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 >>> > (usb) >>> > UDEV [1325.919282] remove >>> > >>> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 >>> > (usb) >>> > UDEV [1325.923005] remove >>> > >>> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 >>> > (usb) >>> > UDEV [1325.928437] remove >>> > >>> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.15 >>> > (usb_device) >>> > UDEV [1325.932709] remove >>> > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 >>> (usb) >>> > camera added >>> > >>> *************************************************************************** >>> > UDEV [1329.344727] add >>> > /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4 >>> (usb) >>> > UDEV [1329.376313] add >>> > >>> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/usb_device/usbdev1.16 >>> > (usb_device) >>> > UDEV [1329.389008] add >>> > >>> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.2 >>> > (usb) >>> > UDEV [1329.396241] add >>> > >>> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.1 >>> > (usb) >>> > UDEV [1329.401795] add >>> > >>> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0 >>> > (usb) >>> > UDEV [1329.406739] add >>> > >>> /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.3 >>> > (usb) >>> > >>> > This is what I get in /var/log/messages >>> > Oct 29 14:17:28 beagleboarduser.info <http://user.info> kernel: usb >>> 1-2.3.4: USB disconnect, >>> > device number 16 >>> > Oct 29 14:17:31 beagleboarduser.info <http://user.info> kernel: usb >>> 1-2.3.4: new high-speed >>> >>> > USB device number 17 using ehci-omap >>> > Is there anything else that I can test / provide >>> >>> OK another thing to try is >>> >>> udevadm test --action=add /sys/.... >>> >>> where /sys/... is path to your device in sysfs >>> >>> this should give enough reason to what udev is doing when its getting >>> an add >>> event for this device. >>> >>> Secondly in your udev rule refer mknod with absolute path like >>> /sbin/mknod or /bin/mknod where ever it is >>> >>> >>> >>> >>> _______________________________________________ >>> yocto mailing list >>> yocto@yoctoproject.org >>> https://lists.yoctoproject.org/listinfo/yocto >>> >> >> -- >> ------------------------------------------------------------ >> Gary Thomas | Consulting for the >> MLB Associates | Embedded world >> ------------------------------------------------------------ >> _______________________________________________ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: adding a udev entry for a camera 2013-10-31 15:45 ` Edward Vidal 2013-10-31 15:55 ` Gary Thomas @ 2013-10-31 16:23 ` Khem Raj 2013-10-31 16:54 ` Edward Vidal 1 sibling, 1 reply; 17+ messages in thread From: Khem Raj @ 2013-10-31 16:23 UTC (permalink / raw) To: Edward Vidal; +Cc: yocto@yoctoproject.org On Thu, Oct 31, 2013 at 8:45 AM, Edward Vidal <vidal.develone@gmail.com> wrote: > > Do I add RUN+="/bin/mknod /dev/video0 c 81 0" see below new version of > 1--c920.rules > cat 10-c920.rules > SUBSYSTEM=="video4linux", BUS=="usb", ATTRS{idvendor}=="0x046d", > ATTRS{idProduct}=="0x082d", NAME="video0", MODE:="0660", RUN+="/bin/mknod > /dev/video0 c 81 0" get rid of BUS construct there ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: adding a udev entry for a camera 2013-10-31 16:23 ` Khem Raj @ 2013-10-31 16:54 ` Edward Vidal 2013-10-31 17:08 ` Khem Raj 0 siblings, 1 reply; 17+ messages in thread From: Edward Vidal @ 2013-10-31 16:54 UTC (permalink / raw) To: Khem Raj; +Cc: yocto@yoctoproject.org [-- Attachment #1: Type: text/plain, Size: 2640 bytes --] hello, I removed the bus udevadm test --action=add /usr/src/kernel/sysfs run_command: calling: test adm_test: version 182 This program is for debugging only, it does not run any program, specified by a RUN key. It may show incorrect results, because some values may be different, or not available at a simulation run. builtin_kmod_init: load module index add_matching_files: unable to open '/var/run/udev/rules.d': No such file or directory parse_file: reading '/etc/udev/rules.d/10-c920.rules' as rules file still no /dev/video0 cat /etc/udev/rules.d/10-c920.rules SUBSYSTEM=="video4linux", ATTRS{idvendor}=="0x046d", ATTRS{idProduct}=="0x082d", NAME="video0", MODE:="0660", RUN="/bin/mknod /dev/video0 c 81 0" still no /dev/video0 The camera is working correctly on my fedora 18 x86_64. Note: * Before camera connected ** After camera connected Linux sim4.swbell.net 3.9.2-200.fc18.x86_64 #1 SMP Mon May 13 13:59:47 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Module Size Used by **snd_usb_audio 145223 1 **snd_usbmidi_lib 24713 1 snd_usb_audio **snd_rawmidi 29531 1 snd_usbmidi_lib *snd_hwdep 17650 1 snd_hda_codec **snd_hwdep 17650 2 snd_usb_audio,snd_hda_codec *snd_seq_device 14136 1 snd_seq **snd_seq_device 14136 2 snd_seq,snd_rawmidi *snd 79379 19 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_hda_codec,snd_hda_intel,snd_seq_device **snd 79379 24 snd_hda_codec_realtek,snd_usb_audio,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_usbmidi_lib,snd_hda_codec,snd_hda_intel,snd_seq_device *video 18991 0 **video 18991 0 This is the beagleboard lsmod Module Size Used by nls_iso8859_1 3673 1 nls_cp437 5339 1 I am going to be checking the video is a module or built into the kernel of the uname -a Linux beagleboard 3.4.36-yocto-standard #1 Mon Oct 28 21:58:22 MDT 2013 armv7l GNU/Linux Thanks On Thu, Oct 31, 2013 at 10:23 AM, Khem Raj <raj.khem@gmail.com> wrote: > On Thu, Oct 31, 2013 at 8:45 AM, Edward Vidal <vidal.develone@gmail.com> > wrote: > > > > Do I add RUN+="/bin/mknod /dev/video0 c 81 0" see below new version of > > 1--c920.rules > > cat 10-c920.rules > > SUBSYSTEM=="video4linux", BUS=="usb", ATTRS{idvendor}=="0x046d", > > ATTRS{idProduct}=="0x082d", NAME="video0", MODE:="0660", RUN+="/bin/mknod > > /dev/video0 c 81 0" > > get rid of BUS construct there > [-- Attachment #2: Type: text/html, Size: 3401 bytes --] ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: adding a udev entry for a camera 2013-10-31 16:54 ` Edward Vidal @ 2013-10-31 17:08 ` Khem Raj 2013-10-31 23:08 ` Edward Vidal 0 siblings, 1 reply; 17+ messages in thread From: Khem Raj @ 2013-10-31 17:08 UTC (permalink / raw) To: Edward Vidal; +Cc: yocto@yoctoproject.org On Thu, Oct 31, 2013 at 9:54 AM, Edward Vidal <vidal.develone@gmail.com> wrote: > hello, > I removed the bus > udevadm test --action=add /usr/src/kernel/sysfs > > run_command: calling: test > adm_test: version 182 > This program is for debugging only, it does not run any program, > specified by a RUN key. It may show incorrect results, because > some values may be different, or not available at a simulation run. > > builtin_kmod_init: load module index > add_matching_files: unable to open '/var/run/udev/rules.d': No such file or > directory > parse_file: reading '/etc/udev/rules.d/10-c920.rules' as rules file > still no /dev/video0 > > cat /etc/udev/rules.d/10-c920.rules > SUBSYSTEM=="video4linux", ATTRS{idvendor}=="0x046d", > ATTRS{idProduct}=="0x082d", NAME="video0", MODE:="0660", RUN="/bin/mknod > /dev/video0 c 81 0" > still no /dev/video0 > The camera is working correctly on my fedora 18 x86_64. OK so atleast your rules file is correct syntax wise. Why not try the 3.8 kernel from meta-beagleboard ? > > Note: > * Before camera connected > ** After camera connected > Linux sim4.swbell.net 3.9.2-200.fc18.x86_64 #1 SMP Mon May 13 13:59:47 UTC > 2013 x86_64 x86_64 x86_64 GNU/Linux > > Module Size Used by > **snd_usb_audio 145223 1 > **snd_usbmidi_lib 24713 1 snd_usb_audio > **snd_rawmidi 29531 1 snd_usbmidi_lib > > *snd_hwdep 17650 1 snd_hda_codec > **snd_hwdep 17650 2 snd_usb_audio,snd_hda_codec > > *snd_seq_device 14136 1 snd_seq > **snd_seq_device 14136 2 snd_seq,snd_rawmidi > > *snd 79379 19 > snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_hda_codec,snd_hda_intel,snd_seq_device > **snd 79379 24 > snd_hda_codec_realtek,snd_usb_audio,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_usbmidi_lib,snd_hda_codec,snd_hda_intel,snd_seq_device > > *video 18991 0 > **video 18991 0 > > This is the beagleboard > lsmod > Module Size Used by > nls_iso8859_1 3673 1 > nls_cp437 5339 1 > I am going to be checking the video is a module or built into the kernel of > the > uname -a > Linux beagleboard 3.4.36-yocto-standard #1 Mon Oct 28 21:58:22 MDT 2013 > armv7l GNU/Linux > > Thanks > > > On Thu, Oct 31, 2013 at 10:23 AM, Khem Raj <raj.khem@gmail.com> wrote: >> >> On Thu, Oct 31, 2013 at 8:45 AM, Edward Vidal <vidal.develone@gmail.com> >> wrote: >> > >> > Do I add RUN+="/bin/mknod /dev/video0 c 81 0" see below new version of >> > 1--c920.rules >> > cat 10-c920.rules >> > SUBSYSTEM=="video4linux", BUS=="usb", ATTRS{idvendor}=="0x046d", >> > ATTRS{idProduct}=="0x082d", NAME="video0", MODE:="0660", >> > RUN+="/bin/mknod >> > /dev/video0 c 81 0" >> >> get rid of BUS construct there > > ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: adding a udev entry for a camera 2013-10-31 17:08 ` Khem Raj @ 2013-10-31 23:08 ` Edward Vidal 2013-10-31 23:27 ` Diego Sueiro 2013-10-31 23:34 ` Gary Thomas 0 siblings, 2 replies; 17+ messages in thread From: Edward Vidal @ 2013-10-31 23:08 UTC (permalink / raw) To: Khem Raj; +Cc: yocto@yoctoproject.org [-- Attachment #1: Type: text/plain, Size: 4604 bytes --] Hello, I had just recently built angstrom a few days ago. I tried the kernel that was built with 3.2.28 with the same results still not getting a /dev/video0. I did the following steps since angstrom uses meta-beagleboard, in hopes of getting a kernel 3.8 version. git commit -a git checkout -b wkg-angstrom-v2013.06-yocto1.4 origin/angstrom-v2013.06-yocto1.4 ./oebb.sh config beagleboard ./oebb.sh update . .oe/environment-angstrom-v2013.06 MACHINE=beagleboard bitbake console-image rm -rf build/tmp-angstrom_v2012_12-eglibc/ Even with meta-beagleboard at commit cdaa65dba20da97be7793404bcc90c498771fb04 Author: Koen Kooi <koen@dominion.thruhere.net> Date: Wed Oct 30 18:31:21 2013 +0100 contrib: bone-flash-tool: use --numeric-owner with tar to keep file ownershi Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Which is a dylan branch it still was building a 3.2.28 kernel git checkout -b 3.8 feb3ea180018d0f commit feb3ea180018d0f64f406f208827413b91122b07 Author: Koen Kooi <koen@dominion.thruhere.net> Date: Sun Oct 27 17:17:06 2013 +0100 linux-mainline 3.8: ADC and MIDI cape patches Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> It still tries to build a 3.2.28 kernel. What should I do to force it to build the 3.8 kernel? Any and all help will be appreciated. Thanks to all On Thu, Oct 31, 2013 at 11:08 AM, Khem Raj <raj.khem@gmail.com> wrote: > On Thu, Oct 31, 2013 at 9:54 AM, Edward Vidal <vidal.develone@gmail.com> > wrote: > > hello, > > I removed the bus > > udevadm test --action=add /usr/src/kernel/sysfs > > > > run_command: calling: test > > adm_test: version 182 > > This program is for debugging only, it does not run any program, > > specified by a RUN key. It may show incorrect results, because > > some values may be different, or not available at a simulation run. > > > > builtin_kmod_init: load module index > > add_matching_files: unable to open '/var/run/udev/rules.d': No such file > or > > directory > > parse_file: reading '/etc/udev/rules.d/10-c920.rules' as rules file > > still no /dev/video0 > > > > cat /etc/udev/rules.d/10-c920.rules > > SUBSYSTEM=="video4linux", ATTRS{idvendor}=="0x046d", > > ATTRS{idProduct}=="0x082d", NAME="video0", MODE:="0660", RUN="/bin/mknod > > /dev/video0 c 81 0" > > still no /dev/video0 > > The camera is working correctly on my fedora 18 x86_64. > > OK so atleast your rules file is correct syntax wise. Why not try the > 3.8 kernel from meta-beagleboard ? > > > > > Note: > > * Before camera connected > > ** After camera connected > > Linux sim4.swbell.net 3.9.2-200.fc18.x86_64 #1 SMP Mon May 13 13:59:47 > UTC > > 2013 x86_64 x86_64 x86_64 GNU/Linux > > > > Module Size Used by > > **snd_usb_audio 145223 1 > > **snd_usbmidi_lib 24713 1 snd_usb_audio > > **snd_rawmidi 29531 1 snd_usbmidi_lib > > > > *snd_hwdep 17650 1 snd_hda_codec > > **snd_hwdep 17650 2 snd_usb_audio,snd_hda_codec > > > > *snd_seq_device 14136 1 snd_seq > > **snd_seq_device 14136 2 snd_seq,snd_rawmidi > > > > *snd 79379 19 > > > snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_hda_codec,snd_hda_intel,snd_seq_device > > **snd 79379 24 > > > snd_hda_codec_realtek,snd_usb_audio,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_usbmidi_lib,snd_hda_codec,snd_hda_intel,snd_seq_device > > > > *video 18991 0 > > **video 18991 0 > > > > This is the beagleboard > > lsmod > > Module Size Used by > > nls_iso8859_1 3673 1 > > nls_cp437 5339 1 > > I am going to be checking the video is a module or built into the kernel > of > > the > > uname -a > > Linux beagleboard 3.4.36-yocto-standard #1 Mon Oct 28 21:58:22 MDT 2013 > > armv7l GNU/Linux > > > > Thanks > > > > > > On Thu, Oct 31, 2013 at 10:23 AM, Khem Raj <raj.khem@gmail.com> wrote: > >> > >> On Thu, Oct 31, 2013 at 8:45 AM, Edward Vidal <vidal.develone@gmail.com > > > >> wrote: > >> > > >> > Do I add RUN+="/bin/mknod /dev/video0 c 81 0" see below new version of > >> > 1--c920.rules > >> > cat 10-c920.rules > >> > SUBSYSTEM=="video4linux", BUS=="usb", ATTRS{idvendor}=="0x046d", > >> > ATTRS{idProduct}=="0x082d", NAME="video0", MODE:="0660", > >> > RUN+="/bin/mknod > >> > /dev/video0 c 81 0" > >> > >> get rid of BUS construct there > > > > > [-- Attachment #2: Type: text/html, Size: 6153 bytes --] ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: adding a udev entry for a camera 2013-10-31 23:08 ` Edward Vidal @ 2013-10-31 23:27 ` Diego Sueiro 2013-11-01 23:40 ` Edward Vidal 2013-10-31 23:34 ` Gary Thomas 1 sibling, 1 reply; 17+ messages in thread From: Diego Sueiro @ 2013-10-31 23:27 UTC (permalink / raw) To: Edward Vidal; +Cc: yocto@yoctoproject.org [-- Attachment #1: Type: text/plain, Size: 5160 bytes --] Edward, Is uvcvideo module loaded? What is lsmod and dmesg output when webcam is connected? Regards, -- *dS Diego Sueiro /*long live rock 'n roll*/ 2013/10/31 Edward Vidal <vidal.develone@gmail.com> > Hello, > I had just recently built angstrom a few days ago. I tried the kernel > that was built with 3.2.28 with the same results still not getting a > /dev/video0. > I did the following steps since angstrom uses meta-beagleboard, in hopes > of getting a kernel 3.8 version. > > git commit -a > git checkout -b wkg-angstrom-v2013.06-yocto1.4 > origin/angstrom-v2013.06-yocto1.4 > ./oebb.sh config beagleboard > ./oebb.sh update > > . .oe/environment-angstrom-v2013.06 > MACHINE=beagleboard bitbake console-image > rm -rf build/tmp-angstrom_v2012_12-eglibc/ > > Even with meta-beagleboard at > commit cdaa65dba20da97be7793404bcc90c498771fb04 > Author: Koen Kooi <koen@dominion.thruhere.net> > Date: Wed Oct 30 18:31:21 2013 +0100 > > contrib: bone-flash-tool: use --numeric-owner with tar to keep file > ownershi > > Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> > Which is a dylan branch it still was building a 3.2.28 kernel > > git checkout -b 3.8 feb3ea180018d0f > commit feb3ea180018d0f64f406f208827413b91122b07 > Author: Koen Kooi <koen@dominion.thruhere.net> > Date: Sun Oct 27 17:17:06 2013 +0100 > > linux-mainline 3.8: ADC and MIDI cape patches > > Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> > It still tries to build a 3.2.28 kernel. > What should I do to force it to build the 3.8 kernel? > > Any and all help will be appreciated. > Thanks to all > > > On Thu, Oct 31, 2013 at 11:08 AM, Khem Raj <raj.khem@gmail.com> wrote: > >> On Thu, Oct 31, 2013 at 9:54 AM, Edward Vidal <vidal.develone@gmail.com> >> wrote: >> > hello, >> > I removed the bus >> > udevadm test --action=add /usr/src/kernel/sysfs >> > >> > run_command: calling: test >> > adm_test: version 182 >> > This program is for debugging only, it does not run any program, >> > specified by a RUN key. It may show incorrect results, because >> > some values may be different, or not available at a simulation run. >> > >> > builtin_kmod_init: load module index >> > add_matching_files: unable to open '/var/run/udev/rules.d': No such >> file or >> > directory >> > parse_file: reading '/etc/udev/rules.d/10-c920.rules' as rules file >> > still no /dev/video0 >> > >> > cat /etc/udev/rules.d/10-c920.rules >> > SUBSYSTEM=="video4linux", ATTRS{idvendor}=="0x046d", >> > ATTRS{idProduct}=="0x082d", NAME="video0", MODE:="0660", RUN="/bin/mknod >> > /dev/video0 c 81 0" >> > still no /dev/video0 >> > The camera is working correctly on my fedora 18 x86_64. >> >> OK so atleast your rules file is correct syntax wise. Why not try the >> 3.8 kernel from meta-beagleboard ? >> >> > >> > Note: >> > * Before camera connected >> > ** After camera connected >> > Linux sim4.swbell.net 3.9.2-200.fc18.x86_64 #1 SMP Mon May 13 13:59:47 >> UTC >> > 2013 x86_64 x86_64 x86_64 GNU/Linux >> > >> > Module Size Used by >> > **snd_usb_audio 145223 1 >> > **snd_usbmidi_lib 24713 1 snd_usb_audio >> > **snd_rawmidi 29531 1 snd_usbmidi_lib >> > >> > *snd_hwdep 17650 1 snd_hda_codec >> > **snd_hwdep 17650 2 snd_usb_audio,snd_hda_codec >> > >> > *snd_seq_device 14136 1 snd_seq >> > **snd_seq_device 14136 2 snd_seq,snd_rawmidi >> > >> > *snd 79379 19 >> > >> snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_hda_codec,snd_hda_intel,snd_seq_device >> > **snd 79379 24 >> > >> snd_hda_codec_realtek,snd_usb_audio,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_usbmidi_lib,snd_hda_codec,snd_hda_intel,snd_seq_device >> > >> > *video 18991 0 >> > **video 18991 0 >> > >> > This is the beagleboard >> > lsmod >> > Module Size Used by >> > nls_iso8859_1 3673 1 >> > nls_cp437 5339 1 >> > I am going to be checking the video is a module or built into the >> kernel of >> > the >> > uname -a >> > Linux beagleboard 3.4.36-yocto-standard #1 Mon Oct 28 21:58:22 MDT 2013 >> > armv7l GNU/Linux >> > >> > Thanks >> > >> > >> > On Thu, Oct 31, 2013 at 10:23 AM, Khem Raj <raj.khem@gmail.com> wrote: >> >> >> >> On Thu, Oct 31, 2013 at 8:45 AM, Edward Vidal < >> vidal.develone@gmail.com> >> >> wrote: >> >> > >> >> > Do I add RUN+="/bin/mknod /dev/video0 c 81 0" see below new version >> of >> >> > 1--c920.rules >> >> > cat 10-c920.rules >> >> > SUBSYSTEM=="video4linux", BUS=="usb", ATTRS{idvendor}=="0x046d", >> >> > ATTRS{idProduct}=="0x082d", NAME="video0", MODE:="0660", >> >> > RUN+="/bin/mknod >> >> > /dev/video0 c 81 0" >> >> >> >> get rid of BUS construct there >> > >> > >> > > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > [-- Attachment #2: Type: text/html, Size: 7268 bytes --] ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: adding a udev entry for a camera 2013-10-31 23:27 ` Diego Sueiro @ 2013-11-01 23:40 ` Edward Vidal 0 siblings, 0 replies; 17+ messages in thread From: Edward Vidal @ 2013-11-01 23:40 UTC (permalink / raw) To: Diego Sueiro; +Cc: yocto@yoctoproject.org [-- Attachment #1.1: Type: text/plain, Size: 6567 bytes --] Hello All, Some progress getting the zImage to boot which was another problem before not getting /dev/video0. for the camera. I have been trying to get 3.10.11 from dora to boot. This kinda of works the following is in my uEnv.txt. vram=16M mpurate=1000 mmcboot=echo Booting from mmc ...; run mmcargs;mmc rescan ; fatload mmc 0:1 0x80300000 zImage; bootz 0x80300000 This will now boot with the command run mmcboot These are the files on my /run/media/vidal/BOOT 3.2.28 3.4.43 MLO u-boot.img uEnv.txt zImage. With 3.2.28 and 3.4.43 I was just switching uImage,.u-boot.bin & MLO worked okay with either kernel. With 3.10.11 I needed to replace uImage with zImage and MLO and u-boot.img This kernel is not working as well as 3.4.36 no lsusb root@beagleboard:~# lsusb --verbose unable to initialize libusb: -99 No /dev/video0. see attached. My next steps will be using the rootfs that was built with dora and 3.10.11 kernel, I will be adding the zImage-omap3-beagle-xm.dtb that was introduce with my dora. The attached file has the boot and dmesg. Any any all help will be welcomed.. Have a great weekend On Thu, Oct 31, 2013 at 5:27 PM, Diego Sueiro <diego.sueiro@gmail.com>wrote: > Edward, > > Is uvcvideo module loaded? > What is lsmod and dmesg output when webcam is connected? > > Regards, > > -- > *dS > Diego Sueiro > > /*long live rock 'n roll*/ > > > 2013/10/31 Edward Vidal <vidal.develone@gmail.com> > >> Hello, >> I had just recently built angstrom a few days ago. I tried the kernel >> that was built with 3.2.28 with the same results still not getting a >> /dev/video0. >> I did the following steps since angstrom uses meta-beagleboard, in hopes >> of getting a kernel 3.8 version. >> >> git commit -a >> git checkout -b wkg-angstrom-v2013.06-yocto1.4 >> origin/angstrom-v2013.06-yocto1.4 >> ./oebb.sh config beagleboard >> ./oebb.sh update >> >> . .oe/environment-angstrom-v2013.06 >> MACHINE=beagleboard bitbake console-image >> rm -rf build/tmp-angstrom_v2012_12-eglibc/ >> >> Even with meta-beagleboard at >> commit cdaa65dba20da97be7793404bcc90c498771fb04 >> Author: Koen Kooi <koen@dominion.thruhere.net> >> Date: Wed Oct 30 18:31:21 2013 +0100 >> >> contrib: bone-flash-tool: use --numeric-owner with tar to keep file >> ownershi >> >> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> >> Which is a dylan branch it still was building a 3.2.28 kernel >> >> git checkout -b 3.8 feb3ea180018d0f >> commit feb3ea180018d0f64f406f208827413b91122b07 >> Author: Koen Kooi <koen@dominion.thruhere.net> >> Date: Sun Oct 27 17:17:06 2013 +0100 >> >> linux-mainline 3.8: ADC and MIDI cape patches >> >> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> >> It still tries to build a 3.2.28 kernel. >> What should I do to force it to build the 3.8 kernel? >> >> Any and all help will be appreciated. >> Thanks to all >> >> >> On Thu, Oct 31, 2013 at 11:08 AM, Khem Raj <raj.khem@gmail.com> wrote: >> >>> On Thu, Oct 31, 2013 at 9:54 AM, Edward Vidal <vidal.develone@gmail.com> >>> wrote: >>> > hello, >>> > I removed the bus >>> > udevadm test --action=add /usr/src/kernel/sysfs >>> > >>> > run_command: calling: test >>> > adm_test: version 182 >>> > This program is for debugging only, it does not run any program, >>> > specified by a RUN key. It may show incorrect results, because >>> > some values may be different, or not available at a simulation run. >>> > >>> > builtin_kmod_init: load module index >>> > add_matching_files: unable to open '/var/run/udev/rules.d': No such >>> file or >>> > directory >>> > parse_file: reading '/etc/udev/rules.d/10-c920.rules' as rules file >>> > still no /dev/video0 >>> > >>> > cat /etc/udev/rules.d/10-c920.rules >>> > SUBSYSTEM=="video4linux", ATTRS{idvendor}=="0x046d", >>> > ATTRS{idProduct}=="0x082d", NAME="video0", MODE:="0660", >>> RUN="/bin/mknod >>> > /dev/video0 c 81 0" >>> > still no /dev/video0 >>> > The camera is working correctly on my fedora 18 x86_64. >>> >>> OK so atleast your rules file is correct syntax wise. Why not try the >>> 3.8 kernel from meta-beagleboard ? >>> >>> > >>> > Note: >>> > * Before camera connected >>> > ** After camera connected >>> > Linux sim4.swbell.net 3.9.2-200.fc18.x86_64 #1 SMP Mon May 13 >>> 13:59:47 UTC >>> > 2013 x86_64 x86_64 x86_64 GNU/Linux >>> > >>> > Module Size Used by >>> > **snd_usb_audio 145223 1 >>> > **snd_usbmidi_lib 24713 1 snd_usb_audio >>> > **snd_rawmidi 29531 1 snd_usbmidi_lib >>> > >>> > *snd_hwdep 17650 1 snd_hda_codec >>> > **snd_hwdep 17650 2 snd_usb_audio,snd_hda_codec >>> > >>> > *snd_seq_device 14136 1 snd_seq >>> > **snd_seq_device 14136 2 snd_seq,snd_rawmidi >>> > >>> > *snd 79379 19 >>> > >>> snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_hda_codec,snd_hda_intel,snd_seq_device >>> > **snd 79379 24 >>> > >>> snd_hda_codec_realtek,snd_usb_audio,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_usbmidi_lib,snd_hda_codec,snd_hda_intel,snd_seq_device >>> > >>> > *video 18991 0 >>> > **video 18991 0 >>> > >>> > This is the beagleboard >>> > lsmod >>> > Module Size Used by >>> > nls_iso8859_1 3673 1 >>> > nls_cp437 5339 1 >>> > I am going to be checking the video is a module or built into the >>> kernel of >>> > the >>> > uname -a >>> > Linux beagleboard 3.4.36-yocto-standard #1 Mon Oct 28 21:58:22 MDT 2013 >>> > armv7l GNU/Linux >>> > >>> > Thanks >>> > >>> > >>> > On Thu, Oct 31, 2013 at 10:23 AM, Khem Raj <raj.khem@gmail.com> wrote: >>> >> >>> >> On Thu, Oct 31, 2013 at 8:45 AM, Edward Vidal < >>> vidal.develone@gmail.com> >>> >> wrote: >>> >> > >>> >> > Do I add RUN+="/bin/mknod /dev/video0 c 81 0" see below new version >>> of >>> >> > 1--c920.rules >>> >> > cat 10-c920.rules >>> >> > SUBSYSTEM=="video4linux", BUS=="usb", ATTRS{idvendor}=="0x046d", >>> >> > ATTRS{idProduct}=="0x082d", NAME="video0", MODE:="0660", >>> >> > RUN+="/bin/mknod >>> >> > /dev/video0 c 81 0" >>> >> >>> >> get rid of BUS construct there >>> > >>> > >>> >> >> >> _______________________________________________ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto >> >> > [-- Attachment #1.2: Type: text/html, Size: 9125 bytes --] [-- Attachment #2: capture.txt --] [-- Type: text/plain, Size: 25114 bytes --] * - * Qodem 0.1.2 Capture Generated Fri, 01 Nov 2013 17:14:29 -0600 BEGIN * - * U-Boot SPL 2013.07 (Oct 31 2013 - 23:25:55) OMAP SD/MMC: 0 reading u-boot.img reading u-boot.img U-Boot 2013.07 (Oct 31 2013 - 23:25:55) OMAP3630/3730-GP ES1.2, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz OMAP3 Beagle board + LPDDR/NAND I2C: ready DRAM: 512 MiB NAND: 0 MiB MMC: OMAP SD/MMC: 0 *** Warning - readenv() failed, using default environment In: serial Out: serial Err: serial Beagle xM Rev C No EEPROM on expansion board Die ID #4fe800029ff80000016071640e01d006 musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 1.800 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Peripheral mode controller at 480ab000 using PIO, IRQ 0 Net: usb_ether Hit any key to stop autoboot: 3 2 1 0 mmc0 is current device gpio: pin 173 (gpio 173) value is 0 gpio: pin 4 (gpio 4) value is 0 SD/MMC found on device 0 reading uEnv.txt 135 bytes read in 4 ms (32.2 KiB/s) Loaded environment from uEnv.txt Importing environment from mmc ... ** File not found /boot/uImage ** Booting from nand ... no devices available Wrong Image Format for bootm command ERROR: can't get kernel image! OMAP3 beagleboard.org # run mmcboot Booting from mmc ... reading zImage 4642776 bytes read in 288 ms (15.4 MiB/s) Kernel image @ 0x80300000 [ 0x000000 - 0x46d7d8 ] Starting kernel ... Booting Linux on physical CPU 0x0 Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Initializing cgroup subsys cpuacct Linux version 3.10.11-yocto-standard (vidal@ws009.swbell.net) (gcc version 4.8.1 (GCC) ) #1 Thu Oct 31 22:07:26 MDT 2013 CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache Machine: OMAP3 Beagle Board Memory policy: ECC disabled, Data cache writeback CPU: All CPU(s) started in SVC mode. OMAP3630 ES1.2 (l2cache iva sgx neon isp 192mhz_clk ) Built 1 zonelists in Zone order, mobility grouping on. Total pages: 129792 Kernel command line: console=ttyO2,115200n8 mpurate=1000 buddy=none camera=none vram=16M omapfb.mode=dvi:640x480MR-16@60 omapdss.def_disp=dvi root=/dev/mmcblk0p 2 rw rootfstype=ext3 rootwait PID hash table entries: 2048 (order: 1, 8192 bytes) Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) allocated 1048576 bytes of page_cgroup please try 'cgroup_disable=memory' option if you don't want memory cgroups Memory: 511MB = 511MB total Memory: 506796k/506796k available, 17492k reserved, 0K highmem Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) vmalloc : 0xe0800000 - 0xff000000 ( 488 MB) lowmem : 0xc0000000 - 0xe0000000 ( 512 MB) pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) modules : 0xbf000000 - 0xbfe00000 ( 14 MB) .text : 0xc0008000 - 0xc08d1880 (8999 kB) .init : 0xc08d2000 - 0xc09542b4 ( 521 kB) .data : 0xc0956000 - 0xc09eafa0 ( 596 kB) .bss : 0xc09eafa0 - 0xc0aa4360 ( 741 kB) SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 NR_IRQS:16 nr_irqs:16 16 IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts Total of 96 interrupts on 1 active controller Clocking rate (Crystal/Core/MPU): 26.0/400/600 MHz OMAP clockevent source: timer12 at 32768 Hz sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms OMAP clocksource: 32k_counter at 32768 Hz Console: colour dummy device 80x30 Calibrating delay loop... 329.31 BogoMIPS (lpj=1646592) pid_max: default: 32768 minimum: 301 Security Framework initialized Mount-cache hash table entries: 512 Initializing cgroup subsys debug Initializing cgroup subsys memory Initializing cgroup subsys devices Initializing cgroup subsys freezer Initializing cgroup subsys net_cls Initializing cgroup subsys blkio CPU: Testing write buffer coherency: ok ftrace: allocating 24224 entries in 72 pages Setting up static identity map for 0xc060bdd0 - 0xc060be28 devtmpfs: initialized xor: measuring software checksum speed arm4regs : 622.800 MB/sec 8regs : 459.200 MB/sec 32regs : 598.800 MB/sec xor: using function: arm4regs (622.800 MB/sec) pinctrl core: initialized pinctrl subsystem regulator-dummy: no parameters NET: Registered protocol family 16 DMA: preallocated 256 KiB pool for atomic coherent allocations omap-gpmc omap-gpmc: GPMC revision 5.0 OMAP GPIO hardware version 2.5 omap_mux_init: Add partition: #1: core, flags: 4 OMAP3 Beagle Rev: xM C omap_mux_get_by_name: Could not find signal uart4_rx.uart4_rx Reprogramming SDRC clock to 400000000 Hz hw-breakpoint: debug architecture 0x4 unsupported. omap-mcbsp.2: alias fck already exists omap-mcbsp.3: alias fck already exists Switched to new clocking rate (Crystal/Core/MPU): 26.0/400/600 MHz OMAP DMA hardware revision 5.0 arm-pmu: alias fck already exists bio: create slab <bio-0> at 0 raid6: int32x1 81 MB/s raid6: int32x2 98 MB/s raid6: int32x4 82 MB/s raid6: int32x8 84 MB/s raid6: using algorithm int32x2 (98 MB/s) raid6: using intx1 recovery algorithm omap-dma-engine omap-dma-engine: OMAP DMA engine driver SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb twl 1-0048: PIH (irq 23) chaining IRQs 338..346 twl 1-0048: power (irq 343) chaining IRQs 346..353 twl4030_gpio twl4030_gpio: gpio (irq 338) chaining IRQs 354..371 hsusb2_reset: 3300 mV hsusb2_vcc: 3300 mV vdd_mpu_iva: 600 <--> 1450 mV normal vdd_core: 600 <--> 1450 mV normal VMMC1: 1850 <--> 3150 mV at 3150 mV normal standby VDAC: 1800 mV normal standby VDVI: 1800 mV normal standby VSIM: 1800 <--> 3000 mV at 1800 mV normal standby omap_i2c omap_i2c.1: bus 1 rev4.4 at 2600 kHz omap_i2c omap_i2c.3: bus 3 rev4.4 at 100 kHz Advanced Linux Sound Architecture Driver Initialized. cfg80211: Calling CRDA to update world regulatory domain Switching to clocksource 32k_counter NET: Registered protocol family 2 TCP established hash table entries: 4096 (order: 3, 32768 bytes) TCP bind hash table entries: 4096 (order: 2, 16384 bytes) TCP: Hash tables configured (established 4096 bind 4096) TCP: reno registered UDP hash table entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. CPU PMU: probing PMU on CPU 0 hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available NFS: Registering the id_resolver key type Key type id_resolver registered Key type id_legacy registered bio: create slab <bio-1> at 1 Btrfs loaded aufs 3.10-20130819 msgmni has been set to 989 Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) OMAP DSS rev 2.0 omapfb omapfb: no driver for display: dvi omapfb omapfb: failed to find default display omapfb omapfb: failed to setup omapfb omapfb: probe of omapfb failed with error -22 omap_uart.0: ttyO0 at MMIO 0x4806a000 (irq = 88) is a OMAP UART0 omap_uart.1: ttyO1 at MMIO 0x4806c000 (irq = 89) is a OMAP UART1 omap_uart.2: ttyO2 at MMIO 0x49020000 (irq = 90) is a OMAP UART2 console [ttyO2] enabled omap_uart.3: ttyO3 at MMIO 0x49042000 (irq = 96) is a OMAP UART3 brd: module loaded Trying ONFI probe in 16 bits mode, aborting ! No NAND device found No NAND device found usbcore: registered new interface driver kaweth pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB Ethernet driver usbcore: registered new interface driver pegasus usbcore: registered new interface driver rtl8150 usbcore: registered new interface driver asix usbcore: registered new interface driver ax88179_178a usbcore: registered new interface driver cdc_ether usbcore: registered new interface driver dm9601 usbcore: registered new interface driver smsc75xx usbcore: registered new interface driver smsc95xx usbcore: registered new interface driver net1080 usbcore: registered new interface driver cdc_subset usbcore: registered new interface driver zaurus usbcore: registered new interface driver MOSCHIP usb-ethernet driver usbcore: registered new interface driver int51x1 usbcore: registered new interface driver cdc_ncm ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver ehci-omap: OMAP-EHCI Host Controller driver ehci-omap ehci-omap.0: Can't get PHY device for port 1: -6 usbcore: registered new interface driver usb-storage musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -6 mousedev: PS/2 mouse device common for all mice twl_rtc twl_rtc: Enabling TWL-RTC twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0 omap_wdt: OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec cpuidle: using governor ladder cpuidle: using governor menu omap-dma-engine omap-dma-engine: allocating channel for 62 omap-dma-engine omap-dma-engine: allocating channel for 61 usbcore: registered new interface driver usbhid usbhid: USB HID core driver omap-twl4030 omap-twl4030: twl4030-hifi <-> omap-mcbsp.2 mapping ok oprofile: using arm/armv7 u32 classifier Actions configured TCP: cubic registered NET: Registered protocol family 10 sit: IPv6 over IPv4 tunneling driver NET: Registered protocol family 17 Key type dns_resolver registered VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3 ThumbEE CPU extension supported. VDVI: incomplete constraints, leaving on VDAC: incomplete constraints, leaving on console [netcon0] enabled netconsole: network logging started twl_rtc twl_rtc: setting system clock to 2013-10-29 16:07:06 UTC (1383062826) ALSA device list: #0: omap3beagle Waiting for root device /dev/mmcblk0p2... mmc0: host does not support reading read-only switch. assuming write-enable. mmc0: new high speed SDHC card at address 1234 mmcblk0: mmc0:1234 SA04G 3.67 GiB mmcblk0: p1 p2 kjournald starting. Commit interval 5 seconds EXT3-fs (mmcblk0p2): using internal journal EXT3-fs (mmcblk0p2): recovery complete EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode VFS: Mounted root (ext3 filesystem) on device 179:2. devtmpfs: mounted Freeing unused kernel memory: 520K (c08d2000 - c0954000) INIT: version 2.88 booting Error opening /dev/fb0: No such file or directory Starting udev udevd[76]: starting version 182 FAT-fs (mmcblk0p1): codepage cp437 not found Starting Bootlog daemon: bootlogd. ALSA: Restoring mixer settings... Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device ifconfig: SIOCGIFFLAGS: No such device Starting rpcbind daemon...done. INIT: Entering runlevel: 5 Starting Xserver open /dev/fb0: No such file or directory Starting system message bus: dbus. Starting Connection Manager Starting OpenBSD Secure Shell server: sshd done. Starting advanced power management daemon: apmd. apmd[546]: apmd 3.2.1 interfacing with apm driver 1.13 and APM BIOS 1.2 Starting Distributed Compiler Daemon: distcc. Starting syslogd/klogd: done * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon [ ok ] Starting Telephony daemon Starting Linux NFC daemon ps: invalid option -- 'a' BusyBox v1.20.2 (2013-10-28 22:22:35 MDT) multi-call binary. Usage: ps cups: started scheduler. Starting OProfileUI server Starting tcf-agent: OK Stopping Bootlog daemon: bootlogd. Poky 9.0 (Yocto Project 1.4 Reference Distro) 1.4.1 beagleboard ttyO2 beagleboard login: root root@beagleboard:~# uname -a Linux beagleboard 3.10.11-yocto-standard #1 Thu Oct 31 22:07:26 MDT 2013 armv7l GNU/Linux root@beagleboard:~# lsmod Module Size Used by root@beagleboard:~# ls /dev/vv * /dev/vcs /dev/vcs1 /dev/vcs2/dev/vcsa /dev/vcsa1 /dev/vcsa2 root@beagleboard:~# ls ess /etc/udev/rules.d/10-c920.rules SUBSYSTEM=="video4linux", ATTRS{idvendor}=="0x046d", ATTRS{idProduct}=="0x082d" , NAME="video0", MODE:="0660", RUN="/bin/mknod /dev/video0 c 81 0" /etc/udev/rules.d/10-c920.rules (END)root@beagleboard:~# demesg -c -sh: demesg: command not found root@beagleboard:~# de mesg -c [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.10.11-yocto-standard (vidal@ws009.swbell.net) (gc c version 4.8.1 (GCC) ) #1 Thu Oct 31 22:07:26 MDT 2013 [ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instructio n cache [ 0.000000] Machine: OMAP3 Beagle Board [ 0.000000] Memory policy: ECC disabled, Data cache writeback [ 0.000000] On node 0 totalpages: 130816 [ 0.000000] free_area_init_node: node 0, pgdat c09e3ddc, node_mem_map c0aa500 0 [ 0.000000] Normal zone: 1024 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 130816 pages, LIFO batch:31 [ 0.000000] CPU: All CPU(s) started in SVC mode. [ 0.000000] OMAP3630 ES1.2 (l2cache iva sgx neon isp 192mhz_clk ) [ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 [ 0.000000] pcpu-alloc: [0] 0 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pag es: 129792 [ 0.000000] Kernel command line: console=ttyO2,115200n8 mpurate=1000 buddy=no ne camera=none vram=16M omapfb.mode=dvi:640x480MR-16@60 omapdss.def_disp=dvi roo t=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait [ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [ 0.000000] allocated 1048576 bytes of page_cgroup [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memor y cgroups [ 0.000000] Memory: 511MB = 511MB total [ 0.000000] Memory: 506796k/506796k available, 17492k reserved, 0K highmem [ 0.000000] Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) vmalloc : 0xe0800000 - 0xff000000 ( 488 MB) lowmem : 0xc0000000 - 0xe0000000 ( 512 MB) pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) modules : 0xbf000000 - 0xbfe00000 ( 14 MB) .text : 0xc0008000 - 0xc08d1880 (8999 kB) .init : 0xc08d2000 - 0xc09542b4 ( 521 kB) .data : 0xc0956000 - 0xc09eafa0 ( 596 kB) .bss : 0xc09eafa0 - 0xc0aa4360 ( 741 kB) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 [ 0.000000] NR_IRQS:16 nr_irqs:16 16 [ 0.000000] IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupt s [ 0.000000] Total of 96 interrupts on 1 active controller [ 0.000000] Clocking rate (Crystal/Core/MPU): 26.0/400/600 MHz [ 0.000000] OMAP clockevent source: timer12 at 32768 Hz [ 0.000000] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 13 1071999ms [ 0.000000] OMAP clocksource: 32k_counter at 32768 Hz [ 0.000000] Console: colour dummy device 80x30 [ 0.000183] Calibrating delay loop... 329.31 BogoMIPS (lpj=1646592) [ 0.041290] pid_max: default: 32768 minimum: 301 [ 0.041442] Security Framework initialized [ 0.041717] Mount-cache hash table entries: 512 [ 0.042419] Initializing cgroup subsys debug [ 0.042449] Initializing cgroup subsys memory [ 0.042480] Initializing cgroup subsys devices [ 0.042480] Initializing cgroup subsys freezer [ 0.042510] Initializing cgroup subsys net_cls [ 0.042510] Initializing cgroup subsys blkio [ 0.042572] CPU: Testing write buffer coherency: ok [ 0.042602] ftrace: allocating 24224 entries in 72 pages [ 0.139434] Setting up static identity map for 0xc060bdd0 - 0xc060be28 [ 0.146514] devtmpfs: initialized [ 0.212036] xor: measuring software checksum speed [ 0.290191] arm4regs : 622.800 MB/sec [ 0.373626] 8regs : 459.200 MB/sec [ 0.457092] 32regs : 598.800 MB/sec [ 0.457092] xor: using function: arm4regs (622.800 MB/sec) [ 0.457122] pinctrl core: initialized pinctrl subsystem [ 0.457580] regulator-dummy: no parameters [ 0.457946] NET: Registered protocol family 16 [ 0.458709] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.459075] omap-gpmc omap-gpmc: GPMC revision 5.0 [ 0.460845] OMAP GPIO hardware version 2.5 [ 0.464263] omap_mux_init: Add partition: #1: core, flags: 4 [ 0.465545] OMAP3 Beagle Rev: xM C [ 0.468383] omap_mux_get_by_name: Could not find signal uart4_rx.uart4_rx [ 0.474517] Reprogramming SDRC clock to 400000000 Hz [ 0.476226] hw-breakpoint: debug architecture 0x4 unsupported. [ 0.479339] omap-mcbsp.2: alias fck already exists [ 0.479583] omap-mcbsp.3: alias fck already exists [ 0.480438] Switched to new clocking rate (Crystal/Core/MPU): 26.0/400/600 MH z [ 0.480621] OMAP DMA hardware revision 5.0 [ 0.481872] arm-pmu: alias fck already exists [ 0.488677] bio: create slab <bio-0> at 0 [ 0.624084] raid6: int32x1 81 MB/s [ 0.766235] raid6: int32x2 98 MB/s [ 0.908264] raid6: int32x4 82 MB/s [ 1.049652] raid6: int32x8 84 MB/s [ 1.049652] raid6: using algorithm int32x2 (98 MB/s) [ 1.049682] raid6: using intx1 recovery algorithm [ 1.063537] omap-dma-engine omap-dma-engine: OMAP DMA engine driver [ 1.064270] SCSI subsystem initialized [ 1.064544] usbcore: registered new interface driver usbfs [ 1.064605] usbcore: registered new interface driver hub [ 1.064971] usbcore: registered new device driver usb [ 1.069366] twl 1-0048: PIH (irq 23) chaining IRQs 338..346 [ 1.069488] twl 1-0048: power (irq 343) chaining IRQs 346..353 [ 1.070404] twl4030_gpio twl4030_gpio: gpio (irq 338) chaining IRQs 354..371 [ 1.071319] hsusb2_reset: 3300 mV [ 1.072052] hsusb2_vcc: 3300 mV [ 1.072601] vdd_mpu_iva: 600 <--> 1450 mV normal [ 1.072998] vdd_core: 600 <--> 1450 mV normal [ 1.073516] VMMC1: 1850 <--> 3150 mV at 3150 mV normal standby [ 1.074005] VDAC: 1800 mV normal standby [ 1.074523] VDVI: 1800 mV normal standby [ 1.075195] VSIM: 1800 <--> 3000 mV at 1800 mV normal standby [ 1.075500] omap_i2c omap_i2c.1: bus 1 rev4.4 at 2600 kHz [ 1.076080] omap_i2c omap_i2c.3: bus 3 rev4.4 at 100 kHz [ 1.076477] Advanced Linux Sound Architecture Driver Initialized. [ 1.077484] cfg80211: Calling CRDA to update world regulatory domain [ 1.079040] Switching to clocksource 32k_counter [ 1.137634] NET: Registered protocol family 2 [ 1.138397] TCP established hash table entries: 4096 (order: 3, 32768 bytes) [ 1.138488] TCP bind hash table entries: 4096 (order: 2, 16384 bytes) [ 1.138549] TCP: Hash tables configured (established 4096 bind 4096) [ 1.138641] TCP: reno registered [ 1.138641] UDP hash table entries: 256 (order: 0, 4096 bytes) [ 1.138671] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [ 1.139038] NET: Registered protocol family 1 [ 1.139526] RPC: Registered named UNIX socket transport module. [ 1.139556] RPC: Registered udp transport module. [ 1.139556] RPC: Registered tcp transport module. [ 1.139556] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 1.141174] CPU PMU: probing PMU on CPU 0 [ 1.141204] hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counter s available [ 1.363128] NFS: Registering the id_resolver key type [ 1.363220] Key type id_resolver registered [ 1.363220] Key type id_legacy registered [ 1.364654] bio: create slab <bio-1> at 1 [ 1.365844] Btrfs loaded [ 1.366485] aufs 3.10-20130819 [ 1.366516] msgmni has been set to 989 [ 1.368499] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 2 52) [ 1.368530] io scheduler noop registered [ 1.368530] io scheduler deadline registered [ 1.368713] io scheduler cfq registered (default) [ 1.369476] OMAP DSS rev 2.0 [ 1.371398] omapfb omapfb: no driver for display: dvi [ 1.371429] omapfb omapfb: failed to find default display [ 1.371582] omapfb omapfb: failed to setup omapfb [ 1.371582] omapfb: probe of omapfb failed with error -22 [ 1.441040] omap_uart.0: ttyO0 at MMIO 0x4806a000 (irq = 88) is a OMAP UART0 [ 1.441619] omap_uart.1: ttyO1 at MMIO 0x4806c000 (irq = 89) is a OMAP UART1 [ 1.442199] omap_uart.2: ttyO2 at MMIO 0x49020000 (irq = 90) is a OMAP UART2 [ 2.013854] console [ttyO2] enabled [ 2.016723] omap_uart.3: ttyO3 at MMIO 0x49042000 (irq = 96) is a OMAP UART3 [ 2.031097] brd: module loaded [ 2.034393] Trying ONFI probe in 16 bits mode, aborting ! [ 2.038726] No NAND device found [ 2.040985] No NAND device found [ 2.044586] usbcore: registered new interface driver kaweth [ 2.049133] pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB Ethernet dri ver [ 2.055603] usbcore: registered new interface driver pegasus [ 2.060272] usbcore: registered new interface driver rtl8150 [ 2.064910] usbcore: registered new interface driver asix [ 2.069274] usbcore: registered new interface driver ax88179_178a [ 2.074340] usbcore: registered new interface driver cdc_ether [ 2.079193] usbcore: registered new interface driver dm9601 [ 2.083740] usbcore: registered new interface driver smsc75xx [ 2.088500] usbcore: registered new interface driver smsc95xx [ 2.093231] usbcore: registered new interface driver net1080 [ 2.097869] usbcore: registered new interface driver cdc_subset [ 2.102783] usbcore: registered new interface driver zaurus [ 2.107330] usbcore: registered new interface driver MOSCHIP usb-ethernet dri ver [ 2.113861] usbcore: registered new interface driver int51x1 [ 2.118499] usbcore: registered new interface driver cdc_ncm [ 2.123107] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 2.128601] ehci-omap: OMAP-EHCI Host Controller driver [ 2.132873] ehci-omap ehci-omap.0: Can't get PHY device for port 1: -6 [ 2.138519] usbcore: registered new interface driver usb-storage [ 2.143585] musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with stat us -6 [ 2.150848] mousedev: PS/2 mouse device common for all mice [ 2.156280] twl_rtc twl_rtc: Enabling TWL-RTC [ 2.161926] twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0 [ 2.168304] omap_wdt: OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec [ 2.174285] cpuidle: using governor ladder [ 2.177215] cpuidle: using governor menu [ 2.180816] omap-dma-engine omap-dma-engine: allocating channel for 62 [ 2.186340] omap-dma-engine omap-dma-engine: allocating channel for 61 [ 2.559509] usbcore: registered new interface driver usbhid [ 2.563995] usbhid: USB HID core driver [ 2.652954] omap-twl4030 omap-twl4030: twl4030-hifi <-> omap-mcbsp.2 mapping ok [ 2.661285] oprofile: using arm/armv7 [ 2.663909] u32 classifier [ 2.665374] Actions configured [ 2.667968] TCP: cubic registered [ 2.670928] NET: Registered protocol family 10 [ 2.675109] sit: IPv6 over IPv4 tunneling driver [ 2.679473] NET: Registered protocol family 17 [ 2.682922] Key type dns_resolver registered [ 2.686340] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3 [ 2.697113] ThumbEE CPU extension supported. [ 2.701171] VDVI: incomplete constraints, leaving on [ 2.705200] VDAC: incomplete constraints, leaving on [ 2.709686] console [netcon0] enabled [ 2.712188] netconsole: network logging started [ 2.716522] twl_rtc twl_rtc: setting system clock to 2013-10-29 16:07:06 UTC (1383062826) [ 2.724182] ALSA device list: [ 2.725921] #0: omap3beagle [ 2.728332] Waiting for root device /dev/mmcblk0p2... [ 2.737670] mmc0: host does not support reading read-only switch. assuming wr ite-enable. [ 2.747100] mmc0: new high speed SDHC card at address 1234 [ 2.752044] mmcblk0: mmc0:1234 SA04G 3.67 GiB [ 2.757781] mmcblk0: p1 p2 [ 13.626098] kjournald starting. Commit interval 5 seconds [ 14.269042] EXT3-fs (mmcblk0p2): using internal journal [ 14.281738] EXT3-fs (mmcblk0p2): recovery complete [ 14.285400] EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode [ 14.291351] VFS: Mounted root (ext3 filesystem) on device 179:2. [ 14.301971] devtmpfs: mounted [ 14.304748] Freeing unused kernel memory: 520K (c08d2000 - c0954000) [ 15.208465] udevd[76]: starting version 182 [ 18.681427] FAT-fs (mmcblk0p1): codepage cp437 not found root@beagleboard:~# dmesg -c root@beagleboard:~# dmesg root@beagleboard:~# lsusb --verbose unable to initialize libusb: -99 root@beagleboard:~# lsusb unable to initialize libusb: -99 root@beagleboard:~# * - * Qodem 0.1.2 Capture Generated Fri, 01 Nov 2013 17:18:27 -0600 END * - * ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: adding a udev entry for a camera 2013-10-31 23:08 ` Edward Vidal 2013-10-31 23:27 ` Diego Sueiro @ 2013-10-31 23:34 ` Gary Thomas 1 sibling, 0 replies; 17+ messages in thread From: Gary Thomas @ 2013-10-31 23:34 UTC (permalink / raw) To: yocto On 2013-10-31 17:08, Edward Vidal wrote: > Hello, > I had just recently built angstrom a few days ago. I tried the kernel that was built with 3.2.28 with the same results still not getting a /dev/video0. > I did the following steps since angstrom uses meta-beagleboard, in hopes of getting a kernel 3.8 version. > > git commit -a > git checkout -b wkg-angstrom-v2013.06-yocto1.4 origin/angstrom-v2013.06-yocto1.4 > ./oebb.sh config beagleboard > ./oebb.sh update > > . .oe/environment-angstrom-v2013.06 > MACHINE=beagleboard bitbake console-image > rm -rf build/tmp-angstrom_v2012_12-eglibc/ > > Even with meta-beagleboard at > commit cdaa65dba20da97be7793404bcc90c498771fb04 > Author: Koen Kooi <koen@dominion.thruhere.net <mailto:koen@dominion.thruhere.net>> > Date: Wed Oct 30 18:31:21 2013 +0100 > > contrib: bone-flash-tool: use --numeric-owner with tar to keep file ownershi > > Signed-off-by: Koen Kooi <koen@dominion.thruhere.net <mailto:koen@dominion.thruhere.net>> > Which is a dylan branch it still was building a 3.2.28 kernel > > git checkout -b 3.8 feb3ea180018d0f > commit feb3ea180018d0f64f406f208827413b91122b07 > Author: Koen Kooi <koen@dominion.thruhere.net <mailto:koen@dominion.thruhere.net>> > Date: Sun Oct 27 17:17:06 2013 +0100 > > linux-mainline 3.8: ADC and MIDI cape patches > > Signed-off-by: Koen Kooi <koen@dominion.thruhere.net <mailto:koen@dominion.thruhere.net>> > It still tries to build a 3.2.28 kernel. > What should I do to force it to build the 3.8 kernel? Both meta-beagleboard and meta-ti seem to be stuck at 3.2.28 for the BeagleBoard. Not unlike my cell phone, old devices get left in the dust (even if they are only weeks old...)! You might try building with meta-yocto-bsp as it will build 3.10+ > > Any and all help will be appreciated. > Thanks to all > > > On Thu, Oct 31, 2013 at 11:08 AM, Khem Raj <raj.khem@gmail.com <mailto:raj.khem@gmail.com>> wrote: > > On Thu, Oct 31, 2013 at 9:54 AM, Edward Vidal <vidal.develone@gmail.com <mailto:vidal.develone@gmail.com>> wrote: > > hello, > > I removed the bus > > udevadm test --action=add /usr/src/kernel/sysfs > > > > run_command: calling: test > > adm_test: version 182 > > This program is for debugging only, it does not run any program, > > specified by a RUN key. It may show incorrect results, because > > some values may be different, or not available at a simulation run. > > > > builtin_kmod_init: load module index > > add_matching_files: unable to open '/var/run/udev/rules.d': No such file or > > directory > > parse_file: reading '/etc/udev/rules.d/10-c920.rules' as rules file > > still no /dev/video0 > > > > cat /etc/udev/rules.d/10-c920.rules > > SUBSYSTEM=="video4linux", ATTRS{idvendor}=="0x046d", > > ATTRS{idProduct}=="0x082d", NAME="video0", MODE:="0660", RUN="/bin/mknod > > /dev/video0 c 81 0" > > still no /dev/video0 > > The camera is working correctly on my fedora 18 x86_64. > > OK so atleast your rules file is correct syntax wise. Why not try the > 3.8 kernel from meta-beagleboard ? > > > > > Note: > > * Before camera connected > > ** After camera connected > > Linuxsim4.swbell.net <http://sim4.swbell.net> 3.9.2-200.fc18.x86_64 #1 SMP Mon May 13 13:59:47 UTC > > 2013 x86_64 x86_64 x86_64 GNU/Linux > > > > Module Size Used by > > **snd_usb_audio 145223 1 > > **snd_usbmidi_lib 24713 1 snd_usb_audio > > **snd_rawmidi 29531 1 snd_usbmidi_lib > > > > *snd_hwdep 17650 1 snd_hda_codec > > **snd_hwdep 17650 2 snd_usb_audio,snd_hda_codec > > > > *snd_seq_device 14136 1 snd_seq > > **snd_seq_device 14136 2 snd_seq,snd_rawmidi > > > > *snd 79379 19 > > snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_hda_codec,snd_hda_intel,snd_seq_device > > **snd 79379 24 > > snd_hda_codec_realtek,snd_usb_audio,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_usbmidi_lib,snd_hda_codec,snd_hda_intel,snd_seq_device > > > > *video 18991 0 > > **video 18991 0 > > > > This is the beagleboard > > lsmod > > Module Size Used by > > nls_iso8859_1 3673 1 > > nls_cp437 5339 1 > > I am going to be checking the video is a module or built into the kernel of > > the > > uname -a > > Linux beagleboard 3.4.36-yocto-standard #1 Mon Oct 28 21:58:22 MDT 2013 > > armv7l GNU/Linux > > > > Thanks > > > > > > On Thu, Oct 31, 2013 at 10:23 AM, Khem Raj <raj.khem@gmail.com <mailto:raj.khem@gmail.com>> wrote: > >> > >> On Thu, Oct 31, 2013 at 8:45 AM, Edward Vidal <vidal.develone@gmail.com <mailto:vidal.develone@gmail.com>> > >> wrote: > >> > > >> > Do I add RUN+="/bin/mknod /dev/video0 c 81 0" see below new version of > >> > 1--c920.rules > >> > cat 10-c920.rules > >> > SUBSYSTEM=="video4linux", BUS=="usb", ATTRS{idvendor}=="0x046d", > >> > ATTRS{idProduct}=="0x082d", NAME="video0", MODE:="0660", > >> > RUN+="/bin/mknod > >> > /dev/video0 c 81 0" > >> > >> get rid of BUS construct there > > > > > > > > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ ^ permalink raw reply [flat|nested] 17+ messages in thread
end of thread, other threads:[~2013-11-01 23:40 UTC | newest] Thread overview: 17+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2013-10-30 20:51 adding a udev entry for a camera Edward Vidal 2013-10-30 23:58 ` Khem Raj 2013-10-31 1:12 ` Edward Vidal 2013-10-31 10:27 ` Gary Thomas 2013-10-31 10:58 ` Diego Sueiro 2013-10-31 14:41 ` Khem Raj 2013-10-31 15:45 ` Edward Vidal 2013-10-31 15:55 ` Gary Thomas 2013-10-31 16:20 ` Khem Raj 2013-10-31 16:34 ` Gary Thomas 2013-10-31 16:23 ` Khem Raj 2013-10-31 16:54 ` Edward Vidal 2013-10-31 17:08 ` Khem Raj 2013-10-31 23:08 ` Edward Vidal 2013-10-31 23:27 ` Diego Sueiro 2013-11-01 23:40 ` Edward Vidal 2013-10-31 23:34 ` Gary Thomas
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.