Hallo zusammen,
ich habe VDR 2.0.6 (vdr-current) 'from source' compiliert inklusive streamdev und live, hat alles funktioniert, kein Thema.
ABER:
Der VDR scheint NICHT auf das DVB-Device zugreifen zu können, ich erhalte immer ein "Error -22 on get_lock_status". Mein System ist ein Ubuntu 13.10 (64bit), meine DVB-Karte funktioniert einwandfrei, unter Kaffeine kann ich ganz normal schauen, kein Problem.
Hier ist mein Log:
Code
Apr 12 21:32:30 vdr: [2769] VDR version 2.0.6 started
Apr 12 21:32:30 vdr: [2769] codeset is 'UTF-8' - known
Apr 12 21:32:30 vdr: [2769] found 28 locales in /usr/local/share/locale
Apr 12 21:32:30 vdr: [2769] loading plugin: /usr/local/lib/vdr/libvdr-streamdev-server.so.2.0.6
Apr 12 21:32:30 vdr: [2769] loading /var/lib/vdr/setup.conf
Apr 12 21:32:30 vdr: [2769] loading /var/lib/vdr/sources.conf
Apr 12 21:32:30 vdr: [2769] loading /var/lib/vdr/diseqc.conf
Apr 12 21:32:30 vdr: [2769] loading /var/lib/vdr/scr.conf
Apr 12 21:32:30 vdr: [2769] loading /var/lib/vdr/channels.conf
Apr 12 21:32:30 vdr: [2769] loading /var/lib/vdr/svdrphosts.conf
Apr 12 21:32:30 vdr: [2769] loading /var/lib/vdr/keymacros.conf
Apr 12 21:32:30 vdr: [2769] registered source parameters for 'A - ATSC'
Apr 12 21:32:30 vdr: [2770] video directory scanner thread started (pid=2769, tid=2770, prio=high)
Apr 12 21:32:30 vdr: [2769] registered source parameters for 'C - DVB-C'
Apr 12 21:32:30 vdr: [2769] registered source parameters for 'S - DVB-S'
Apr 12 21:32:30 vdr: [2769] registered source parameters for 'T - DVB-T'
Apr 12 21:32:30 vdr: [2771] video directory scanner thread started (pid=2769, tid=2771, prio=high)
Apr 12 21:32:30 vdr: [2769] probing /dev/dvb/adapter0/frontend0
Apr 12 21:32:30 vdr: [2769] creating cDvbDevice
Apr 12 21:32:30 vdr: [2772] epg data reader thread started (pid=2769, tid=2772, prio=high)
Apr 12 21:32:30 vdr: [2769] new device number 1
Apr 12 21:32:30 vdr: [2772] reading EPG data from /var/cache/vdr/epg.data
Apr 12 21:32:30 vdr: [2770] video directory scanner thread ended (pid=2769, tid=2770)
Apr 12 21:32:30 vdr: [2771] video directory scanner thread ended (pid=2769, tid=2771)
Apr 12 21:32:30 vdr: [2772] epg data reader thread ended (pid=2769, tid=2772)
Apr 12 21:32:30 vdr: [2769] DVB API version is 0x050A (VDR was built with 0x050A)
Apr 12 21:32:30 vdr: [2769] frontend 0/0 provides DVB-C,(null),DVB-T with QAM16,QAM32,QAM64,QAM128,QAM256 ("DRXK DVB-C DVB-T")
Apr 12 21:32:30 vdr: [2774] tuner on frontend 0/0 thread started (pid=2769, tid=2774, prio=high)
Apr 12 21:32:30 vdr: [2769] cTimeMs: using monotonic clock (resolution is 1 ns)
Apr 12 21:32:30 vdr: [2775] section handler thread started (pid=2769, tid=2775, prio=low)
Apr 12 21:32:30 vdr: [2769] found 1 DVB device
Apr 12 21:32:30 vdr: [2769] initializing plugin: streamdev-server (0.6.1-git): VDR Streaming Server
Apr 12 21:32:30 vdr: [2769] setting primary device to 1
Apr 12 21:32:30 vdr: [2769] device 1 has no MPEG decoder
Apr 12 21:32:30 vdr: [2769] assuming manual start of VDR
Apr 12 21:32:30 vdr: [2769] SVDRP listening on port 6419
Apr 12 21:32:30 vdr: [2769] setting current skin to "lcars"
Apr 12 21:32:30 vdr: [2769] loading /var/lib/vdr/themes/lcars-default.theme
Apr 12 21:32:30 vdr: [2769] starting plugin: streamdev-server
Apr 12 21:32:30 vdr: [2769] loading /var/lib/vdr/plugins/streamdev-server/streamdevhosts.conf
Apr 12 21:32:30 vdr: [2776] streamdev server thread started (pid=2769, tid=2776, prio=high)
Apr 12 21:32:30 vdr: [2769] remote control KBD - learning keys
Apr 12 21:32:30 vdr: [2776] Streamdev: Listening (VTP) on port 2004
Apr 12 21:32:30 vdr: [2776] Streamdev: Listening (HTTP) on port 3000
Apr 12 21:32:30 vdr: [2777] KBD remote control thread started (pid=2769, tid=2777, prio=high)
Apr 12 21:32:30 vdr: [2769] ERROR: no OSD provider available - using dummy OSD!
Apr 12 21:32:30 kernel: [ 939.023606] drxk: Error -22 on get_lock_status
Apr 12 21:32:31 kernel: [ 940.036787] drxk: Error -22 on get_lock_status
Apr 12 21:32:32 kernel: [ 941.050179] drxk: Error -22 on get_lock_status
Apr 12 21:32:33 kernel: [ 942.063396] drxk: Error -22 on get_lock_status
Apr 12 21:32:34 kernel: [ 943.076594] drxk: Error -22 on get_lock_status
Apr 12 21:32:35 kernel: [ 944.089651] drxk: Error -22 on get_lock_status
Apr 12 21:32:36 kernel: [ 945.102746] drxk: Error -22 on get_lock_status
Apr 12 21:32:37 kernel: [ 946.115860] drxk: Error -22 on get_lock_status
Apr 12 21:32:38 kernel: [ 947.128981] drxk: Error -22 on get_lock_status
Apr 12 21:32:39 kernel: [ 948.142129] drxk: Error -22 on get_lock_status
Apr 12 21:32:40 vdr: [2769] switching to channel 1
Apr 12 21:32:40 kernel: [ 949.042657] drxk: Error -22 on get_lock_status
Apr 12 21:32:40 vdr: [2774] ERROR (dvbdevice.c,786): Die Operation wird nicht unterstützt
Apr 12 21:32:40 vdr: [2774] ERROR (dvbdevice.c,787): Die Operation wird nicht unterstützt
Apr 12 21:32:40 vdr: [2774] ERROR: frontend 0/0: Das Argument ist ungültig
Apr 12 21:32:40 vdr: [2769] OSD size changed to 720x480 @ 1
Apr 12 21:32:40 vdr: [2769] ERROR: no OSD provider available - using dummy OSD!
Apr 12 21:32:40 kernel: [ 949.054860] drxk: Error -22 on get_lock_status
Apr 12 21:32:40 kernel: [ 949.076154] drxk: Error -22 on get_lock_status
Apr 12 21:32:40 vdr: [2769] ERROR: Kanal blockiert (zeichnet auf)!
Apr 12 21:32:41 kernel: [ 950.067931] drxk: Error -22 on get_lock_status
Apr 12 21:32:42 kernel: [ 951.081281] drxk: Error -22 on get_lock_status
Apr 12 21:32:42 kernel: [ 951.112077] drxk: Error -22 on get_lock_status
Apr 12 21:32:43 kernel: [ 951.973246] drxk: Error -22 on get_lock_status
Apr 12 21:32:43 kernel: [ 952.094663] drxk: Error -22 on get_lock_status
Apr 12 21:32:44 kernel: [ 952.968287] drxk: Error -22 on get_lock_status
Apr 12 21:32:44 kernel: [ 953.107999] drxk: Error -22 on get_lock_status
Apr 12 21:32:45 kernel: [ 953.973589] drxk: Error -22 on get_lock_status
Apr 12 21:32:45 kernel: [ 954.121248] drxk: Error -22 on get_lock_status
Apr 12 21:32:46 kernel: [ 955.134293] drxk: Error -22 on get_lock_status
Apr 12 21:32:47 kernel: [ 956.147357] drxk: Error -22 on get_lock_status
Apr 12 21:32:48 kernel: [ 957.160618] drxk: Error -22 on get_lock_status
Apr 12 21:32:49 kernel: [ 958.173931] drxk: Error -22 on get_lock_status
Apr 12 21:32:50 kernel: [ 959.187021] drxk: Error -22 on get_lock_status
Apr 12 21:32:51 kernel: [ 960.200306] drxk: Error -22 on get_lock_status
Apr 12 21:32:52 kernel: [ 961.213474] drxk: Error -22 on get_lock_status
Alles anzeigen
Wie gesagt: Unter Kaffeine funktioniert alles wunderbar, es scheint also eine Eigenheit des VDR zu sein.
Bitte helft mir!