[solved] [yavdr0.5-beta] SoftHDDevice kommt nicht hoch

DocViper · 20. September 2012

Auf meinem Testsystem (siehe Signatur):

Habe von einem älteren Stand der 0.5 alpha auf die beta per update und anschließendem dist-upgrade aktualisiert.
Daraufhin verweigerte Softhddevice seinen Dienst.

Dachte es ist irgendwas im Argen und installierte neu mit der 0.5 beta iso.
Hier läuft softhddevice auch nicht.
Nach update und anschließendem dist-upgrade auch keine Besserung.

Nach umstellen auf vdr-sxfe im Webfrontend bricht es ab mit der Fehlermeldung "Fehler beim Speichern"
LÖSUNG:
[yavdr0.5-beta] SoftHDDevice kommt nicht hoch

Diese Fehlermeldung "Fehler beim Speichern" kommt auch wenn ich bei Audio etwas ändere und speichere - kann es sein dass hier Timeout sehr sehr knapp gesetzt wurden ? )
siehe Screenshot

Hier das Syslog vom Umschalten des Frontends auf vdr-sxfe :

Code

Sep 20 22:24:08 htpc /usr/bin/signal-event.real[3470]: processing signal change-frontend
Sep 20 22:24:08 htpc /usr/bin/signal-event.real[3470]: processing action /usr/share/yavdr/events/change-frontend/10_change-frontend change-frontend
Sep 20 22:24:08 htpc /usr/bin/signal-event.real[3470]: processing action /usr/share/yavdr/events/change-frontend/15_create-menuorg-xml change-frontend
Sep 20 22:24:08 htpc /usr/bin/signal-event.real[3470]: processing action /usr/share/yavdr/events/change-frontend/20_stop-vdr change-frontend
Sep 20 22:24:08 htpc /usr/bin/signal-event.real[3470]: processing action /usr/share/yavdr/events/change-frontend/21_stop-x change-frontend
Sep 20 22:24:09 htpc kernel: [ 1619.026018] init: openbox main process (3152) terminated with status 1
Sep 20 22:24:09 htpc /usr/bin/signal-event.real[3470]: processing action /usr/share/yavdr/events/change-frontend/22_create-xorg-conf-yavdr change-frontend
Sep 20 22:24:09 htpc /usr/bin/signal-event.real[3470]: processing action /usr/share/yavdr/events/change-frontend/23_create-etc-init change-frontend
Sep 20 22:24:09 htpc /usr/bin/signal-event.real[3470]: processing action /usr/share/yavdr/events/change-frontend/24_pvr350-grub change-frontend
Sep 20 22:24:09 htpc /usr/bin/signal-event.real[3470]: processing action /usr/share/yavdr/events/change-frontend/26_start-x change-frontend
Sep 20 22:24:09 htpc kernel: [ 1619.145250] init: plymouth-stop pre-start process (3574) terminated with status 1
Sep 20 22:24:09 htpc /usr/bin/signal-event.real[3470]: processing action /usr/share/yavdr/events/change-frontend/30_start-vdr change-frontend
Sep 20 22:24:09 htpc /usr/bin/signal-event.real[3406]: processing action /usr/share/yavdr/events/change-frontend/21_stop-x change-frontend
Sep 20 22:24:09 htpc acpid: client 3162[0:0] has disconnected
Sep 20 22:24:09 htpc acpid: client 3162[0:0] has disconnected
Sep 20 22:24:09 htpc acpid: client connected from 3586[0:0]
Sep 20 22:24:09 htpc acpid: 1 client rule loaded
Sep 20 22:24:11 htpc acpid: client connected from 3586[0:0]
Sep 20 22:24:11 htpc acpid: 1 client rule loaded
Sep 20 22:24:12 htpc /usr/bin/signal-event.real[3406]: processing action /usr/share/yavdr/events/change-frontend/22_create-xorg-conf-yavdr change-frontend
Sep 20 22:24:12 htpc kernel: [ 1621.385811] init: openbox main process (3575) terminated with status 1
Sep 20 22:24:12 htpc /usr/bin/signal-event.real[3406]: processing action /usr/share/yavdr/events/change-frontend/23_create-etc-init change-frontend
Sep 20 22:24:12 htpc /usr/bin/signal-event.real[3406]: processing action /usr/share/yavdr/events/change-frontend/24_pvr350-grub change-frontend
Sep 20 22:24:12 htpc /usr/bin/signal-event.real[3406]: processing action /usr/share/yavdr/events/change-frontend/26_start-x change-frontend
Sep 20 22:24:12 htpc kernel: [ 1621.505369] init: plymouth-stop pre-start process (3642) terminated with status 1
Sep 20 22:24:12 htpc /usr/bin/signal-event.real[3406]: processing action /usr/share/yavdr/events/change-frontend/30_start-vdr change-frontend
Sep 20 22:24:12 htpc /usr/bin/signal-event.real[3406]: finished processing signal change-frontend
Sep 20 22:24:12 htpc acpid: client 3586[0:0] has disconnected
Sep 20 22:24:12 htpc acpid: client 3586[0:0] has disconnected
Sep 20 22:24:12 htpc acpid: client connected from 3653[0:0]
Sep 20 22:24:12 htpc acpid: 1 client rule loaded
Sep 20 22:24:13 htpc acpid: client connected from 3653[0:0]
Sep 20 22:24:13 htpc acpid: 1 client rule loaded
Sep 20 22:24:14 htpc vdr: [3263] stopping plugin: dynamite
Sep 20 22:24:14 htpc vdr: [3263] dynamite: force detaching all devices
Sep 20 22:24:14 htpc vdr: [3263] stopping plugin: wirbelscan
Sep 20 22:24:14 htpc vdr: [3263] stopping plugin: iptv
Sep 20 22:24:14 htpc vdr: [3263] stopping plugin: epgsearchonly
Sep 20 22:24:14 htpc vdr: [3263] stopping plugin: xvdr
Sep 20 22:24:14 htpc vdr: [3263] XVDR: XVDR Server stopped
Sep 20 22:24:14 htpc vdr: [3263] stopping plugin: epgsearch
Sep 20 22:24:14 htpc vdr: [3263] stopping plugin: skinpearlhd
Sep 20 22:24:14 htpc vdr: [3263] stopping plugin: streamdev-server
Sep 20 22:24:14 htpc vdr: [3363] streamdev server thread ended (pid=3263, tid=3363)
Sep 20 22:24:14 htpc vdr: [3263] stopping plugin: extrecmenu
Sep 20 22:24:14 htpc vdr: [3362] extrecmenu worker thread thread ended (pid=3263, tid=3362)
Sep 20 22:24:14 htpc vdr: [3263] stopping plugin: conflictcheckonly
Sep 20 22:24:14 htpc vdr: [3263] stopping plugin: text2skin
Sep 20 22:24:14 htpc vdr: [3263] stopping plugin: quickepgsearch
Sep 20 22:24:14 htpc vdr: [3263] stopping plugin: live
Sep 20 22:24:14 htpc vdr: [3263] stopping plugin: menuorg
Sep 20 22:24:14 htpc vdr: [3263] stopping plugin: restfulapi
Sep 20 22:24:14 htpc vdr: [3263] restfulapi: will end server thread: /1348172654/
Sep 20 22:24:14 htpc vdr: [3332] restfulapi: server thread end: /1348172654/
Sep 20 22:24:14 htpc vdr: [3332] restfulapi: server thread ended (pid=3263)
Sep 20 22:24:14 htpc vdr: [3263] stopping plugin: channellists
Sep 20 22:24:14 htpc vdr: [3263] stopping plugin: dbus2vdr
Sep 20 22:24:14 htpc vdr: [3263] dbus2vdr: emit upstart-signal stopped for all plugins
Sep 20 22:24:14 htpc vdr: [3263] dbus2vdr: upstart-signal stopped queued
Sep 20 22:24:14 htpc vdr: [3263] dbus2vdr: stop DBus-Upstart-Signal-Sender
Sep 20 22:24:14 htpc vdr: [3402] dbus2vdr: dequeue signal vdr-plugin/stopped
Sep 20 22:24:14 htpc vdr: [3402] dbus2vdr: retrieving connection for sending signal
Sep 20 22:24:14 htpc vdr: [3402] dbus2vdr: SendSignal Lock
Sep 20 22:24:14 htpc vdr: [3402] dbus2vdr: SendSignal Unlock
Sep 20 22:24:14 htpc vdr: [3402] dbus2vdr: SendSignal: dbus_connection_send
Sep 20 22:24:14 htpc vdr: [3402] dbus2vdr: SendSignal: dbus_message_unref
Sep 20 22:24:14 htpc vdr: [3402] dbus2vdr: signal sent
Sep 20 22:24:14 htpc vdr: [3402] dbus2vdr: emit upstart-signal vdr-plugin for stopped
Sep 20 22:24:14 htpc vdr: [3402] dbus2vdr: DBus-Upstart-Signal-Sender thread ended (pid=3263, tid=3402)
Sep 20 22:24:14 htpc vdr: [3331] dbus2vdr: connection has messages to send, flushing
Sep 20 22:24:14 htpc vdr: [3331] dbus2vdr: done flushing
Sep 20 22:24:14 htpc vdr: [3263] dbus2vdr: delete DBus-Upstart-Signal-Sender
Sep 20 22:24:14 htpc vdr: [3263] dbus2vdr: StopMonitor Lock
Sep 20 22:24:14 htpc vdr: [3331] dbus2vdr: monitor stopped on bus de.tvdr.vdr
Sep 20 22:24:14 htpc vdr: [3263] dbus2vdr: StopMonitor Unlock 2
Sep 20 22:24:14 htpc vdr: [3263] dbus2vdr: deleting 0 message handlers
Sep 20 22:24:14 htpc vdr: [3263] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.epg
Sep 20 22:24:14 htpc vdr: [3263] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.osd
Sep 20 22:24:14 htpc vdr: [3263] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.plugin
Sep 20 22:24:14 htpc vdr: [3263] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.recording
Sep 20 22:24:14 htpc vdr: [3263] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.remote
Sep 20 22:24:14 htpc vdr: [3263] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.setup
Sep 20 22:24:14 htpc vdr: [3263] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.shutdown
Sep 20 22:24:14 htpc vdr: [3263] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.skin
Sep 20 22:24:14 htpc vdr: [3263] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.timer
Sep 20 22:24:14 htpc vdr: [3263] stopping plugin: markad
Sep 20 22:24:14 htpc vdr: [3263] stopping plugin: femon
Sep 20 22:24:14 htpc vdr: [3263] stopping plugin: softhddevice
Sep 20 22:24:15 htpc vdr: [3263] [softhddev]SetPlayMode: 0
Sep 20 22:24:15 htpc vdr: [3263] [softhddev]SetVideoDisplayFormat: 1
Sep 20 22:24:15 htpc vdr: [3401] TS buffer on device 1 thread ended (pid=3263, tid=3401)
Sep 20 22:24:15 htpc vdr: [3399] buffer stats: 179352 (4%) used
Sep 20 22:24:15 htpc vdr: [3399] receiver on device 1 thread ended (pid=3263, tid=3399)
Sep 20 22:24:15 htpc vdr: [3263] saved setup to /var/lib/vdr/setup.conf
Sep 20 22:24:15 htpc vdr: [3328] section handler thread ended (pid=3263, tid=3328)
Sep 20 22:24:15 htpc vdr: [3327] tuner on frontend 0/0 thread ended (pid=3263, tid=3327)
Sep 20 22:24:15 htpc vdr: [3263] dynamite: deleted device for /dev/dvb/adapter0/frontend0
Sep 20 22:24:16 htpc vdr: [3325] section handler thread ended (pid=3263, tid=3325)
Sep 20 22:24:16 htpc vdr: [3263] deleting plugin: dynamite
Sep 20 22:24:16 htpc vdr: [3321] dynamite udev monitor for subsystem dvb thread ended (pid=3263, tid=3321)
Sep 20 22:24:16 htpc vdr: [3263] deleting plugin: wirbelscan
Sep 20 22:24:16 htpc vdr: [3263] deleting plugin: iptv
Sep 20 22:24:16 htpc vdr: [3263] deleting plugin: epgsearchonly
Sep 20 22:24:16 htpc vdr: [3263] deleting plugin: xvdr
Sep 20 22:24:16 htpc vdr: [3263] deleting plugin: epgsearch
Sep 20 22:24:16 htpc vdr: [3364] EPGSearch: Leaving conflict check thread
Sep 20 22:24:16 htpc vdr: [3364] EPGSearch: conflictcheck thread ended (pid=3263, tid=3364)
Sep 20 22:24:16 htpc vdr: [3263] deleting plugin: skinpearlhd
Sep 20 22:24:16 htpc vdr: [3263] deleting plugin: streamdev-server
Sep 20 22:24:16 htpc vdr: [3263] deleting plugin: extrecmenu
Sep 20 22:24:16 htpc vdr: [3263] deleting plugin: conflictcheckonly
Sep 20 22:24:16 htpc vdr: [3263] deleting plugin: text2skin
Sep 20 22:24:16 htpc vdr: [3263] deleting plugin: quickepgsearch
Sep 20 22:24:16 htpc vdr: [3263] deleting plugin: live
Sep 20 22:24:16 htpc vdr: [3263] deleting plugin: menuorg
Sep 20 22:24:16 htpc vdr: [3263] deleting plugin: restfulapi
Sep 20 22:24:16 htpc vdr: [3263] deleting plugin: channellists
Sep 20 22:24:16 htpc vdr: [3263] deleting plugin: dbus2vdr
Sep 20 22:24:16 htpc vdr: [3263] deleting plugin: markad
Sep 20 22:24:16 htpc vdr: [3263] deleting plugin: femon
Sep 20 22:24:16 htpc vdr: [3263] deleting plugin: softhddevice
Sep 20 22:24:17 htpc vdr: [3263] =====================
Sep 20 22:24:17 htpc vdr: [3263] EPG bugfix statistics
Sep 20 22:24:17 htpc vdr: [3263] =====================
Sep 20 22:24:17 htpc vdr: [3263] IF SOMEBODY WHO IS IN CHARGE OF THE EPG DATA FOR ONE OF THE LISTED
Sep 20 22:24:17 htpc vdr: [3263] CHANNELS READS THIS: PLEASE TAKE A LOOK AT THE FUNCTION cEvent::FixEpgBugs()
Sep 20 22:24:17 htpc vdr: [3263] IN VDR/epg.c TO LEARN WHAT'S WRONG WITH YOUR DATA, AND FIX IT!
Sep 20 22:24:17 htpc vdr: [3263] =====================
Sep 20 22:24:17 htpc vdr: [3263] Fix Hits Channels
Sep 20 22:24:17 htpc vdr: [3263] 4   1    ZDF
Sep 20 22:24:17 htpc vdr: [3263] 6   143  ZDFinfo, zdf.kultur, KiKA, zdf_neo, DLF, DKULTUR, 3sat
Sep 20 22:24:17 htpc vdr: [3263] 7   170  DRadio Wissen, DKULTUR, DLF
Sep 20 22:24:17 htpc vdr: [3263] =====================
Sep 20 22:24:17 htpc vdr: [3263] caught signal 15
Sep 20 22:24:17 htpc vdr: [3263] exiting, exit code 0
Sep 20 22:24:18 htpc vdr: [3754] VDR version 1.7.27 started
Sep 20 22:24:18 htpc vdr: [3754] switched to user 'vdr'
Sep 20 22:24:18 htpc vdr: [3754] codeset is 'UTF-8' - known
Sep 20 22:24:18 htpc vdr: [3754] found 28 locales in /usr/share/locale
Sep 20 22:24:18 htpc vdr: [3754] cTimeMs: using monotonic clock (resolution is 1 ns)
Sep 20 22:24:18 htpc vdr: [3754] [general.debug] using new 1.7.11+ capture code
Sep 20 22:24:18 htpc vdr: [3754] loading plugin: /usr/lib/vdr/plugins/libvdr-xineliboutput.so.1.7.27
Sep 20 22:24:18 htpc vdr: [3754] [xine..put] Listening on address '127.0.0.1' port 37890
Sep 20 22:24:18 htpc vdr: [3754] loading plugin: /usr/lib/vdr/plugins/libvdr-femon.so.1.7.27
Sep 20 22:24:18 htpc vdr: [3754] loading plugin: /usr/lib/vdr/plugins/libvdr-markad.so.1.7.27
Sep 20 22:24:18 htpc vdr: [3754] loading plugin: /usr/lib/vdr/plugins/libvdr-dbus2vdr.so.1.7.27
Sep 20 22:24:18 htpc vdr: [3754] dbus2vdr: use shutdown-hooks in /usr/share/vdr/shutdown-hooks
Sep 20 22:24:18 htpc vdr: [3754] dbus2vdr: use shutdown-hooks-wrapper /usr/share/vdr-plugin-dbus2vdr/shutdown-wrapper
Sep 20 22:24:18 htpc vdr: [3754] dbus2vdr: enable Upstart support
Sep 20 22:24:18 htpc vdr: [3754] loading plugin: /usr/lib/vdr/plugins/libvdr-channellists.so.1.7.27
Sep 20 22:24:18 htpc vdr: [3754] loading plugin: /usr/lib/vdr/plugins/libvdr-restfulapi.so.1.7.27
Sep 20 22:24:18 htpc vdr: [3754] restfulapi: Port has been set to 8002!
Sep 20 22:24:18 htpc vdr: [3754] restfulapi: Ip has been set to 0.0.0.0!
Sep 20 22:24:18 htpc vdr: [3754] restfulapi: trying to parse command line arguments
Sep 20 22:24:18 htpc vdr: [3754] restfulapi: Port has been set to 8002!
Sep 20 22:24:18 htpc vdr: [3754] restfulapi: Ip has been set to 0.0.0.0!
Sep 20 22:24:18 htpc vdr: [3754] RESTful-API Settings: port: 8002, ip: 0.0.0.0, eimgs: , cimgs: i, headers: activated
Sep 20 22:24:18 htpc vdr: [3754] loading plugin: /usr/lib/vdr/plugins/libvdr-menuorg.so.1.7.27
Sep 20 22:24:18 htpc vdr: [3754] loading plugin: /usr/lib/vdr/plugins/libvdr-live.so.1.7.27
Sep 20 22:24:18 htpc vdr: [3754] [live] INFO: validating server ip '0.0.0.0'
Sep 20 22:24:18 htpc vdr: [3754] loading plugin: /usr/lib/vdr/plugins/libvdr-quickepgsearch.so.1.7.27
Sep 20 22:24:18 htpc vdr: [3754] loading plugin: /usr/lib/vdr/plugins/libvdr-text2skin.so.1.7.27
Sep 20 22:24:18 htpc vdr: [3754] loading plugin: /usr/lib/vdr/plugins/libvdr-conflictcheckonly.so.1.7.27
Sep 20 22:24:18 htpc vdr: [3754] loading plugin: /usr/lib/vdr/plugins/libvdr-extrecmenu.so.1.7.27
Sep 20 22:24:18 htpc vdr: [3754] loading plugin: /usr/lib/vdr/plugins/libvdr-streamdev-server.so.1.7.27
Sep 20 22:24:18 htpc vdr: [3754] loading plugin: /usr/lib/vdr/plugins/libvdr-skinpearlhd.so.1.7.27
Sep 20 22:24:18 htpc vdr: [3754] loading plugin: /usr/lib/vdr/plugins/libvdr-epgsearch.so.1.7.27
Sep 20 22:24:18 htpc vdr: [3754] loading plugin: /usr/lib/vdr/plugins/libvdr-xvdr.so.1.7.27
Sep 20 22:24:18 htpc vdr: [3754] loading plugin: /usr/lib/vdr/plugins/libvdr-epgsearchonly.so.1.7.27
Sep 20 22:24:18 htpc vdr: [3754] loading plugin: /usr/lib/vdr/plugins/libvdr-iptv.so.1.7.27
Sep 20 22:24:18 htpc vdr: [3754] loading plugin: /usr/lib/vdr/plugins/libvdr-wirbelscan.so.1.7.27
Sep 20 22:24:18 htpc vdr: [3754] loading plugin: /usr/lib/vdr/plugins/libvdr-dynamite.so.1.7.27
Sep 20 22:24:18 htpc vdr: [3754] loading /var/lib/vdr/setup.conf
Sep 20 22:24:18 htpc vdr: [3754] ERROR: unknown config parameter: streamdev-server.SuspendMode = 1
Sep 20 22:24:18 htpc vdr: [3754] loading /var/lib/vdr/sources.conf
Sep 20 22:24:18 htpc vdr: [3754] loading /var/lib/vdr/diseqc.conf
Sep 20 22:24:18 htpc vdr: [3754] loading /var/lib/vdr/scr.conf
Sep 20 22:24:18 htpc vdr: [3754] loading /var/lib/vdr/channels.conf
Sep 20 22:24:18 htpc vdr: [3754] loading /var/lib/vdr/timers.conf
Sep 20 22:24:18 htpc vdr: [3754] loading /var/lib/vdr/commands.conf
Sep 20 22:24:18 htpc vdr: [3754] loading /var/lib/vdr/reccmds.conf
Sep 20 22:24:18 htpc vdr: [3754] loading /var/lib/vdr/svdrphosts.conf
Sep 20 22:24:18 htpc vdr: [3754] loading /var/lib/vdr/remote.conf
Sep 20 22:24:18 htpc vdr: [3754] loading /var/lib/vdr/keymacros.conf
Sep 20 22:24:18 htpc vdr: [3754] ERROR: unknown plugin 'osdteletext'
Sep 20 22:24:18 htpc vdr: [3754] ERROR: empty key macro
Sep 20 22:24:18 htpc vdr: [3754] ERROR: unknown plugin 'softhddevice'
Sep 20 22:24:18 htpc vdr: [3754] registered source parameters for 'A - ATSC'
Sep 20 22:24:18 htpc vdr: [3812] dynamite udev monitor for subsystem dvb thread started (pid=3754, tid=3812)
Sep 20 22:24:18 htpc vdr: [3813] video directory scanner thread started (pid=3754, tid=3813)
Sep 20 22:24:18 htpc vdr: [3813] video directory scanner thread ended (pid=3754, tid=3813)
Sep 20 22:24:18 htpc vdr: [3815] epg data reader thread started (pid=3754, tid=3815)
Sep 20 22:24:18 htpc vdr: [3815] reading EPG data from /var/cache/vdr/epg.data
Sep 20 22:24:18 htpc vdr: [3814] video directory scanner thread started (pid=3754, tid=3814)
Sep 20 22:24:18 htpc vdr: [3814] video directory scanner thread ended (pid=3754, tid=3814)
Sep 20 22:24:18 htpc vdr: [3754] registered source parameters for 'C - DVB-C'
Sep 20 22:24:18 htpc vdr: [3754] registered source parameters for 'S - DVB-S'
Sep 20 22:24:18 htpc vdr: [3754] registered source parameters for 'T - DVB-T'
Sep 20 22:24:18 htpc vdr: [3754] probing /dev/dvb/adapter0/frontend0
Sep 20 22:24:18 htpc vdr: [3754] dynamite: preparing 8 dynamic device slots for dvb devices
Sep 20 22:24:18 htpc vdr: [3754] new device number 1
Sep 20 22:24:18 htpc vdr: [3754] new device number 2
Sep 20 22:24:18 htpc vdr: [3754] new device number 3
Sep 20 22:24:18 htpc vdr: [3754] new device number 4
Sep 20 22:24:18 htpc vdr: [3754] new device number 5
Sep 20 22:24:18 htpc vdr: [3754] new device number 6
Sep 20 22:24:18 htpc vdr: [3754] new device number 7
Sep 20 22:24:18 htpc vdr: [3754] new device number 8
Sep 20 22:24:18 htpc vdr: [3754] dynamite: grab dvb device 0/0
Sep 20 22:24:18 htpc vdr: [3754] found 1 DVB device
Sep 20 22:24:18 htpc vdr: [3754] initializing plugin: xineliboutput (1.0.90-cvs): X11/xine-lib output plugin
Sep 20 22:24:18 htpc vdr: [3754] new device number 16
Sep 20 22:24:18 htpc vdr: [3754] [xine..put] cTimePts: clock_gettime(CLOCK_MONOTONIC): clock resolution 0 us
Sep 20 22:24:18 htpc vdr: [3754] [xine..put] cTimePts: using monotonic clock
Sep 20 22:24:18 htpc vdr: [3754] [xine..put] RTP SSRC: 0x2fee85b6
Sep 20 22:24:18 htpc vdr: [3754] initializing plugin: femon (1.7.17): DVB Signal Information Monitor (OSD)
Sep 20 22:24:18 htpc vdr: [3754] initializing plugin: markad (0.1.4pre): Mark advertisements
Sep 20 22:24:18 htpc vdr: [3754] initializing plugin: dbus2vdr (0.0.8a): control vdr via D-Bus
Sep 20 22:24:18 htpc vdr: [3754] initializing plugin: channellists (0.0.4): Manage your channellists
Sep 20 22:24:18 htpc vdr: [3754] initializing plugin: restfulapi (0.1.0): Offers a RESTful-API to retrieve data from VDR
Sep 20 22:24:18 htpc vdr: [3754] initializing plugin: menuorg (0.4.5): Reorganizes the main menu
Sep 20 22:24:18 htpc vdr: [3754] loading menuorg config file from /var/lib/vdr/plugins/menuorg.xml
Sep 20 22:24:18 htpc vdr: [3754] initializing plugin: live (0.2.0): Live Interactive VDR Environment
Sep 20 22:24:18 htpc vdr: [3754] initializing plugin: quickepgsearch (0.0.1): Quick search for broadcasts
Sep 20 22:24:18 htpc vdr: [3754] initializing plugin: text2skin (1.3.2+git): Loader for text-based skins
Sep 20 22:24:18 htpc vdr: [3754] initializing plugin: conflictcheckonly (0.0.1): Direct access to epgsearch's conflict check menu
Sep 20 22:24:18 htpc vdr: [3754] initializing plugin: extrecmenu (1.2.2): Extended recordings menu
Sep 20 22:24:18 htpc vdr: [3754] initializing plugin: streamdev-server (0.6.0-git): VDR Streaming Server
Sep 20 22:24:18 htpc vdr: [3754] initializing plugin: skinpearlhd (0.0.1): PearlHD Skin
Sep 20 22:24:18 htpc vdr: [3754] initializing plugin: epgsearch (1.0.1.beta2): search the EPG for repeats and more
Sep 20 22:24:18 htpc vdr: [3754] initializing plugin: xvdr (0.9.5): VDR-Network-Streaming-Interface (XVDR) Server
Sep 20 22:24:18 htpc vdr: [3754] initializing plugin: epgsearchonly (0.0.1): Direct access to epgsearch's search menu
Sep 20 22:24:18 htpc vdr: [3754] initializing plugin: iptv (0.5.2): Experience the IPTV
Sep 20 22:24:18 htpc vdr: [3754] registered source parameters for 'I - IPTV'
Sep 20 22:24:18 htpc vdr: [3754] new device number 17
Sep 20 22:24:18 htpc vdr: [3754] creating IPTV device 0 (CardIndex=16)
Sep 20 22:24:18 htpc vdr: [3754] initializing plugin: wirbelscan (0.0.7): DVB and pvrinput channel scan for VDR
Sep 20 22:24:18 htpc vdr: [3754] initializing plugin: dynamite (0.0.9f): attach/detach devices on the fly
Sep 20 22:24:18 htpc vdr: [3754] dynamite: creating dynamic device slots as much as possible
Sep 20 22:24:18 htpc vdr: [3754] new device number 18
Sep 20 22:24:18 htpc vdr: [3754] new device number 19
Sep 20 22:24:18 htpc vdr: [3754] new device number 20
Sep 20 22:24:18 htpc vdr: [3754] new device number 21
Sep 20 22:24:18 htpc vdr: [3754] new device number 22
Sep 20 22:24:18 htpc vdr: [3754] new device number 23
Sep 20 22:24:18 htpc vdr: [3754] dynamite: probing /dev/dvb/adapter0/frontend0
Sep 20 22:24:18 htpc vdr: [3754] dynamite: /dev/dvb/adapter0/frontend0 is a dvb adapter trying to set card index to 0
Sep 20 22:24:18 htpc vdr: [3816] [xine..put] Have CAP_SYS_NICE capability
Sep 20 22:24:18 htpc vdr: [3754] [general.debug] capturing device 0/0 (subsystem ID d4709022)
Sep 20 22:24:18 htpc vdr: [3754] [general.debug] creating standard device 0/0
Sep 20 22:24:18 htpc vdr: [3754] new sub-device number 1
Sep 20 22:24:18 htpc vdr: [3817] section handler thread started (pid=3754, tid=3817)
Sep 20 22:24:18 htpc vdr: [3754] frontend 0/0 provides DVB-S,DVB-S2 with QPSK ("Montage Technology DS3000/TS2020")
Sep 20 22:24:18 htpc vdr: [3754] dynamite: attached device /dev/dvb/adapter0/frontend0 to dynamic device slot 1
Sep 20 22:24:18 htpc vdr: [3754] dynamite: /dev/dvb/adapter0/frontend0 is a dvb adapter trying to set card index to 0
Sep 20 22:24:18 htpc vdr: [3754] dynamite: /dev/dvb/adapter0/frontend0 is already attached
Sep 20 22:24:18 htpc vdr: [3754] setting primary device to 9
Sep 20 22:24:18 htpc vdr: [3754] assuming manual start of VDR
Sep 20 22:24:18 htpc vdr: [3754] SVDRP listening on port 6419
Sep 20 22:24:18 htpc vdr: [3754] skin "anthra_1920_FSE" not available - using "sttng" instead
Sep 20 22:24:18 htpc vdr: [3754] loading /var/lib/vdr/themes/sttng-default.theme
Sep 20 22:24:18 htpc vdr: [3754] starting plugin: xineliboutput
Sep 20 22:24:18 htpc vdr: [3823] Remote decoder/display server (cXinelibServer) thread started (pid=3754, tid=3823)
Sep 20 22:24:18 htpc vdr: [3823] [xine..put] Have CAP_SYS_NICE capability
Sep 20 22:24:18 htpc vdr: [3823] [xine..put] cXinelibServer priority set successful SCHED_RR 2 [1,99]
Sep 20 22:24:18 htpc vdr: [3823] [xine..put] Binding server to 127.0.0.1:37890
Sep 20 22:24:18 htpc vdr: [3823] [xine..put] Listening on port 37890
Sep 20 22:24:18 htpc vdr: [3823] [xine..put] Listening for UDP broadcasts on port 37890
Sep 20 22:24:18 htpc vdr: [3823] [discovery] BROADCAST: VDR xineliboutput DISCOVERY 1.0#015#012Server port: 37890#015#012Server address: 127.0.0.1#015#012Server version: xineliboutput-1.0.90-cvs#015#012#015
Sep 20 22:24:18 htpc vdr: [3820] section handler thread started (pid=3754, tid=3820)
Sep 20 22:24:18 htpc vdr: [3819] tuner on frontend 0/0 thread started (pid=3754, tid=3819)
Sep 20 22:24:18 htpc vdr: [3815] epg data reader thread ended (pid=3754, tid=3815)
Sep 20 22:24:18 htpc vdr: [3754] [xine..put] cXinelibDevice::StartDevice(): Device started
Sep 20 22:24:18 htpc vdr: [3754] starting plugin: femon
Sep 20 22:24:18 htpc vdr: [3754] starting plugin: markad
Sep 20 22:24:18 htpc vdr: [3754] starting plugin: dbus2vdr
Sep 20 22:24:18 htpc vdr: [3754] dbus2vdr: new message dispatcher for interface de.tvdr.vdr.epg
Sep 20 22:24:18 htpc vdr: [3754] dbus2vdr: new message dispatcher for interface de.tvdr.vdr.osd
Sep 20 22:24:18 htpc vdr: [3754] dbus2vdr: new message dispatcher for interface de.tvdr.vdr.plugin
Sep 20 22:24:18 htpc vdr: [3754] dbus2vdr: new message dispatcher for interface de.tvdr.vdr.recording
Sep 20 22:24:18 htpc vdr: [3754] dbus2vdr: new message dispatcher for interface de.tvdr.vdr.remote
Sep 20 22:24:18 htpc vdr: [3754] dbus2vdr: new message dispatcher for interface de.tvdr.vdr.setup
Sep 20 22:24:18 htpc vdr: [3754] dbus2vdr: new message dispatcher for interface de.tvdr.vdr.shutdown
Sep 20 22:24:18 htpc vdr: [3754] dbus2vdr: new message dispatcher for interface de.tvdr.vdr.skin
Sep 20 22:24:18 htpc vdr: [3754] dbus2vdr: new message dispatcher for interface de.tvdr.vdr.timer
Sep 20 22:24:18 htpc vdr: [3754] dbus2vdr: StartMonitor Lock
Sep 20 22:24:18 htpc vdr: [3824] dbus2vdr: monitor started on bus de.tvdr.vdr
Sep 20 22:24:18 htpc vdr: [3754] dbus2vdr: StartMonitor Unlock 2
Sep 20 22:24:18 htpc vdr: [3754] starting plugin: channellists
Sep 20 22:24:18 htpc vdr: [3754] starting plugin: restfulapi
Sep 20 22:24:18 htpc vdr: [3754] restfulapi: Used settings: port: 8002, ip: 0.0.0.0, eimgs: , cimgs: , headers: activated
Sep 20 22:24:18 htpc vdr: [3754] restfulapi: found 25 files in /*.
Sep 20 22:24:18 htpc vdr: [3754] restfulapi: found 25 files in /*.
Sep 20 22:24:18 htpc vdr: [3754] restfulapi: Initializing inotify for epgimages or channellogos failed! (Check restfulapi-settings!)
Sep 20 22:24:18 htpc vdr: [3754] restfulapi: Initializing inotify for epgimages or channellogos failed! (Check restfulapi-settings!)
Sep 20 22:24:18 htpc vdr: [3754] create server
Sep 20 22:24:18 htpc vdr: [3754] starting plugin: menuorg
Sep 20 22:24:18 htpc vdr: [3754] starting plugin: live
Sep 20 22:24:18 htpc vdr: [3754] LIVE: initial file cache has 82 entries and needs 377394 bytes of data!
Sep 20 22:24:18 htpc vdr: [3754] starting plugin: quickepgsearch
Sep 20 22:24:18 htpc vdr: [3754] starting plugin: text2skin
Sep 20 22:24:18 htpc vdr: [3754] text2skin: loading /var/lib/vdr/plugins/text2skin/anthra_1280_FS/anthra_1280_FS.colors
Sep 20 22:24:18 htpc vdr: [3754] parsing /var/lib/vdr/plugins/text2skin/anthra_1280_FS/anthra_1280_FS.skin
Sep 20 22:24:18 htpc vdr: [3754] text2skin: loading /var/lib/vdr/plugins/text2skin/anthra_1920_FS/anthra_1920_FS.colors
Sep 20 22:24:18 htpc vdr: [3754] parsing /var/lib/vdr/plugins/text2skin/anthra_1920_FS/anthra_1920_FS.skin
Sep 20 22:24:18 htpc vdr: [3824] dbus2vdr: Action Lock
Sep 20 22:24:18 htpc vdr: [3824] dbus2vdr: try to connect to system bus
Sep 20 22:24:18 htpc vdr: [3824] dbus2vdr: connect to system bus successful
Sep 20 22:24:18 htpc vdr: [3824] dbus2vdr: Action Unlock
Sep 20 22:24:18 htpc vdr: [3824] dbus2vdr: new message, object /org/freedesktop/DBus, interface org.freedesktop.DBus, member NameAcquired
Sep 20 22:24:18 htpc vdr: [3824] dbus2vdr: NameAcquired: get ownership of name de.tvdr.vdr
Sep 20 22:24:18 htpc vdr: [3826] [live] INFO: attempt to listen on ip = '0.0.0.0'
Sep 20 22:24:18 htpc vdr: [3826] [live] ERROR: Unable to load cert/key (/var/lib/vdr/plugins/live/live.pem//var/lib/vdr/plugins/live/live-key.pem): No such file or directory
Sep 20 22:24:18 htpc vdr: [3754] text2skin: loading /var/lib/vdr/plugins/text2skin/NarrowHD/NarrowHD.colors
Sep 20 22:24:18 htpc vdr: [3754] parsing /var/lib/vdr/plugins/text2skin/NarrowHD/NarrowHD.skin
Sep 20 22:24:18 htpc vdr: [3754] text2skin: loading /var/lib/vdr/plugins/text2skin/anthra_1280_OS/anthra_1280_OS.colors
Sep 20 22:24:18 htpc vdr: [3754] parsing /var/lib/vdr/plugins/text2skin/anthra_1280_OS/anthra_1280_OS.skin
Sep 20 22:24:18 htpc vdr: [3754] text2skin: loading /var/lib/vdr/plugins/text2skin/anthra_1920_OS/anthra_1920_OS.colors
Sep 20 22:24:18 htpc vdr: [3754] parsing /var/lib/vdr/plugins/text2skin/anthra_1920_OS/anthra_1920_OS.skin
Sep 20 22:24:18 htpc vdr: [3754] text2skin: loading /var/lib/vdr/plugins/text2skin/anthra_1920_FSE/anthra_1920_FSE.colors
Sep 20 22:24:18 htpc vdr: [3754] parsing /var/lib/vdr/plugins/text2skin/anthra_1920_FSE/anthra_1920_FSE.skin
Sep 20 22:24:18 htpc vdr: [3754] starting plugin: conflictcheckonly
Sep 20 22:24:18 htpc rsyslogd-2177: imuxsock begins to drop messages from pid 3754 due to rate-limiting
Sep 20 22:24:48 htpc rsyslogd-2177: imuxsock lost 26 messages from pid 3754 due to rate-limiting

Alles anzeigen

So erscheint kein Frontend am System (das Menü auf der linken Seite ist vorhanden und der Mousezeiger ist auch da - Xorg sollte somit nicht das Problem sein)

Nach Reboot des Rechners bekomme ich dann ein Bild (wenn ich vdr-sxfe gewählt hatte)
(Btw. über das Liveplugin bzw. Streamdev und auch über xvdr läuft es einwandfrei)

Mögliche Auslöser die ich mir noch ansehen muss:
- Installation erfolgte auf ziemlich langsamem USB Stick (mit der alpha gings einwandfrei)
- Und ich habe nur eine Sat-Karte im Testsystem (ev ist VDR dann mit Streamdev-server, Xvdr und Frontend überfordert)
- Habe noch keine Fernbedienung aktiviert - kann es sein dass das SoftHddevice nicht "aufwacht" - hier ist ja ein neuer Stromsparmodus reingekommen (aber mit dem assuming manual start sollte das auch kein Problem sein)

So schnell gebe ich nicht auf - aber vielleicht hat ja jemand eine gute Idee ?

lg
Joe

seahawk1986 · 20. September 2012

Zitat von DocViper

- Habe noch keine Fernbedienung aktiviert - kann es sein dass das SoftHddevice nicht "aufwacht" - hier ist ja ein neuer Stromsparmodus reingekommen (aber mit dem assuming manual start sollte das auch kein Problem sein)

Genau, das macht er eigentlich nur wenn er denkt, dass er für einen Timer oder ACPI-Wakeup Event hochgefahren wurde - und dann solltest du auch eine entsprechende Meldung auf dem Schirm sehen, dass das Frontend detached ist.

Admira98 · 21. September 2012

Mir gehts genauso. Hab gestern die 0.5 beta frisch installiert und nur sudo apt-get update && upgrade gemacht.

Beim Hochfahren kommt nur der Mauszeiger.
Nach
svdrpsend plug softhddevice stat
svdrpsend plug softhddevice atta -d :1
hab ich dann auch ein Bild plus Ton.

Was könnte ich unternehmen um Bild und Ton gleich nach dem Startup zu sehen?

seahawk1986 · 21. September 2012

Zeig mal ein komplettes Syslog und die /var/log/upstart/vdr-frontend.log

mini73 · 21. September 2012

Moin!

Zitat von Admira98

sudo apt-get update && upgrade

Bei yaVDR immer dist-upgrade, niemals upgrade.

Lars.

Admira98 · 23. September 2012

Vielen Dank. Nach einem dist-upgrade funktioniert die Box nach dem Startup.

Torsten73 · 23. September 2012

Zitat von DocViper

Nach umstellen auf vdr-sxfe im Webfrontend bricht es ab mit der Fehlermeldung "Fehler beim Speichern"

Diese Fehlermeldung "Fehler beim Speichern" kommt auch wenn ich bei Audio etwas ändere und speichere - kann es sein dass hier Timeout sehr sehr knapp gesetzt wurden ? )
siehe Screenshot

Dieses Verhalten habe ich auch schon lange beobachtet. Und dann mit dem nächsten Update kann ich wieder Änderungen speichern. Da ich wenig am 0.5er am arbeiten bin; ist es immer noch die Erstinstallation von der 0.5 alpha der ersten Tage. Und diese habe ich bei kurzen Abständen mit upgrade und bei langen Abständen mit dist-upgrade aktualisiert.

Zitat von mini73

Bei yaVDR immer dist-upgrade, niemals upgrade.

Möglich dass es immer nach einem dist-upgrade nicht auftritt. Aber warum ist das so? Das einzige was beim dist-upgrade zusätzlich kommt sind die kernel upgrades. Oder ?

mini73 · 24. September 2012

Moin!

upgrade: es werden nur vorhandene Pakete aktualisiert
dist-upgrade: es werden auch neue Pakete installiert, die von neuen Version der vorhandenen Pakete gebraucht werden.

Bei einem upgrade kann es also passieren, dass yaVDR hinterher nicht mehr läuft, weil wir ein neues Paket hinzugenommen haben, dass auf Grund des upgrade-Aufrufs nicht mitinstalliert werden darf.
Dann bleibt die alte Version bestehen und wird fröhlich gemixt, weil ein anderes Paket evtl. doch aktualisiert werden kann.
Deshalb immer dist-upgrade bei yaVDR.

Lars.

DocViper · 25. September 2012

Zitat von seahawk1986

Zeig mal ein komplettes Syslog und die /var/log/upstart/vdr-frontend.log

Bin erst jetzt zu meiner Testumgebung gekommen.
Nach dem Update && dist-upgrade - inclusive der nvidia-driver update fixerei Geschichte aus diesem Thread ( yaVDR 0.5 Beta User: keine Updates die nächsten 24 Stunden machen! )
Hier der auszug aus der
/var/log/upstart/vdr-frontend.log

Code

vo_vdpau: vdp_video_mixer_render error : An invalid handle value was provided.
vo_vdpau: vdp_video_mixer_render error : An invalid handle value was provided.
vo_vdpau: VDPAU was pre-empted. Reinit.
vo_vdpau: Can't create vdp device : unsupported GPU?
vo_vdpau: vdp_video_mixer_render error : An invalid handle value was provided.
vo_vdpau: vdp_video_mixer_render error : An invalid handle value was provided.
vo_vdpau: VDPAU was pre-empted. Reinit.
vo_vdpau: Can't create vdp device : unsupported GPU?
vo_vdpau: vdp_video_mixer_render error : An invalid handle value was provided.
vo_vdpau: vdp_video_mixer_render error : An invalid handle value was provided.
vo_vdpau: VDPAU was pre-empted. Reinit.
vo_vdpau: Can't create vdp device : unsupported GPU?
vo_vdpau: vdp_video_mixer_render error : An invalid handle value was provided.
vo_vdpau: vdp_video_mixer_render error : An invalid handle value was provided.
vo_vdpau: VDPAU was pre-empted. Reinit.
vo_vdpau: Can't create vdp device : unsupported GPU?
vo_vdpau: vdp_video_mixer_render error : An invalid handle value was provided.
vo_vdpau: vdp_video_mixer_render error : An invalid handle value was provided.
vo_vdpau: VDPAU was pre-empted. Reinit.
vo_vdpau: Can't create vdp device : unsupported GPU?
vo_vdpau: vdp_video_mixer_render error : An invalid handle value was provided.
vo_vdpau: vdp_video_mixer_render error : An invalid handle value was provided.
vo_vdpau: VDPAU was pre-empted. Reinit.
vo_vdpau: Can't create vdp device : unsupported GPU?
vo_vdpau: vdp_video_mixer_render error : An invalid handle value was provided.
vo_vdpau: vdp_video_mixer_render error : An invalid handle value was provided.
vo_vdpau: VDPAU was pre-empted. Reinit.
vo_vdpau: Can't create vdp device : unsupported GPU?
vo_vdpau: vdp_video_mixer_render error : An invalid handle value was provided.
vo_vdpau: vdp_video_mixer_render error : An invalid handle value was provided.
vdpau_set_property: property=0, value=0
vo_vdpau: deinterlace: none
vdpau_set_property: property=2, value=0
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vo_vdpau: error, can't set csc matrix !!
vdpau_set_property: property=3, value=100
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vo_vdpau: error, can't set csc matrix !!
vdpau_set_property: property=5, value=0
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vo_vdpau: error, can't set csc matrix !!
vdpau_set_property: property=24, value=0
vo_vdpau: disable sharpness.
vdpau_set_property: property=25, value=0
vo_vdpau: disable noise reduction.
vdpau_set_property: property=4, value=100
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vo_vdpau: error, can't set csc matrix !!
vdpau_set_property: property=1, value=0
vo_vdpau: failed to get surface bits !! An invalid handle value was provided.
vo_vdpau: failed to put surface bits !! An invalid handle value was provided.
vo_vdpau: VDPAU was pre-empted. Reinit.
vo_vdpau: Can't create vdp device : unsupported GPU?
vo_vdpau: vdp_video_mixer_render error : An invalid handle value was provided.
vo_vdpau: failed to create surface !! An invalid handle value was provided.
vdpau_set_property: property=8, value=100
vdpau_set_property: property=2, value=0
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vo_vdpau: error, can't set csc matrix !!
vdpau_set_property: property=3, value=100
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vo_vdpau: error, can't set csc matrix !!
vdpau_set_property: property=5, value=0
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vo_vdpau: error, can't set csc matrix !!
vdpau_set_property: property=24, value=0
vo_vdpau: disable sharpness.
vdpau_set_property: property=25, value=0
vo_vdpau: disable noise reduction.
vdpau_set_property: property=4, value=100
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vo_vdpau: error, can't set csc matrix !!
vdpau_set_property: property=1, value=0
vo_vdpau: VDPAU was pre-empted. Reinit.
vo_vdpau: Can't create vdp device : unsupported GPU?
vo_vdpau: vdp_video_surface_putbits_ycbcr YV12 error : An invalid handle value was provided.
vo_vdpau: vdp_video_mixer_render error : An invalid handle value was provided.
vdpau_set_property: property=0, value=1
vo_vdpau: deinterlace: temporal_spatial
vdpau_set_property: property=0, value=0
vo_vdpau: deinterlace: none
vdpau_set_property: property=2, value=0
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vo_vdpau: error, can't set csc matrix !!
vdpau_set_property: property=3, value=100
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vo_vdpau: error, can't set csc matrix !!
vdpau_set_property: property=5, value=0
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vo_vdpau: error, can't set csc matrix !!
vdpau_set_property: property=24, value=0
vo_vdpau: disable sharpness.
vdpau_set_property: property=25, value=0
vo_vdpau: disable noise reduction.
vdpau_set_property: property=4, value=100
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vo_vdpau: error, can't set csc matrix !!
vdpau_set_property: property=1, value=0
vo_vdpau: VDPAU was pre-empted. Reinit.
vo_vdpau: Can't create vdp device : unsupported GPU?
vo_vdpau: vdp_video_surface_putbits_ycbcr YV12 error : An invalid handle value was provided.
vo_vdpau: vdp_video_mixer_render error : An invalid handle value was provided.
vdpau_set_property: property=2, value=0
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vo_vdpau: error, can't set csc matrix !!
vdpau_set_property: property=3, value=100
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vo_vdpau: error, can't set csc matrix !!
vdpau_set_property: property=5, value=0
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vo_vdpau: error, can't set csc matrix !!
vdpau_set_property: property=24, value=0
vo_vdpau: disable sharpness.
vdpau_set_property: property=25, value=0
vo_vdpau: disable noise reduction.
vdpau_set_property: property=4, value=100
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vo_vdpau: error, can't set csc matrix !!
vdpau_set_property: property=1, value=0
vo_vdpau: VDPAU was pre-empted. Reinit.
vo_vdpau: Can't create vdp device : unsupported GPU?
vo_vdpau: vdp_video_surface_putbits_ycbcr YV12 error : An invalid handle value was provided.
vo_vdpau: vdp_video_mixer_render error : An invalid handle value was provided.
vo_vdpau: VDPAU was pre-empted. Reinit.
vdpau_set_property: property=2, value=0
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vo_vdpau: error, can't set csc matrix !!
vdpau_set_property: property=3, value=100
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vo_vdpau: error, can't set csc matrix !!
vdpau_set_property: property=5, value=0
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vo_vdpau: error, can't set csc matrix !!
vdpau_set_property: property=24, value=0
vo_vdpau: disable sharpness.
vdpau_set_property: property=25, value=0
vo_vdpau: disable noise reduction.
vdpau_set_property: property=4, value=100
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vo_vdpau: error, can't set csc matrix !!
vdpau_set_property: property=1, value=0
vo_vdpau: Can't create vdp device : unsupported GPU?
vo_vdpau: vdp_video_surface_putbits_ycbcr YV12 error : An invalid handle value was provided.
vo_vdpau: vdp_video_mixer_render error : An invalid handle value was provided.
vo_vdpau: VDPAU was pre-empted. Reinit.
vo_vdpau: Can't create vdp device : unsupported GPU?
vo_vdpau: vdp_video_surface_putbits_ycbcr YV12 error : An invalid handle value was provided.
vo_vdpau: vdp_video_mixer_render error : An invalid handle value was provided.
start: You do not have permission to modify job: wait-for-job-state
start: You do not have permission to modify job: wait-for-job-state
start: You do not have permission to modify job: wait-for-job-state
vdr-sxfe 1.0.90-cvs  (build with xine-lib 1.2.2, using xine-lib 1.2.2)


Post plugins: tvtime:method=use_vo_driver
Automatic reconnection enabled
Audio driver: alsa
vo_vdpau: Use lock display synchronization for some vdpau calls
vo_vdpau: vdpau API version : 1
vo_vdpau: vdpau implementation description : NVIDIA VDPAU Driver Shared Library  295.75  Fri Aug 24 13:10:34 PDT 2012
vo_vdpau: maximum video surface size for chroma type 4:2:2 is 4096x4096
vo_vdpau: maximum video surface size for chroma type 4:2:0 is 4096x4096
vo_vdpau: maximum output surface size is 8192x8192
vo_vdpau: hold a maximum of 10 video output surfaces for reuse
vo_vdpau: using 4 output surfaces of size 1280x720 for display queue
vo_vdpau: this hardware doesn't support mpeg4-part2.
vdpau_set_property: property=8, value=100
vdpau_set_property: property=2, value=0
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vdpau_set_property: property=3, value=100
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vdpau_set_property: property=5, value=0
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vdpau_set_property: property=24, value=0
vo_vdpau: disable sharpness.
vdpau_set_property: property=25, value=0
vo_vdpau: disable noise reduction.
vdpau_set_property: property=4, value=100
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vdpau_set_property: property=1, value=0
vo_vdpau: deinterlace: none
vo_vdpau: set_scaling_level=0
vo_vdpau: enabled features: inverse_telecine=0
vo_vdpau: disable noise reduction.
vo_vdpau: disable sharpness.
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vo_vdpau: skip_chroma = 1
vo_vdpau: background_color = 0
vdpau_set_property: property=0, value=1
vo_vdpau: deinterlace: temporal_spatial
vdpau_set_property: property=0, value=0
vo_vdpau: deinterlace: none
vdpau_set_property: property=0, value=1
vo_vdpau: deinterlace: temporal_spatial
vdpau_set_property: property=0, value=0
vo_vdpau: deinterlace: none
vdpau_set_property: property=2, value=0
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vdpau_set_property: property=3, value=100
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vdpau_set_property: property=5, value=0
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vdpau_set_property: property=24, value=0
vo_vdpau: disable sharpness.
vdpau_set_property: property=25, value=0
vo_vdpau: disable noise reduction.
vdpau_set_property: property=4, value=100
vo_vdpau: vdpau_update_csc: hue=0.000000, saturation=1.000000, contrast=1.000000, brightness=0.000000, color_standard=0 studio_levels=0
vdpau_set_property: property=1, value=0
wait-for-job-state stop/waiting

Alles anzeigen

Nach der eingabe der oben genannten Befehle

Code

svdrpsend plug softhddevice stat
svdrpsend plug softhddevice atta -d :1

läuft es dann normal

Hoffe das hilft euch weiter beim debuggen.
Danke schon mal für die Arbeit

lg
Joe

seahawk1986 · 25. September 2012

Das sieht sehr merkwürdig aus... zumal bei softhddevice eigentlich immer drei Einträge für wait-for-job-state kommen sollten...
Was sagen denn

Code

dkms status
uname -r

ofenheizer · 25. September 2012

N'abend.

Das habe ich aber auch recht häufig, dass das softhddevice nicht "hochkommt". Ein svdrpsend läuft bei mir in einen Timeout. Das syslog sieht in diesem Fall immer so aus:

Code

Sep 25 07:47:58 vdr vdr: [1815] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.epg
Sep 25 07:47:58 vdr vdr: [1815] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.osd
Sep 25 07:47:58 vdr vdr: [1815] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.plugin
Sep 25 07:47:58 vdr vdr: [1815] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.recording
Sep 25 07:47:58 vdr vdr: [1815] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.remote
Sep 25 07:47:58 vdr vdr: [1815] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.setup
Sep 25 07:47:58 vdr vdr: [1815] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.shutdown
Sep 25 07:47:58 vdr vdr: [1815] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.skin
Sep 25 07:47:58 vdr vdr: [1815] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.timer
Sep 25 07:48:01 vdr vdr: [1815] ERROR: dbus2vdr message handler thread 1815 won't end (waited 3 seconds) - canceling it...
Sep 25 07:48:09 vdr ntpdate[1820]: adjust time server 91.189.94.4 offset 0.000082 sec
Sep 25 07:48:09 vdr vdr: [1757] EPGSearch: search timer update finished
Sep 25 07:48:23 vdr kernel: [   51.743149] init: vdr-frontend main process (1807) terminated with status 1
Sep 25 07:48:23 vdr kernel: [   51.743181] init: vdr-frontend main process ended, respawning
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: new message, object /Plugins/softhddevice, interface de.tvdr.vdr.plugin, member SVDRPCommand
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: don't know what to do...
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: new message, object /Plugins/softhddevice, interface de.tvdr.vdr.plugin, member SVDRPCommand
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: don't know what to do...
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: new message, object /Shutdown, interface org.freedesktop.DBus.Introspectable, member Introspect
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: introspect object /Shutdown with Introspect
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: can't introspect object /Shutdown
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: new message, object /Shutdown, interface de.tvdr.vdr.shutdown, member ManualStart
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: don't know what to do...
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: new message, object /Remote, interface org.freedesktop.DBus.Introspectable, member Introspect
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: introspect object /Remote with Introspect
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: can't introspect object /Remote
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: new message, object /Remote, interface de.tvdr.vdr.remote, member Disable
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: don't know what to do...
Sep 25 07:48:45 vdr kernel: [   73.593071] init: vdr main process (1008) killed by ABRT signal
Sep 25 07:48:45 vdr kernel: [   73.595972] init: vdr-frontend main process (1850) killed by TERM signal
Sep 25 07:49:08 vdr dbus[731]: [system] Failed to activate service 'de.tvdr.vdr': timed out
Sep 25 07:49:33 vdr dbus[731]: [system] Failed to activate service 'de.tvdr.vdr': timed out
Sep 25 07:49:33 vdr vdr-crash: vdr exit with signal ABRT . Restarting

Alles anzeigen

Ich glaube das passiert immer nur, wenn der Fernseher schon an ist. Kann mich aber auch irren. Bei Timeraufnahmen wo der Fernseher aus ist und das Plugin im detached-Mode startet, ist mir der Fehler im Log noch nicht vorgekommen.

Gruss
Markus

seahawk1986 · 25. September 2012

Da kommt der VDR nicht richtig hoch und die vdr-frontend versucht sich zu attachen, wenn er gerade dabei ist wieder zu stoppen und das dbus2vdr-Plugin seine dbus-Dienste gelöst hat... hast du ein Log von einem kompletten Start?
Steht da dann auch eine entsprechende Fehlermeldung in der /var/log/upstart/vdr-frontend.log, dass er keine Verbindung bekommt?

ofenheizer · 25. September 2012

Hier mal das komplette Syslog von heute Morgen, vom Einschalten bis ich dann Bild hatte (ich glaube ich hatte dann noch ein restart vdr abgesetzt):
http://paste.ubuntu.com/1227380/

Im Frontendlog stehen leider keine Zeitstempel bei, daher einmal die Datei, wo auch der Fehlstart mit drin sein muss und zum Vergleich die beiden automatischen Timerstarts von heute, wo der Fernseher nicht an war.
http://paste.ubuntu.com/1227410/
http://paste.ubuntu.com/1227395/

seahawk1986 · 25. September 2012

Hallo,
Aus irgendeinem Grund wird da der VDR beendet und das dbus2vdr Plugin funktioniert dann in dem Zeitraum des Beendens nicht mehr:

Code

Sep 25 07:47:58 vdr vdr: [1815] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.epg
Sep 25 07:47:58 vdr vdr: [1815] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.osd
Sep 25 07:47:58 vdr vdr: [1815] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.plugin
Sep 25 07:47:58 vdr vdr: [1815] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.recording
Sep 25 07:47:58 vdr vdr: [1815] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.remote
Sep 25 07:47:58 vdr vdr: [1815] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.setup
Sep 25 07:47:58 vdr vdr: [1815] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.shutdown
Sep 25 07:47:58 vdr vdr: [1815] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.skin
Sep 25 07:47:58 vdr vdr: [1815] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.timer
Sep 25 07:48:01 vdr vdr: [1815] ERROR: dbus2vdr message handler thread 1815 won't end (waited 3 seconds) - canceling it...
Sep 25 07:48:09 vdr ntpdate[1820]: adjust time server 91.189.94.4 offset 0.000082 sec
Sep 25 07:48:09 vdr vdr: [1757] EPGSearch: search timer update finished
Sep 25 07:48:23 vdr kernel: [   51.743149] init: vdr-frontend main process (1807) terminated with status 1
Sep 25 07:48:23 vdr kernel: [   51.743181] init: vdr-frontend main process ended, respawning
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: new message, object /Plugins/softhddevice, interface de.tvdr.vdr.plugin, member SVDRPCommand
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: don't know what to do...
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: new message, object /Plugins/softhddevice, interface de.tvdr.vdr.plugin, member SVDRPCommand
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: don't know what to do...
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: new message, object /Shutdown, interface org.freedesktop.DBus.Introspectable, member Introspect
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: introspect object /Shutdown with Introspect
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: can't introspect object /Shutdown
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: new message, object /Shutdown, interface de.tvdr.vdr.shutdown, member ManualStart
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: don't know what to do...
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: new message, object /Remote, interface org.freedesktop.DBus.Introspectable, member Introspect
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: introspect object /Remote with Introspect
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: can't introspect object /Remote
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: new message, object /Remote, interface de.tvdr.vdr.remote, member Disable
Sep 25 07:48:23 vdr vdr: [1760] dbus2vdr: don't know what to do...
Sep 25 07:48:45 vdr kernel: [   73.593071] init: vdr main process (1008) killed by ABRT signal
Sep 25 07:48:45 vdr kernel: [   73.595972] init: vdr-frontend main process (1850) killed by TERM signal
Sep 25 07:49:08 vdr dbus[731]: [system] Failed to activate service 'de.tvdr.vdr': timed out
Sep 25 07:49:33 vdr dbus[731]: [system] Failed to activate service 'de.tvdr.vdr': timed out
Sep 25 07:49:33 vdr vdr-crash: vdr exit with signal ABRT . Restarting
Sep 25 07:49:33 vdr kernel: [  121.591093] init: vdr-exit-other main process (2038) terminated with status 1

Alles anzeigen

Da passiert zuvor irgendwas, das die maximale Logging-Rate sprengt:

Code

Sep 25 07:47:57 vdr rsyslogd-2177: imuxsock begins to drop messages from pid 1008 due to rate-limiting
Sep 25 07:47:57 vdr kernel: [   26.252310] init: wait-for-job-state (vdr-frontendvdr) main process (990) killed by TERM signal
Sep 25 07:47:58 vdr rsyslogd-2177: imuxsock lost 55 messages from pid 1008 due to rate-limiting

Kannst du mal deine /etc/rsyslog.conf so anpassen, damit man sehen kann, was da genau passiert?
http://paste.ubuntu.com/1227430/
Dann bitte nochmal ein Log posten, wenn das Problem auftritt.

ofenheizer · 26. September 2012

OK. Änderung gemacht.
Log kommt, wenn der Fehler wieder auftritt.

ofenheizer · 26. September 2012

Guten Morgen seahawk.

Der Start von heute Morgen hatte den Fehler nicht. Ich hänge trotzdem das Log ran.
Es wundert mich nämlich, warum nach dem ersten Start des VDR, dieser dann noch ein zweites Mal gestartet wird. Somit dauert es recht lange bis ich Bild habe.
http://paste.ubuntu.com/1228025/
Um 08:08:06 habe ich den VDR eingeschaltet.
Um 08:08:08 startet lt. Log der VDR.
Und um 08:09:17 gibt es einen Restart des VDR.

Irgendwelche Ideen?

Danke und Gruss.
Markus

seahawk1986 · 26. September 2012

Was auffällt ist das hier:

Code

Sep 26 08:08:26 vdr vdr: video/vdpau: can't create presentation queue: A catch-all error, used when no other error code applies.
Sep 26 08:08:26 vdr vdr: [1825] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.epg
Sep 26 08:08:26 vdr vdr: [1825] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.osd
Sep 26 08:08:26 vdr vdr: [1825] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.plugin
Sep 26 08:08:26 vdr vdr: [1825] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.recording
Sep 26 08:08:26 vdr vdr: [1825] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.remote
Sep 26 08:08:26 vdr vdr: [1825] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.setup
Sep 26 08:08:26 vdr vdr: [1825] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.shutdown
Sep 26 08:08:26 vdr vdr: [1825] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.skin
Sep 26 08:08:26 vdr vdr: [1825] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.timer
Sep 26 08:08:26 vdr vdr: [1007] connect from 127.0.0.1, port 35006 - accepted
Sep 26 08:08:26 vdr vdr: [1007] timer 63 (44 0457-0606 'Manu's Bastelzeugs~Mirjam Asam - Mode mit Stil~2012.10.05-05:00-Fr') added
Sep 26 08:08:26 vdr kernel: [   31.006094] vdr[1007]: segfault at 0 ip 00007fa54c6e7236 sp 00007fffa85639c0 error 4 in libvdr-live.so.1.7.27[7fa54c6a2000+199000]
Sep 26 08:08:26 vdr kernel: [   31.022149] init: vdr main process (1007) killed by SEGV signal
Sep 26 08:08:26 vdr kernel: [   31.024431] init: vdr-frontend main process (1817) killed by TERM signal

Alles anzeigen

Johns hatte vermutet, dass da der X-Server noch nicht komplett da ist: [yaVDR64-0.5.0-alpha1]vdr wird sporadisch beim starten gekillt

hummel99 und Boostar haben das durch ein 5-Sekunden Delay beim Start der vdr-frontend umgangen: [yaVDR64-0.5.0-alpha1]vdr wird sporadisch beim starten gekillt
Eine elegantere Lösung scheint es noch nicht zu geben...

mini73 · 26. September 2012

Moin!

Zuerst einmal stürzt da irgendwas beim Booten ab:

Code

Sep 26 08:08:09 vdr kernel: [   13.414579] ------------[ cut here ]------------
Sep 26 08:08:09 vdr kernel: [   13.414590] WARNING: at /build/buildd/linux-3.2.0/arch/x86/mm/ioremap.c:102 __ioremap_caller+0x312/0x390()
Sep 26 08:08:09 vdr kernel: [   13.414593] Hardware name: To Be Filled By O.E.M.
Sep 26 08:08:09 vdr kernel: [   13.414595] Modules linked in: snd_hda_codec_hdmi ds3000 cx88_dvb cx88_vp3054_i2c videobuf_dvb rc_tevii_nec nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc snd_hda_intel snd_hda_codec snd_hwdep snd_pcm tuner nvidia(P) cx8800 snd_seq_midi snd_rawmidi cx8802 cx88xx tveeprom v4l2_common psmouse xfs videodev v4l2_compat_ioctl32 videobuf_dma_sg snd_seq_midi_event serio_raw videobuf_core btcx_risc snd_seq nls_iso8859_1 nls_cp437 snd_timer ir_lirc_codec lirc_dev snd_seq_device ir_mce_kbd_decoder dvb_usb_dw2102 ir_sony_decoder dvb_usb ir_jvc_decoder ir_rc6_decoder dvb_core ir_rc5_decoder rc_rc6_mce ir_nec_decoder nuvoton_cir vfat snd fat rc_core i915 drm_kms_helper mac_hid soundcore snd_page_alloc drm i2c_algo_bit mei(C) video w83627ehf hwmon_vid coretemp lp parport r8169
Sep 26 08:08:09 vdr kernel: [   13.414653] Pid: 972, comm: Xorg Tainted: P         C O 3.2.0-31-generic #50-Ubuntu
Sep 26 08:08:09 vdr kernel: [   13.414656] Call Trace:
Sep 26 08:08:09 vdr kernel: [   13.414663]  [<ffffffff81066d7f>] warn_slowpath_common+0x7f/0xc0
Sep 26 08:08:09 vdr kernel: [   13.414667]  [<ffffffff81066dda>] warn_slowpath_null+0x1a/0x20
Sep 26 08:08:09 vdr kernel: [   13.414670]  [<ffffffff810410d2>] __ioremap_caller+0x312/0x390
Sep 26 08:08:09 vdr kernel: [   13.414674]  [<ffffffff8103dcf9>] ? default_spin_lock_flags+0x9/0x10
Sep 26 08:08:09 vdr kernel: [   13.414784]  [<ffffffffa0aa9e35>] ? os_map_kernel_space+0x85/0xf0 [nvidia]
Sep 26 08:08:09 vdr kernel: [   13.414791]  [<ffffffff81524d6b>] ? pci_conf1_read+0xcb/0x120
Sep 26 08:08:09 vdr kernel: [   13.414795]  [<ffffffff81041184>] ioremap_cache+0x14/0x20
Sep 26 08:08:09 vdr kernel: [   13.414878]  [<ffffffffa0aa9e35>] os_map_kernel_space+0x85/0xf0 [nvidia]
Sep 26 08:08:09 vdr kernel: [   13.414968]  [<ffffffffa0a70771>] _nv014630rm+0xeb/0x10b [nvidia]
Sep 26 08:08:09 vdr kernel: [   13.415043]  [<ffffffffa03b8eba>] ? _nv009556rm+0x89/0x140 [nvidia]
Sep 26 08:08:09 vdr kernel: [   13.415117]  [<ffffffffa03b9029>] ? _nv014196rm+0xb8/0x102 [nvidia]
Sep 26 08:08:09 vdr kernel: [   13.415191]  [<ffffffffa03b94d7>] ? _nv014236rm+0x58/0x9e [nvidia]
Sep 26 08:08:09 vdr kernel: [   13.415264]  [<ffffffffa03b4448>] ? _nv014206rm+0xbe/0x2f0 [nvidia]
Sep 26 08:08:09 vdr kernel: [   13.415337]  [<ffffffffa03b4725>] ? _nv014241rm+0xab/0x174 [nvidia]
Sep 26 08:08:09 vdr kernel: [   13.415409]  [<ffffffffa03b483e>] ? _nv014205rm+0x50/0x5d [nvidia]
Sep 26 08:08:09 vdr kernel: [   13.415484]  [<ffffffffa03bb8a6>] ? _nv014181rm+0x9ef/0xb29 [nvidia]
Sep 26 08:08:09 vdr kernel: [   13.415596]  [<ffffffffa0a84d6f>] ? _nv012451rm+0x174/0x662 [nvidia]
Sep 26 08:08:09 vdr kernel: [   13.415683]  [<ffffffffa0a84ced>] ? _nv012451rm+0xf2/0x662 [nvidia]
Sep 26 08:08:09 vdr kernel: [   13.415776]  [<ffffffffa0402ee1>] ? _nv003982rm+0x1e5/0x1deb [nvidia]
Sep 26 08:08:09 vdr kernel: [   13.415964]  [<ffffffffa07e5fcf>] ? _nv004007rm+0xab92/0xd298 [nvidia]
Sep 26 08:08:09 vdr kernel: [   13.416153]  [<ffffffffa07e45e8>] ? _nv004007rm+0x91ab/0xd298 [nvidia]
Sep 26 08:08:09 vdr kernel: [   13.416219]  [<ffffffffa037e5ee>] ? _nv009852rm+0x25/0x40 [nvidia]
Sep 26 08:08:09 vdr kernel: [   13.416305]  [<ffffffffa0a84a81>] ? _nv014687rm+0x7c8/0x942 [nvidia]
Sep 26 08:08:09 vdr kernel: [   13.416392]  [<ffffffffa0a85bab>] ? _nv001089rm+0x4fc/0x750 [nvidia]
Sep 26 08:08:09 vdr kernel: [   13.416478]  [<ffffffffa0a7c03c>] ? rm_init_adapter+0xae/0x1bb [nvidia]
Sep 26 08:08:09 vdr kernel: [   13.416483]  [<ffffffff810da70b>] ? request_threaded_irq+0xab/0x1c0
Sep 26 08:08:09 vdr kernel: [   13.416567]  [<ffffffffa0a9f52c>] ? nv_kern_open+0x46c/0x820 [nvidia]
Sep 26 08:08:09 vdr kernel: [   13.416571]  [<ffffffff8117ba40>] ? mount_fs+0x1b0/0x1b0
Sep 26 08:08:09 vdr kernel: [   13.416576]  [<ffffffff8117c48a>] ? chrdev_open+0xda/0x230
Sep 26 08:08:09 vdr kernel: [   13.416579]  [<ffffffff81175bd0>] ? __dentry_open+0x290/0x360
Sep 26 08:08:09 vdr kernel: [   13.416583]  [<ffffffff8117c3b0>] ? cdev_put+0x30/0x30
Sep 26 08:08:09 vdr kernel: [   13.416587]  [<ffffffff8129cdbc>] ? security_inode_permission+0x1c/0x30
Sep 26 08:08:09 vdr kernel: [   13.416591]  [<ffffffff8118389a>] ? inode_permission+0x4a/0x110
Sep 26 08:08:09 vdr kernel: [   13.416595]  [<ffffffff8117624d>] ? vfs_open+0x3d/0x40
Sep 26 08:08:09 vdr kernel: [   13.416598]  [<ffffffff81177130>] ? nameidata_to_filp+0x40/0x50
Sep 26 08:08:09 vdr kernel: [   13.416602]  [<ffffffff811860d8>] ? do_last+0x3f8/0x730
Sep 26 08:08:09 vdr kernel: [   13.416605]  [<ffffffff811877b1>] ? path_openat+0xd1/0x3f0
Sep 26 08:08:09 vdr kernel: [   13.416610]  [<ffffffff8165a4fe>] ? _raw_spin_lock+0xe/0x20
Sep 26 08:08:09 vdr kernel: [   13.416614]  [<ffffffff8112ede0>] ? shmem_xattr_get.isra.24+0x80/0xd0
Sep 26 08:08:09 vdr kernel: [   13.416618]  [<ffffffff81187bf2>] ? do_filp_open+0x42/0xa0
Sep 26 08:08:09 vdr kernel: [   13.416624]  [<ffffffff81319321>] ? strncpy_from_user+0x31/0x40
Sep 26 08:08:09 vdr kernel: [   13.416627]  [<ffffffff81182f3a>] ? do_getname+0x10a/0x180
Sep 26 08:08:09 vdr kernel: [   13.416630]  [<ffffffff8165a4fe>] ? _raw_spin_lock+0xe/0x20
Sep 26 08:08:09 vdr kernel: [   13.416634]  [<ffffffff81194eb7>] ? alloc_fd+0xf7/0x150
Sep 26 08:08:09 vdr kernel: [   13.416638]  [<ffffffff8117722d>] ? do_sys_open+0xed/0x220
Sep 26 08:08:09 vdr kernel: [   13.416642]  [<ffffffff8119759f>] ? mntput+0x1f/0x30
Sep 26 08:08:09 vdr kernel: [   13.416645]  [<ffffffff81177380>] ? sys_open+0x20/0x30
Sep 26 08:08:09 vdr kernel: [   13.416649]  [<ffffffff81662b02>] ? system_call_fastpath+0x16/0x1b
Sep 26 08:08:09 vdr kernel: [   13.416652] ---[ end trace 75905257df5e507d ]---

Alles anzeigen

Wenn ich raten müsste, sieht das nach NVidia aus, hab aber, ehrlich gesagt, keine Ahnung, was das wirklich ist.

Dann musst du deine setup.conf mal überprüfen, da steht Mist drin:

Code

Sep 26 08:08:13 vdr vdr: [1007] ERROR: invalid sat cable number in '�9N'

Und da vermutlich der Grafiktreiber nicht richtig läuft, kommt softhddevice aus dem Tritt und beendet den vdr:

Code

Sep 26 08:08:26 vdr vdr: video/vdpau: can't create presentation queue: A catch-all error, used when no other error code applies.

Ist aber nur geraten...

Lars.

ofenheizer · 26. September 2012

Servus mini.

Der Absturz ist "normal". Der Nvidia-treiber kann noch nicht mit UEFI-Boot umgehen. Gibt es Berichte im Inet und sogar hier im Forum.
Sollte aber nicht stören und tut es im betrieb auch nicht.

Die zweiten Meldungen hat CKone auch. Steht auch nix besonderes in der setup.conf drin und im OSD habe ich da schon mal nachgesehen. Jeder Adapter hat sein eigenes Kabel zugewiesen.

Hm. Der Grafikktreiber läuft ja auch, wenn der VDR autom. für einen Timer startet, also softhddevice detached startet. Da gibt es diese Probleme aber nie lt. Log.

Gruss.
Markus

seahawk1986 · 26. September 2012

Was wäre denn, wenn man z.B. den mplayer mit einem kurzen Video unter Nutzung von VDPAU als "Testballon" vor dem attachen des Frontends laufen lassen würde, um zu sehen ob der Treiber/X-Server schon so weit ist?

[solved] [yavdr0.5-beta] SoftHDDevice kommt nicht hoch

Jetzt mitmachen!

Teilen