Brett, Thanks. Looking at 50.xxx there are rules for v4l devices but for some reason they do not seem to be turning on:
# v4l devices KERNEL="video[0-9]*", NAME="v4l/video%n", SYMLINK="video%n", GROUP="video" KERNEL="radio[0-9]*", NAME="v4l/radio%n", GROUP="video" KERNEL="vbi[0-9]*", NAME="v4l/vbi%n", SYMLINK="vbi%n", GROUP="video" KERNEL="vtx[0-9]*", NAME="v4l/vtx%n", GROUP="video" My wife's Gentoo machine serves as our MythTV backend machine at home. It uses udev and it makes the devices automatically but for some reason this new installation doesn't. I do not know that udev is my problem but my wife's machine has never run anything except udev. My dad's machine (I'm there visiting right now) ran devfs when I built it 18 months but I switched it to udev yesterday trying to make some headway on getting MythTV running here while I'm visiting for a few days. I hope someone has some ideas. It may not be udev at all and maybe I'm focusing on the wrong thing. I've followed the Gentoo-wiki for MythTV before. It has a number of small mistakes or at least ambiguities in it, from what I remember, when I did my wife's machine. Maybe I've missed something. Back to the drawing board. Thanks, Mark On 5/22/05, Brett I. Holcomb <[EMAIL PROTECTED]> wrote: > You may need to define the devices in /etc/udev/rules/10.xxxx. The 50.xxx > file is for standard devices but you can add some - I've done that for a > couple of my devices. If you haven't already Gentoo docs have a udev > guide with links to some good sites. > > > On Sun, 22 May 2005, Mark Knecht wrote: > > > Hi, > > I'm not 100% sure of this but I've been trying to set up a MythTV > > backend on a second system. The system was running and older kernel > > and devfs. I updated the kernel to 2.6.11-gentoo-r9 and included v4l > > support built into the kernel. I was using devfs at that time > > yesterday. I *thought* that after doing that I had some /dev/v4l > > entries but I'm not positive. Somewhere along the way I decided that > > since I'm here I'd convert the machine to udev. That went OK as far as > > I can tell, but now I notice that I don't have any /dev/v4l entries on > > this machine. Maybe they weren't there before. I'm no longer very > > sure. > > > > In the new machine we've got the new PVR-150 card working with the > > development version of ivtv (Not portage - ver. 0.3.3k) and now doing > > the test of the card we capture video. > > > > cat /dev/video0 >test.mpg > > > > and then playing the video in mplayer everything looks good. > > > > At this point I'm not sure what creates /dev/v4l entries. I have > > them in my backend machine in Northern CA which uses a PVR-250 and > > currently ivtv-0.2.0 from their site. (not portage) > > > > dragonfly linux # ls -al /dev/v4l > > total 0 > > drwxr-xr-x 2 root root 160 May 11 10:55 . > > drwxr-xr-x 25 root root 32660 May 20 09:15 .. > > crw-rw---- 1 root video 81, 64 May 11 10:55 radio0 > > crw------- 1 evelyn sys 81, 224 May 11 10:55 vbi0 > > crw------- 1 evelyn sys 81, 32 May 11 10:55 video > > crw------- 1 evelyn sys 81, 0 May 11 10:55 video0 > > crw------- 1 evelyn sys 81, 24 May 11 10:55 video24 > > crw------- 1 evelyn sys 81, 32 May 11 10:55 video32 > > dragonfly linux # uname -r > > 2.6.11-gentoo-r6 > > dragonfly linux # > > > > But not on the new backend machine in southern CA: > > > > gandalf linux # ls -al /dev/v4l > > ls: /dev/v4l: No such file or directory > > gandalf linux # uname -r > > 2.6.11-gentoo-r9 > > gandalf linux # > > > > I've checked that both have v4l support enabled in the kernel. What > > am I missing on this new machine? I'm sure there must just be some > > other thign required to get this turned on? I don't seem to be able > > to configure MythTV without this. > > > > Thanks, > > Mark > > > > > > -- > > Brett I. Holcomb > [EMAIL PROTECTED] > Registered Linux User #188143 > Remove R777 to email > -- > gentoo-user@gentoo.org mailing list > > -- gentoo-user@gentoo.org mailing list
