Posts by ruediger-isolde

Hallo,

habe im syslog ein bischen gestöbert und es könnte ein problem mit dem PCIE sein.

 Feb  3 13:27:10 raspberrypi kernel: [    1.330354] brcm-pcie fd500000.pcie: host bridge /scb/pcie@7d500000 ranges:
Feb  3 13:27:10 raspberrypi kernel: [    1.332980] brcm-pcie fd500000.pcie:   No bus range found for /scb/pcie@7d500000, using [bus 00-ff]
Feb  3 13:27:10 raspberrypi kernel: [    1.335682] brcm-pcie fd500000.pcie:      MEM 0x0600000000..0x063fffffff -> 0x00c0000000
Feb  3 13:27:10 raspberrypi avahi-daemon[364]: Network interface enumeration completed.
Feb  3 13:27:10 raspberrypi kernel: [    1.338378] brcm-pcie fd500000.pcie:   IB MEM 0x0000000000..0x007fffffff -> 0x0400000000
Feb  3 13:27:10 raspberrypi kernel: [    1.387993] brcm-pcie fd500000.pcie: link up, 5.0 GT/s PCIe x1 (SSC)
Feb  3 13:27:10 raspberrypi kernel: [    1.390970] brcm-pcie fd500000.pcie: PCI host bridge to bus 0000:00
Feb  3 13:27:10 raspberrypi kernel: [    1.393578] pci_bus 0000:00: root bus resource [bus 00-ff]
Feb  3 13:27:10 raspberrypi kernel: [    1.396228] pci_bus 0000:00: root bus resource [mem 0x600000000-0x63fffffff] (bus address [0xc0000000-0xffffffff])
Feb  3 13:27:10 raspberrypi kernel: [    1.398984] pci 0000:00:00.0: [14e4:2711] type 01 class 0x060400
Feb  3 13:27:10 raspberrypi avahi-daemon[364]: Registering new address record for ::1 on lo.*.
Feb  3 13:27:10 raspberrypi kernel: [    1.401898] pci 0000:00:00.0: PME# supported from D0 D3hot
Feb  3 13:27:10 raspberrypi kernel: [    1.408186] pci 0000:00:00.0: bridge configuration invalid ([bus ff-ff]), reconfiguring
Feb  3 13:27:10 raspberrypi kernel: [    1.411122] pci 0000:01:00.0: [12d8:2304] type 01 class 0x060400
Feb  3 13:27:10 raspberrypi kernel: [    1.414157] pci 0000:01:00.0: supports D1 D2
Feb  3 13:27:10 raspberrypi kernel: [    1.416781] pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold
Feb  3 13:27:10 raspberrypi avahi-daemon[364]: Registering new address record for 127.0.0.1 on lo.IPv4.
Feb  3 13:27:10 raspberrypi kernel: [    1.419484] pci 0000:01:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x1 link at 0000:00:00.0 (capable of 8.000 Gb/s with 5.0 GT/s PCIe x2 link)
Feb  3 13:27:10 raspberrypi kernel: [    1.428354] pci 0000:01:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
Feb  3 13:27:10 raspberrypi kernel: [    1.431548] pci 0000:02:01.0: [12d8:2304] type 01 class 0x060400
Feb  3 13:27:10 raspberrypi kernel: [    1.434705] pci 0000:02:01.0: supports D1 D2
Feb  3 13:27:10 raspberrypi systemd[1]: Starting System Logging Service...
Feb  3 13:27:10 raspberrypi kernel: [    1.437442] pci 0000:02:01.0: PME# supported from D0 D1 D2 D3hot D3cold
Feb  3 13:27:10 raspberrypi kernel: [    1.440609] pci 0000:02:02.0: [12d8:2304] type 01 class 0x060400
Feb  3 13:27:10 raspberrypi kernel: [    1.443685] pci 0000:02:02.0: supports D1 D2
Feb  3 13:27:10 raspberrypi kernel: [    1.446373] pci 0000:02:02.0: PME# supported from D0 D1 D2 D3hot D3cold
Feb  3 13:27:10 raspberrypi kernel: [    1.452391] pci 0000:02:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
Feb  3 13:27:10 raspberrypi kernel: [    1.455111] pci 0000:02:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
Feb  3 13:27:10 raspberrypi kernel: [    1.458014] pci 0000:03:00.0: [1b4b:9215] type 00 class 0x010601
Feb  3 13:27:10 raspberrypi kernel: [    1.460642] pci 0000:03:00.0: reg 0x10: [io  0x8000-0x8007]
Feb  3 13:27:10 raspberrypi kernel: [    1.463249] pci 0000:03:00.0: reg 0x14: [io  0x8040-0x8043]
Feb  3 13:27:10 raspberrypi kernel: [    1.465802] pci 0000:03:00.0: reg 0x18: [io  0x8100-0x8107]
Feb  3 13:27:10 raspberrypi systemd[1]: Condition check resulted in Turn on SSH if /boot/ssh is present being skipped.
Feb  3 13:27:10 raspberrypi kernel: [    1.468329] pci 0000:03:00.0: reg 0x1c: [io  0x8140-0x8143]
Feb  3 13:27:10 raspberrypi kernel: [    1.470813] pci 0000:03:00.0: reg 0x20: [io  0x800000-0x80001f]
Feb  3 13:27:10 raspberrypi kernel: [    1.473261] pci 0000:03:00.0: reg 0x24: [mem 0x00900000-0x009007ff]
Feb  3 13:27:10 raspberrypi kernel: [    1.475686] pci 0000:03:00.0: reg 0x30: [mem 0x610000000-0x61000ffff pref]
Feb  3 13:27:10 raspberrypi kernel: [    1.478133] pci 0000:03:00.0: Enabling fixed DMA alias to 00.1
Feb  3 13:27:10 raspberrypi kernel: [    1.480669] pci 0000:03:00.0: PME# supported from D3hot
Feb  3 13:27:10 raspberrypi systemd[1]: Starting User Login Management...
Feb  3 13:27:10 raspberrypi kernel: [    1.486631] pci_bus 0000:03: busn_res: [bus 03-ff] end is updated to 03
Feb  3 13:27:10 raspberrypi kernel: [    1.489352] pci 0000:04:00.0: [dd01:0005] type 00 class 0x048000
Feb  3 13:27:10 raspberrypi kernel: [    1.491877] pci 0000:04:00.0: reg 0x10: [mem 0xffffffffffff0000-0xffffffffffffffff 64bit]
Feb  3 13:27:10 raspberrypi kernel: [    1.498059] pci_bus 0000:04: busn_res: [bus 04-ff] end is updated to 04
Feb  3 13:27:10 raspberrypi kernel: [    1.500504] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 04
Feb  3 13:27:10 raspberrypi rsyslogd: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd.  [v8.2102.0]
Feb  3 13:27:10 raspberrypi kernel: [    1.502938] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 04
Feb  3 13:27:10 raspberrypi kernel: [    1.505364] pci 0000:00:00.0: BAR 8: assigned [mem 0x600000000-0x6001fffff]
Feb  3 13:27:10 raspberrypi kernel: [    1.507786] pci 0000:01:00.0: BAR 8: assigned [mem 0x600000000-0x6001fffff]
Feb  3 13:27:10 raspberrypi kernel: [    1.510170] pci 0000:01:00.0: BAR 7: no space for [io  size 0x1000]
Feb  3 13:27:10 raspberrypi kernel: [    1.512524] pci 0000:01:00.0: BAR 7: failed to assign [io  size 0x1000]
Feb  3 13:27:10 raspberrypi rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="390" x-info="https://www.rsyslog.com"] start
Feb  3 13:27:10 raspberrypi kernel: [    1.514884] pci 0000:02:01.0: BAR 8: assigned [mem 0x600000000-0x6000fffff]
Feb  3 13:27:10 raspberrypi kernel: [    1.517239] pci 0000:02:02.0: BAR 8: assigned [mem 0x600100000-0x6001fffff]
Feb  3 13:27:10 raspberrypi kernel: [    1.519581] pci 0000:02:01.0: BAR 7: no space for [io  size 0x1000]
Feb  3 13:27:10 raspberrypi kernel: [    1.521937] pci 0000:02:01.0: BAR 7: failed to assign [io  size 0x1000]
Feb  3 13:27:10 raspberrypi kernel: [    1.524277] pci 0000:03:00.0: BAR 6: assigned [mem 0x600000000-0x60000ffff pref]
Feb  3 13:27:10 raspberrypi kernel: [    1.526609] pci 0000:03:00.0: BAR 5: assigned [mem 0x600010000-0x6000107ff]
Feb  3 13:27:10 raspberrypi kernel: [    1.528907] pci 0000:03:00.0: BAR 4: no space for [io  size 0x0020]
Feb  3 13:27:10 raspberrypi kernel: [    1.531204] pci 0000:03:00.0: BAR 4: failed to assign [io  size 0x0020]
Feb  3 13:27:10 raspberrypi kernel: [    1.533468] pci 0000:03:00.0: BAR 0: no space for [io  size 0x0008]
Feb  3 13:27:10 raspberrypi kernel: [    1.535713] pci 0000:03:00.0: BAR 0: failed to assign [io  size 0x0008]
Feb  3 13:27:10 raspberrypi kernel: [    1.537981] pci 0000:03:00.0: BAR 2: no space for [io  size 0x0008]
Feb  3 13:27:10 raspberrypi kernel: [    1.540197] pci 0000:03:00.0: BAR 2: failed to assign [io  size 0x0008]
Feb  3 13:27:10 raspberrypi kernel: [    1.542375] pci 0000:03:00.0: BAR 1: no space for [io  size 0x0004]
Feb  3 13:27:10 raspberrypi kernel: [    1.544571] pci 0000:03:00.0: BAR 1: failed to assign [io  size 0x0004]
Feb  3 13:27:10 raspberrypi kernel: [    1.546759] pci 0000:03:00.0: BAR 3: no space for [io  size 0x0004]
Feb  3 13:27:10 raspberrypi kernel: [    1.548907] pci 0000:03:00.0: BAR 3: failed to assign [io  size 0x0004]
Feb  3 13:27:10 raspberrypi kernel: [    1.551067] pci 0000:02:01.0: PCI bridge to [bus 03]
Feb  3 13:27:10 raspberrypi kernel: [    1.553216] pci 0000:02:01.0:   bridge window [mem 0x600000000-0x6000fffff]
Feb  3 13:27:10 raspberrypi kernel: [    1.555418] pci 0000:04:00.0: BAR 0: assigned [mem 0x600100000-0x60010ffff 64bit]
Feb  3 13:27:10 raspberrypi kernel: [    1.557616] pci 0000:02:02.0: PCI bridge to [bus 04]
Feb  3 13:27:10 raspberrypi kernel: [    1.559763] pci 0000:02:02.0:   bridge window [mem 0x600100000-0x6001fffff]
Feb  3 13:27:10 raspberrypi kernel: [    1.561951] pci 0000:01:00.0: PCI bridge to [bus 02-04]
Feb  3 13:27:10 raspberrypi kernel: [    1.564060] pci 0000:01:00.0:   bridge window [mem 0x600000000-0x6001fffff]
Feb  3 13:27:10 raspberrypi kernel: [    1.566217] pci 0000:00:00.0: PCI bridge to [bus 01-04]
Feb  3 13:27:10 raspberrypi kernel: [    1.568324] pci 0000:00:00.0:   bridge window [mem 0x600000000-0x6001fffff]

hat jemand eine idee woher die Probleme kommen.

Kernel 5.16.4-v8+ und dddvb-0.9.37.

Gruß

Rüdiger

Hallo,

leider der gleiche Fehler mit Ausgabeplugin(vnsiserver).

Der rot makierte Eintrag scheind das Problem zu seit.

Feb 1 13:24:12 raspberrypi vdr: [29803] VDR version 2.4.1 started

Feb 1 13:24:12 raspberrypi vdr: [29803] switched to user 'vdr'

Feb 1 13:24:12 raspberrypi vdr: [29803] codeset is 'UTF-8' - known

Feb 1 13:24:12 raspberrypi vdr: [29803] found 28 locales in /usr/share/locale

Feb 1 13:24:12 raspberrypi vdr: [29803] loading plugin: /usr/lib/vdr/plugins/libvdr-vnsiserver.so.2.4.1

Feb 1 13:24:12 raspberrypi vdr: [29803] loading /var/lib/vdr/setup.conf

Feb 1 13:24:12 raspberrypi vdr: [29803] loading /var/lib/vdr/sources.conf

Feb 1 13:24:12 raspberrypi vdr: [29803] loading /var/lib/vdr/diseqc.conf

Feb 1 13:24:12 raspberrypi vdr: [29803] loading /var/lib/vdr/scr.conf

Feb 1 13:24:12 raspberrypi vdr: [29803] loading /var/lib/vdr/channels.conf

Feb 1 13:24:12 raspberrypi vdr: [29803] loading /var/lib/vdr/timers.conf

Feb 1 13:24:12 raspberrypi vdr: [29803] loading /var/lib/vdr/commands.conf

Feb 1 13:24:12 raspberrypi vdr: [29803] loading /var/lib/vdr/reccmds.conf

Feb 1 13:24:12 raspberrypi vdr: [29803] loading /var/lib/vdr/svdrphosts.conf

Feb 1 13:24:12 raspberrypi vdr: [29803] loading /var/lib/vdr/keymacros.conf

Feb 1 13:24:12 raspberrypi vdr: [29803] registered source parameters for 'A - ATSC'

Feb 1 13:24:12 raspberrypi vdr: [29804] video directory scanner thread started (pid=29803, tid=29804, prio=low)

Feb 1 13:24:12 raspberrypi vdr: [29803] registered source parameters for 'C - DVB-C'

Feb 1 13:24:12 raspberrypi vdr: [29805] epg data reader thread started (pid=29803, tid=29805, prio=high)

Feb 1 13:24:12 raspberrypi vdr: [29803] registered source parameters for 'S - DVB-S'

Feb 1 13:24:12 raspberrypi vdr: [29805] reading EPG data from /var/cache/vdr/epg.data

Feb 1 13:24:12 raspberrypi vdr: [29803] registered source parameters for 'T - DVB-T'

Feb 1 13:24:12 raspberrypi vdr: [29803] detected /dev/dvb/adapter3/frontend0

Feb 1 13:24:12 raspberrypi vdr: [29805] epg data reader thread ended (pid=29803, tid=29805)

Feb 1 13:24:12 raspberrypi vdr: [29803] detected /dev/dvb/adapter2/frontend0

Feb 1 13:24:12 raspberrypi vdr: [29803] detected /dev/dvb/adapter1/frontend0

Feb 1 13:24:12 raspberrypi vdr: [29803] detected /dev/dvb/adapter0/frontend0

Feb 1 13:24:12 raspberrypi vdr: [29803] probing /dev/dvb/adapter0/frontend0

Feb 1 13:24:12 raspberrypi vdr: [29803] creating cDvbDevice

Feb 1 13:24:12 raspberrypi vdr: [29803] new device number 1 (card index 1)

Feb 1 13:24:12 raspberrypi vdr: [29803] DVB API version is 0x050B (VDR was built with 0x050B)

Feb 1 13:24:12 raspberrypi vdr: [29803] frontend 0/0 provides DVB-S,DVB-S2,DSS with QPSK ("STV0910")

Feb 1 13:24:12 raspberrypi vdr: [29808] frontend 0/0 tuner thread started (pid=29803, tid=29808, prio=high)

Feb 1 13:24:12 raspberrypi vdr: [29808] cTimeMs: using monotonic clock (resolution is 1 ns)

Feb 1 13:24:12 raspberrypi vdr: [29803] probing /dev/dvb/adapter1/frontend0

Feb 1 13:24:12 raspberrypi vdr: [29803] creating cDvbDevice

Feb 1 13:24:12 raspberrypi vdr: [29803] new device number 2 (card index 2)

Feb 1 13:24:12 raspberrypi vdr: [29809] device 1 section handler thread started (pid=29803, tid=29809, prio=low)

Feb 1 13:24:12 raspberrypi vdr: [29803] frontend 1/0 provides DVB-S,DVB-S2,DSS with QPSK ("STV0910")

Feb 1 13:24:12 raspberrypi vdr: [29812] frontend 1/0 tuner thread started (pid=29803, tid=29812, prio=high)

Feb 1 13:24:12 raspberrypi vdr: [29803] probing /dev/dvb/adapter2/frontend0

Feb 1 13:24:12 raspberrypi vdr: [29803] creating cDvbDevice

Feb 1 13:24:12 raspberrypi vdr: [29803] new device number 3 (card index 3)

Feb 1 13:24:12 raspberrypi vdr: [29813] device 2 section handler thread started (pid=29803, tid=29813, prio=low)

Feb 1 13:24:12 raspberrypi vdr: [29803] frontend 2/0 provides DVB-S,DVB-S2,DSS with QPSK ("STV0910")

Feb 1 13:24:12 raspberrypi vdr: [29816] frontend 2/0 tuner thread started (pid=29803, tid=29816, prio=high)

Feb 1 13:24:12 raspberrypi vdr: [29803] probing /dev/dvb/adapter3/frontend0

Feb 1 13:24:12 raspberrypi vdr: [29803] creating cDvbDevice

Feb 1 13:24:12 raspberrypi vdr: [29803] new device number 4 (card index 4)

Feb 1 13:24:12 raspberrypi vdr: [29817] device 3 section handler thread started (pid=29803, tid=29817, prio=low)

Feb 1 13:24:12 raspberrypi systemd[1]: Started Video Disk Recorder.

Feb 1 13:24:12 raspberrypi vdr: [29803] frontend 3/0 provides DVB-S,DVB-S2,DSS with QPSK ("STV0910")

Feb 1 13:24:12 raspberrypi vdr: [29819] frontend 3/0 tuner thread started (pid=29803, tid=29819, prio=high)

Feb 1 13:24:12 raspberrypi vdr: [29803] found 4 DVB devices

Feb 1 13:24:12 raspberrypi vdr: [29820] device 4 section handler thread started (pid=29803, tid=29820, prio=low)

Feb 1 13:24:12 raspberrypi vdr: [29803] initializing plugin: vnsiserver (1.8.0): VDR-Network-Streaming-Interface (VNSI) Server

Feb 1 13:24:12 raspberrypi vdr: [29803] setting primary device to 1

Feb 1 13:24:12 raspberrypi vdr: [29803] device 1 has no MPEG decoder

Feb 1 13:24:12 raspberrypi vdr: [29803] assuming manual start of VDR

Feb 1 13:24:12 raspberrypi vdr: [29803] setting current skin to "lcars"

Feb 1 13:24:12 raspberrypi vdr: [29803] loading /var/lib/vdr/themes/lcars-default.theme

Feb 1 13:24:12 raspberrypi vdr: [29803] starting plugin: vnsiserver

Feb 1 13:24:12 raspberrypi vdr: [29803] VNSI: Starting vnsi server at port=34890

Feb 1 13:24:12 raspberrypi vdr: [29803] VNSI: VNSI Server started

Feb 1 13:24:12 raspberrypi vdr: [29821] VNSI Server thread started (pid=29803, tid=29821, prio=high)

Feb 1 13:24:12 raspberrypi vdr: [29803] VNSI: Channel streaming timeout: 10 seconds

Feb 1 13:24:12 raspberrypi vdr: [29803] loading /var/cache/vdr/cam.data

Feb 1 13:24:12 raspberrypi vdr: [29803] switching to channel 1 S19.2E-1-1089-12003 (RTL Television)

Feb 1 13:24:12 raspberrypi vdr: [29803] setting watchdog timer to 60 seconds

Feb 1 13:24:12 raspberrypi vdr: [29824] SVDRP server handler thread started (pid=29803, tid=29824, prio=low)

Feb 1 13:24:12 raspberrypi vdr: [29824] SVDRP raspberrypi opening port 6419/tcp

Feb 1 13:24:12 raspberrypi vdr: [29824] SVDRP raspberrypi listening on port 6419/tcp

Feb 1 13:24:12 raspberrypi vdr: [29822] VNSIStatus thread started (pid=29803, tid=29822, prio=high)

Feb 1 13:24:12 raspberrypi vdr: [29823] VNSITimers thread started (pid=29803, tid=29823, prio=high)

Feb 1 13:24:12 raspberrypi vdr: [29803] OSD size changed to 720x480 @ 1

Feb 1 13:24:12 raspberrypi vdr: [29803] ERROR: no OSD provider available - using dummy OSD!

Feb 1 13:24:12 raspberrypi vdr: [29803] ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1235)

Feb 1 13:24:12 raspberrypi vdr: [29804] video directory scanner thread ended (pid=29803, tid=29804)

Feb 1 13:24:12 raspberrypi vdr: [29803] ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1301)

Feb 1 13:24:12 raspberrypi vdr: [29808] ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1670)

Feb 1 13:24:12 raspberrypi kernel: [59612.044227] ddbridge 0000:04:00.0: dtv_property_process_set: SET cmd 0x00000000 undefined

Feb 1 13:24:12 raspberrypi vdr: [29803] ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1235)

Feb 1 13:24:12 raspberrypi vdr: [29803] ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1301)

Feb 1 13:24:14 raspberrypi vdr: [29803] ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1235)

Feb 1 13:24:14 raspberrypi vdr: [29803] ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1301)

Feb 1 13:24:14 raspberrypi vdr: [29803] max. latency time 1 seconds

Feb 1 13:24:15 raspberrypi vdr: [29803] ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1235)

Feb 1 13:24:15 raspberrypi vdr: [29803] ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1301)

Feb 1 13:24:15 raspberrypi vdr: [29822] VNSI: Requesting clients to reload recordings list (1)

Feb 1 13:24:16 raspberrypi vdr: [29803] ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1235)

Feb 1 13:24:16 raspberrypi vdr: [29803] ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1301)

Feb 1 13:24:17 raspberrypi vdr: [29803] ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1235)

Feb 1 13:24:17 raspberrypi vdr: [29803] ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1301)

Gruß

Rüdiger

Hallo,

jetzt das log ab systemctl stop vdr und systemctl start vdr.

Feb 1 08:27:08 raspberrypi systemd[1]: Starting Video Disk Recorder...

Feb 1 08:27:08 raspberrypi vdr: [27339] VDR version 2.4.1 started

Feb 1 08:27:08 raspberrypi vdr: [27339] switched to user 'vdr'

Feb 1 08:27:08 raspberrypi vdr: [27339] codeset is 'UTF-8' - known

Feb 1 08:27:08 raspberrypi vdr: [27339] found 28 locales in /usr/share/locale

Feb 1 08:27:08 raspberrypi vdr: [27339] loading /var/lib/vdr/setup.conf

Feb 1 08:27:08 raspberrypi vdr: [27339] loading /var/lib/vdr/sources.conf

Feb 1 08:27:08 raspberrypi vdr: [27339] loading /var/lib/vdr/diseqc.conf

Feb 1 08:27:08 raspberrypi vdr: [27339] loading /var/lib/vdr/scr.conf

Feb 1 08:27:08 raspberrypi vdr: [27339] loading /var/lib/vdr/channels.conf

Feb 1 08:27:08 raspberrypi vdr: [27339] loading /var/lib/vdr/timers.conf

Feb 1 08:27:08 raspberrypi vdr: [27339] loading /var/lib/vdr/commands.conf

Feb 1 08:27:08 raspberrypi vdr: [27339] loading /var/lib/vdr/reccmds.conf

Feb 1 08:27:08 raspberrypi vdr: [27339] loading /var/lib/vdr/svdrphosts.conf

Feb 1 08:27:08 raspberrypi vdr: [27339] loading /var/lib/vdr/keymacros.conf

Feb 1 08:27:08 raspberrypi vdr: [27339] registered source parameters for 'A - ATSC'

Feb 1 08:27:08 raspberrypi vdr: [27339] registered source parameters for 'C - DVB-C'

Feb 1 08:27:08 raspberrypi vdr: [27339] registered source parameters for 'S - DVB-S'

Feb 1 08:27:08 raspberrypi vdr: [27341] epg data reader thread started (pid=27339, tid=27341, prio=high)

Feb 1 08:27:08 raspberrypi vdr: [27339] registered source parameters for 'T - DVB-T'

Feb 1 08:27:08 raspberrypi vdr: [27341] reading EPG data from /var/cache/vdr/epg.data

Feb 1 08:27:08 raspberrypi vdr: [27340] video directory scanner thread started (pid=27339, tid=27340, prio=low)

Feb 1 08:27:08 raspberrypi vdr: [27339] detected /dev/dvb/adapter3/frontend0

Feb 1 08:27:08 raspberrypi vdr: [27339] detected /dev/dvb/adapter2/frontend0

Feb 1 08:27:08 raspberrypi vdr: [27341] epg data reader thread ended (pid=27339, tid=27341)

Feb 1 08:27:08 raspberrypi vdr: [27339] detected /dev/dvb/adapter1/frontend0

Feb 1 08:27:08 raspberrypi vdr: [27339] detected /dev/dvb/adapter0/frontend0

Feb 1 08:27:08 raspberrypi vdr: [27339] probing /dev/dvb/adapter0/frontend0

Feb 1 08:27:08 raspberrypi vdr: [27339] creating cDvbDevice

Feb 1 08:27:08 raspberrypi vdr: [27339] new device number 1 (card index 1)

Feb 1 08:27:08 raspberrypi vdr: [27339] DVB API version is 0x050B (VDR was built with 0x050B)

Feb 1 08:27:08 raspberrypi vdr: [27339] frontend 0/0 provides DVB-S,DVB-S2,DSS with QPSK ("STV0910")

Feb 1 08:27:08 raspberrypi vdr: [27344] frontend 0/0 tuner thread started (pid=27339, tid=27344, prio=high)

Feb 1 08:27:08 raspberrypi vdr: [27344] cTimeMs: using monotonic clock (resolution is 1 ns)

Feb 1 08:27:08 raspberrypi vdr: [27339] probing /dev/dvb/adapter1/frontend0

Feb 1 08:27:08 raspberrypi vdr: [27339] creating cDvbDevice

Feb 1 08:27:08 raspberrypi vdr: [27339] new device number 2 (card index 2)

Feb 1 08:27:08 raspberrypi vdr: [27345] device 1 section handler thread started (pid=27339, tid=27345, prio=low)

Feb 1 08:27:08 raspberrypi vdr: [27339] frontend 1/0 provides DVB-S,DVB-S2,DSS with QPSK ("STV0910")

Feb 1 08:27:08 raspberrypi vdr: [27348] frontend 1/0 tuner thread started (pid=27339, tid=27348, prio=high)

Feb 1 08:27:08 raspberrypi vdr: [27349] device 2 section handler thread started (pid=27339, tid=27349, prio=low)

Feb 1 08:27:08 raspberrypi vdr: [27339] probing /dev/dvb/adapter2/frontend0

Feb 1 08:27:08 raspberrypi vdr: [27339] creating cDvbDevice

Feb 1 08:27:08 raspberrypi vdr: [27339] new device number 3 (card index 3)

Feb 1 08:27:08 raspberrypi vdr: [27339] frontend 2/0 provides DVB-S,DVB-S2,DSS with QPSK ("STV0910")

Feb 1 08:27:08 raspberrypi vdr: [27352] frontend 2/0 tuner thread started (pid=27339, tid=27352, prio=high)

Feb 1 08:27:08 raspberrypi vdr: [27339] probing /dev/dvb/adapter3/frontend0

Feb 1 08:27:08 raspberrypi vdr: [27339] creating cDvbDevice

Feb 1 08:27:08 raspberrypi vdr: [27353] device 3 section handler thread started (pid=27339, tid=27353, prio=low)

Feb 1 08:27:08 raspberrypi vdr: [27339] new device number 4 (card index 4)

Feb 1 08:27:08 raspberrypi vdr: [27339] frontend 3/0 provides DVB-S,DVB-S2,DSS with QPSK ("STV0910")

Feb 1 08:27:08 raspberrypi vdr: [27356] frontend 3/0 tuner thread started (pid=27339, tid=27356, prio=high)

Feb 1 08:27:08 raspberrypi vdr: [27339] found 4 DVB devices

Feb 1 08:27:08 raspberrypi vdr: [27357] device 4 section handler thread started (pid=27339, tid=27357, prio=low)

Feb 1 08:27:08 raspberrypi vdr: [27339] setting primary device to 1

Feb 1 08:27:08 raspberrypi vdr: [27339] device 1 has no MPEG decoder

Feb 1 08:27:08 raspberrypi systemd[1]: Started Video Disk Recorder.

Feb 1 08:27:08 raspberrypi vdr: [27339] assuming manual start of VDR

Feb 1 08:27:08 raspberrypi vdr: [27339] setting current skin to "lcars"

Feb 1 08:27:08 raspberrypi vdr: [27339] loading /var/lib/vdr/themes/lcars-default.theme

Feb 1 08:27:08 raspberrypi vdr: [27339] loading /var/cache/vdr/cam.data

Feb 1 08:27:08 raspberrypi vdr: [27339] switching to channel 1 S19.2E-1-1089-12003 (RTL Television)

Feb 1 08:27:08 raspberrypi vdr: [27339] setting watchdog timer to 60 seconds

Feb 1 08:27:08 raspberrypi vdr: [27358] SVDRP server handler thread started (pid=27339, tid=27358, prio=low)

Feb 1 08:27:08 raspberrypi vdr: [27358] SVDRP raspberrypi opening port 6419/tcp

Feb 1 08:27:08 raspberrypi vdr: [27358] SVDRP raspberrypi listening on port 6419/tcp

Feb 1 08:27:08 raspberrypi vdr: [27339] OSD size changed to 720x480 @ 1

Feb 1 08:27:08 raspberrypi vdr: [27339] ERROR: no OSD provider available - using dummy OSD!

Feb 1 08:27:08 raspberrypi vdr: [27339] ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1235)

Feb 1 08:27:08 raspberrypi vdr: [27339] ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1301)

Feb 1 08:27:08 raspberrypi vdr: [27344] ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1670)

Feb 1 08:27:08 raspberrypi kernel: [41787.642908] ddbridge 0000:04:00.0: dtv_property_process_set: SET cmd 0x00000000 undefined

Feb 1 08:27:08 raspberrypi vdr: [27339] ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1235)

Feb 1 08:27:08 raspberrypi vdr: [27339] ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1301)

Feb 1 08:27:09 raspberrypi vdr: [27339] ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1235)

Feb 1 08:27:09 raspberrypi vdr: [27339] ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1301)

Feb 1 08:27:09 raspberrypi vdr: [27339] max. latency time 1 seconds

Feb 1 08:27:10 raspberrypi vdr: [27340] video directory scanner thread ended (pid=27339, tid=27340)

Feb 1 08:27:10 raspberrypi vdr: [27339] ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1235)

Feb 1 08:27:10 raspberrypi vdr: [27339] ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1301)

Feb 1 08:27:11 raspberrypi vdr: [27339] ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1235)

Feb 1 08:27:11 raspberrypi vdr: [27339] ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1301)

Feb 1 08:27:12 raspberrypi vdr: [27339] ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1235)

Feb 1 08:27:12 raspberrypi vdr: [27339] ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1301)

Gruß

Rüdiger

Hallo,

OS ist Raspberry PI OS und Kernel 5.10.92-v7l+.

Gruß

Rüdiger

Hallo,

Beim Aufbau eines neuen VDR Server mit

Raspberry Pi CM4 IO Board

PCI bridge: Pericom Semiconductor PI7C9X2G304 EL/SL PCIe2 3-Port/4-Lane Packet Switch (rev 05)

SATA controller: Marvell Technology Group Ltd. 88SE9215 PCIe 2.0 x1 4-port SATA 6 Gb/s Controller (rev 11)

Multimedia controller: Digital Devices GmbH Octopus Bridge V3

habe ich beim starten habe ich folgende errors im log.

ERROR: frontend 0/0: Das Argument ist ungültig (dvbdevice.c:1670)

ddbridge 0000:04:00.0: dtv_property_process_set: SET cmd 0x00000000 undefined

VDR version 2.4.1 mit apt-get installiert

dddvb von https://github.com/DigitalDevices/dddvb nach Anleitung von http://support.digital-devices.eu/index.php?article=151

dmesg | grep dvb gibt mir:

[ 5.124968] dvb_core: loading out-of-tree module taints kernel.

[ 5.383188] dvbdev: DVB: registering new adapter (DDBridge)

[ 5.383204] dvbdev: DVB: registering new adapter (DDBridge)

[ 5.383220] dvbdev: DVB: registering new adapter (DDBridge)

[ 5.383235] dvbdev: DVB: registering new adapter (DDBridge)

was habe ich vergessen oder nicht beachtet.

Gruß

Rüdiger

Hallo,

habe streamdev und vdr abgeändert.
wenn am vdr ein timer programmiert und abgespeichert wird, wird der timer über streamdev-client zum server übertragen und am server ausgeführt.
Habe noch das Problem das ich die Timer auf dem Server mit dem Client nicht löschen kann.
Ab Version ? wurde der aufruf vom Streamdev Menue rausgenommen

cOsdObject *cPluginStreamdevClient::MainMenuAction() {
return NULL;
//return new cStreamdevMenu;
}
Wenn jemand daran Arbeitet würde ich mich über eine rückmeldung freuen.

gruß rüdi

Habe Lösung gefunden.
Die neuste Version vom Streamdev übersetzt und auf den Server überspielt.

Gruß Rüdi

Habe leider eine unstimmigkeit gefunden.
Beim Client/Server Betrieb (Eisfair Server, Linvdr Client) wollte ich beim Client einen neuen Timer über streamdev auf dem Server erstellen.
Leider wurde der Timer nicht auf dem Server angelegt.
Hat schon jemand die das gleiche Problem, oder noch besser eine Lösungsmöglichkeit.

Gruß Rüdi

Das thema wurde schon in http://www.vdrportal.de/board/thread.php?threadid=31929&sid=&hilightuser=2759 behandelt.
Quelltext wieder vorhanden.

gruß rüdiger

Melde dich unter root an.

Gruß
rüdi

Hallo burki,
der Timer wird mit der Housekeeping Funktion die das streamdev plugin
hat automatisch auf den Server übertragen,
Bei mir nach ca. 150 sek. wenn man den Client in ruhe läst, also nicht umschalte.

eine gemeinsame timers.conf datei geht leider nicht. da die Datei nur beim starten des VDR eingelesen wird.

Gruß
Rüdi

Hallo burki,
das streamdev-plugin als ansatzpunlt weil es die funktion zum Timer erstellen und auf den
Server übertrage in der version 0.3.1 schon hat. Ich habe als "nur" den Localen Timer ausgelesen ihn mit "NEWT" des Video Transfer Protocol übertragen und anschliesend
den Timer local gelöscht.

Bin jetzt dabei die Funktion erneut in Quelltext zu packen und einige weitere erweiterungen einzubauen z.b. Uhrzeit vom Server zum Client übertragen um die Uhr des Clients zu stellen.

Gruß Rüdi

Hallo almaron,
ich bin auch über dieses Problem gestolpert.
habe für linvdr0.6 auch eine Lösung, leider ist der Quelltext mir abhandengekommen
so das ich leider nur das ergebnis zur ferfügung stellen kann.
Ich habe das stremdev plugin abgewandelt, so das es die Timer die Local auf dem Client
erstellt sind auf dem server überträgt und anschliesend auf dem Client löscht.
bei interesse bitte meldung.

Gruß Rüdi

Ich habe das dxr3 plugin auf linvdr 0.6 aufgespielt, alles prima
leider kann ich mit dem MPlayer plugin nichts abspielen.
Meldung kein dvb vorhanden.
Meine Frage in welcher Datei muss ich einstellen das der MPlayer die dxr3 als ausgabe nutzt.

Gruß
ruedi

Hallo Leute,

ich möchte über die DXR3 VDR auf dem Monitor darstellen,
ich habe folgendes Problem:
- es wird nur die halbe ausgabe von vdr im overlay dargestellt,
bei xine ist alles ok.

hat jemand da einen Lösungsvorschlag ?

Gruß
Rüdiger