On Friday 19 January 2007 10:59, Anne Wilson wrote:
> On Thursday 18 January 2007 22:19, Anne Wilson wrote:
> > On Thursday 18 January 2007 21:00, Paulo Cavalcanti wrote:
> > > > It's necessary to run 'udevtrigger' to activate them.
> > > >
> > > > Next question, then. Should I put that command into my
> > > > .bash_profile?
> > >
> > > Anne,
> > >
> > > could you post the udev rules you created?
> > >
> > > These are the rules I use:
> > >
> > > [naja:/etc/udev/rules.d] more 83-video.rules
> > > # Persistent symlinks for webcam and tuner
> > > KERNEL=="video*", SYSFS{idProduct}=="4036", SYSFS{idVendor}=="041e", \
> > > SYMLINK+="webcam"
> > > KERNEL=="video*", SYSFS{device}=="0x036e", SYSFS{vendor}=="0x109e", \
> > > SYMLINK+="tvtuner"
> > >
> > > and these are the corresponding links:
> > >
> > > [naja:/etc/udev/rules.d] ls -al /dev/tvtuner
> > > lrwxrwxrwx 1 root root 6 Jan 16 07:48 /dev/tvtuner -> video0
> > > [naja:/etc/udev/rules.d] ls -al /dev/webcam
> > > lrwxrwxrwx 1 root root 6 Jan 16 07:48 /dev/webcam -> video1
> >
> > # Persistent symlinks for webcam and DC10+
> > KERNEL=="video*", SYSFS{model}=="Pixart PAC207-BCA", SYMLINK+="webcam"
> > KERNEL=="video*", SUBSYSTEM=="video4linux", SYSFS{name}=="DC10plus_0_"
> > , SYMLINK+="DC10plus"
> >
> > I copied and pasted the entries from udevinfo, to make sure that I got
> > them exactly right.
> >
> > Something has gone wrong again, though. I made a test recording before I
> > rebooted, but now I can't, and /dev/DC10plus seems to be wrongly
> > directed.
> >
> > [anne@david ~]$ ls -al /dev/webcam
> > lrwxrwxrwx 1 root root 6 Jan 18 19:45 /dev/webcam -> video0
> > [anne@david ~]$ ls -al /dev/DC10plus
> > lrwxrwxrwx 1 root root 4 Jan 18 19:47 /dev/DC10plus -> hda1
> >
> > I don't understand why it should work once, then not again.
>
> This morning /dev/DC10plus was pointing to hdd - a DVD drive. After
> running udevtrigger manually it pointed to ram3. Running it again made it
> point to ram14. This seems very random. I'll look at udevinfo again and
> see whether I can add further identifying lines. I'll report back whether
> that makes any difference.
>
Alas, the only identifying information I can get is
looking at device '/class/video4linux/video0':
KERNEL=="video0"
SUBSYSTEM=="video4linux"
SYSFS{name}=="DC10plus_0_"
SYSFS{dev}=="81:0"
Trying a different tack -
Problem -
1. Webcam required for ekiga, kopete, amsn - all looking to video0
Requirement - find a way to map these applications to /dev/webcam, which
appears to function correctly.
2. Camcorder attaches to DC10+ capture card, a pci device. /dev/DC10plus
appears to map to random devices, rather than that specified in the rules.
Temporary solution - disable the /dev/DC10plus rule, locate video* for device
and manually change $LAV_VIDEO_DEV to point to it.
Longer term - investigate, but no leads at the moment. Any suggestions
gratefully received.
Anne
Attachment:
pgpEmKOXFETaN.pgp
Description: PGP signature
