1. Diese Seite verwendet Cookies. Wenn du dich weiterhin auf dieser Seite aufhältst, akzeptierst du unseren Einsatz von Cookies. Weitere Informationen

Talk yaVDR 0.5 sc von Best Friend startet nicht!

Dieses Thema im Forum "CS VDR-SC" wurde erstellt von mafe68, 4. November 2012.

  1. mafe68
    Offline

    mafe68 Ist oft hier

    Registriert:
    9. August 2011
    Beiträge:
    196
    Zustimmungen:
    70
    Punkte für Erfolge:
    28
    Beruf:
    CVT
    Hallo zusammen!

    Habe folgendes Problem. Habe yaVDR 0.5 mit sc von Best-Friend alles installiert auch sc als erster stelle eingetragen in der order.conf und SoftCam.Key in /etc/vdr/plugins/sc so wie schon oft mal vorher auch schon und meine Line in die /etc/vdr/plugins/sc/cardclient.conf Nach einen Neustart des System bekomme ich nichts hell. Habe hier noch meine syslog angehängt. Ich finde keinen Fehler dort drin. Vier Augen sehen aber mehr als zwei vielleicht findet von euch wer den Fehler.
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] loading /var/lib/vdr/sources.conf
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] loading /var/lib/vdr/diseqc.conf
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] loading /var/lib/vdr/scr.conf
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] loading /var/lib/vdr/channels.conf
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] loading /var/lib/vdr/timers.conf
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] loading /var/lib/vdr/commands.conf
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] loading /var/lib/vdr/reccmds.conf
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] loading /var/lib/vdr/svdrphosts.conf
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] loading /var/lib/vdr/remote.conf
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] loading /var/lib/vdr/keymacros.conf
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] ERROR: unknown plugin 'osdteletext'
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] ERROR: empty key macro
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] ERROR: unknown plugin 'xineliboutput'
    Nov 4 09:22:59 yandr-0-5 vdr: [2160] video directory scanner thread started (pid=2101, tid=2160)
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] registered source parameters for 'A - ATSC'
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] registered source parameters for 'C - DVB-C'
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] registered source parameters for 'S - DVB-S'
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] registered source parameters for 'T - DVB-T'
    Nov 4 09:22:59 yandr-0-5 vdr: [2161] video directory scanner thread started (pid=2101, tid=2161)
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] probing /dev/dvb/adapter0/frontend0
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] dynamite: preparing 8 dynamic device slots for dvb devices
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] new device number 1
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] new device number 2
    Nov 4 09:22:59 yandr-0-5 vdr: [2162] epg data reader thread started (pid=2101, tid=2162)
    Nov 4 09:22:59 yandr-0-5 vdr: [2160] video directory scanner thread ended (pid=2101, tid=2160)
    Nov 4 09:22:59 yandr-0-5 vdr: [2161] video directory scanner thread ended (pid=2101, tid=2161)
    Nov 4 09:22:59 yandr-0-5 vdr: [2162] reading EPG data from /var/cache/vdr/epg.data
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] new device number 3
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] new device number 4
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] new device number 5
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] new device number 6
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] new device number 7
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] new device number 8
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] dynamite: grab dvb device 0/0
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] probing /dev/dvb/adapter1/frontend0
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] dynamite: grab dvb device 1/0
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] found 2 DVB devices
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] initializing plugin: sc (1.0.0pre-AR-29b7b5f231c8): Ein Software emuliertes CAM
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] [general.info] SC version 1.0.0pre-AR-29b7b5f231c8 initializing (VDR 1.7.27)
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] initializing plugin: conflictcheckonly (0.0.1): Direkter Zugriff auf epgsearch's Konflikt-Prüfungs-Menü
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] initializing plugin: wirbelscan (0.0.7): DVB and pvrinput channel scan for VDR
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] initializing plugin: text2skin (1.3.2+git): Lader für textbasierte Skins
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] initializing plugin: iptv (0.5.2): Erlebe IPTV
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] registered source parameters for 'I - IPTV'
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] new device number 15
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] creating IPTV device 0 (CardIndex=14)
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] initializing plugin: streamdev-server (0.6.0-git): VDR Streaming Server
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] initializing plugin: softhddevice (0.5.2): A software and GPU emulated HD device
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] new device number 16
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] initializing plugin: skinpearlhd (0.0.1): PearlHD Skin
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] initializing plugin: epgsearchonly (0.0.1): Direkter Zugriff auf epgsearch's Suchenmenu
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] initializing plugin: femon (1.7.17): DVB Signal Informationsanzeige (OSD)
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] initializing plugin: channellists (0.0.4): Verwalte deine Kanallisten
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] initializing plugin: menuorg (0.4.5): Reorganisiert das Haupmenü
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] loading menuorg config file from /var/lib/vdr/plugins/menuorg.xml
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] initializing plugin: epgsearch (1.0.1.beta2): Suche im EPG nach Wiederholungen und anderem
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] initializing plugin: quickepgsearch (0.0.1): Schnelle Suche nach Sendungen
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] initializing plugin: xvdr (0.9.5): VDR-Network-Streaming-Interface (XVDR) Server
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] initializing plugin: live (0.2.0): Live Interactive VDR Environment
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] initializing plugin: restfulapi (0.1.0): Offers a RESTful-API to retrieve data from VDR
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] initializing plugin: markad (0.1.4pre): Markiere Werbung
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] initializing plugin: extrecmenu (1.2.2): Erweitertes Aufzeichnungs-Menü
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] initializing plugin: dbus2vdr (0.0.8b): control vdr via D-Bus
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] initializing plugin: dynamite (0.0.9f): attach/detach devices on the fly
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] dynamite: creating dynamic device slots as much as possible
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] new device number 17
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] new device number 18
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] new device number 19
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] new device number 20
    Nov 4 09:22:59 yandr-0-5 vdr: [2163] section handler thread started (pid=2101, tid=2163)
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] new device number 21
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] new device number 22
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] dynamite: probing /dev/dvb/adapter0/frontend0
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] dynamite: probing /dev/dvb/adapter1/frontend0
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] dynamite: /dev/dvb/adapter0/frontend0 is a dvb adapter trying to set card index to 0
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] [general.debug] capturing device 0/0 (subsystem ID dd010020)
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] [general.debug] creating standard device 0/0
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] new sub-device number 1
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] frontend 0/0 provides DVB-S,DVB-S2 with QPSK ("STV090x Multistandard")
    Nov 4 09:22:59 yandr-0-5 vdr: [2165] tuner on frontend 0/0 thread started (pid=2101, tid=2165)
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] dynamite: attached device /dev/dvb/adapter0/frontend0 to dynamic device slot 1
    Nov 4 09:22:59 yandr-0-5 vdr: [2166] section handler thread started (pid=2101, tid=2166)
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] dynamite: /dev/dvb/adapter1/frontend0 is a dvb adapter trying to set card index to 1
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] [general.debug] capturing device 1/0 (subsystem ID dd010020)
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] [general.debug] creating standard device 1/0
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] new sub-device number 2
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] frontend 1/0 provides DVB-S,DVB-S2 with QPSK ("STV090x Multistandard")
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] dynamite: attached device /dev/dvb/adapter1/frontend0 to dynamic device slot 2
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] dynamite: /dev/dvb/adapter0/frontend0 is a dvb adapter trying to set card index to 0
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] dynamite: /dev/dvb/adapter0/frontend0 is already attached
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] dynamite: /dev/dvb/adapter1/frontend0 is a dvb adapter trying to set card index to 1
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] dynamite: /dev/dvb/adapter1/frontend0 is already attached
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] setting primary device to 10
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] [softhddev]MakePrimaryDevice: 1
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] [softhddev]SetVideoFormat: 0
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] [softhddev]SetVideoDisplayFormat: 1
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] [softhddev]SetVolumeDevice: 40
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] assuming manual start of VDR
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] SVDRP listening on port 6419
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] skin "PearlHD(native)" not available - using "sttng" instead
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] loading /var/lib/vdr/themes/sttng-default.theme
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] starting plugin: sc
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] [general.info] SC version 1.0.0pre-AR-29b7b5f231c8 starting (VDR 1.7.27)
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] [general.info] loading cardclient config from /var/lib/vdr/plugins/sc/cardclient.conf
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] [general.warn] no write permission on /var/lib/vdr/plugins/sc/cardclient.conf. Changes will not be saved!
    Nov 4 09:22:59 yandr-0-5 vdr: [2168] tuner on frontend 1/0 thread started (pid=2101, tid=2168)
    Nov 4 09:22:59 yandr-0-5 vdr: [2169] section handler thread started (pid=2101, tid=2169)
    Nov 4 09:22:59 yandr-0-5 vdr: [2162] epg data reader thread ended (pid=2101, tid=2162)
    Nov 4 09:22:59 yandr-0-5 vdr: [2170] Netwatcher thread started (pid=2101, tid=2170)
    Nov 4 09:22:59 yandr-0-5 vdr: [2171] CCcam2 reader thread started (pid=2101, tid=2171)
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] [general.error] failed open /var/lib/vdr/plugins/sc/override.conf: Datei oder Verzeichnis nicht gefunden
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] [general.error] failed open /var/lib/vdr/plugins/sc/smartcard.conf: Datei oder Verzeichnis nicht gefunden
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] [general.error] failed open /var/lib/vdr/plugins/sc/cardslot.conf: Datei oder Verzeichnis nicht gefunden
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] [general.info] loading keys from /var/lib/vdr/plugins/sc/SoftCam.Key
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] [general.warn] no write permission on /var/lib/vdr/plugins/sc/SoftCam.Key. Changes will not be saved!
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] [general.info] Using software decryption on card 1/0
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] [general.info] Using software decryption on card 0/0
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] starting plugin: conflictcheckonly
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] starting plugin: wirbelscan
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] starting plugin: text2skin
    Nov 4 09:22:59 yandr-0-5 vdr: [2174] SC housekeeper thread started (pid=2101, tid=2174)
    Nov 4 09:22:59 yandr-0-5 vdr: [2172] SC-CI adapter on device 1/0 thread started (pid=2101, tid=2172)
    Nov 4 09:22:59 yandr-0-5 vdr: [2173] SC-CI adapter on device 0/0 thread started (pid=2101, tid=2173)
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] text2skin: loading /var/lib/vdr/plugins/text2skin/anthra_1920_FS/anthra_1920_FS.colors
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] parsing /var/lib/vdr/plugins/text2skin/anthra_1920_FS/anthra_1920_FS.skin
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] text2skin: loading /var/lib/vdr/plugins/text2skin/anthra_1280_FS/anthra_1280_FS.colors
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] parsing /var/lib/vdr/plugins/text2skin/anthra_1280_FS/anthra_1280_FS.skin
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] text2skin: loading /var/lib/vdr/plugins/text2skin/NarrowHD/NarrowHD.colors
    Nov 4 09:22:59 yandr-0-5 vdr: [2101] parsing /var/lib/vdr/plugins/text2skin/NarrowHD/NarrowHD.skin
    Nov 4 09:23:00 yandr-0-5 vdr: [2101] text2skin: loading /var/lib/vdr/plugins/text2skin/anthra_1280_OS/anthra_1280_OS.colors
    Nov 4 09:23:00 yandr-0-5 vdr: [2101] parsing /var/lib/vdr/plugins/text2skin/anthra_1280_OS/anthra_1280_OS.skin
    Nov 4 09:23:00 yandr-0-5 vdr: [2101] text2skin: loading /var/lib/vdr/plugins/text2skin/anthra_1920_FSE/anthra_1920_FSE.colors
    Nov 4 09:23:00 yandr-0-5 vdr: [2101] parsing /var/lib/vdr/plugins/text2skin/anthra_1920_FSE/anthra_1920_FSE.skin
    Nov 4 09:23:00 yandr-0-5 vdr: [2101] text2skin: loading /var/lib/vdr/plugins/text2skin/anthra_1920_OS/anthra_1920_OS.colors
    Nov 4 09:23:00 yandr-0-5 vdr: [2101] parsing /var/lib/vdr/plugins/text2skin/anthra_1920_OS/anthra_1920_OS.skin
    Nov 4 09:23:00 yandr-0-5 vdr: [2101] starting plugin: iptv
    Nov 4 09:23:00 yandr-0-5 vdr: [2101] starting plugin: streamdev-server
    Nov 4 09:23:00 yandr-0-5 vdr: [2101] loading /var/lib/vdr/plugins/streamdev-server/streamdevhosts.conf
    Nov 4 09:23:00 yandr-0-5 vdr: [2101] starting plugin: softhddevice
    Nov 4 09:23:00 yandr-0-5 vdr: [softhddev] readydetached
    Nov 4 09:23:00 yandr-0-5 vdr: [2101] starting plugin: skinpearlhd
    Nov 4 09:23:00 yandr-0-5 vdr: [2101] starting plugin: epgsearchonly
    Nov 4 09:23:00 yandr-0-5 vdr: [2101] starting plugin: femon
    Nov 4 09:23:00 yandr-0-5 vdr: [2101] starting plugin: channellists
    Nov 4 09:23:00 yandr-0-5 vdr: [2101] starting plugin: menuorg
    Nov 4 09:23:00 yandr-0-5 vdr: [2101] starting plugin: epgsearch
    Nov 4 09:23:00 yandr-0-5 vdr: [2101] loading /var/lib/vdr/plugins/epgsearch/epgsearchcats.conf
    Nov 4 09:23:00 yandr-0-5 vdr: [2101] loading /var/lib/vdr/plugins/epgsearch/epgsearchmenu.conf
    Nov 4 09:23:00 yandr-0-5 vdr: [2175] streamdev server thread started (pid=2101, tid=2175)
    Nov 4 09:23:00 yandr-0-5 vdr: [2101] starting plugin: quickepgsearch
    Nov 4 09:23:00 yandr-0-5 vdr: [2176] EPGSearch: conflictcheck thread started (pid=2101, tid=2176)
    Nov 4 09:23:00 yandr-0-5 vdr: [2175] Streamdev: Listening (VTP) on port 2004
    Nov 4 09:23:00 yandr-0-5 vdr: [2175] Streamdev: Listening (HTTP) on port 3000
    Nov 4 09:23:00 yandr-0-5 vdr: [2101] starting plugin: xvdr
    Nov 4 09:23:00 yandr-0-5 vdr: [2101] XVDR: XVDR Server started
    Nov 4 09:23:00 yandr-0-5 vdr: [2101] XVDR: Channel streaming timeout: 10 seconds
    Nov 4 09:23:00 yandr-0-5 vdr: [2101] starting plugin: live
    Nov 4 09:23:00 yandr-0-5 vdr: [2177] VDR XVDR Server thread started (pid=2101, tid=2177)
    Nov 4 09:23:00 yandr-0-5 vdr: [2101] LIVE: initial file cache has 82 entries and needs 377394 bytes of data!
    Nov 4 09:23:00 yandr-0-5 rsyslogd-2177: imuxsock begins to drop messages from pid 2101 due to rate-limiting
    Nov 4 09:23:03 yandr-0-5 kernel: [ 88.878992] init: wait-for-job-state (vdr-frontendvdr) main process (1041) killed by TERM signal
    Nov 4 09:23:03 yandr-0-5 vdr-frontend[2211]: watching "HOLTEK Wireless 2.4GHz Trackball Keyboard": /dev/input/event2
    Nov 4 09:23:03 yandr-0-5 vdr-frontend[2211]: watching "MCE IR Keyboard/Mouse (mceusb)": /dev/input/event5
    Nov 4 09:23:03 yandr-0-5 vdr-frontend[2211]: started udev monitoring of input devices
    Nov 4 09:23:54 yandr-0-5 rsyslogd-2177: imuxsock lost 134 messages from pid 2101 due to rate-limiting
    Nov 4 09:23:54 yandr-0-5 vdr: video: slow down video, duping frame
    Nov 4 09:23:54 yandr-0-5 vdr: video: 6:34:41.419 +30 352 240/\ms 16+6 v-buf
    Nov 4 09:23:55 yandr-0-5 kernel: [ 140.751479] ata1.00: exception Emask 0x50 SAct 0x0 SErr 0x90800 action 0xe frozen
    Nov 4 09:23:55 yandr-0-5 kernel: [ 140.751485] ata1.00: SError: { HostInt PHYRdyChg 10B8B }
    Nov 4 09:23:55 yandr-0-5 kernel: [ 140.751489] ata1.00: failed command: WRITE DMA
    Nov 4 09:23:55 yandr-0-5 kernel: [ 140.751496] ata1.00: cmd ca/00:08:58:d8:84/00:00:00:00:00/e6 tag 0 dma 4096 out
    Nov 4 09:23:55 yandr-0-5 kernel: [ 140.751497] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x54 (ATA bus error)
    Nov 4 09:23:55 yandr-0-5 kernel: [ 140.751501] ata1.00: status: { DRDY }
    Nov 4 09:23:55 yandr-0-5 kernel: [ 140.751514] ata1.00: hard resetting link
    Nov 4 09:23:57 yandr-0-5 kernel: [ 142.975014] ata1.01: hard resetting link
    Nov 4 09:23:58 yandr-0-5 kernel: [ 144.000967] ata1.01: failed to resume link (SControl 0)
    Nov 4 09:23:58 yandr-0-5 kernel: [ 144.012318] ata1.00: SATA link down (SStatus 21 SControl 300)
    Nov 4 09:23:58 yandr-0-5 kernel: [ 144.012342] ata1.01: SATA link down (SStatus 0 SControl 0)
    Nov 4 09:24:03 yandr-0-5 kernel: [ 148.999023] ata1.00: hard resetting link
    Nov 4 09:24:05 yandr-0-5 kernel: [ 151.206633] ata1.01: hard resetting link
    Nov 4 09:24:06 yandr-0-5 kernel: [ 152.232584] ata1.01: failed to resume link (SControl 0)
    Nov 4 09:24:06 yandr-0-5 kernel: [ 152.243913] ata1.00: SATA link down (SStatus 21 SControl 300)
    Nov 4 09:24:06 yandr-0-5 kernel: [ 152.243938] ata1.01: SATA link down (SStatus 0 SControl 0)
    Nov 4 09:24:06 yandr-0-5 kernel: [ 152.243968] ata1.00: limiting SATA link speed to 1.5 Gbps
    Nov 4 09:24:09 yandr-0-5 vdr: [2168] frontend 1/0 timed out while tuning to channel 14, tp 110743
    Nov 4 09:24:11 yandr-0-5 kernel: [ 157.230642] ata1.00: hard resetting link
    Nov 4 09:24:12 yandr-0-5 kernel: [ 157.554000] ata1.01: hard resetting link
    Nov 4 09:24:13 yandr-0-5 kernel: [ 158.579954] ata1.01: failed to resume link (SControl 0)
    Nov 4 09:24:13 yandr-0-5 kernel: [ 158.735732] ata1.00: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    Nov 4 09:24:13 yandr-0-5 kernel: [ 158.735754] ata1.01: SATA link down (SStatus 0 SControl 0)
    Nov 4 09:24:13 yandr-0-5 kernel: [ 158.744124] ata1.00: configured for UDMA/133
    Nov 4 09:24:13 yandr-0-5 kernel: [ 158.744131] ata1.00: device reported invalid CHS sector 0
    Nov 4 09:24:13 yandr-0-5 kernel: [ 158.744140] ata1: EH complete
    Nov 4 09:24:30 yandr-0-5 vdr: [2168] frontend 1/0 timed out while tuning to channel 33, tp 110773
    Nov 4 09:24:44 yandr-0-5 vdr: video: slow down video, duping frame
    Nov 4 09:24:44 yandr-0-5 vdr: video: 6:35:31.419 +31 369 240/\ms 13+6 v-buf
    Nov 4 09:24:52 yandr-0-5 vdr: [2168] frontend 1/0 timed out while tuning to channel 64, tp 110920
    Nov 4 09:25:13 yandr-0-5 vdr: [2168] frontend 1/0 timed out while tuning to channel 4, tp 111243
    Nov 4 09:25:34 yandr-0-5 vdr: [2168] frontend 1/0 timed out while tuning to channel 1, tp 111302
    Nov 4 09:25:34 yandr-0-5 vdr: video: slow down video, duping frame
     
    #1
  2. phantom

    Nervigen User Advertisement

  3. legenwaitforitdary
    Offline

    legenwaitforitdary Meister

    Registriert:
    12. November 2011
    Beiträge:
    748
    Zustimmungen:
    147
    Punkte für Erfolge:
    43
    AW: yaVDR 0.5 sc von Best Friend startet nicht!

    Geht ein unverschlüsselter Sender überhaupt?
    Die Meldungen am Schluss sehen irgendwie nicht so gut aus.
    Festplatte oder SSD?
    AHCI oder IDE im BIOS eingestellt?
     
    #2
  4. mafe68
    Offline

    mafe68 Ist oft hier

    Registriert:
    9. August 2011
    Beiträge:
    196
    Zustimmungen:
    70
    Punkte für Erfolge:
    28
    Beruf:
    CVT
    AW: yaVDR 0.5 sc von Best Friend startet nicht!

    Hallo!

    Die anderen Sender gehen einwandfrei und bis gestern ist auch alles andere einwandfrei gegangen und ich habe mir dann die yavdr 0.5 installiert da ich vorher noch die yavdr 0.5 Beta drauf hatte und nur die source.list von testing auf stable aktualisiert und da habe ich immer wieder kleine Probleme gehabt.
    System habe ich auf einer SSD und eingestellt ist im Bios IDE
     
    #3
  5. legenwaitforitdary
    Offline

    legenwaitforitdary Meister

    Registriert:
    12. November 2011
    Beiträge:
    748
    Zustimmungen:
    147
    Punkte für Erfolge:
    43
    AW: yaVDR 0.5 sc von Best Friend startet nicht!

    Dann stell es auf AHCI
     
    #4
  6. blondolli
    Offline

    blondolli Newbie

    Registriert:
    9. März 2011
    Beiträge:
    2
    Zustimmungen:
    0
    Punkte für Erfolge:
    0
    AW: yaVDR 0.5 sc von Best Friend startet nicht!

    Hatte ich aus das Problem. Einfach das Script mit dem Editor öffen und dann per Hand..

    also:
    sudo apt-get instal nano
    sudo add-apt-repository ppa:bpl3f1lmootj/yavdr-stable
    sudo apt-get update && sudo apt-get dist-upgrade
    sudo apt-get install vdr-plugin-sc

    Bei mir funktioniert es, leider braucht der VDR jetzt 30 Sekunden bis er ein Bild bringt. Natürlich bei den FTA Sender.

    Oliver
     
    #5
  7. mafe68
    Offline

    mafe68 Ist oft hier

    Registriert:
    9. August 2011
    Beiträge:
    196
    Zustimmungen:
    70
    Punkte für Erfolge:
    28
    Beruf:
    CVT
    AW: yaVDR 0.5 sc von Best Friend startet nicht!

    @

    Dieser Link ist nur für Mitglieder!!! Jetzt kostenlos Registrieren ?



    Habe ich umgestellt aber da wird dann meine SSD nicht angezeigt nur die SATA die ich drin habe für die Aufnahmen

    @

    Dieser Link ist nur für Mitglieder!!! Jetzt kostenlos Registrieren ?


    Danke für die Info aber das Script und Howto ist von mir. Die Installation ist auch durchgelaufen ohne Fehler nur die c:line und keys gehen nicht
     
    #6
  8. blondolli
    Offline

    blondolli Newbie

    Registriert:
    9. März 2011
    Beiträge:
    2
    Zustimmungen:
    0
    Punkte für Erfolge:
    0
    AW: yaVDR 0.5 sc von Best Friend startet nicht!

    ups, bin dann raus :)
     
    #7
  9. mafe68
    Offline

    mafe68 Ist oft hier

    Registriert:
    9. August 2011
    Beiträge:
    196
    Zustimmungen:
    70
    Punkte für Erfolge:
    28
    Beruf:
    CVT
    AW: yaVDR 0.5 sc von Best Friend startet nicht!

    @

    Dieser Link ist nur für Mitglieder!!! Jetzt kostenlos Registrieren ?



    Nein kein Problem ist immer schön wenn jemand versucht den anderen zu helfen. Zu dem sind wir ja hier im Forum :good:

    - - - Aktualisiert - - -

    @

    Dieser Link ist nur für Mitglieder!!! Jetzt kostenlos Registrieren ?


    Habe jetzt umgestell auf AHCI im BIOS aber eine Änderung außer das das System um vieles schneller startet. Wenigstes hier mal ein Erfolg :)
     
    #8
  10. legenwaitforitdary
    Offline

    legenwaitforitdary Meister

    Registriert:
    12. November 2011
    Beiträge:
    748
    Zustimmungen:
    147
    Punkte für Erfolge:
    43
    AW: yaVDR 0.5 sc von Best Friend startet nicht!

    Und dass TRIM genutzt werden kann, aber das ist dann wohl ne andere Baustelle.

    Du hast auch alle für dich relevanten sc-Pakete installiert?

    Zeig mal nach nem Neustart die /var/log/upstart/vdr.log her
     
    #9
  11. mafe68
    Offline

    mafe68 Ist oft hier

    Registriert:
    9. August 2011
    Beiträge:
    196
    Zustimmungen:
    70
    Punkte für Erfolge:
    28
    Beruf:
    CVT
    AW: yaVDR 0.5 sc von Best Friend startet nicht!

    Hier habe ich die log von /var/log/upstart/vdr.log
    root@yandr-0-5:~# tail -n 300 /var/log/syslog
    Nov 4 15:49:20 yandr-0-5 vdr: [1791] reading EPG data from /var/cache/vdr/epg.data
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] initializing plugin: dbus2vdr (0.0.8b): control vdr via D-Bus
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] initializing plugin: dynamite (0.0.9f): attach/detach devices on the fly
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] dynamite: creating dynamic device slots as much as possible
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] new device number 17
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] new device number 18
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] new device number 19
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] new device number 20
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] new device number 21
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] new device number 22
    Nov 4 15:49:20 yandr-0-5 vdr: [1790] video directory scanner thread ended (pid=1730, tid=1790)
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] dynamite: probing /dev/dvb/adapter0/frontend0
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] dynamite: probing /dev/dvb/adapter1/frontend0
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] dynamite: /dev/dvb/adapter0/frontend0 is a dvb adapter trying to set card index to 0
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] [general.debug] capturing device 0/0 (subsystem ID dd010020)
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] [general.debug] creating standard device 0/0
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] new sub-device number 1
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] frontend 0/0 provides DVB-S,DVB-S2 with QPSK ("STV090x Multistandard")
    Nov 4 15:49:20 yandr-0-5 vdr: [1794] tuner on frontend 0/0 thread started (pid=1730, tid=1794)
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] dynamite: attached device /dev/dvb/adapter0/frontend0 to dynamic device slot 1
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] dynamite: /dev/dvb/adapter1/frontend0 is a dvb adapter trying to set card index to 1
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] [general.debug] capturing device 1/0 (subsystem ID dd010020)
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] [general.debug] creating standard device 1/0
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] new sub-device number 2
    Nov 4 15:49:20 yandr-0-5 vdr: [1795] section handler thread started (pid=1730, tid=1795)
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] frontend 1/0 provides DVB-S,DVB-S2 with QPSK ("STV090x Multistandard")
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] dynamite: attached device /dev/dvb/adapter1/frontend0 to dynamic device slot 2
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] dynamite: /dev/dvb/adapter0/frontend0 is a dvb adapter trying to set card index to 0
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] dynamite: /dev/dvb/adapter0/frontend0 is already attached
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] dynamite: /dev/dvb/adapter1/frontend0 is a dvb adapter trying to set card index to 1
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] dynamite: /dev/dvb/adapter1/frontend0 is already attached
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] setting primary device to 10
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] [softhddev]MakePrimaryDevice: 1
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] [softhddev]SetVideoFormat: 0
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] [softhddev]SetVideoDisplayFormat: 1
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] [softhddev]SetVolumeDevice: 10
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] assuming manual start of VDR
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] SVDRP listening on port 6419
    Nov 4 15:49:20 yandr-0-5 vdr: [1797] tuner on frontend 1/0 thread started (pid=1730, tid=1797)
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] skin "PearlHD(native)" not available - using "sttng" instead
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] loading /var/lib/vdr/themes/sttng-default.theme
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] starting plugin: sc
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] [general.info] SC version 1.0.0pre-AR-29b7b5f231c8 starting (VDR 1.7.27)
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] [general.info] loading cardclient config from /var/lib/vdr/plugins/sc/cardclient.conf
    Nov 4 15:49:20 yandr-0-5 vdr: [1730] [general.warn] no write permission on /var/lib/vdr/plugins/sc/cardclient.conf. Changes will not be saved!
    Nov 4 15:49:20 yandr-0-5 vdr: [1798] section handler thread started (pid=1730, tid=1798)
    Nov 4 15:49:20 yandr-0-5 vdr: [1799] Netwatcher thread started (pid=1730, tid=1799)
    Nov 4 15:49:20 yandr-0-5 vdr: [1791] epg data reader thread ended (pid=1730, tid=1791)
    Nov 4 15:49:23 yandr-0-5 vdr: [1800] CCcam2 reader thread started (pid=1730, tid=1800)
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] [general.error] failed open /var/lib/vdr/plugins/sc/override.conf: Datei oder Verzeichnis nicht gefunden
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] [general.error] failed open /var/lib/vdr/plugins/sc/smartcard.conf: Datei oder Verzeichnis nicht gefunden
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] [general.error] failed open /var/lib/vdr/plugins/sc/cardslot.conf: Datei oder Verzeichnis nicht gefunden
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] [general.info] loading keys from /var/lib/vdr/plugins/sc/SoftCam.Key
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] [general.warn] no write permission on /var/lib/vdr/plugins/sc/SoftCam.Key. Changes will not be saved!
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] [general.info] Using software decryption on card 1/0
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] [general.info] Using software decryption on card 0/0
    Nov 4 15:49:23 yandr-0-5 vdr: [1801] SC-CI adapter on device 1/0 thread started (pid=1730, tid=1801)
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] starting plugin: conflictcheckonly
    Nov 4 15:49:23 yandr-0-5 vdr: [1802] SC-CI adapter on device 0/0 thread started (pid=1730, tid=1802)
    Nov 4 15:49:23 yandr-0-5 vdr: [1803] SC housekeeper thread started (pid=1730, tid=1803)
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] starting plugin: wirbelscan
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] starting plugin: text2skin
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] text2skin: loading /var/lib/vdr/plugins/text2skin/anthra_1920_FS/anthra_1920_FS.colors
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] parsing /var/lib/vdr/plugins/text2skin/anthra_1920_FS/anthra_1920_FS.skin
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] text2skin: loading /var/lib/vdr/plugins/text2skin/anthra_1280_FS/anthra_1280_FS.colors
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] parsing /var/lib/vdr/plugins/text2skin/anthra_1280_FS/anthra_1280_FS.skin
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] text2skin: loading /var/lib/vdr/plugins/text2skin/NarrowHD/NarrowHD.colors
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] parsing /var/lib/vdr/plugins/text2skin/NarrowHD/NarrowHD.skin
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] text2skin: loading /var/lib/vdr/plugins/text2skin/anthra_1280_OS/anthra_1280_OS.colors
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] parsing /var/lib/vdr/plugins/text2skin/anthra_1280_OS/anthra_1280_OS.skin
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] text2skin: loading /var/lib/vdr/plugins/text2skin/anthra_1920_FSE/anthra_1920_FSE.colors
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] parsing /var/lib/vdr/plugins/text2skin/anthra_1920_FSE/anthra_1920_FSE.skin
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] text2skin: loading /var/lib/vdr/plugins/text2skin/anthra_1920_OS/anthra_1920_OS.colors
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] parsing /var/lib/vdr/plugins/text2skin/anthra_1920_OS/anthra_1920_OS.skin
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] starting plugin: iptv
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] starting plugin: streamdev-server
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] loading /var/lib/vdr/plugins/streamdev-server/streamdevhosts.conf
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] starting plugin: softhddevice
    Nov 4 15:49:23 yandr-0-5 vdr: [softhddev] readydetached
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] starting plugin: skinpearlhd
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] starting plugin: epgsearchonly
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] starting plugin: femon
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] starting plugin: channellists
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] starting plugin: menuorg
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] starting plugin: epgsearch
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] loading /var/lib/vdr/plugins/epgsearch/epgsearchcats.conf
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] loading /var/lib/vdr/plugins/epgsearch/epgsearchmenu.conf
    Nov 4 15:49:23 yandr-0-5 vdr: [1804] streamdev server thread started (pid=1730, tid=1804)
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] starting plugin: quickepgsearch
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] starting plugin: xvdr
    Nov 4 15:49:23 yandr-0-5 vdr: [1805] EPGSearch: conflictcheck thread started (pid=1730, tid=1805)
    Nov 4 15:49:23 yandr-0-5 vdr: [1804] Streamdev: Listening (VTP) on port 2004
    Nov 4 15:49:23 yandr-0-5 vdr: [1804] Streamdev: Listening (HTTP) on port 3000
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] XVDR: XVDR Server started
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] XVDR: Channel streaming timeout: 10 seconds
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] starting plugin: live
    Nov 4 15:49:23 yandr-0-5 vdr: [1806] VDR XVDR Server thread started (pid=1730, tid=1806)
    Nov 4 15:49:23 yandr-0-5 vdr: [1730] LIVE: initial file cache has 82 entries and needs 377394 bytes of data!
    Nov 4 15:49:23 yandr-0-5 rsyslogd-2177: imuxsock begins to drop messages from pid 1730 due to rate-limiting
    Nov 4 15:49:26 yandr-0-5 rsyslogd-2177: imuxsock lost 39 messages from pid 1730 due to rate-limiting
    Nov 4 15:49:26 yandr-0-5 vdr: [1801] CAM 1: replies to QUERY - multi channel decryption possible
    Nov 4 15:49:26 yandr-0-5 vdr: [1802] CAM 2: replies to QUERY - multi channel decryption possible
    Nov 4 15:49:27 yandr-0-5 vdr: [1730] switching to channel 88
    Nov 4 15:49:27 yandr-0-5 vdr: [1825] receiver on device 1 thread started (pid=1730, tid=1825)
    Nov 4 15:49:27 yandr-0-5 vdr: [1730] [softhddev]SetVolumeDevice: 10
    Nov 4 15:49:27 yandr-0-5 vdr: [1730] [softhddev]SetPlayMode: 1
    Nov 4 15:49:27 yandr-0-5 vdr: [1826] TS buffer on device 1 thread started (pid=1730, tid=1826)
    Nov 4 15:49:27 yandr-0-5 vdr: [1730] OSD size changed to 1920x1080 @ 1
    Nov 4 15:49:27 yandr-0-5 vdr: [1730] dbus2vdr: raise SIGSTOP for Upstart
    Nov 4 15:49:27 yandr-0-5 vdr: [1730] dbus2vdr: new DBus-Upstart-Signal-Sender
    Nov 4 15:49:27 yandr-0-5 vdr: [1730] dbus2vdr: emit upstart-signal started for all plugins
    Nov 4 15:49:27 yandr-0-5 vdr: [1730] dbus2vdr: upstart-signal started queued
    Nov 4 15:49:27 yandr-0-5 vdr: [1827] dbus2vdr: DBus-Upstart-Signal-Sender thread started (pid=1730, tid=1827)
    Nov 4 15:49:27 yandr-0-5 vdr: [1827] dbus2vdr: dequeue signal vdr-plugin/started
    Nov 4 15:49:27 yandr-0-5 vdr: [1827] dbus2vdr: retrieving connection for sending signal
    Nov 4 15:49:27 yandr-0-5 vdr: [1827] dbus2vdr: SendSignal Lock
    Nov 4 15:49:27 yandr-0-5 vdr: [1827] dbus2vdr: SendSignal Unlock
    Nov 4 15:49:27 yandr-0-5 vdr: [1827] dbus2vdr: SendSignal: dbus_connection_send
    Nov 4 15:49:27 yandr-0-5 vdr: [1827] dbus2vdr: SendSignal: dbus_message_unref
    Nov 4 15:49:27 yandr-0-5 vdr: [1827] dbus2vdr: signal sent
    Nov 4 15:49:27 yandr-0-5 vdr: [1827] dbus2vdr: emit upstart-signal vdr-plugin for started
    Nov 4 15:49:27 yandr-0-5 kernel: [ 90.503278] init: wait-for-job-state (vdr-frontendvdr) main process (990) killed by TERM signal
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: connection has messages to send, flushing
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: done flushing
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: new message, object /Plugins/softhddevice, interface org.freedesktop.DBus.Introspectable, member Introspect
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: introspect object /Plugins/softhddevice with Introspect
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: new message, object /Remote, interface org.freedesktop.DBus.Introspectable, member Introspect
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: introspect object /Remote with Introspect
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: new message, object /Shutdown, interface org.freedesktop.DBus.Introspectable, member Introspect
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: introspect object /Shutdown with Introspect
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: new message, object /Setup, interface org.freedesktop.DBus.Introspectable, member Introspect
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: introspect object /Setup with Introspect
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: new message, object /Shutdown, interface de.tvdr.vdr.shutdown, member ManualStart
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: starting new message handler 0x7fe3500055a0
    Nov 4 15:49:27 yandr-0-5 vdr: [1845] dbus2vdr message handler thread started (pid=1730, tid=1845)
    Nov 4 15:49:27 yandr-0-5 vdr: [1845] dbus2vdr: moving message handler 0x7fe3500055a0 from active to finished
    Nov 4 15:49:27 yandr-0-5 vdr: [1845] dbus2vdr message handler thread ended (pid=1730, tid=1845)
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: connection has messages to send, flushing
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: done flushing
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: new message, object /Plugins, interface org.freedesktop.DBus.Introspectable, member Introspect
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: introspect object /Plugins with Introspect
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: can't introspect object /Plugins
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: new message, object /Plugins, interface de.tvdr.vdr.plugin, member List
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: 1 idle message handler, reusing 0x7fe3500055a0
    Nov 4 15:49:27 yandr-0-5 vdr: [1846] dbus2vdr message handler thread started (pid=1730, tid=1846)
    Nov 4 15:49:27 yandr-0-5 vdr: [1846] dbus2vdr: moving message handler 0x7fe3500055a0 from active to finished
    Nov 4 15:49:27 yandr-0-5 vdr: [1846] dbus2vdr message handler thread ended (pid=1730, tid=1846)
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: connection has messages to send, flushing
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: done flushing
    Nov 4 15:49:27 yandr-0-5 vdr-frontend[1841]: watching "HOLTEK Wireless 2.4GHz Trackball Keyboard": /dev/input/event2
    Nov 4 15:49:27 yandr-0-5 vdr-frontend[1841]: watching "MCE IR Keyboard/Mouse (mceusb)": /dev/input/event5
    Nov 4 15:49:27 yandr-0-5 vdr-frontend[1841]: started udev monitoring of input devices
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: new message, object /Plugins/softhddevice, interface de.tvdr.vdr.plugin, member SVDRPCommand
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: 1 idle message handler, reusing 0x7fe3500055a0
    Nov 4 15:49:27 yandr-0-5 vdr: [1847] dbus2vdr message handler thread started (pid=1730, tid=1847)
    Nov 4 15:49:27 yandr-0-5 vdr: [1847] dbus2vdr: invoking softhddevice.SVDRPCommand("STAT", "None")
    Nov 4 15:49:27 yandr-0-5 vdr: [1847] dbus2vdr: moving message handler 0x7fe3500055a0 from active to finished
    Nov 4 15:49:27 yandr-0-5 vdr: [1847] dbus2vdr message handler thread ended (pid=1730, tid=1847)
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: connection has messages to send, flushing
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: done flushing
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: new message, object /Plugins/softhddevice, interface de.tvdr.vdr.plugin, member SVDRPCommand
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: 1 idle message handler, reusing 0x7fe3500055a0
    Nov 4 15:49:27 yandr-0-5 vdr: [1849] dbus2vdr message handler thread started (pid=1730, tid=1849)
    Nov 4 15:49:27 yandr-0-5 vdr: [1849] dbus2vdr: invoking softhddevice.SVDRPCommand("ATTA", "-d :1.0")
    Nov 4 15:49:27 yandr-0-5 vdr: video/vdpau: VDPAU API version: 1
    Nov 4 15:49:27 yandr-0-5 vdr: video/vdpau: VDPAU information: NVIDIA VDPAU Driver Shared Library 304.51 Tue Sep 18 17:40:30 PDT 2012
    Nov 4 15:49:27 yandr-0-5 vdr: video/vdpau: highest supported high quality scaling 1
    Nov 4 15:49:27 yandr-0-5 vdr: video/vdpau: feature deinterlace temporal supported
    Nov 4 15:49:27 yandr-0-5 vdr: video/vdpau: feature deinterlace temporal spatial supported
    Nov 4 15:49:27 yandr-0-5 vdr: video/vdpau: attribute skip chroma deinterlace supported
    Nov 4 15:49:27 yandr-0-5 vdr: video/vdpau: 4:2:0 chroma format with 4096x4096 supported
    Nov 4 15:49:27 yandr-0-5 vdr: video/vdpau: 4:2:2 chroma format with 4096x4096 supported
    Nov 4 15:49:27 yandr-0-5 vdr: video/vdpau: 8bit BGRA format with 16384x16384 supported
    Nov 4 15:49:27 yandr-0-5 vdr: video/vdpau: 10bit RGBA format with 16384x16384 supported
    Nov 4 15:49:27 yandr-0-5 vdr: audio: 'alsa' output module used
    Nov 4 15:49:27 yandr-0-5 vdr: audio/alsa: supports pause: no
    Nov 4 15:49:27 yandr-0-5 vdr: audio: 44100Hz supports 1 2 3 4 5 6 7 8 channels
    Nov 4 15:49:27 yandr-0-5 vdr: audio: 48000Hz supports 1 2 3 4 5 6 7 8 channels
    Nov 4 15:49:27 yandr-0-5 vdr: [1849] dbus2vdr: moving message handler 0x7fe3500055a0 from active to finished
    Nov 4 15:49:27 yandr-0-5 vdr: [1849] dbus2vdr message handler thread ended (pid=1730, tid=1849)
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: connection has messages to send, flushing
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: done flushing
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: new message, object /Remote, interface de.tvdr.vdr.remote, member Enable
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: 1 idle message handler, reusing 0x7fe3500055a0
    Nov 4 15:49:27 yandr-0-5 vdr: [1851] dbus2vdr message handler thread started (pid=1730, tid=1851)
    Nov 4 15:49:27 yandr-0-5 vdr: [1851] dbus2vdr: moving message handler 0x7fe3500055a0 from active to finished
    Nov 4 15:49:27 yandr-0-5 vdr: [1851] dbus2vdr message handler thread ended (pid=1730, tid=1851)
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: connection has messages to send, flushing
    Nov 4 15:49:27 yandr-0-5 vdr: [1817] dbus2vdr: done flushing
    Nov 4 15:49:27 yandr-0-5 vdr: audio/alsa: using device 'default'
    Nov 4 15:49:27 yandr-0-5 vdr: audio/alsa: start delay 336ms
    Nov 4 15:49:27 yandr-0-5 vdr: [1805] EPGSearch: timer conflict check started
    Nov 4 15:49:27 yandr-0-5 vdr: [1805] EPGSearch: timer conflict check finished
    Nov 4 15:50:31 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 14, tp 110743
    Nov 4 15:50:53 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 33, tp 110773
    Nov 4 15:51:12 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 64, tp 110920
    Nov 4 15:51:36 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 4, tp 111243
    Nov 4 15:51:56 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 1, tp 111302
    Nov 4 15:52:17 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 19, tp 111361
    Nov 4 15:52:37 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 12, tp 111493
    Nov 4 15:52:58 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 18, tp 111582
    Nov 4 15:53:19 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 130, tp 111670
    Nov 4 15:53:39 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 75, tp 111719
    Nov 4 15:54:00 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 37, tp 111758
    Nov 4 15:54:21 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 76, tp 111797
    Nov 4 15:54:43 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 44, tp 111875
    Nov 4 15:55:03 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 41, tp 111914
    Nov 4 15:55:25 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 45, tp 111992
    Nov 4 15:55:46 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 51, tp 112031
    Nov 4 15:56:06 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 40, tp 112070
    Nov 4 15:56:28 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 29, tp 112187
    Nov 4 15:56:49 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 26, tp 112226
    Nov 4 15:57:09 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 48, tp 112304
    Nov 4 15:57:30 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 38, tp 112344
    Nov 4 15:57:51 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 42, tp 112382
    Nov 4 15:58:14 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 13, tp 112421
    Nov 4 15:58:33 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 24, tp 112544
    Nov 4 15:58:55 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 3, tp 112662
    Nov 4 15:59:15 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 7, tp 112692
    Nov 4 15:59:37 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 9, tp 211347
    Nov 4 15:59:58 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 6, tp 212051
    Nov 4 16:00:18 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 34, tp 212480
    Nov 4 16:00:26 yandr-0-5 vdr: [1730] switching to channel 89
    Nov 4 16:00:26 yandr-0-5 vdr: [1730] [softhddev]SetPlayMode: 0
    Nov 4 16:00:26 yandr-0-5 vdr: [1730] [softhddev]SetVideoDisplayFormat: 1
    Nov 4 16:00:26 yandr-0-5 vdr: [1826] TS buffer on device 1 thread ended (pid=1730, tid=1826)
    Nov 4 16:00:26 yandr-0-5 vdr: [1825] buffer stats: 2820 (0%) used
    Nov 4 16:00:26 yandr-0-5 vdr: [1825] receiver on device 1 thread ended (pid=1730, tid=1825)
    Nov 4 16:00:26 yandr-0-5 vdr: [2038] receiver on device 1 thread started (pid=1730, tid=2038)
    Nov 4 16:00:26 yandr-0-5 vdr: [1730] [softhddev]SetPlayMode: 1
    Nov 4 16:00:26 yandr-0-5 vdr: [2039] TS buffer on device 1 thread started (pid=1730, tid=2039)
    Nov 4 16:00:26 yandr-0-5 vdr: audio/alsa: using device 'default'
    Nov 4 16:00:26 yandr-0-5 vdr: audio/alsa: start delay 336ms
    Nov 4 16:00:27 yandr-0-5 vdr: video: decoder buffer empty, duping frame (1/6) 2 v-buf
    Nov 4 16:00:27 yandr-0-5 vdr: video: 14:42:04.917+8888 0 0/\ms 2+5 v-buf
    Nov 4 16:00:27 yandr-0-5 vdr: video/vdpau: missed frame (1/10)
    Nov 4 16:00:27 yandr-0-5 vdr: video/vdpau: missed frame (2/10)
    Nov 4 16:00:27 yandr-0-5 vdr: video: decoder buffer empty, duping frame (2/10) 3 v-buf
    Nov 4 16:00:27 yandr-0-5 vdr: video: 14:42:04.997+8888 0 0/\ms 3+5 v-buf
    Nov 4 16:00:27 yandr-0-5 vdr: audio/alsa: using device 'default'
    Nov 4 16:00:27 yandr-0-5 vdr: video: decoder buffer empty, duping frame (7/16) 0 v-buf
    Nov 4 16:00:27 yandr-0-5 vdr: video: slow down video, duping frame
    Nov 4 16:00:27 yandr-0-5 vdr: video: 14:42:05.117 +816 343 0/\ms 2+5 v-buf
    Nov 4 16:00:27 yandr-0-5 vdr: audio/alsa: start delay 336ms
    Nov 4 16:00:30 yandr-0-5 vdr: [1730] switching to channel 88
    Nov 4 16:00:30 yandr-0-5 vdr: [1730] [softhddev]SetPlayMode: 0
    Nov 4 16:00:30 yandr-0-5 vdr: [1730] [softhddev]SetVideoDisplayFormat: 1
    Nov 4 16:00:30 yandr-0-5 vdr: [2039] TS buffer on device 1 thread ended (pid=1730, tid=2039)
    Nov 4 16:00:30 yandr-0-5 vdr: [2038] buffer stats: 150776 (3%) used
    Nov 4 16:00:30 yandr-0-5 vdr: [2038] receiver on device 1 thread ended (pid=1730, tid=2038)
    Nov 4 16:00:30 yandr-0-5 vdr: [2040] receiver on device 1 thread started (pid=1730, tid=2040)
    Nov 4 16:00:30 yandr-0-5 vdr: [1730] [softhddev]SetPlayMode: 1
    Nov 4 16:00:30 yandr-0-5 vdr: audio/alsa: wait underrun error? 'Datenübergabe unterbrochen (broken pipe)'
    Nov 4 16:00:30 yandr-0-5 vdr: [2041] TS buffer on device 1 thread started (pid=1730, tid=2041)
    Nov 4 16:00:30 yandr-0-5 vdr: audio/alsa: using device 'default'
    Nov 4 16:00:30 yandr-0-5 vdr: audio/alsa: start delay 336ms
    Nov 4 16:00:30 yandr-0-5 vdr: audio/alsa: using device 'default'
    Nov 4 16:00:30 yandr-0-5 vdr: audio/alsa: start delay 336ms
    Nov 4 16:00:31 yandr-0-5 vdr: video: slow down video, duping frame
    Nov 4 16:00:31 yandr-0-5 vdr: video: decoder buffer empty, duping frame (79/184) 0 v-buf
    Nov 4 16:00:31 yandr-0-5 vdr: video: --:--:--.--- +0 0 0/\ms 0+5 v-buf
    Nov 4 16:00:34 yandr-0-5 vdr: [1730] switching to channel 89
    Nov 4 16:00:34 yandr-0-5 vdr: [1730] [softhddev]SetPlayMode: 0
    Nov 4 16:00:34 yandr-0-5 vdr: [1730] [softhddev]SetVideoDisplayFormat: 1
    Nov 4 16:00:34 yandr-0-5 vdr: [2041] TS buffer on device 1 thread ended (pid=1730, tid=2041)
    Nov 4 16:00:34 yandr-0-5 vdr: [2040] buffer stats: 2632 (0%) used
    Nov 4 16:00:34 yandr-0-5 vdr: [2040] receiver on device 1 thread ended (pid=1730, tid=2040)
    Nov 4 16:00:34 yandr-0-5 vdr: [2042] receiver on device 1 thread started (pid=1730, tid=2042)
    Nov 4 16:00:34 yandr-0-5 vdr: [1730] [softhddev]SetPlayMode: 1
    Nov 4 16:00:35 yandr-0-5 vdr: [2043] TS buffer on device 1 thread started (pid=1730, tid=2043)
    Nov 4 16:00:35 yandr-0-5 vdr: audio/alsa: using device 'default'
    Nov 4 16:00:35 yandr-0-5 vdr: [softhddev] invalid PES video packet
    Nov 4 16:00:35 yandr-0-5 vdr: [softhddev] invalid PES video packet
    Nov 4 16:00:35 yandr-0-5 vdr: audio/alsa: start delay 336ms
    Nov 4 16:00:35 yandr-0-5 vdr: video: decoder buffer empty, duping frame (176/184) 0 v-buf
    Nov 4 16:00:35 yandr-0-5 vdr: video/vdpau: missed frame (3/8)
    Nov 4 16:00:35 yandr-0-5 vdr: video: decoder buffer empty, duping frame (177/8) 0 v-buf
    Nov 4 16:00:35 yandr-0-5 vdr: video: 14:42:13.837+8888 0 0/\ms 0+5 v-buf
    Nov 4 16:00:35 yandr-0-5 vdr: video: decoder buffer empty, duping frame (178/8) 0 v-buf
    Nov 4 16:00:35 yandr-0-5 vdr: video/vdpau: missed frame (4/10)
    Nov 4 16:00:35 yandr-0-5 vdr: video: decoder buffer empty, duping frame (179/12) 0 v-buf
    Nov 4 16:00:35 yandr-0-5 vdr: video: 14:42:13.917+8888 0 0/\ms 0+5 v-buf
    Nov 4 16:00:36 yandr-0-5 vdr: audio/alsa: using device 'default'
    Nov 4 16:00:36 yandr-0-5 vdr: audio/alsa: start delay 336ms
    Nov 4 16:00:36 yandr-0-5 vdr: video: decoder buffer empty, duping frame (187/36) 0 v-buf
    Nov 4 16:00:36 yandr-0-5 vdr: video: slow down video, duping frame
    Nov 4 16:00:36 yandr-0-5 vdr: video: 14:42:14.397+1205 380 0/\ms 1+7 v-buf
    Nov 4 16:01:23 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 34, tp 212480
    Nov 4 16:01:25 yandr-0-5 vdr: video: slow down video, duping frame
    Nov 4 16:01:25 yandr-0-5 vdr: video: 14:43:02.477 +36 332 0/\ms 30+6 v-buf
    Nov 4 16:01:45 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 14, tp 110743
    Nov 4 16:02:06 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 33, tp 110773
    Nov 4 16:02:15 yandr-0-5 vdr: video: slow down video, duping frame
    Nov 4 16:02:15 yandr-0-5 vdr: video: 14:43:52.477 +38 398 0/\ms 27+6 v-buf
    Nov 4 16:02:28 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 64, tp 110920
    Nov 4 16:02:47 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 4, tp 111243
    Nov 4 16:03:05 yandr-0-5 vdr: video: slow down video, duping frame
    Nov 4 16:03:05 yandr-0-5 vdr: video: 14:44:42.477 +40 390 0/\ms 29+6 v-buf
    Nov 4 16:03:10 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 1, tp 111302
    Nov 4 16:03:31 yandr-0-5 vdr: [1797] frontend 1/0 timed out while tuning to channel 19, tp 111361
    root@yandr-0-5:~#
     
    #10
  12. legenwaitforitdary
    Offline

    legenwaitforitdary Meister

    Registriert:
    12. November 2011
    Beiträge:
    748
    Zustimmungen:
    147
    Punkte für Erfolge:
    43
    AW: yaVDR 0.5 sc von Best Friend startet nicht!

    Ist zwar die falsche Datei, aber mal ne andere frage: Hast du zwei seperate Kabel angeshlossen?
     
    #11
  13. mafe68
    Offline

    mafe68 Ist oft hier

    Registriert:
    9. August 2011
    Beiträge:
    196
    Zustimmungen:
    70
    Punkte für Erfolge:
    28
    Beruf:
    CVT
    AW: yaVDR 0.5 sc von Best Friend startet nicht!

    Ja habe ich! Habe eine DigitalDevices DVB-S2 sonst gehen die HD Sender nicht. Welche log.datei hast gemeint? Das ist die aber aus der /var/log/upstart/vdr.log und mit dem Befehl erstellt
    Code:
    tail -n 300 /var/log/syslog
    
     
    #12
  14. legenwaitforitdary
    Offline

    legenwaitforitdary Meister

    Registriert:
    12. November 2011
    Beiträge:
    748
    Zustimmungen:
    147
    Punkte für Erfolge:
    43
    AW: yaVDR 0.5 sc von Best Friend startet nicht!

    /var/log/upstart/vdr.log ≠ /var/log/syslog

    Du hast auch alle notwendigen Module des Plugins mitinstalliert, hast du vorhin nicht beantwortet ?
     
    #13
  15. mafe68
    Offline

    mafe68 Ist oft hier

    Registriert:
    9. August 2011
    Beiträge:
    196
    Zustimmungen:
    70
    Punkte für Erfolge:
    28
    Beruf:
    CVT
    AW: yaVDR 0.5 sc von Best Friend startet nicht!

    Ja die ich sonst auch immer Installiert habe!

    Code:
    sudo add-apt-repository ppa:bpl3f1lmootj/yavdr-stable
    sudo apt-get update
    sudo apt-get install vdr-plugin-sc
    sudo apt-get install vdr-plugin-sc-cardclient
    sudo apt-get install vdr-plugin-sc-nagra
    sudo apt-get install vdr-plugin-sc-constcw
    sudo apt-get install vdr-plugin-sc-cryptoworks
    
    Und den Rest wie ich es in meinem HowTo stehen habe
     
    #14
  16. legenwaitforitdary
    Offline

    legenwaitforitdary Meister

    Registriert:
    12. November 2011
    Beiträge:
    748
    Zustimmungen:
    147
    Punkte für Erfolge:
    43
    AW: yaVDR 0.5 sc von Best Friend startet nicht!

    Ohne vdr.log ist das leider immernoch Rätselraten.
     
    #15

Diese Seite empfehlen