[mythtv-users] UDEV rules

[Yianni]

Hi, Daryl.

First of all, as a warning, I use OpenSuSE, so there is a chance the folders and/or the module parameters are not exactly the same.

I've got my video devices (saa7134 and HDPVR) set up using udev rules, but without touching the original devices in /dev. I made rules that created additional devices: My HD-PVR appears as /dev/video1 but I created an additional static device called  /dev/hdpvr1 and I use that in mythtv.

However, if you want to use the modprobe way, create a .conf file in /etc/modprobe.d with the rules you want.

The name doesn't matter, it's just a reminder for you when in 6 months you browse the folder. It must end in ".conf", however.

You can check the parameters the modules accept upon loading with the modinfo command:
sudo modinfo cx23885.

It will produce a LOT of info, which includes the:

parm:           adapter_nr:DVB adapter numbers (array of short)

line.

The "adapter_nr" is the parameter you can use to set the videoX number for this device.

Based on the devices below, 
**********************************
>>> 02:00.0 Multimedia video controller: Conexant Systems, Inc. CX23885
>>> PCI Video and Audio Decoder (rev 04)
>>> Capabilities: <access denied>
>>> Kernel driver in use: cx23885
>>> Kernel modules: cx23885

>>> 04:00.0 Multimedia controller: Philips Semiconductors
>>> SAA7131/SAA7133/SAA7135 Video Broadcast Decoder (rev d1)
>>> Subsystem: KWorld Computer Co. Ltd. Device a135
>>> Kernel driver in use: saa7134
>>> Kernel modules: saa7134

>>> 04:01.0 Multimedia video controller: Internext Compression Inc iTVC16
>>> (CX23416) Video Decoder (rev 01)
>>> Kernel driver in use: ivtv
>>> Kernel modules: ivtv
***********************************

and the modinfo command for cx23885, saa7134 and ivtv,

the /etc/modprobe.d/whatever.conf file you should create would include:
**********
options cx23885 adapter_nr=1
options saa7134 video_nr=2
**********

I am not sure about the ivtv module, so I HOPE it will take number 3 on its own as the first two will be occupied ;)

A restart will be necessary or 'sudo rmmod' and 'sudo modprobe' for each of the modules used.

>>> As per the wiki when I run the command " udevadm info -a -p $(udevadm
>>> info -q path -n /dev/video0)" I can't identify the Philips card

Maybe it's not /dev/video0. Have you tried /dev/video1 or 2?

If nothing is using the card, you can try a 

'sudo rmmod saa7134' to unload its module, then 
'sudo modprobe saa7134' to re-load it.
Then 'sudo dmesg' will show you what got installed.


If you are interested, I can include my udev rules files.

Yianni.