No UVC modules with kernel 3.6.11-kirkwood-tld

Hi
still trying to get a web cam running on the pogoplug.
New webcam Logitech C270, works fine on the laptop, but /dev/video0 is not being created when its plugged in.

hwifo --usb shows

03: USB 00.0: 0000 Unclassified device
[Created at usb.122]
Unique ID: dwDZ.VY6alo95Db5
Parent ID: ADDn.d7FDLX76qXB
SysFS ID: /devices/platform/orion-ehci.0/usb1/1-1/1-1.3/1-1.3:1.0
SysFS BusID: 1-1.3:1.0
Hardware Class: unknown
Model: "Logitech Unclassified device"
Hotplug: USB
Vendor: usb 0x046d "Logitech, Inc."
Device: usb 0x0825
Revision: "0.10"
Serial ID: "DE626B20"
Speed: 480 Mbps
Module Alias: "usb:v046Dp0825d0010dcEFdsc02dp01ic0Eisc01ip00in00"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #8 (Hub)

The module alias doesn't help a lot

starting motion -s doesn't show which module its loaded either

root@debian:/# motion -s
[0] Processing thread 0 - config file /etc/motion/motion.conf
[0] Motion 3.2.12 Started
[0] ffmpeg LIBAVCODEC_BUILD 3482368 LIBAVFORMAT_BUILD 3478785
[0] Motion running in setup mode.
[0] Thread 1 is from /etc/motion/motion.conf
[0] Thread 1 is device: /dev/video0 input 8
[0] Webcam port 7661
[0] Waiting for threads to finish, pid: 1885
[0] motion-httpd/3.2.12 running, accepting connections
[0] motion-httpd: waiting for data on port TCP 7660
[1] Thread 1 started
[1] Failed to open video device /dev/video0: No such file or directory
[1] Could not fetch initial image from camera
[1] Motion continues using width and height from config file(s)
[1] Resizing pre_capture buffer to 1 items
[1] Started stream webcam server in port 7661


Plugging the webcam in on the laptop shows it as a UVC camera

lsmod | grep uvc shows nothing

root@debian:/# locate uvc
/lib/modules/2.6.32-5-kirkwood/kernel/drivers/media/video/uvc
/lib/modules/2.6.32-5-kirkwood/kernel/drivers/media/video/uvc/uvcvideo.ko
/lib/modules/3.2.0-4-kirkwood/kernel/drivers/media/video/uvc
/lib/modules/3.2.0-4-kirkwood/kernel/drivers/media/video/uvc/uvcvideo.ko
/usr/include/linux/uvcvideo.h

I suspect I will need v4l2 modules as well , and they aren't there either.


root@debian:/dev# locate v4l
/lib/modules/2.6.32-5-kirkwood/kernel/drivers/media/video/v4l1-compat.ko
/lib/modules/2.6.32-5-kirkwood/kernel/drivers/media/video/v4l2-common.ko
/lib/modules/2.6.32-5-kirkwood/kernel/drivers/media/video/v4l2-int-device.ko
/lib/modules/3.2.0-4-kirkwood/kernel/drivers/media/video/v4l2-common.ko
/lib/modules/3.2.0-4-kirkwood/kernel/drivers/media/video/v4l2-int-device.ko
/lib/udev/v4l_id
/lib/udev/rules.d/60-persistent-v4l.rules
/usr/include/linux/v4l2-mediabus.h
/usr/include/linux/v4l2-subdev.h
/usr/lib/arm-linux-gnueabi/directfb-1.2-9/interfaces/IDirectFBVideoProvider/libidirectfbvideoprovider_v4l.so
root@debian:/dev# uname -r
3.6.11-kirkwood-tld
root@debian:/dev# cd /lib/modules/3.6.11-kirkwood-tld/kernel/drivers
root@debian:/lib/modules/3.6.11-kirkwood-tld/kernel/drivers# ls
ata bcma cdrom crypto hwmon input md mfd mtd pci ptp scsi staging uio video
atm block char firewire i2c isdn memstick misc net power regulator spi target usb w1
base bluetooth connector hid ieee802154 leds message mmc parport pps rtc ssb tty uwb watchdog


Can the modules that are missing be copied from kernel 3.2, or are the signed ??????
or is it grab the kernel source and build the modules, and the last time I did that was on a 2.0 kernel , so I forgotten how.

Thanks


Thanks

Richard,

I'm recompiling the kernel to include this. I'm not familiar with the video drivers, so will see if I'll get the correct modules. Also, I could upload the kernel headers, too , if that's what you need (so you compile the module).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

many thanks Bodhi
I'm pretty sure its uvcvideo.ko and v4l2-common.ko
The headers would be useful, I've not built a kernel module for about 10 years., when it could take up to 2hours to build a kernel..
Maybe a useful exercise to relearn
BTW LED's still orange :)

Thanks

Richard,

If you see the LEDs class now in your system:

# ls /sys/class/leds/
.  ..  status:green:health  status:orange:fault

Then put these 2 lines in your /etc/rc.local (at the end):

echo none > /sys/class/leds/status:orange:fault/trigger
echo default-on > /sys/class/leds/status:green:health/trigger

And this line should go in the halt script /etc/rc0.d/K07halt before the halt command

log_action_msg "Will now halt"
        echo none  > /sys/class/leds/status:green:health/trigger
halt -d -f $netdown $poweroff $hddown

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 04/26/2013 04:21PM by bodhi.

Hi
added the lines first time the rc.local lines were added before the exit 0
rebooted , LED goes off as it should, and when it back its orange.
So
I put the lines after exit 0 in rc.local
rebooted and its still orange
BTW its a black E02
The colours are right in Arch, but that needs machid dd6 to work
machid dd6 stops Debian from booting, I can pretend its green :)

Thanks

If that's the case, without machid dd6, your arcNumber is practically 2097 :) So you can find out in /sys/class/leds what is the trigger file name (could be plug:green:health or something like that) and do the same "echo default-on" to that trigger file.

BTW, the echo line should be placed before exit 0 line in rc.local.

I find it strange that you can't boot with machid dd6 and arcNumber 3542. Must be some other problem.



Edited 1 time(s). Last edit at 04/26/2013 05:07PM by bodhi.

root@debian:~# cd /sys/class/leds/
root@debian:/sys/class/leds
# ls
plug:red:misc status:blue:health status:green:health
root@debian:/sys/class/leds# cd status\:green\:health
root@debian:/sys/class/leds/status:green:health
# ls
brightness device max_brightness subsystem trigger uevent
root@debian:/sys/class/leds/status:green:health
# cat trigger
[none] nand-disk timer default-on mmc0

root@debian:~# cd /sys/class/leds
root@debian:/sys/class/leds# ls
plug:red:misc status:blue:health status:green:health

root@debian:/sys/class/leds# cd status\:green\:health

have a look at that last line
I was using auto complete, ie type a couple of characters and hit Tab, its treating it as if there is a space between.

the machid dd6

I could get to the position of either booting Arch and not Debian or vice versa.

So while I could boot Arch and not Debian, I reloaded Uboot resetting every thing
And both booted.
Made a note of fw_printenv , and that Arch booted in to an Orange Led.
Added machid dd6 and Debian refused to boot, removed it and it did again.
Adding machiddd6 set the Led on Arch to green
I didn't see what I had to do the stop Arch booting. Being able to boot into either by swapping drives was enough.

You say arch number practically 2097, do you mean that it behaves as 2097 or it should be 2097 ????
If I could remember where I put my fone down, I could see if 0Xdd6 + 2097 =3542
The fones got a wicked hex/dec calculator, great for 2's comp
Does this mean archnumber =(0xdd6+3542)


before I get flamed , found my fone , and 0xdd6 =3542. Where does 2097 come from ?

Just tried adding back slashes in the dir name status:green:health, it made no difference ..still orange


-----------------------------------
Just for the hell of it I set machid to dd6, and I have a GREEN Led

So what ever you did in this kernel has fixed that problem ,, nice one :)
But its still gonna catch out anyone using stock kernels for Squeeze and Wheezy if they have used Arch before.
It needs to be put in the install wiki to warn anyone using the stock kernels.
Thanks



Edited 3 time(s). Last edit at 04/26/2013 06:20PM by richard-g8jvm.

Hi Richard,

I built this kernel with patches for Pogo E02 and other Kirkwood plugs (contributed by other members here and at Arch site).

arcNumber 2097 is the basic reference board number. Because the current version of uBoot we are using has a bug (that has been fixed by davygravy, btw) . So machid needs to be set in addition to arcNumber. Even though you have arcNumber 3542, it is treated as was 2097 if machid is not set to dd6.

Once arcNumber recognized by the kernel, it will created the LED class files for that machine during booting up. That's why you have your current set of trigger files, instead of the Pogo E02 set.

You could boot into netconsole and set machid to dd6 there, and then boot, and watch the progress to see anything strange happening.

> setenv machid dd6
> boot

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Dropbox links to video driver modules for Logitech C270:

v4l2-common.ko
uvcvideo.ko

Copy these to your /lib/modules/3.6.11-kirkwood/kernel/drivers/media/video/
and add the modprobe commands to /etc/rc.local

modprobe v4l2-common
modprobe uvcvideo



Edited 1 time(s). Last edit at 04/27/2013 12:54AM by bodhi.

Many thanks Bohdi,

I created the media directory and loaded the modules
Added modprobe uvcvideo to rc.local
and rebooted
the modules did not load
Tried from CLI and got the FATAL not found message

next went in the directory the modules were in and modprobe ./uvcvideo

no error message but lsmod showed them not loaded.

Any suggestions please.
Thanks
----------------------------------------------------------------------------------------
after a few hours of playing

root@debian:/lib/modules/3.6.11-kirkwood-tld/kernel/drivers/media/video# modprobe -a -f -vvv ./uvcvideo
libkmod: DEBUG ../libkmod/libkmod-module.c:519 kmod_module_new_from_lookup: input alias=./uvcvideo, normalized=./uvcvideo
libkmod: DEBUG ../libkmod/libkmod-module.c:525 kmod_module_new_from_lookup: lookup modules.dep ./uvcvideo
libkmod: DEBUG ../libkmod/libkmod.c:542 kmod_search_moddep: use mmaped index 'modules.dep' modname=./uvcvideo
libkmod: DEBUG ../libkmod/libkmod-module.c:529 kmod_module_new_from_lookup: lookup modules.symbols ./uvcvideo
libkmod: DEBUG ../libkmod/libkmod-module.c:533 kmod_module_new_from_lookup: lookup install and remove commands ./uvcvideo
libkmod: DEBUG ../libkmod/libkmod-module.c:537 kmod_module_new_from_lookup: lookup modules.aliases ./uvcvideo
libkmod: DEBUG ../libkmod/libkmod.c:422 kmod_lookup_alias_from_alias_bin: use mmaped index 'modules.alias' for name=./uvcvideo
libkmod: DEBUG ../libkmod/libkmod-module.c:541 kmod_module_new_from_lookup: lookup modules.builtin ./uvcvideo
libkmod: DEBUG ../libkmod/libkmod.c:492 kmod_lookup_alias_from_builtin_file: use mmaped index 'modules.builtin' modname=./uvcvideo
libkmod: DEBUG ../libkmod/libkmod-module.c:546 kmod_module_new_from_lookup: lookup ./uvcvideo=0, list=(nil)
DEBUG: lookup failed - trying to check if it's builtin
libkmod: DEBUG ../libkmod/libkmod.c:390 kmod_pool_get_module: get module name='' found=(nil)
libkmod: DEBUG ../libkmod/libkmod.c:398 kmod_pool_add_module: add 0xb78fe2d0 key=''
libkmod: DEBUG ../libkmod/libkmod-module.c:1651 kmod_module_get_initstate: could not open '/sys/module//initstate': No such file or directory
libkmod: DEBUG ../libkmod/libkmod-module.c:435 kmod_module_unref: kmod_module 0xb78fe2d0 released
libkmod: DEBUG ../libkmod/libkmod.c:406 kmod_pool_del_module: del 0xb78fe2d0 key=''
builtin ./uvcvideo
libkmod: INFO ../libkmod/libkmod.c:319 kmod_unref: context 0xb78fe110 released

I hope that gives a clue ???????????



Edited 1 time(s). Last edit at 04/27/2013 12:47PM by richard-g8jvm.

Richard,

There might be other dendencies that we don't know about? do you have a working installation (i.e. squeeze) that you can do lsmod to compare with your current system?

I have another flash drive with Arch on it and I think thats a kernel -3,
If not I had a spare flash I could put squeeze on, but thats kernel-2

--------------------------------------------------------------------------------------------------
Booted into Arch
[root@pogopig ~]# lsmod
Module Size Used by
ipv6 259694 14
snd_usb_audio 72415 0
snd_usbmidi_lib 15419 1 snd_usb_audio
uvcvideo 55554 0
snd_hwdep 4741 1 snd_usb_audio
snd_rawmidi 15590 1 snd_usbmidi_lib
snd_seq_device 4659 1 snd_rawmidi
snd_pcm 59121 1 snd_usb_audio
snd_page_alloc 4687 1 snd_pcm
videodev 70822 1 uvcvideo
snd_timer 16535 1 snd_pcm
snd 35232 7 snd_timer,snd_pcm,snd_seq_device,snd_rawmidi,snd_hwdep,snd_usbmidi_lib,snd_usb_audio
i2c_core 15344 1 videodev
soundcore 690 1 snd
mv_cesa 9128 0
autofs4 22074 2

[root@pogopig ~]# uname -r
3.1.10-16-ARCH

might be videodev needed as well Bohdi

Thanks



Edited 1 time(s). Last edit at 04/27/2013 04:39PM by richard-g8jvm.

You can do lsmod on Arch to get the list of modules. It'll be good to see that list.