Arch Linux

peque

Member

From: Denmark - Møn

Registered: 2005-06-26

Posts: 441

Problems with tunercards

Well I'm trying to setup my mythTV center and runs into a funny problem.
I have a Hauppauge PVR-500 and a Hauppauge HVR-4000.

They seems to me to be changing places each time I reboot - and after a little googling udev-rules seems to the answer.
At first at MythTV setup I can find the HVR-4000 as /dev/v4l/video0 and tuner1 from PVR-500 as video1 - but after a reboot mythtv finds this the oppesite way - pvr is video0 and HVR is video1 and nothing works

But then hmmm - here I'm offline in how:
So here's the output from udevadm:

[root@core ~]# udevadm info -a -p `udevadm info -q path -n /dev/v4l/video0`

  looking at device '/class/video4linux/video0':
    KERNEL=="video0"
    SUBSYSTEM=="video4linux"
    DRIVER==""
    ATTR{name}=="cx88[0] video (Hauppauge WinTV-"
    ATTR{index}=="0"

  looking at parent device '/devices/pci0000:00/0000:00:1e.0/0000:04:00.0':
    KERNELS=="0000:04:00.0"
    SUBSYSTEMS=="pci"
    DRIVERS=="cx8800"
    ATTRS{vendor}=="0x14f1"
    ATTRS{device}=="0x8800"
    ATTRS{subsystem_vendor}=="0x0070"
    ATTRS{subsystem_device}=="0x6902"
    ATTRS{class}=="0x040000"
    ATTRS{irq}=="16"
    ATTRS{local_cpus}=="ffff"
    ATTRS{local_cpulist}=="0-15"
    ATTRS{modalias}=="pci:v000014F1d00008800sv00000070sd00006902bc04sc00i00"
    ATTRS{enable}=="1"
    ATTRS{broken_parity_status}=="0"
    ATTRS{msi_bus}==""

  looking at parent device '/devices/pci0000:00/0000:00:1e.0':
    KERNELS=="0000:00:1e.0"
    SUBSYSTEMS=="pci"
    DRIVERS==""
    ATTRS{vendor}=="0x8086"
    ATTRS{device}=="0x244e"
    ATTRS{subsystem_vendor}=="0x0000"
    ATTRS{subsystem_device}=="0x0000"
    ATTRS{class}=="0x060401"
    ATTRS{irq}=="0"
    ATTRS{local_cpus}=="ffff"
    ATTRS{local_cpulist}=="0-15"
    ATTRS{modalias}=="pci:v00008086d0000244Esv00000000sd00000000bc06sc04i01"
    ATTRS{enable}=="1"
    ATTRS{broken_parity_status}=="0"
    ATTRS{msi_bus}=="1"

  looking at parent device '/devices/pci0000:00':
    KERNELS=="pci0000:00"
    SUBSYSTEMS==""
    DRIVERS==""

[root@core ~]# udevadm info -a -p `udevadm info -q path -n /dev/v4l/video1`

  looking at device '/class/video4linux/video1':
    KERNEL=="video1"
    SUBSYSTEM=="video4linux"
    DRIVER==""
    ATTR{name}=="ivtv0 encoder MPG"
    ATTR{index}=="0"

  looking at parent device '/devices/pci0000:00/0000:00:1e.0/0000:04:02.0/0000:05:08.0':
    KERNELS=="0000:05:08.0"
    SUBSYSTEMS=="pci"
    DRIVERS=="ivtv"
    ATTRS{vendor}=="0x4444"
    ATTRS{device}=="0x0016"
    ATTRS{subsystem_vendor}=="0x0070"
    ATTRS{subsystem_device}=="0xe807"
    ATTRS{class}=="0x040000"
    ATTRS{irq}=="18"
    ATTRS{local_cpus}=="ffff"
    ATTRS{local_cpulist}=="0-15"
    ATTRS{modalias}=="pci:v00004444d00000016sv00000070sd0000E807bc04sc00i00"
    ATTRS{enable}=="1"
    ATTRS{broken_parity_status}=="0"
    ATTRS{msi_bus}==""

  looking at parent device '/devices/pci0000:00/0000:00:1e.0/0000:04:02.0':
    KERNELS=="0000:04:02.0"
    SUBSYSTEMS=="pci"
    DRIVERS==""
    ATTRS{vendor}=="0x3388"
    ATTRS{device}=="0x0021"
    ATTRS{subsystem_vendor}=="0x0000"
    ATTRS{subsystem_device}=="0x0000"
    ATTRS{class}=="0x060400"
    ATTRS{irq}=="0"
    ATTRS{local_cpus}=="ffff"
    ATTRS{local_cpulist}=="0-15"
    ATTRS{modalias}=="pci:v00003388d00000021sv00000000sd00000000bc06sc04i00"
    ATTRS{enable}=="1"
    ATTRS{broken_parity_status}=="0"
    ATTRS{msi_bus}=="1"

  looking at parent device '/devices/pci0000:00/0000:00:1e.0':
    KERNELS=="0000:00:1e.0"
    SUBSYSTEMS=="pci"
    DRIVERS==""
    ATTRS{vendor}=="0x8086"
    ATTRS{device}=="0x244e"
    ATTRS{subsystem_vendor}=="0x0000"
    ATTRS{subsystem_device}=="0x0000"
    ATTRS{class}=="0x060401"
    ATTRS{irq}=="0"
    ATTRS{local_cpus}=="ffff"
    ATTRS{local_cpulist}=="0-15"
    ATTRS{modalias}=="pci:v00008086d0000244Esv00000000sd00000000bc06sc04i01"
    ATTRS{enable}=="1"
    ATTRS{broken_parity_status}=="0"
    ATTRS{msi_bus}=="1"

  looking at parent device '/devices/pci0000:00':
    KERNELS=="pci0000:00"
    SUBSYSTEMS==""
    DRIVERS==""

[root@core ~]# udevadm info -a -p `udevadm info -q path -n /dev/v4l/video2`

  looking at device '/class/video4linux/video2':
    KERNEL=="video2"
    SUBSYSTEM=="video4linux"
    DRIVER==""
    ATTR{name}=="ivtv1 encoder MPG"
    ATTR{index}=="0"

  looking at parent device '/devices/pci0000:00/0000:00:1e.0/0000:04:02.0/0000:05:09.0':
    KERNELS=="0000:05:09.0"
    SUBSYSTEMS=="pci"
    DRIVERS=="ivtv"
    ATTRS{vendor}=="0x4444"
    ATTRS{device}=="0x0016"
    ATTRS{subsystem_vendor}=="0x0070"
    ATTRS{subsystem_device}=="0xe817"
    ATTRS{class}=="0x040000"
    ATTRS{irq}=="19"
    ATTRS{local_cpus}=="ffff"
    ATTRS{local_cpulist}=="0-15"
    ATTRS{modalias}=="pci:v00004444d00000016sv00000070sd0000E817bc04sc00i00"
    ATTRS{enable}=="1"
    ATTRS{broken_parity_status}=="0"
    ATTRS{msi_bus}==""

  looking at parent device '/devices/pci0000:00/0000:00:1e.0/0000:04:02.0':
    KERNELS=="0000:04:02.0"
    SUBSYSTEMS=="pci"
    DRIVERS==""
    ATTRS{vendor}=="0x3388"
    ATTRS{device}=="0x0021"
    ATTRS{subsystem_vendor}=="0x0000"
    ATTRS{subsystem_device}=="0x0000"
    ATTRS{class}=="0x060400"
    ATTRS{irq}=="0"
    ATTRS{local_cpus}=="ffff"
    ATTRS{local_cpulist}=="0-15"
    ATTRS{modalias}=="pci:v00003388d00000021sv00000000sd00000000bc06sc04i00"
    ATTRS{enable}=="1"
    ATTRS{broken_parity_status}=="0"
    ATTRS{msi_bus}=="1"

  looking at parent device '/devices/pci0000:00/0000:00:1e.0':
    KERNELS=="0000:00:1e.0"
    SUBSYSTEMS=="pci"
    DRIVERS==""
    ATTRS{vendor}=="0x8086"
    ATTRS{device}=="0x244e"
    ATTRS{subsystem_vendor}=="0x0000"
    ATTRS{subsystem_device}=="0x0000"
    ATTRS{class}=="0x060401"
    ATTRS{irq}=="0"
    ATTRS{local_cpus}=="ffff"
    ATTRS{local_cpulist}=="0-15"
    ATTRS{modalias}=="pci:v00008086d0000244Esv00000000sd00000000bc06sc04i01"
    ATTRS{enable}=="1"
    ATTRS{broken_parity_status}=="0"
    ATTRS{msi_bus}=="1"

  looking at parent device '/devices/pci0000:00':
    KERNELS=="pci0000:00"
    SUBSYSTEMS==""
    DRIVERS==""

But how can I make sure that the HVR-4000 are /dev/v4l/video0 each time at boot??
Looking into the wiki - It'll looks for 3 different atributes - but they aren't here for the tunercards. Eventhough I get from this output that the names ARE for HVR-4000 video0 -> MythTV now recognize its as video1.

How come isn't there a output for the DVB-S /dev/dvb/adapter0
Or is there way to many problems between those 2 cards as it isn't possible to run them on the same backend.

---

Just getting better .... All the time

QuimaxW

Member

From: Papua New Guinea

Registered: 2006-12-03

Posts: 228

Website

Re: Problems with tunercards

Random thought...there is a way (perhaps in modprobe.conf???) to force one device to load before another. I think the logic is usually applied to network cards or sound cards. Perhaps look through the wiki for one of those and apply the same logic to the tuner cards.

---

"He is no fool who gives what he cannot keep to gain that which he cannot lose." -Jim Elliot

peque

Member

From: Denmark - Møn

Registered: 2005-06-26

Posts: 441

Re: Problems with tunercards

Hey QuimaxW

Thanks for your replym, but in denmark all analog signal is now turned off - so all cards are HVR-4000 - as long as the cards are all the same - Its OK - no problem

---

Just getting better .... All the time

Doc Angelo

Member

From: Germany

Registered: 2007-11-28

Posts: 52

Re: Problems with tunercards

With a udev rule you can symlink new device nodes as you like to. You can make sure you always have consistent node names with the following in /etc/udev/rules.d/10-local.rules:

# Heres a sample line which works for the input device on my dvb card
#ATTRS{name}=="*saa7146*", SYMLINK+="input/ir-receiver_tt-budget_s2-3200"

# something like this should work for your first device
ATTRS{vendor}=="0x14f1", ATTRS{device}=="0x8800", SYMLINK+="dvb/your_card"

Now you should be able to access your card under /dev/dvb/your_card.