( Gelöst) Client Server Kanalwechsel hakt

  • Hallo,


    leider komme ich nicht weiter. Auf dem YAVDR Client (Streamdev-client) hakt der Kanalwechsel. Auf dem openelec client (xvdr) und auf dem Windows XBMC Client läuft alles wunderbar.
    Die Client Server Installation ist frisch installiert. Den gleichen Fehler hatte ich vorher schon bei der Installation von 0.5 Testing. Meine Vermutung geht Richtung Imon/ Soundgraph.


    Hier die Meldung auf dem Client/Server:


    Aug 18 14:14:00 yavdrclient vdr: [991] switching to channel 3
    Aug 18 14:14:00 yavdrclient vdr: [1886] ERROR (device.c,1843): Ungültiger Dateideskriptor
    Aug 18 14:14:00 yavdrclient vdr: [1886] TS buffer on device 24 thread ended (pid=991, tid=1886)
    Aug 18 14:14:00 yavdrclient vdr: [1885] buffer stats: 0 (0%) used
    Aug 18 14:14:00 yavdrclient vdr: [1885] receiver on device 24 thread ended (pid=991, tid=1885)
    Aug 18 14:14:00 yavdrclient vdr: [1897] receiver on device 24 thread started (pid=991, tid=1897)
    Aug 18 14:14:00 yavdrclient vdr: [1898] TS buffer on device 24 thread started (pid=991, tid=1898)
    Aug 18 14:14:01 yavdrclient vdr: [1897] cVideoRepacker: operating in H.264 mode
    Aug 18 14:14:01 yavdrclient vdr: [1897] SetBrokenLink: no GOP header found in video packet
    Aug 18 14:14:05 yavdrclient vdr: [1896] Text2Skin: channelInfo display update thread ended (pid=991, tid=1896)
    Aug 18 14:14:06 yavdrclient kernel: [ 94.408270] init: openbox main process (1888) terminated with status 1
    Aug 18 14:14:06 yavdrclient kernel: [ 94.408301] init: openbox main process ended, respawning
    Aug 18 14:14:06 yavdrclient kernel: [ 94.422142] init: plymouth-stop pre-start process (1901) terminated with status 1
    Aug 18 14:14:06 yavdrclient acpid: client 1895[0:0] has disconnected
    Aug 18 14:14:06 yavdrclient acpid: client connected from 1909[0:0]
    Aug 18 14:14:06 yavdrclient acpid: 1 client rule loaded
    Aug 18 14:14:21 yavdrclient kernel: [ 109.421557] init: openbox main process (1902) terminated with status 1
    Aug 18 14:14:21 yavdrclient kernel: [ 109.421589] init: openbox main process ended, respawning
    Aug 18 14:14:21 yavdrclient kernel: [ 109.435441] init: plymouth-stop pre-start process (1910) terminated with status 1
    Aug 18 14:14:21 yavdrclient acpid: client 1909[0:0] has disconnected
    Aug 18 14:14:21 yavdrclient acpid: client connected from 1918[0:0]
    Aug 18 14:14:21 yavdrclient acpid: 1 client rule loaded
    Aug 18 14:14:30 yavdrclient vdr: [1919] Text2Skin: channelInfo display update thread started (pid=991, tid=1919)
    Aug 18 14:14:31 yavdrclient vdr: [991] switching to channel 4
    Aug 18 14:14:31 yavdrclient vdr: [1898] ERROR (device.c,1843): Ungültiger Dateideskriptor
    Aug 18 14:14:31 yavdrclient vdr: [1898] TS buffer on device 24 thread ended (pid=991, tid=1898)
    Aug 18 14:14:31 yavdrclient vdr: [1897] buffer stats: 312644 (14%) used
    Aug 18 14:14:31 yavdrclient vdr: [1897] receiver on device 24 thread ended (pid=991, tid=1897)
    Aug 18 14:14:31 yavdrclient vdr: [1920] receiver on device 24 thread started (pid=991, tid=1920)
    Aug 18 14:14:31 yavdrclient vdr: [1921] TS buffer on device 24 thread started (pid=991, tid=1921)
    Aug 18 14:14:32 yavdrclient vdr: [1920] cVideoRepacker: switching to MPEG1/2 mode
    Aug 18 14:14:32 yavdrclient vdr: [1920] cVideoRepacker: operating in MPEG1/2 mode
    Aug 18 14:14:32 yavdrclient vdr: [991] switching to channel 4
    Aug 18 14:14:33 yavdrclient vdr: [1921] ERROR (device.c,1843): Ungültiger Dateideskriptor
    Aug 18 14:14:33 yavdrclient vdr: [1921] TS buffer on device 24 thread ended (pid=991, tid=1921)
    Aug 18 14:14:33 yavdrclient vdr: [1920] buffer stats: 6204 (0%) used
    Aug 18 14:14:33 yavdrclient vdr: [1920] receiver on device 24 thread ended (pid=991, tid=1920)
    Aug 18 14:14:33 yavdrclient vdr: [1922] receiver on device 24 thread started (pid=991, tid=1922)
    Aug 18 14:14:33 yavdrclient vdr: [1923] TS buffer on device 24 thread started (pid=991, tid=1923)
    Aug 18 14:14:33 yavdrclient vdr: [1922] cVideoRepacker: switching to MPEG1/2 mode
    Aug 18 14:14:33 yavdrclient vdr: [1922] cVideoRepacker: operating in MPEG1/2 mode
    Aug 18 14:14:36 yavdrclient kernel: [ 124.434779] init: openbox main process (1911) terminated with status 1



    Aug 18 14:14:03 yavdrserver vdr: [925] switching to channel 3
    Aug 18 14:14:03 yavdrserver vdr: [925] info: Streamen im Gange
    Aug 18 14:14:31 yavdrserver vdr: [1700] streamdev-livestreaming thread ended (pid=925, tid=1700)
    Aug 18 14:14:31 yavdrserver vdr: [1699] streamdev-writer thread ended (pid=925, tid=1699)
    Aug 18 14:14:31 yavdrserver vdr: [995] buffer stats: 208116 (5%) used
    Aug 18 14:14:31 yavdrserver vdr: [1705] streamdev-writer thread started (pid=925, tid=1705)
    Aug 18 14:14:31 yavdrserver vdr: [1706] streamdev-livestreaming thread started (pid=925, tid=1706)
    Aug 18 14:14:31 yavdrserver vdr: [1702] TS buffer on device 1 thread ended (pid=925, tid=1702)
    Aug 18 14:14:31 yavdrserver vdr: [1701] buffer stats: 207740 (9%) used
    Aug 18 14:14:31 yavdrserver vdr: [1701] receiver on device 1 thread ended (pid=925, tid=1701)
    Aug 18 14:14:31 yavdrserver vdr: [1707] receiver on device 1 thread started (pid=925, tid=1707)
    Aug 18 14:14:32 yavdrserver vdr: [1708] TS buffer on device 1 thread started (pid=925, tid=1708)
    Aug 18 14:14:32 yavdrserver vdr: [1706] streamdev-livestreaming thread ended (pid=925, tid=1706)
    Aug 18 14:14:32 yavdrserver vdr: [1705] streamdev-writer thread ended (pid=925, tid=1705)
    Aug 18 14:14:32 yavdrserver vdr: [1708] TS buffer on device 1 thread ended (pid=925, tid=1708)
    Aug 18 14:14:32 yavdrserver vdr: [925] switching to channel 3
    Aug 18 14:14:32 yavdrserver vdr: [1707] buffer stats: 26320 (1%) used
    Aug 18 14:14:32 yavdrserver vdr: [1707] receiver on device 1 thread ended (pid=925, tid=1707)
    Aug 18 14:14:32 yavdrserver vdr: [995] Streamdev: Setting data connection to 192.xxx.xxx.xx:42944
    Aug 18 14:14:32 yavdrserver vdr: [1709] streamdev-writer thread started (pid=925, tid=1709)
    Aug 18 14:14:32 yavdrserver vdr: [1710] receiver on device 1 thread started (pid=925, tid=1710)
    Aug 18 14:14:32 yavdrserver vdr: [1711] TS buffer on device 1 thread started (pid=925, tid=1711)
    Aug 18 14:14:32 yavdrserver vdr: [1712] streamdev-livestreaming thread started (pid=925, tid=1712)
    Aug 18 14:14:33 yavdrserver vdr: [1712] streamdev-livestreaming thread ended (pid=925, tid=1712)
    Aug 18 14:14:33 yavdrserver vdr: [1709] streamdev-writer thread ended (pid=925, tid=1709)
    Aug 18 14:14:33 yavdrserver vdr: [1711] TS buffer on device 1 thread ended (pid=925, tid=1711)
    Aug 18 14:14:33 yavdrserver vdr: [995] buffer stats: 6580 (0%) used
    Aug 18 14:14:33 yavdrserver vdr: [1713] streamdev-writer thread started (pid=925, tid=1713)
    Aug 18 14:14:33 yavdrserver vdr: [1710] buffer stats: 206424 (9%) used
    Aug 18 14:14:33 yavdrserver vdr: [1710] receiver on device 1 thread ended (pid=925, tid=1710)
    Aug 18 14:14:33 yavdrserver vdr: [1713] streamdev-writer thread ended (pid=925, tid=1713)
    Aug 18 14:14:33 yavdrserver vdr: [995] Streamdev: Setting data connection to 192.xxx.xxx.xx:57986
    Aug 18 14:14:33 yavdrserver vdr: [1714] streamdev-writer thread started (pid=925, tid=1714)
    Aug 18 14:14:33 yavdrserver vdr: [1715] streamdev-livestreaming thread started (pid=925, tid=1715)
    Aug 18 14:14:33 yavdrserver vdr: [1716] receiver on device 1 thread started (pid=925, tid=1716)
    Aug 18 14:14:33 yavdrserver vdr: [1717] TS buffer on device 1 thread started (pid=925, tid=1717)
    Aug 18 14:14:34 yavdrserver vdr: [925] switching to channel 3
    Aug 18 14:14:34 yavdrserver vdr: [925] info: Kanal nicht verfügbar!
    Aug 18 14:14:36 yavdrserver vdr: [925] switching to channel 4
    Aug 18 14:14:36 yavdrserver vdr: [925] info: Streamen im Gange
    Aug 18 14:14:52 yavdrserver vdr: [1715] streamdev-livestreaming thread ended (pid=925, tid=1715)
    Aug 18 14:14:52 yavdrserver vdr: [925] switching to channel 4
    Aug 18 14:14:52 yavdrserver vdr: [1714] streamdev-writer thread ended (pid=925, tid=1714)
    Aug 18 14:14:52 yavdrserver vdr: [995] buffer stats: 93248 (2%) used
    Aug 18 14:14:52 yavdrserver vdr: [1721] streamdev-writer thread started (pid=925, tid=1721)
    Aug 18 14:14:52 yavdrserver vdr: [1717] TS buffer on device 1 thread ended (pid=925, tid=1717)
    Aug 18 14:14:52 yavdrserver vdr: [1716] buffer stats: 92872 (4%) used


    Auffällig ist der Zeitunterschied. Stimmt der geladene DVB Treiber mit der Cine S2 V6 überein? Könnte IMON Probleme bereiten?


    lspci Server:
    00:00.0 Host bridge: Intel Corporation Ivy Bridge DRAM Controller (rev 09)
    00:01.0 PCI bridge: Intel Corporation Ivy Bridge PCI Express Root Port (rev 09)
    00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
    00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 05)
    00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
    00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
    00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
    00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5)
    00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5)
    00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
    00:1f.0 ISA bridge: Intel Corporation H67 Express Chipset Family LPC Controller (rev 05)
    00:1f.2 IDE interface: Intel Corporation 6 Series/C200 Series Chipset Family 4 port SATA IDE Controller (rev 05)
    00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
    00:1f.5 IDE interface: Intel Corporation 6 Series/C200 Series Chipset Family 2 port SATA IDE Controller (rev 05)
    01:00.0 VGA compatible controller: NVIDIA Corporation Device 0fc1 (rev a1)
    01:00.1 Audio device: NVIDIA Corporation Device 0e1b (rev a1)
    02:00.0 PCI bridge: Integrated Technology Express, Inc. Device 8892 (rev 10)
    04:00.0 Multimedia controller: Digital Devices GmbH Octopus LE DVB adapter
    05:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03)


    Ping Informationen zum Netzwerk (geringer Unterschied zwischen Server und Client)


    --- www.google.de ping statistics ---
    19 packets transmitted, 19 received, 0% packet loss, time 18024ms
    rtt min/avg/max/mdev = 38.997/39.834/41.036/0.566 ms
    Server:
    dmesg |grep DVB
    [ 5.837091] DDBridge driver detected: Digital Devices Cine S2 V6 DVB adapter
    [ 5.848830] Port 0 (TAB 1): DUAL DVB-S2
    [ 5.850880] DVB: registering new adapter (DDBridge)
    [ 5.850881] DVB: registering new adapter (DDBridge)
    [ 6.262926] DDBridge 0000:04:00.0: DVB: registering adapter 0 frontend 0 (STV090x Multistandard)...
    [ 6.304564] DDBridge 0000:04:00.0: DVB: registering adapter 1 frontend 0 (STV090x Multistandard)...


    dmesg | grep ngene
    [ 5.833741] ngene-octopus-test: a8742d5952072f2237cdf28ae4cbb78fa6039f80 ddbridge: Add Digital Devices Cine S2 V6.5


    Client:
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
    Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
    Bus 002 Device 003: ID 15c2:0036 SoundGraph Inc. LC16M VFD Display/IR Receiver

  • Hallo,


    ganz genau kann ich nicht sagen, woran es lag.
    Aber nach einigen Installationen habe ich im Server den Ton getestet. Der war nicht vorhanden. (On Board und Nvidia spielten nicht zusammen). Das Herausnehmen der Karte brachte noch keine Besserung. Aber das zusätzliche installieren des LCDProc plugins auf dem Client machte das System nutzbar.

    YaVDR Server: Intel DH67BL B3 + Intel G1610/ 4x1GB Kingston RAM/64GB SSD/2TB HDD/CineS2 V6/Netzteil Be Quiet Pure Power BQT L7-300W 300Watt / YaVDR- 0.5.0a Headless
    Client 1: Intel DH67CF-B3/ 2x2GB Kingston/ 64 GB SSD/Zotac GeForce GT 640/Origenae M10/ Yavdr 0.5.0
    Client 2: Macbook xbmc
    Client 3: Andoid Tablet Ainol Novo 7 Elf XBMC
    Client 4: Raspberry PI: Openelec Gotham

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!