Cine CT V6.1 auf DVB-C umstellen, wie?

UFO · 22. März 2015

Zitat von mini73

Ich nutze den Treiber und sogar einen älteren vdr ohne Probleme mit meiner CineCT.
Neuere Versionen haben wir in stable (noch) nicht. Sollten auch nicht unbedingt nötig sein.

Ok, dann bin ich hier raus.

CU
Oliver

mini73 · 23. März 2015

Mit dynamite benutze ich folgende udev-Regel:

Code

$ cat /etc/udev/rules.d/90-dynamite.rules
ACTION=="add", SUBSYSTEM=="dvb", ENV{DVB_DEVICE_TYPE}=="frontend", ATTRS{vendor}=="0xdd01", ENV{dynamite_sources}="C"

Statt "vendor" kannst du auch was anderes zur eindeutigen Identifikation benutzen. Eine Auswahl gibt dir

Code

$ udevadm info --name=/dev/dvb/adapter0/frontend0 --query=all --attribute-walk


Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.


  looking at device '/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/dvb/dvb0.frontend0':
    KERNEL=="dvb0.frontend0"
    SUBSYSTEM=="dvb"
    DRIVER==""


  looking at parent device '/devices/pci0000:00/0000:00:1c.2/0000:04:00.0':
    KERNELS=="0000:04:00.0"
    SUBSYSTEMS=="pci"
    DRIVERS=="DDBridge"
    ATTRS{vendor}=="0xdd01"
    ATTRS{device}=="0x0003"
    ATTRS{subsystem_vendor}=="0xdd01"
    ATTRS{subsystem_device}=="0x0002"
    ATTRS{class}=="0x048000"
    ATTRS{irq}=="49"
    ATTRS{local_cpus}=="00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000003"
    ATTRS{local_cpulist}=="0-1"
    ATTRS{numa_node}=="-1"
    ATTRS{dma_mask_bits}=="32"
    ATTRS{consistent_dma_mask_bits}=="32"
    ATTRS{broken_parity_status}=="0"
    ATTRS{msi_bus}==""


  looking at parent device '/devices/pci0000:00/0000:00:1c.2':
    KERNELS=="0000:00:1c.2"
    SUBSYSTEMS=="pci"
    DRIVERS=="pcieport"
    ATTRS{vendor}=="0x8086"
    ATTRS{device}=="0x1c14"
    ATTRS{subsystem_vendor}=="0x8086"
    ATTRS{subsystem_device}=="0x2002"
    ATTRS{class}=="0x060400"
    ATTRS{irq}=="42"
    ATTRS{local_cpus}=="00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000003"
    ATTRS{local_cpulist}=="0-1"
    ATTRS{numa_node}=="-1"
    ATTRS{dma_mask_bits}=="32"
    ATTRS{consistent_dma_mask_bits}=="32"
    ATTRS{broken_parity_status}=="0"
    ATTRS{msi_bus}=="1"


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

Alles anzeigen

Aber nicht jedes Attribut ist geeignet.

Lars.

rom770 · 24. März 2015

Hi

Meine Karte liefert bei ähnliche Ergebnisse:

Code

root@vdr:/lib/udev/rules.d# udevadm info --name=/dev/dvb/adapter0/frontend0 --query=all --attribute-walk


Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.


  looking at device '/devices/pci0000:00/0000:00:04.0/0000:02:00.0/dvb/dvb0.frontend0':
    KERNEL=="dvb0.frontend0"
    SUBSYSTEM=="dvb"
    DRIVER==""


  looking at parent device '/devices/pci0000:00/0000:00:04.0/0000:02:00.0':
    KERNELS=="0000:02:00.0"
    SUBSYSTEMS=="pci"
    DRIVERS=="ddbridge"
    ATTRS{irq}=="44"
    ATTRS{subsystem_vendor}=="0xdd01"
    ATTRS{broken_parity_status}=="0"
    ATTRS{class}=="0x048000"
    ATTRS{consistent_dma_mask_bits}=="32"
    ATTRS{dma_mask_bits}=="32"
    ATTRS{local_cpus}=="00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000003"
    ATTRS{device}=="0x0003"
    ATTRS{enable}=="1"
    ATTRS{msi_bus}==""
    ATTRS{local_cpulist}=="0-1"
    ATTRS{vendor}=="0xdd01"
    ATTRS{subsystem_device}=="0x0030"
    ATTRS{numa_node}=="0"
    ATTRS{d3cold_allowed}=="1"


  looking at parent device '/devices/pci0000:00/0000:00:04.0':
    KERNELS=="0000:00:04.0"
    SUBSYSTEMS=="pci"
    DRIVERS=="pcieport"
    ATTRS{irq}=="41"
    ATTRS{subsystem_vendor}=="0x1458"
    ATTRS{broken_parity_status}=="0"
    ATTRS{class}=="0x060400"
    ATTRS{consistent_dma_mask_bits}=="32"
    ATTRS{dma_mask_bits}=="32"
    ATTRS{local_cpus}=="00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000003"
    ATTRS{device}=="0x7914"
    ATTRS{enable}=="2"
    ATTRS{msi_bus}=="1"
    ATTRS{local_cpulist}=="0-1"
    ATTRS{vendor}=="0x1002"
    ATTRS{subsystem_device}=="0x5000"
    ATTRS{numa_node}=="0"
    ATTRS{d3cold_allowed}=="0"


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

Alles anzeigen

Also habe ich eine Datei mit gleichen Einstellungen unter /lib/udev/rules.d angelegt, vdr herunter gefahren, channels.conf neu angelegt und den Rechner neu gebootet. Allerdings das gleiche Ergebnis, immer noch kein Signal. Immerhin zeigt Signalinfo an, dass nur DVB-C benutzt wird.

Hier der syslog-Auszug:

Code

Mar 24 00:12:29 vdr vdr: [2701] dynamite udev monitor for subsystem dvb thread started (pid=2700, tid=2701, prio=high)
Mar 24 00:12:29 vdr vdr: [2701] dynamite udev monitor for subsystem dvb thread ended (pid=2700, tid=2701)
Mar 24 00:12:29 vdr vdr: [2782] VDR version 2.0.6 started
Mar 24 00:12:29 vdr vdr: [2782] switched to user 'vdr'
Mar 24 00:12:29 vdr vdr: [2782] codeset is 'UTF-8' - known
Mar 24 00:12:29 vdr vdr: [2782] found 28 locales in /usr/share/locale
Mar 24 00:12:29 vdr vdr: [2782] loading plugin: /usr/lib/vdr/plugins/libvdr-menuorg.so.2.0.6
Mar 24 00:12:29 vdr vdr: [2782] loading plugin: /usr/lib/vdr/plugins/libvdr-mplayer.so.2.0.6
Mar 24 00:12:29 vdr vdr: [2782] loading plugin: /usr/lib/vdr/plugins/libvdr-text2skin.so.2.0.6
Mar 24 00:12:29 vdr vdr: [2782] loading plugin: /usr/lib/vdr/plugins/libvdr-osdteletext.so.2.0.6
Mar 24 00:12:29 vdr vdr: [2782] loading plugin: /usr/lib/vdr/plugins/libvdr-extrecmenu.so.2.0.6
Mar 24 00:12:29 vdr vdr: [2782] loading plugin: /usr/lib/vdr/plugins/libvdr-markad.so.2.0.6
Mar 24 00:12:29 vdr vdr: [2782] loading plugin: /usr/lib/vdr/plugins/libvdr-conflictcheckonly.so.2.0.6
Mar 24 00:12:29 vdr vdr: [2782] loading plugin: /usr/lib/vdr/plugins/libvdr-epgsearch.so.2.0.6
Mar 24 00:12:29 vdr vdr: [2782] loading plugin: /usr/lib/vdr/plugins/libvdr-quickepgsearch.so.2.0.6
Mar 24 00:12:29 vdr vdr: [2782] loading plugin: /usr/lib/vdr/plugins/libvdr-vdrmanager.so.2.0.6
Mar 24 00:12:29 vdr vdr: [2782] loading plugin: /usr/lib/vdr/plugins/libvdr-tvonscreen.so.2.0.6
Mar 24 00:12:29 vdr vdr: [2782] loading plugin: /usr/lib/vdr/plugins/libvdr-femon.so.2.0.6
Mar 24 00:12:29 vdr vdr: [2782] loading plugin: /usr/lib/vdr/plugins/libvdr-live.so.2.0.6
Mar 24 00:12:29 vdr vdr: [2782] [live] INFO: validating server ip '0.0.0.0'
Mar 24 00:12:29 vdr vdr: [2782] loading plugin: /usr/lib/vdr/plugins/libvdr-streamdev-server.so.2.0.6
Mar 24 00:12:29 vdr vdr: [2782] loading plugin: /usr/lib/vdr/plugins/libvdr-epgsearchonly.so.2.0.6
Mar 24 00:12:29 vdr vdr: [2782] loading plugin: /usr/lib/vdr/plugins/libvdr-skinenigmang.so.2.0.6
Mar 24 00:12:29 vdr vdr: [2782] loading plugin: /usr/lib/vdr/plugins/libvdr-skinelchi.so.2.0.6
Mar 24 00:12:29 vdr vdr: [2782] loading plugin: /usr/lib/vdr/plugins/libvdr-xineliboutput.so.2.0.6
Mar 24 00:12:29 vdr vdr: [2782] [xine..put] Listening on address '127.0.0.1' port 37890
Mar 24 00:12:29 vdr vdr: [2782] loading plugin: /usr/lib/vdr/plugins/libvdr-skinsoppalusikka.so.2.0.6
Mar 24 00:12:29 vdr vdr: [2782] loading plugin: /usr/lib/vdr/plugins/libvdr-dynamite.so.2.0.6
Mar 24 00:12:29 vdr vdr: [2782] loading /var/lib/vdr/setup.conf
Mar 24 00:12:29 vdr vdr: [2783] dynamite udev monitor for subsystem dvb thread started (pid=2782, tid=2783, prio=high)
Mar 24 00:12:29 vdr vdr: [2782] ERROR: unknown config parameter: PrimaryLimit = 0
Mar 24 00:12:29 vdr vdr: [2782] loading /var/lib/vdr/sources.conf
Mar 24 00:12:29 vdr vdr: [2782] loading /var/lib/vdr/diseqc.conf
Mar 24 00:12:29 vdr vdr: [2782] loading /var/lib/vdr/scr.conf
Mar 24 00:12:29 vdr vdr: [2782] loading /var/lib/vdr/channels.conf
Mar 24 00:12:29 vdr vdr: [2782] loading /var/lib/vdr/timers.conf
Mar 24 00:12:29 vdr vdr: [2782] ERROR: channel T-8468-773-16418 not defined
Mar 24 00:12:29 vdr vdr: [2782] ERROR: error in /var/lib/vdr/timers.conf, line 1
Mar 24 00:12:29 vdr vdr: [2782] ERROR: channel T-8468-769-16408 not defined
Mar 24 00:12:29 vdr vdr: [2782] ERROR: error in /var/lib/vdr/timers.conf, line 2
Mar 24 00:12:29 vdr vdr: [2782] ERROR: channel T-8468-769-16408 not defined
Mar 24 00:12:29 vdr vdr: [2782] ERROR: error in /var/lib/vdr/timers.conf, line 3
Mar 24 00:12:29 vdr vdr: [2782] ERROR: channel T-8468-769-16408 not defined
Mar 24 00:12:29 vdr vdr: [2782] ERROR: error in /var/lib/vdr/timers.conf, line 4
Mar 24 00:12:29 vdr vdr: [2782] ERROR: channel T-8468-769-16408 not defined
Mar 24 00:12:29 vdr vdr: [2782] ERROR: error in /var/lib/vdr/timers.conf, line 5
Mar 24 00:12:29 vdr vdr: [2782] ERROR: channel T-8468-769-16408 not defined
Mar 24 00:12:29 vdr vdr: [2782] ERROR: error in /var/lib/vdr/timers.conf, line 6
Mar 24 00:12:29 vdr vdr: [2782] ERROR: channel T-8468-769-16408 not defined
Mar 24 00:12:29 vdr vdr: [2782] ERROR: error in /var/lib/vdr/timers.conf, line 7
Mar 24 00:12:29 vdr vdr: [2782] ERROR: channel T-8468-769-16408 not defined
Mar 24 00:12:29 vdr vdr: [2782] ERROR: error in /var/lib/vdr/timers.conf, line 8
Mar 24 00:12:29 vdr vdr: [2782] ERROR: channel T-8468-773-16405 not defined
Mar 24 00:12:29 vdr vdr: [2782] ERROR: error in /var/lib/vdr/timers.conf, line 9
Mar 24 00:12:29 vdr vdr: [2782] ERROR: channel T-8468-773-16405 not defined
Mar 24 00:12:29 vdr vdr: [2782] ERROR: error in /var/lib/vdr/timers.conf, line 10
Mar 24 00:12:29 vdr vdr: [2782] loading /var/lib/vdr/commands.conf
Mar 24 00:12:29 vdr vdr: [2782] loading /var/lib/vdr/reccmds.conf
Mar 24 00:12:29 vdr vdr: [2782] loading /var/lib/vdr/svdrphosts.conf
Mar 24 00:12:29 vdr vdr: [2782] loading /var/lib/vdr/remote.conf
Mar 24 00:12:29 vdr vdr: [2782] loading /var/lib/vdr/keymacros.conf
Mar 24 00:12:29 vdr vdr: [2784] video directory scanner thread started (pid=2782, tid=2784, prio=high)
Mar 24 00:12:29 vdr vdr: [2782] registered source parameters for 'A - ATSC'
Mar 24 00:12:29 vdr vdr: [2782] registered source parameters for 'C - DVB-C'
Mar 24 00:12:29 vdr vdr: [2782] registered source parameters for 'S - DVB-S'
Mar 24 00:12:29 vdr vdr: [2782] registered source parameters for 'T - DVB-T'
Mar 24 00:12:29 vdr vdr: [2785] video directory scanner thread started (pid=2782, tid=2785, prio=high)
Mar 24 00:12:29 vdr vdr: [2782] probing /dev/dvb/adapter0/frontend0
Mar 24 00:12:29 vdr vdr: [2782] dynamite: preparing 8 dynamic device slots for dvb devices
Mar 24 00:12:29 vdr vdr: [2782] new device number 1
Mar 24 00:12:29 vdr vdr: [2782] new device number 2
Mar 24 00:12:29 vdr vdr: [2782] new device number 3
Mar 24 00:12:29 vdr vdr: [2782] new device number 4
Mar 24 00:12:29 vdr vdr: [2782] new device number 5
Mar 24 00:12:29 vdr vdr: [2782] new device number 6
Mar 24 00:12:29 vdr vdr: [2782] new device number 7
Mar 24 00:12:29 vdr vdr: [2782] new device number 8
Mar 24 00:12:29 vdr vdr: [2782] dynamite: grab dvb device 0/0
Mar 24 00:12:29 vdr vdr: [2782] probing /dev/dvb/adapter1/frontend0
Mar 24 00:12:29 vdr vdr: [2782] dynamite: grab dvb device 1/0
Mar 24 00:12:29 vdr vdr: [2782] probing /dev/dvb/adapter2/frontend0
Mar 24 00:12:29 vdr vdr: [2782] dynamite: grab dvb device 2/0
Mar 24 00:12:29 vdr vdr: [2782] found 3 DVB devices
Mar 24 00:12:29 vdr vdr: [2782] initializing plugin: menuorg (0.5.1): Reorganisiert das Haupmenü
Mar 24 00:12:29 vdr vdr: [2782] loading menuorg config file from /var/lib/vdr/plugins/menuorg.xml
Mar 24 00:12:29 vdr vdr: [2782] initializing plugin: mplayer (0.10.2): Media replay via MPlayer
Mar 24 00:12:29 vdr vdr: [2782] loading /var/lib/vdr/plugins/mplayersources.conf
Mar 24 00:12:29 vdr vdr: [2782] initializing plugin: text2skin (1.3.2+git): Lader für textbasierte Skins
Mar 24 00:12:29 vdr vdr: [2782] initializing plugin: osdteletext (0.9.4): Zeigt den Videotext auf dem OSD an
Mar 24 00:12:29 vdr vdr: [2782] initializing plugin: extrecmenu (1.2.4): Erweitertes Aufzeichnungs-Menü
Mar 24 00:12:29 vdr vdr: [2782] initializing plugin: markad (0.1.5pre): Markiere Werbung
Mar 24 00:12:29 vdr vdr: [2782] initializing plugin: conflictcheckonly (0.0.1): Direkter Zugriff auf epgsearch's Konflikt-Prüfungs-Menü
Mar 24 00:12:29 vdr vdr: [2782] initializing plugin: epgsearch (1.0.1.beta5): Suche im EPG nach Wiederholungen und anderem
Mar 24 00:12:29 vdr vdr: [2782] initializing plugin: quickepgsearch (0.0.1): Schnelle Suche nach Sendungen
Mar 24 00:12:29 vdr vdr: [2782] initializing plugin: vdrmanager (0.12): VDR-Manager support plugin
Mar 24 00:12:29 vdr vdr: [2782] initializing plugin: tvonscreen (1.1.142): Zeigt EPG als TV-Magazin
Mar 24 00:12:29 vdr vdr: [2782] initializing plugin: femon (2.0.0): DVB Signal Informationsanzeige (OSD)
Mar 24 00:12:29 vdr vdr: [2782] initializing plugin: live (0.3.0): Live Interactive VDR Environment
Mar 24 00:12:29 vdr vdr: [2782] initializing plugin: streamdev-server (0.6.1-git): VDR Streaming Server
Mar 24 00:12:29 vdr vdr: [2782] initializing plugin: epgsearchonly (0.0.1): Direkter Zugriff auf epgsearch's Suchenmenu
Mar 24 00:12:29 vdr vdr: [2782] initializing plugin: skinenigmang (0.1.2): EnigmaNG Oberfläche
Mar 24 00:12:29 vdr vdr: [2782] initializing plugin: skinelchi (0.2.8): Elchi Oberfläche
Mar 24 00:12:29 vdr vdr: [2782] initializing plugin: xineliboutput (2.0.0-cvs): X11/xine-lib Ausgabe-Plugin
Mar 24 00:12:29 vdr vdr: [2782] new device number 14
Mar 24 00:12:29 vdr vdr: [2782] [xine..put] cTimePts: clock_gettime(CLOCK_MONOTONIC): clock resolution 0 us
Mar 24 00:12:29 vdr vdr: [2782] [xine..put] cTimePts: using monotonic clock
Mar 24 00:12:29 vdr vdr: [2782] [xine..put] RTP SSRC: 0x09e7cfd7
Mar 24 00:12:29 vdr vdr: [2782] initializing plugin: skinsoppalusikka (2.0.0): Soppalusikka Oberfläche
Mar 24 00:12:29 vdr vdr: [2782] initializing plugin: dynamite (0.2.1): Empfangsgeräte während des Betriebs ein- und aushängen
Mar 24 00:12:29 vdr vdr: [2782] dynamite: xineliboutput detected, leaving 1 additional slot(s) free
Mar 24 00:12:29 vdr vdr: [2782] dynamite: creating dynamic device slots as much as possible
Mar 24 00:12:29 vdr vdr: [2782] new device number 15
Mar 24 00:12:29 vdr vdr: [2782] new device number 16
Mar 24 00:12:29 vdr vdr: [2782] new device number 17
Mar 24 00:12:29 vdr vdr: [2782] new device number 18
Mar 24 00:12:29 vdr vdr: [2782] new device number 19
Mar 24 00:12:29 vdr vdr: [2782] new device number 20
Mar 24 00:12:29 vdr vdr: [2782] dynamite: probing /dev/dvb/adapter0/frontend0
Mar 24 00:12:29 vdr vdr: [2782] dynamite: probing /dev/dvb/adapter1/frontend0
Mar 24 00:12:29 vdr vdr: [2782] dynamite: probing /dev/dvb/adapter2/frontend0
Mar 24 00:12:29 vdr vdr: [2787] [xine..put] Have CAP_SYS_NICE capability
Mar 24 00:12:29 vdr vdr: [2782] dynamite: /dev/dvb/adapter0/frontend0 is a dvb adapter trying to set card index to 0
Mar 24 00:12:29 vdr vdr: [2782] new sub-device number 1
Mar 24 00:12:29 vdr vdr: [2782] DVB API version is 0x050A (VDR was built with 0x0504)
Mar 24 00:12:29 vdr vdr: [2782] frontend 0/0 provides DVB-C,DVB-T with QAM16,QAM32,QAM64,QAM128,QAM256 ("STV0367 DVB-C DVB-T")
Mar 24 00:12:29 vdr vdr: [2782] cTimeMs: using monotonic clock (resolution is 1 ns)
Mar 24 00:12:29 vdr vdr: [2782] dynamite: attached device /dev/dvb/adapter0/frontend0 to dynamic device slot 1
Mar 24 00:12:29 vdr vdr: [2782] dynamite: /dev/dvb/adapter1/frontend0 is a dvb adapter trying to set card index to 1
Mar 24 00:12:29 vdr vdr: [2782] new sub-device number 2
Mar 24 00:12:29 vdr vdr: [2786] epg data reader thread started (pid=2782, tid=2786, prio=high)
Mar 24 00:12:29 vdr vdr: [2786] reading EPG data from /var/cache/vdr/epg.data
Mar 24 00:12:29 vdr vdr: [2786] epg data reader thread ended (pid=2782, tid=2786)
Mar 24 00:12:29 vdr vdr: [2782] frontend 1/0 provides DVB-C,DVB-T with QAM16,QAM32,QAM64,QAM128,QAM256 ("STV0367 DVB-C DVB-T")
Mar 24 00:12:29 vdr vdr: [2789] tuner on frontend 0/0 thread started (pid=2782, tid=2789, prio=high)
Mar 24 00:12:29 vdr vdr: [2782] dynamite: attached device /dev/dvb/adapter1/frontend0 to dynamic device slot 2
Mar 24 00:12:29 vdr vdr: [2782] dynamite: /dev/dvb/adapter2/frontend0 is a dvb adapter trying to set card index to 2
Mar 24 00:12:29 vdr vdr: [2782] new sub-device number 3
Mar 24 00:12:29 vdr vdr: [2790] section handler thread started (pid=2782, tid=2790, prio=low)
Mar 24 00:12:29 vdr vdr: [2793] section handler thread started (pid=2782, tid=2793, prio=low)
Mar 24 00:12:29 vdr vdr: [2792] tuner on frontend 1/0 thread started (pid=2782, tid=2792, prio=high)
Mar 24 00:12:29 vdr vdr: [2782] frontend 2/0 provides DVB-T with QPSK,QAM16,QAM64 ("Conexant CX22702 DVB-T")
Mar 24 00:12:29 vdr vdr: [2782] dynamite: attached device /dev/dvb/adapter2/frontend0 to dynamic device slot 3
Mar 24 00:12:29 vdr vdr: [2782] dynamite: /dev/dvb/adapter0/frontend0 is a dvb adapter trying to set card index to 0
Mar 24 00:12:29 vdr vdr: [2782] dynamite: /dev/dvb/adapter0/frontend0 is already attached
Mar 24 00:12:29 vdr vdr: [2782] dynamite: /dev/dvb/adapter1/frontend0 is a dvb adapter trying to set card index to 1
Mar 24 00:12:29 vdr vdr: [2782] dynamite: /dev/dvb/adapter1/frontend0 is already attached
Mar 24 00:12:29 vdr vdr: [2782] dynamite: /dev/dvb/adapter2/frontend0 is a dvb adapter trying to set card index to 2
Mar 24 00:12:29 vdr vdr: [2782] dynamite: /dev/dvb/adapter2/frontend0 is already attached
Mar 24 00:12:29 vdr vdr: [2782] setting primary device to 9
Mar 24 00:12:29 vdr vdr: [2782] assuming manual start of VDR
Mar 24 00:12:29 vdr vdr: [2782] SVDRP listening on port 6419
Mar 24 00:12:29 vdr vdr: [2782] skin "EnigmaNG" not available - using "lcars" instead
Mar 24 00:12:29 vdr vdr: [2782] starting plugin: menuorg
Mar 24 00:12:29 vdr vdr: [2782] starting plugin: mplayer
Mar 24 00:12:29 vdr vdr: [2782] starting plugin: text2skin
Mar 24 00:12:29 vdr vdr: [2782] text2skin: loading /var/lib/vdr/plugins/text2skin/anthra_SD/anthra_SD.colors
Mar 24 00:12:29 vdr vdr: [2782] parsing /var/lib/vdr/plugins/text2skin/anthra_SD/anthra_SD.skin
Mar 24 00:12:29 vdr vdr: [2796] section handler thread started (pid=2782, tid=2796, prio=low)
Mar 24 00:12:29 vdr vdr: [2795] tuner on frontend 2/0 thread started (pid=2782, tid=2795, prio=high)
Mar 24 00:12:29 vdr vdr: [2782] text2skin: loading /var/lib/vdr/plugins/text2skin/pearlhd_NG/pearlhd_NG.colors
Mar 24 00:12:29 vdr vdr: [2782] parsing /var/lib/vdr/plugins/text2skin/pearlhd_NG/pearlhd_NG.skin
Mar 24 00:12:29 vdr vdr: [2785] video directory scanner thread ended (pid=2782, tid=2785)
Mar 24 00:12:29 vdr vdr: [2782] starting plugin: osdteletext
Mar 24 00:12:29 vdr vdr: [2782] starting plugin: extrecmenu
Mar 24 00:12:29 vdr vdr: [2782] starting plugin: markad
Mar 24 00:12:29 vdr vdr: [2782] starting plugin: conflictcheckonly
Mar 24 00:12:29 vdr vdr: [2782] starting plugin: epgsearch
Mar 24 00:12:29 vdr vdr: [2782] loading /var/lib/vdr/plugins/epgsearch/epgsearchcats.conf
Mar 24 00:12:29 vdr vdr: [2782] loading /var/lib/vdr/plugins/epgsearch/epgsearchmenu.conf
Mar 24 00:12:29 vdr vdr: [2782] starting plugin: quickepgsearch
Mar 24 00:12:29 vdr vdr: [2782] starting plugin: vdrmanager
Mar 24 00:12:29 vdr vdr: [2782] starting plugin: tvonscreen
Mar 24 00:12:29 vdr vdr: [2782] starting plugin: femon
Mar 24 00:12:29 vdr vdr: [2782] starting plugin: live
Mar 24 00:12:29 vdr vdr: [2799] [vdrmanager] created non SSL server socket on port 6420
Mar 24 00:12:29 vdr vdr: [2799] [vdrmanager] SSL key files /etc/vdr/plugins/vdrmanager/vdrmanager.pem and /etc/vdr/plugins/vdrmanager/vdrmanager.pem can't be read. SSL disabled.
Mar 24 00:12:29 vdr vdr: [2797] extrecmenu worker thread thread started (pid=2782, tid=2797, prio=high)
Mar 24 00:12:29 vdr vdr: [2798] EPGSearch: conflictcheck thread started (pid=2782, tid=2798, prio=high)
Mar 24 00:12:29 vdr vdr: [2782] LIVE: initial file cache has 82 entries and needs 377394 bytes of data!
Mar 24 00:12:29 vdr vdr: [2782] starting plugin: streamdev-server
Mar 24 00:12:29 vdr vdr: [2782] loading /var/lib/vdr/plugins/streamdev-server/streamdevhosts.conf
Mar 24 00:12:29 vdr vdr: [2782] starting plugin: epgsearchonly
Mar 24 00:12:29 vdr vdr: [2782] starting plugin: skinenigmang
Mar 24 00:12:29 vdr vdr: [2782] starting plugin: skinelchi
Mar 24 00:12:29 vdr vdr: [2782] SkinElchi: using channel logo base dir '/var/lib/vdr/plugins/skinelchi'
Mar 24 00:12:29 vdr vdr: [2782] starting plugin: xineliboutput
Mar 24 00:12:29 vdr vdr: [2800] [live] INFO: attempt to listen on ip = '0.0.0.0'
Mar 24 00:12:29 vdr vdr: [2800] [live] ERROR: Unable to load cert/key (/var/lib/vdr/plugins/live/live.pem//var/lib/vdr/plugins/live/live-key.pem): Datei oder Verzeichnis nicht gefunden
Mar 24 00:12:29 vdr vdr: [2801] streamdev server thread started (pid=2782, tid=2801, prio=high)
Mar 24 00:12:29 vdr vdr: [2802] Remote decoder/display server (cXinelibServer) thread started (pid=2782, tid=2802, prio=high)
Mar 24 00:12:29 vdr vdr: [2801] Streamdev: Listening (VTP) on port 2004
Mar 24 00:12:29 vdr vdr: [2801] Streamdev: Listening (HTTP) on port 3000
Mar 24 00:12:29 vdr vdr: [2802] [xine..put] Have CAP_SYS_NICE capability
Mar 24 00:12:29 vdr vdr: [2802] [xine..put] cXinelibServer priority set successful SCHED_RR 2 [1,99]
Mar 24 00:12:29 vdr vdr: [2802] [xine..put] Binding server to 127.0.0.1:37890
Mar 24 00:12:29 vdr vdr: [2802] [xine..put] Listening on port 37890
Mar 24 00:12:29 vdr vdr: [2802] [xine..put] Listening for UDP broadcasts on port 37890
Mar 24 00:12:29 vdr vdr: [2802] [discovery] BROADCAST: VDR xineliboutput DISCOVERY 1.0#015#012Server port: 37890#015#012Server address: 127.0.0.1#015#012Server version: xineliboutput-2.0.0-cvs#015#012#015
Mar 24 00:12:29 vdr vdr: [2784] video directory scanner thread ended (pid=2782, tid=2784)
Mar 24 00:12:29 vdr vdr: [2782] [xine..put] cXinelibDevice::StartDevice(): Device started
Mar 24 00:12:29 vdr vdr: [2782] starting plugin: skinsoppalusikka
Mar 24 00:12:29 vdr vdr: [2782] starting plugin: dynamite
Mar 24 00:12:29 vdr rsyslogd-2177: imuxsock begins to drop messages from pid 2782 due to rate-limiting

Alles anzeigen

Hier fällt mir auf, das dynamite die Karte wohl zweimal zuweisen will, aber ob das das Problem ist ...?

mini73 · 24. März 2015

Nein, das ist kein Problem, das ist normal.

Vielleicht taugen die C-Kanäle nichts, die du benutzen möchtest. Probiere doch mal, mit w_scan eine channels.conf zu erstellen.

Lars

mini73 · 24. März 2015

Ach ja, dein rsyslog verschluckt Meldungen, weil da zu viele auf mal kommen. Das kann man wegkonfigurieren, vielleicht sieht man dann eher, was da los ist. Ich kann nachher mal suchen, es gibt den Schnipsel aber auch hier irgendwo im Portal.

Lars

rom770 · 25. März 2015

Zitat von mini73

Nein, das ist kein Problem, das ist normal.

Vielleicht taugen die C-Kanäle nichts, die du benutzen möchtest. Probiere doch mal, mit w_scan eine channels.conf zu erstellen.

Habe ich auch schon probiert - nix. Ich werde mir nochmal die Windows-Hardware ausborgen, nicht das inzwischen gar kein Signal mehr ankommt. Da mein Kollege aber gerade im Urlaub ist, werde ich 2 Wochen warten müssen. Aber ich halte Euch auf dem laufenden.

Cine CT V6.1 auf DVB-C umstellen, wie?

Jetzt mitmachen!

Teilen