kernel config? no video0

[Chris]

Oh dear, I tried later, and there is no video0 in /dev, and if I go
to debug directory, cd to microdia, but no video0 shows there.



I tried rebooting and then

mknod /dev/video0 c 81 0
chmod 777 /dev/video0
chgrp video /dev/video0
ln -s /dev/video0
so that there is a file there

before the videodev and compat modprobes
and then insmod micrododia.ko

with the same result

doing the mplayer tv:// -tv thing just says video0 no such device.
So, how do I get the video0 file in /dev to be recognised as a device?

lsmod shows videodev depending on v4l1_compat and microdia depending
on usb-core and v4l1, I guess this should depend on v4l2-common. Being
new
to loading and unloading modules I am not sure what to do about this
or whether it is as it should be.

Is this why I get no video0 as well, or is all as it should be?

In the config file I have

CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_DEV_V4L2_COMMON=m
CONFIG_VIDEO_ALLOW_V4L1=y
CONFIG_VIDEO__VL1_COMPAT=y
CONFIG_DVB_CORE=m
CONFIG_VIDEO_MEDIA=m

so v4l1-compat is compiled into the kernel?
Menuconfig-> device drivers-> multimedia devices-> shows video for
linux cannot be unchecked. So are the above dependencies right after
all?

[GWater]

Chris schrieb:

please post the output of
$ sudo cat /var/log/messages | grep microdia

after you insmod microdia.ko

GWater

[Chris]

I just get
microdia: Microdia USB2.0 webcam driver startup
usbcore: registered new interface driver usb_microdia_driver
microdia: v0.0.0 : Microdia USB Video Camera

And that's it. Looks pretty innocent...

[Chris]

In my root directory I have a file called rootmicrodia
and a copy of microdia.ko

I have cut and paste from this, so this is exactly what

sh rootmicrodia does, no typos!

mount -t debugfs none /sys/kernel/debug

mknod /dev/video0 c 81 0
chmod 777 /dev/video0
chgrp video /dev/video0

ln -s /dev/video0 /dev/video
sync; sleep 1; sync
modprobe v4l2-common
modprobe videodev
modprobe compat-ioctl32
insmod microdia.ko
depmod -a
lsmod

plus i did an slocate -u after

[GWater]

Chris schrieb:

Ok,
here's the explanation:
your webcam is not yet supported.

Maybe we already have support for the same chipset/sensor combination
but your webcams usb-id is not yet associated with it.

Therefore we need to know which bridge and sensor your webcam has.

GWater

[Chris]

That explains a lot!

All I know is from taking an instrument screwdriver to the thing is
that there is an E218418 chip on it

The IDs on the other side are
VP-38R(01) and VP-38C(02)

I doubt if this helps any though.

[GWater]

Chris schrieb:

If you have access to a windows system try installing the driver and
find the *.inf file for it. In many cases the bridge-sensor combination
is in there.

GWater

[GWater]

Chris schrieb:

I am of course referring to the windows driver that came with your webcam.

GWater