Posts by mori

  • wirbelscan auf e-tobi installieren

    Hallo,

    ich hab versucht Wirbelscan- Plugin auf e-tobi aus den sourcen von Wirbelscan zu bauen, leider schlägt das fehl weil da was fehlt...

    Display Spoiler

    root@debian-v8:/usr/local/src/vdr/PLUGINS/src/wirbelscan-0.0.9# make plugins

    Makefile:31: ../../../Make.global: Datei oder Verzeichnis nicht gefunden

    make: *** No rule to make target '../../../Make.global'. Schluss.

    root@debian-v8:/usr/local/src/vdr/PLUGINS/src/wirbelscan-0.0.9#


    ....ich brauch mal ein bisschen Hilfe oder ne schöne Anleitung.

    Danke schon mal und Grüße!

  • Problem mit IPTV und VLC

    Hallochen,

    ich hab ein Problem mit IPTV, Debian Jessi mit e-Tobi Paketen (VDR 2.2.0) und weiß nicht was da schief läuft.......

    syslog

    Display Spoiler

    Dec 4 14:10:45 debian-v8 pulseaudio[21648]: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
    Dec 4 14:10:45 debian-v8 pulseaudio[21648]: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
    Dec 4 14:10:45 debian-v8 vdr[21505]: Dez 4 14:10:17.070 [core.ci] 1/0.0 -> 00 01[0000000001018a18] core interface error: no suitable interface module
    Dec 4 14:10:45 debian-v8 vdr[21505]: [0000000000e08118] core libvlc error: interface "globalhotkeys,none" initialization failed
    Dec 4 14:10:45 debian-v8 vdr[21505]: [0000000001018a18] dbus interface error: Failed to connect to the D-Bus session daemon: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
    Dec 4 14:10:45 debian-v8 vdr[21505]: [0000000001018a18] core interface error: no suitable interface module
    Dec 4 14:10:45 debian-v8 vdr[21505]: [0000000000e08118] core libvlc error: interface "dbus,none" initialization failed
    Dec 4 14:10:45 debian-v8 vdr[21505]: [0000000000ed8548] dummy interface: using the dummy interface module...
    Dec 4 14:10:46 debian-v8 vdr[21505]: [00007f28240009b8] core input error: ES_OUT_RESET_PCR called
    Dec 4 14:10:47 debian-v8 vdr[21505]: [h264 @ 0x7f282c013240] Missing reference picture
    Dec 4 14:10:47 debian-v8 vdr[21505]: [h264 @ 0x7f282c013240] decode_slice_header error
    Dec 4 14:10:47 debian-v8 vdr[21505]: [00007f28280088e8] stream_out_transcode stream out: input interval 66666 (base 2)
    Dec 4 14:10:47 debian-v8 vdr[21505]: [00007f28280088e8] stream_out_transcode stream out: output interval 16666 (base 1)

    ....angezeigt bekomme ich ja ein Bild von meiner Webcam, nur leider in Super-slowmotion,,,,,
    keine Ahnung was da schief läuft

    Grüße

  • vdr 2.0.3 startet ständig neu mit s952 UPDATE

    Hallo,

    hab mein VDR auf neuer HW aufgesetzt mit Wheezy eTobi Paketen und S952 DVB-S2. Treiber neu gebaut und jetzt restartet der VDR in einer endlos Schleife.....

    Display Spoiler

    Mar 16 22:03:19 debian-V8 vdr: [5778] [general.debug] creating standard device 0/0
    Mar 16 22:03:19 debian-V8 vdr: [5778] new device number 1
    Mar 16 22:03:19 debian-V8 vdr: [5781] epg data reader thread ended (pid=5778, tid=5781)
    Mar 16 22:03:19 debian-V8 vdr: [5778] DVB API version is 0x050A (VDR was built with 0x0504)
    Mar 16 22:03:19 debian-V8 vdr: [5778] frontend 0/0 provides DVB-S,DVB-S2 with QPSK ("Montage DS3103/TS2022")
    Mar 16 22:03:19 debian-V8 vdr: [5778] probing /dev/dvb/adapter1/frontend0
    Mar 16 22:03:19 debian-V8 vdr: [5783] tuner on frontend 0/0 thread started (pid=5778, tid=5783, prio=high)
    Mar 16 22:03:19 debian-V8 vdr: [5784] section handler thread started (pid=5778, tid=5784, prio=low)
    Mar 16 22:03:19 debian-V8 vdr: [5778] [general.debug] capturing device 1/0 (subsystem ID 42540952)
    Mar 16 22:03:19 debian-V8 vdr: [5778] [general.debug] creating standard device 1/0
    Mar 16 22:03:19 debian-V8 vdr: [5778] new device number 2
    Mar 16 22:03:19 debian-V8 vdr: [5778] frontend 1/0 provides DVB-S,DVB-S2 with QPSK ("Montage DS3103/TS2022")
    Mar 16 22:03:19 debian-V8 vdr: [5778] found 2 DVB devices
    Mar 16 22:03:19 debian-V8 vdr: [5786] tuner on frontend 1/0 thread started (pid=5778, tid=5786, prio=high)
    Mar 16 22:03:19 debian-V8 vdr: [5787] section handler thread started (pid=5778, tid=5787, prio=low)
    Mar 16 22:03:19 debian-V8 runvdr: restarting VDR
    Mar 16 22:03:19 debian-V8 kernel: [ 348.271845] vdr[5778]: segfault at 7df ip 000000000048e628 sp 00007fff97813c10 error 4 in vdr[400000+165000]
    Mar 16 22:03:19 debian-V8 acpid: input device has been disconnected, fd 7
    Mar 16 22:03:19 debian-V8 acpid: input device has been disconnected, fd 6
    Mar 16 22:03:22 debian-V8 kernel: [ 350.798284] cx23885 driver version 0.0.3 loaded
    Mar 16 22:03:22 debian-V8 kernel: [ 350.798527] CORE cx23885[0]: subsystem: 4254:0952, board: DVBSKY S952 [card=41,autodetected]
    Mar 16 22:03:22 debian-V8 kernel: [ 351.028116] cx25840 6-0044: cx23885 A/V decoder found @ 0x88 (cx23885[0])
    Mar 16 22:03:22 debian-V8 kernel: [ 351.041389] cx25840 6-0044: firmware: agent loaded v4l-cx23885-avcore-01.fw into memory
    Mar 16 22:03:22 debian-V8 kernel: [ 351.639950] cx25840 6-0044: loaded v4l-cx23885-avcore-01.fw firmware (16382 bytes)
    Mar 16 22:03:22 debian-V8 kernel: [ 351.656146] cx23885_dvb_register() allocating 1 frontend(s)
    Mar 16 22:03:22 debian-V8 kernel: [ 351.656150] cx23885[0]: cx23885 based dvb card
    Mar 16 22:03:22 debian-V8 kernel: [ 351.656164] M88DS3103 tuner read stops = 0.
    Mar 16 22:03:22 debian-V8 kernel: [ 351.656633] DS3000 chip version: d0 attached.
    Mar 16 22:03:22 debian-V8 kernel: [ 351.657437] TS202x chip version[1]: c0 attached.
    Mar 16 22:03:23 debian-V8 kernel: [ 351.675379] TS202x chip version[2]: c3 attached.
    Mar 16 22:03:23 debian-V8 kernel: [ 351.722915] m88ds3103_load_firmware: Waiting for firmware upload (dvb-fe-ds3103.fw)...
    Mar 16 22:03:23 debian-V8 kernel: [ 351.726469] cx23885 0000:0e:00.0: firmware: agent loaded dvb-fe-ds3103.fw into memory
    Mar 16 22:03:23 debian-V8 kernel: [ 351.726473] m88ds3103_load_firmware: Waiting for firmware upload(2)...
    Mar 16 22:03:23 debian-V8 kernel: [ 352.616215] DVB: registering new adapter (cx23885[0])
    Mar 16 22:03:23 debian-V8 kernel: [ 352.616218] cx23885 0000:0e:00.0: DVB: registering adapter 0 frontend 0 (Montage DS3103/TS2022)...
    Mar 16 22:03:23 debian-V8 kernel: [ 352.643413] DVBSKY PCIe MAC= 00:17:42:54:09:52
    Mar 16 22:03:23 debian-V8 kernel: [ 352.643415] cx23885_dvb_register() allocating 1 frontend(s)
    Mar 16 22:03:23 debian-V8 kernel: [ 352.643419] cx23885[0]: cx23885 based dvb card
    Mar 16 22:03:23 debian-V8 kernel: [ 352.643427] M88DS3103 tuner read stops = 0.
    Mar 16 22:03:23 debian-V8 kernel: [ 352.643896] DS3000 chip version: d0 attached.
    Mar 16 22:03:23 debian-V8 kernel: [ 352.644698] TS202x chip version[1]: c0 attached.
    Mar 16 22:03:24 debian-V8 kernel: [ 352.663146] TS202x chip version[2]: c3 attached.
    Mar 16 22:03:24 debian-V8 kernel: [ 352.710628] m88ds3103_load_firmware: Waiting for firmware upload (dvb-fe-ds3103.fw)...
    Mar 16 22:03:24 debian-V8 kernel: [ 352.714160] cx23885 0000:0e:00.0: firmware: agent loaded dvb-fe-ds3103.fw into memory
    Mar 16 22:03:24 debian-V8 kernel: [ 352.714163] m88ds3103_load_firmware: Waiting for firmware upload(2)...
    Mar 16 22:03:24 debian-V8 kernel: [ 353.603431] DVB: registering new adapter (cx23885[0])
    Mar 16 22:03:24 debian-V8 kernel: [ 353.603434] cx23885 0000:0e:00.0: DVB: registering adapter 1 frontend 0 (Montage DS3103/TS2022)...
    Mar 16 22:03:24 debian-V8 kernel: [ 353.630596] DVBSKY PCIe MAC= 00:17:42:54:09:53
    Mar 16 22:03:24 debian-V8 kernel: [ 353.630599] cx23885_dev_checkrevision() Hardware revision = 0xa5
    Mar 16 22:03:24 debian-V8 kernel: [ 353.630603] cx23885[0]/0: found at 0000:0e:00.0, rev: 4, irq: 30, latency: 0, mmio: 0xfbe00000
    Mar 16 22:03:24 debian-V8 kernel: [ 353.630611] cx23885 0000:0e:00.0: setting latency timer to 64
    Mar 16 22:03:24 debian-V8 kernel: [ 353.630633] Registered IR keymap rc-dvbsky
    Mar 16 22:03:24 debian-V8 kernel: [ 353.630693] input: cx23885 IR (DVBSKY S952) as /devices/pci0000:00/0000:00:07.0/0000:0e:00.0/rc/rc15/input34
    Mar 16 22:03:24 debian-V8 kernel: [ 353.634379] rc15: cx23885 IR (DVBSKY S952) as /devices/pci0000:00/0000:00:07.0/0000:0e:00.0/rc/rc15
    Mar 16 22:03:24 debian-V8 kernel: [ 353.634674] input: MCE IR Keyboard/Mouse (cx23885) as /devices/virtual/input/input35
    Mar 16 22:03:24 debian-V8 kernel: [ 353.634985] rc rc15: lirc_dev: driver ir-lirc-codec (cx23885) registered at minor = 0
    Mar 16 22:03:40 debian-V8 vdr: [5867] VDR version 2.0.3 started
    Mar 16 22:03:40 debian-V8 vdr: [5867] switched to user 'vdr'
    Mar 16 22:03:40 debian-V8 vdr: [5867] codeset is 'UTF-8' - known
    Mar 16 22:03:40 debian-V8 vdr: [5867] found 28 locales in /usr/share/locale


    hab schon mehrere Treiberversionen versucht, immer das selbe.....
    auf meiner alten Kiste lief das ohne Probleme...

    Update:
    ich glaube das hat was mit dkms zu tun, werden da nicht die Treiber geladen?
    ....denn nach einem reboot kann ich auf der Kiste keine VM starten, erst nachdem ich die vboxdrv neu geladen hab! Kann ich die Treiber für die S952 irgendwie neu laden?

  • bind9 mit isc-dhcp-server probleme

    Hi,

    das ist ein Teil meiner dhcpd.conf mit Bind9 und damit läuft das bei mir ohne Probleme......ich glaub nicht das es was mit Bind9 zu tun hat....

    allow client-updates;
    allow unknown-clients;
    ddns-domainname "workgroup";
    # ddns-update-style none;
    authoritative;
    ddns-update-style interim;
    ddns-updates on;
    update-static-leases on;
    INTERFACES="bond0";

    # This is the key so that DHCP can authenticate it's self to BIND9
    include "/etc/bind/rndc.key";

    # This is the communication zone
    zone workgroup. {
    primary 127.0.0.1;
    key rndc-key;
    }

    subnet 192.168.0.0 netmask 255.255.255.0 {
    option routers 192.168.0.1;
    option subnet-mask 255.255.255.0;
    option domain-name "WORKGROUP";
    #option time-offset 1;
    option broadcast-address 192.168.0.255;
    option domain-name-servers 192.168.0.254, 192.168.0.1;
    range 192.168.0.230 192.168.0.240;
    default-lease-time 21600;
    max-lease-time 43200;

    Grüße

  • Probleme mit externremux.sh

    ...ich hab das jetzt geändert auf bin/bash und jetzt gehts :D ...ursprünglich stand da auch bin/bash und es ging nicht, deshalb hab ich es gänerdert! Warum das jetzt geht weiß ich aber nicht... naja egal, Hauptsache es geht!
    Danke noch mal!!!

    Grüße

  • Probleme mit externremux.sh

    tja, gute Frage....wenn ich das richtig sehe sollte das log in /tmp/... landen, da wird auch ein Ordner z.Bsp. externremux-12345 mit einer Datei out.avi angelegt die aber 0 Bit groß ist...??? Kann man den Pfad in der externremux.sh einstellen? Find da nix.. :(

  • Probleme mit externremux.sh

    OK, jetzt is das mit der nicht gefundenen Datei weg, aber ansonsten noch das gleiche..... :(

    Sep 9 13:23:27 debian-x64 vdr: [19824] Streamdev: Accepted new client (HTTP) 192.168.0.202:17633
    Sep 9 13:23:27 debian-x64 vdr: [20043] streamdev-livestreaming thread started (pid=19791, tid=20043)
    Sep 9 13:23:27 debian-x64 vdr: [20042] streamdev-writer thread started (pid=19791, tid=20042)
    Sep 9 13:23:27 debian-x64 vdr: [20044] receiver on device 2 thread started (pid=19791, tid=20044)
    Sep 9 13:23:27 debian-x64 vdr: [20045] TS buffer on device 2 thread started (pid=19791, tid=20045)
    Sep 9 13:23:28 debian-x64 vdr: [20043] ERROR (extern.c,292): write failed: Datenübergabe unterbrochen (broken pipe)
    Sep 9 13:23:28 debian-x64 vdr: [20043] ERROR (extern.c,292): write failed: Datenübergabe unterbrochen (broken pipe)

    ....muß ich in der plugin.streamdev-server.conf eigentlich noch was mitgeben ausser den Pfad???

  • Probleme mit externremux.sh

    Hallo,

    ich bekomme das Streamen über externremux irgendwie nicht hin... :( normals Streamen funktioniert! Im log steht das die Datei externremux.sh fehlt, sie is aber da und komischer Weise wird sie aber geladen wenn ich das richtig sehe....

    Sep 9 11:01:49 debian-x64 vdr: [16310] Streamdev: Accepted new client (HTTP) 192.168.0.202:11926
    Sep 9 11:01:49 debian-x64 vdr: [16322] streamdev-server =/var/lib/vdr/plugins/streamdev-server/externremux.sh: Datei oder Verzeichnis nicht gefunden
    Sep 9 11:01:49 debian-x64 vdr: [16325] streamdev-livestreaming thread started (pid=16277, tid=16325)
    Sep 9 11:01:49 debian-x64 vdr: [16326] receiver on device 2 thread started (pid=16277, tid=16326)
    Sep 9 11:01:49 debian-x64 vdr: [16324] streamdev-writer thread started (pid=16277, tid=16324)
    Sep 9 11:01:49 debian-x64 vdr: [16327] TS buffer on device 2 thread started (pid=16277, tid=16327)
    Sep 9 11:01:49 debian-x64 vdr: [16323] streamdev-server: EOF reading from externremux
    Sep 9 11:01:50 debian-x64 vdr: [16325] ERROR (extern.c,292): write failed: Datenübergabe unterbrochen (broken pipe)
    Sep 9 11:01:50 debian-x64 vdr: [16325] ERROR (extern.c,292): write failed: Datenübergabe unterbrochen (broken pipe)
    Sep 9 11:01:50 debian-x64 vdr: [16325] ERROR (extern.c,292): write failed: Datenübergabe unterbrochen (broken pipe)
    Sep 9 11:01:50 debian-x64 vdr: [16325] ERROR (extern.c,292): write failed: Datenübergabe unterbrochen (broken pipe)
    Sep 9 11:01:50 debian-x64 vdr: [16325] ERROR (extern.c,292): write failed: Datenübergabe unterbrochen (broken pipe)
    Sep 9 11:01:50 debian-x64 vdr: [16325] ERROR (extern.c,292): write failed: Datenübergabe unterbrochen (broken pipe)

    root@debian-x64:~# ps -ef|grep vdr
    root 16263 1 0 11:00 ? 00:00:00 /bin/sh /usr/sbin/runvdr -v /var/lib/video.00 -c /var/lib/vdr -L /usr/lib/vdr/plugins -r /usr/lib/vdr/vdr-recordingaction -s /usr/lib/vdr/vdr-shutdown.wrapper -E /var/cache/vdr/epg.data -u vdr -g /tmp --port 6419 --lirc -P "sc " -P conflictcheckonly -P "live --port=8008 --ip=0.0.0.0" -P epgsearch -P svdrposd -P quickepgsearch -P "streamdev-server -r=/var/lib/vdr/plugins/streamdev-server/externremux.sh -a user:Isabell.1112" -P epgsearchonly -P svdrpservice --vfat -w 60
    vdr 16277 16263 2 11:00 ? 00:00:27 /usr/bin/vdr -v /var/lib/video.00 -c /var/lib/vdr -L /usr/lib/vdr/plugins -r /usr/lib/vdr/vdr-recordingaction -s /usr/lib/vdr/vdr-shutdown.wrapper -E /var/cache/vdr/epg.data -u vdr -g /tmp --port 6419 --lirc -P sc -P conflictcheckonly -P live --port=8008 --ip=0.0.0.0 -P epgsearch -P svdrposd -P quickepgsearch -P streamdev-server -r=/var/lib/vdr/plugins/streamdev-server/externremux.sh -a user:Isabell.1112 -P epgsearchonly -P svdrpservice --vfat -w 60
    root 16731 16684 0 11:20 pts/2 00:00:00 grep vdr
    vdr 25029 1 0 Sep07 ? 00:00:00 /bin/bash /var/lib/vdr/plugins/streamdev-server/externremux.sh
    vdr 25030 25029 0 Sep07 ? 00:00:00 /bin/bash /var/lib/vdr/plugins/streamdev-server/externremux.sh
    vdr 25031 25030 0 Sep07 ? 00:00:00 logger -t vdr: [25029] externremux.sh
    vdr 25044 25029 0 Sep07 ? 00:00:00 cat /tmp/externremux-23260
    vdr 25116 1 0 Sep07 ? 00:00:00 /bin/bash /var/lib/vdr/plugins/streamdev-server/externremux.sh
    vdr 25117 25116 0 Sep07 ? 00:00:00 /bin/bash /var/lib/vdr/plugins/streamdev-server/externremux.sh
    vdr 25118 25117 0 Sep07 ? 00:00:00 logger -t vdr: [25116] externremux.sh
    vdr 25131 25116 0 Sep07 ? 00:00:00 cat /tmp/externremux-31288
    vdr 28546 1 0 Sep07 ? 00:00:00 sh -c /var/lib/vdr/plugins/streamdev-server/externremux.sh
    vdr 28548 28546 0 Sep07 ? 00:00:00 /bin/bash /var/lib/vdr/plugins/streamdev-server/externremux.sh
    vdr 28549 28548 0 Sep07 ? 00:00:00 /bin/bash /var/lib/vdr/plugins/streamdev-server/externremux.sh
    vdr 28550 28549 0 Sep07 ? 00:00:00 logger -t vdr: [28548] externremux.sh
    vdr 28563 28548 0 Sep07 ? 00:00:00 cat /tmp/externremux-8074
    root@debian-x64:~#

    ...nur wo es jetzt hängt weis ich nicht..... :(

  • hohe CPU last

    OK... das kann schon sein das ich da am Kabel rumbespielt hab und der Emfang weg war, denn das Kabel ist sonst am Server und da geht alles.... jetzt steht auch "nur" "ERROR: driver buffer overflow on device 1" im log....
    wie kann ich den ein Downgrade auf ne andere VDR-Version machen? Auf mein Server läuft zum Bsp. 1.7.28 einwandfrei seit Monaten.....

    Danke

  • hohe CPU last

    Hallochen,

    ich hab ein VDR mit e-tobi Paketen auf Debian 7 x86 aufgesetzt als reinen Streamingserver, also ohne Ausgabe. Das ganze auf ein Asus-Board mit P4 3.20 GHz 2 Kerne 1,5 GB RAM und TT-Budget-CI, bei Aufnahmen von SD geht die CPU-Last auf ca. 25% hoch, genau wie auch beim Streamen und bei HD bis auf über 50% und beim Streamen hackt das Bild nur und in den Aufnahmen auch.....keine Ahnung was da schief läuft....
    Anbei mal ein Auszug aus dem log...

    Display Spoiler

    Jul 11 11:07:15 debian-v7 vdr: [4134] recording thread started (pid=4022, tid=4134, prio=high)
    Jul 11 11:07:15 debian-v7 vdr: [4135] receiver on device 1 thread started (pid=4022, tid=4135, prio=high)
    Jul 11 11:07:15 debian-v7 vdr: [4136] TS buffer on device 1 thread started (pid=4022, tid=4136, prio=high)
    Jul 11 11:07:34 debian-v7 vdr: [4026] frontend 0/0 lost lock on channel 12, tp 110773
    Jul 11 11:07:36 debian-v7 vdr: [4026] frontend 0/0 timed out while tuning to channel 12, tp 110773
    Jul 11 11:07:37 debian-v7 vdr: [4026] frontend 0/0 regained lock on channel 12, tp 110773
    Jul 11 11:08:02 debian-v7 vdr: [4026] frontend 0/0 lost lock on channel 12, tp 110773
    Jul 11 11:08:04 debian-v7 vdr: [4026] frontend 0/0 timed out while tuning to channel 12, tp 110773
    Jul 11 11:08:04 debian-v7 vdr: [4026] frontend 0/0 regained lock on channel 12, tp 110773
    Jul 11 11:08:16 debian-v7 vdr: [4136] buffer usage: 70% (tid=4135)
    Jul 11 11:08:16 debian-v7 vdr: [4136] buffer usage: 80% (tid=4135)
    Jul 11 11:08:17 debian-v7 vdr: [4136] buffer usage: 90% (tid=4135)
    Jul 11 11:08:17 debian-v7 vdr: [4136] buffer usage: 100% (tid=4135)
    Jul 11 11:08:19 debian-v7 vdr: [4136] ERROR: driver buffer overflow on device 1
    Jul 11 11:08:22 debian-v7 vdr: [4136] ERROR: driver buffer overflow on device 1
    Jul 11 11:08:24 debian-v7 vdr: [4136] ERROR: driver buffer overflow on device 1
    Jul 11 11:08:25 debian-v7 vdr: [4135] ERROR: skipped 3898044 bytes to sync on TS packet on device 1
    Jul 11 11:08:25 debian-v7 vdr: [4136] buffer usage: 10% (tid=4135)
    Jul 11 11:08:25 debian-v7 vdr: [4135] ERROR: skipped 233279 bytes to sync on TS packet on device 1
    Jul 11 11:08:31 debian-v7 vdr: [4136] buffer usage: 70% (tid=4135)
    Jul 11 11:08:32 debian-v7 vdr: [4136] buffer usage: 80% (tid=4135)
    Jul 11 11:08:33 debian-v7 vdr: [4136] buffer usage: 90% (tid=4135)
    Jul 11 11:08:40 debian-v7 vdr: [4026] frontend 0/0 lost lock on channel 12, tp 110773
    Jul 11 11:08:42 debian-v7 vdr: [4026] frontend 0/0 timed out while tuning to channel 12, tp 110773
    Jul 11 11:08:42 debian-v7 vdr: [4026] frontend 0/0 regained lock on channel 12, tp 110773
    Jul 11 11:08:42 debian-v7 vdr: [4136] buffer usage: 40% (tid=4135)
    Jul 11 11:08:49 debian-v7 vdr: [4136] buffer usage: 70% (tid=4135)
    Jul 11 11:08:50 debian-v7 vdr: [4136] buffer usage: 80% (tid=4135)
    Jul 11 11:08:50 debian-v7 vdr: [4136] buffer usage: 90% (tid=4135)
    Jul 11 11:08:50 debian-v7 vdr: [4136] buffer usage: 100% (tid=4135)
    Jul 11 11:08:55 debian-v7 vdr: [4136] ERROR: driver buffer overflow on device 1
    Jul 11 11:09:02 debian-v7 vdr: [4135] ERROR: skipped 3354657 bytes to sync on TS packet on device 1
    Jul 11 11:09:02 debian-v7 vdr: [4136] buffer usage: 30% (tid=4135)
    Jul 11 11:09:02 debian-v7 vdr: [4135] ERROR: skipped 814642 bytes to sync on TS packet on device 1
    Jul 11 11:09:08 debian-v7 vdr: [4026] frontend 0/0 lost lock on channel 12, tp 110773
    Jul 11 11:09:10 debian-v7 vdr: [4026] frontend 0/0 timed out while tuning to channel 12, tp 110773
    Jul 11 11:09:10 debian-v7 vdr: [4026] frontend 0/0 regained lock on channel 12, tp 110773
    Jul 11 11:09:18 debian-v7 vdr: [4136] buffer usage: 70% (tid=4135)
    Jul 11 11:09:18 debian-v7 vdr: [4136] buffer usage: 60% (tid=4135)
    Jul 11 11:09:18 debian-v7 vdr: [4136] buffer usage: 70% (tid=4135)
    Jul 11 11:09:19 debian-v7 vdr: [4136] buffer usage: 80% (tid=4135)
    Jul 11 11:09:19 debian-v7 vdr: [4136] buffer usage: 90% (tid=4135)
    Jul 11 11:09:20 debian-v7 vdr: [4136] buffer usage: 100% (tid=4135)
    Jul 11 11:09:25 debian-v7 vdr: [4136] ERROR: driver buffer overflow on device 1
    Jul 11 11:09:28 debian-v7 vdr: [4136] ERROR: driver buffer overflow on device 1


    EDIT: VDR 2.0.0

  • DVB-S2 Treiber Probleme mit TT und S952

    Weil das mit den "Treibern Mischen" nicht so richtig geklappt hat, hab ich mir noch ne dvbsky S952 bestellt und hab das Problem immer noch! Mit einer Karte läuft es einwandfrei und sofern ich die 2. mit einbaue laufen die Clienten ne Weile und dann wird die Verbindung gekappt. Einmal umaschalten und es läuft wieder ne Weile... Hier mal ein Auszug vom Log beim Abbruch, ich kann da nichts sehen was da schief läuft.....


    Mar 17 14:42:16 yaServer vdr: [4858] client (VTP) 192.168.0.199:57912 has closed connection
    Mar 17 14:42:16 yaServer vdr: [4858] streamdev-server: closing VTP connection to 192.168.0.199:57912
    Mar 17 14:42:16 yaServer vdr: [25660] streamdev-livestreaming thread ended (pid=4773, tid=25660)
    Mar 17 14:42:16 yaServer vdr: [25659] streamdev-writer thread ended (pid=4773, tid=25659)
    Mar 17 14:42:16 yaServer vdr: [4858] buffer stats: 417360 (11%) used
    Mar 17 14:42:16 yaServer vdr: [25654] streamdev-filterstreaming thread ended (pid=4773, tid=25654)
    Mar 17 14:42:16 yaServer vdr: [25662] TS buffer on device 1 thread ended (pid=4773, tid=25662)
    Mar 17 14:42:16 yaServer vdr: [25661] buffer stats: 371864 (8%) used
    Mar 17 14:42:16 yaServer vdr: [25661] receiver on device 1 thread ended (pid=4773, tid=25661)
    Mar 17 14:42:17 yaServer vdr: [25653] streamdev-writer thread ended (pid=4773, tid=25653)
    Mar 17 14:42:17 yaServer vdr: [4858] buffer stats: 0 (0%) used
    Mar 17 14:42:17 yaServer vdr: [4858] Streamdev: Accepted new client (VTP) 192.168.0.199:33103
    Mar 17 14:42:44 yaServer vdr: [4858] Streamdev: Setting data connection to 192.168.0.199:56017
    Mar 17 14:42:44 yaServer vdr: [25880] streamdev-writer thread started (pid=4773, tid=25880)
    Mar 17 14:42:44 yaServer vdr: [25881] streamdev-filterstreaming thread started (pid=4773, tid=25881)
    Mar 17 14:42:44 yaServer vdr: [4858] Streamdev: Setting data connection to 192.168.0.199:60619
    Mar 17 14:42:44 yaServer vdr: [25882] streamdev-writer thread started (pid=4773, tid=25882)
    Mar 17 14:42:44 yaServer vdr: [25883] streamdev-livestreaming thread started (pid=4773, tid=25883)
    Mar 17 14:42:44 yaServer vdr: [25884] receiver on device 1 thread started (pid=4773, tid=25884)
    Mar 17 14:42:44 yaServer vdr: [25885] TS buffer on device 1 thread started (pid=4773, tid=25885)
    Mar 17 14:42:46 yaServer vdr: [25883] streamdev-livestreaming thread ended (pid=4773, tid=25883)
    Mar 17 14:42:46 yaServer vdr: [25885] TS buffer on device 1 thread ended (pid=4773, tid=25885)
    Mar 17 14:42:46 yaServer vdr: [25884] buffer stats: 43240 (1%) used
    Mar 17 14:42:46 yaServer vdr: [25884] receiver on device 1 thread ended (pid=4773, tid=25884)
    Mar 17 14:42:46 yaServer vdr: [25882] streamdev-writer thread ended (pid=4773, tid=25882)
    Mar 17 14:42:46 yaServer vdr: [4858] buffer stats: 43616 (1%) used
    Mar 17 14:42:46 yaServer vdr: [4858] Streamdev: Setting data connection to 192.168.0.199:38357
    Mar 17 14:42:46 yaServer vdr: [25886] streamdev-writer thread started (pid=4773, tid=25886)
    Mar 17 14:42:46 yaServer vdr: [25887] streamdev-livestreaming thread started (pid=4773, tid=25887)
    Mar 17 14:42:46 yaServer vdr: [25888] receiver on device 1 thread started (pid=4773, tid=25888)
    Mar 17 14:42:46 yaServer vdr: [25889] TS buffer on device 1 thread started (pid=4773, tid=25889)

    Grüße