Raspberry pi 2 installation -> VDR problems

[rebelkiller]

Hello,
I just wanted to give a feedback to a fresh rpi2 installation. I updated my LMCE-installation (Core and MD) today (31620).

Basically installation process works fine.
I am using VDR. I have still problems getting VDR to work:

Here are my observations:
- vdr-plugin-remotetimers is not getting installed -> apt-show cache shows it as a virtual package?
- adding e-tobi-repos for VDR in sources.list fixed installation von remotetimer-plugin
- in /etc/vdr/conf.d I had to manually edit some config files (e.g. video directory, disabling lirc as it fires error messages in syslog etc.)

Now that VDR-client is starting and running I still get a black screen when pressing TV on the rpi2-Orbiter. I don't really find out where the problem is.

Maybe some can help.


/var/log/syslog from rpi-MD after pressing TV on the orbiter:

Code: [Select]

...
Nov 17 19:53:30 moon127 vdr: [31046] loading /var/lib/vdr/themes/lcars-default.theme
Nov 17 19:53:30 moon127 vdr: [31046] starting plugin: remotetimers
Nov 17 19:53:30 moon127 vdr: [31046] starting plugin: streamdev-client
Nov 17 19:53:30 moon127 vdr: [31046] starting plugin: svdrpservice
Nov 17 19:53:30 moon127 vdr: [31046] starting plugin: xineliboutput
Nov 17 19:53:30 moon127 vdr: [31098] Remote decoder/display server (cXinelibServer) thread started (pid=31046, tid=31098, prio=high)
v 17 19:53:30 moon127 vdr: [31046] no DVB device found
Nov 17 19:53:30 moon127 vdr: [31095] reading EPG data from /var/cache/vdr/epg.data
Nov 17 19:53:30 moon127 vdr: [31046] initializing plugin: remotetimers (1.0.2): Timer eines anderen VDR bearbeiten
Nov 17 19:53:30 moon127 vdr: [31095] epg data reader thread ended (pid=31046, tid=31095)
Nov 17 19:53:30 moon127 vdr: [31046] initializing plugin: streamdev-client (0.6.1-git): VTP Streaming Client
Nov 17 19:53:30 moon127 vdr: [31046] initializing plugin: svdrpservice (1.0.0): SVDRP client
Nov 17 19:53:30 moon127 vdr: [31046] initializing plugin: xineliboutput (2.0.0-cvs): X11/xine-lib Ausgabe-Plugin
Nov 17 19:53:30 moon127 vdr: [31046] new device number 1
Nov 17 19:53:30 moon127 vdr: [31046] [xine..put] cTimePts: clock_gettime(CLOCK_MONOTONIC): clock resolution 0 us
Nov 17 19:53:30 moon127 vdr: [31046] [xine..put] cTimePts: using monotonic clock
Nov 17 19:53:30 moon127 vdr: [31046] [xine..put] RTP SSRC: 0x7392389b
Nov 17 19:53:30 moon127 vdr: [31046] setting primary device to 1
Nov 17 19:53:30 moon127 vdr: [31046] assuming manual start of VDR
Nov 17 19:53:30 moon127 vdr: [31046] SVDRP listening on port 2001
Nov 17 19:53:30 moon127 vdr: [31046] setting current skin to "lcars"
Nov 17 19:53:30 moon127 vdr: [31046] loading /var/lib/vdr/themes/lcars-default.theme
Nov 17 19:53:30 moon127 vdr: [31046] starting plugin: remotetimers
Nov 17 19:53:30 moon127 vdr: [31046] starting plugin: streamdev-client
Nov 17 19:53:30 moon127 vdr: [31046] starting plugin: svdrpservice
Nov 17 19:53:30 moon127 vdr: [31046] starting plugin: xineliboutput
Nov 17 19:53:30 moon127 vdr: [31098] Remote decoder/display server (cXinelibServer) thread started (pid=31046, tid=31098, prio=high)
Nov 17 19:53:30 moon127 vdr: [31098] [xine..put] cXinelibServer priority set successful SCHED_RR 2 [1,99]
Nov 17 19:53:30 moon127 vdr: [31097] remotetimers update file watcher thread started (pid=31046, tid=31097, prio=high)
Nov 17 19:53:30 moon127 vdr: [31098] [xine..put] Binding server to 127.0.0.1:37890
Nov 17 19:53:30 moon127 vdr: [31097] remotetimers update file watcher now monitoring '/var/lib/video.00/.update'
Nov 17 19:53:30 moon127 vdr: [31098] [xine..put] Listening on port 37890
Nov 17 19:53:30 moon127 vdr: [31098] [xine..put] Listening for UDP broadcasts on port 37890
Nov 17 19:53:30 moon127 vdr: [31098] [discovery] BROADCAST: VDR xineliboutput DISCOVERY 1.0#015#012Server port: 37890#015#012Server address: 127.0.0.1#015#012Server version: xineliboutput-2.0.0-cvs#015#012#015
Nov 17 19:53:30 moon127 vdr: [31094] video directory scanner thread ended (pid=31046, tid=31094)
Nov 17 19:53:30 moon127 vdr: [31093] video directory scanner thread ended (pid=31046, tid=31093)
Nov 17 19:53:30 moon127 vdr: [31046] [xine..put] cXinelibDevice::StartDevice(): Device started
Nov 17 19:53:30 moon127 vdr: [31046] cTimeMs: using monotonic clock (resolution is 1 ns)
Nov 17 19:53:30 moon127 vdr: [31046] switching to channel 1 (Aristo.TV)
Nov 17 19:53:30 moon127 vdr: [31046] info: Kanal nicht verfügbar!
Nov 17 19:53:30 moon127 vdr: [31046] [xine..put] cXinelibOsd::CanHandleAreas(): Device does not support ARGB
Nov 17 19:53:32 moon127 vdr: [31046] setting watchdog timer to 60 seconds
Nov 17 19:53:32 moon127 vdr: [31046] OSD size changed to 720x576 @ 1,42222
Nov 17 19:53:32 moon127 vdr: [31046] [xine..put] cXinelibOsd::CanHandleAreas(): Device does not support ARGB
...

I know that channel 1 not available in this example. LMCE should show at least "nosignal" but it does not.


When starting "StartVDRClient.sh" from the command line I am getting some error messages:

Code: [Select]

Starting Linux Video Disk Recorder: vdr - seems to be running already.
220 moon127 SVDRP VideoDiskRecorder 2.2.0; Tue Nov 17 19:59:20 2015; UTF-8
250 Key "Ok" accepted
221 moon127 closing connection
vdr-sxfe 2.0.0-cvs  (build with xine-lib 1.2.6, using xine-lib 1.2.6)

Automatic reconnection enabled
Post plugins: tvtime:method=use_vo_driver
Fullscreen mode
Protocol: TCP
Verbose mode

VDR server not given, searching ...
Found VDR server: host 127.0.0.1, port 37890
Loaded configuration from file '/root/.xine/config_xineliboutput'
Benchmarking memcpy methods (smaller is better):
        libc memcpy() : 196590365

...
load_plugins: plugin /usr/lib/xine/plugins/2.5/xineplug_decode_spucmml.so found
load_plugins: plugin /usr/lib/xine/plugins/2.5/xineplug_decode_spu.so found
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
vo_vdpau: Can't create vdp device : No vdpau implementation.
video_out_dxr3: Failed to open control device /dev/em8300-0 (No such file or directory)
libva info: VA-API version 0.36.0
libva info: va_getDriverName() returns -1
libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)
video_out_vaapi Error : vaInitialize(): unknown libva error
video_out_vaapi vaapi_init : error init vaapi
video_out_xv: Xv extension is present but I couldn't find a usable yuv12 port.
        Looks like your graphics hardware driver doesn't support Xv?!
video_out_opengl: Testing for hardware accelerated direct rendering visual
video_out_opengl: Didn't find any
vo_opengl2 : compiling shader yuv420_frag
vo_opengl2 : compiling shader yuv422_frag
vo_opengl2: initialized.
audio_alsa_out : supported modes are 8bit 16bit 24bit 32bit mono stereo (4-channel not enabled in xine config) (4.1-channel not enabled in xine config) (5-channel not enabled in xine config) (5.1-channel not enabled in xine config) (a/52 and DTS pass-through not enabled in xine config)
...

Available SPU decoder plugins:   dxr3-spudec spudec spuhdmv spucc spucmml spudvb sputext
params.c:OpenConfFile() - Unable to open configuration file "/root/.smb/smb.conf.append":
        No such file or directory
added interface eth0 ip=192.168.80.2 bcast=192.168.80.255 netmask=255.255.255.0
xine: found input plugin  : VDR (Video Disk Recorder) input plugin
unknown option in get_option: 4100
input cache plugin disabled
xine: found demuxer plugin: XVDR demux plugin


Press Esc to exit

av_offset=0 pts
setterm: argument error: 'off'
video_out_opengl2: b 0 c 128 s 128 h 0 [ITU-R 470 BG / SDTV]
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  72 (X_PutImage)
  Serial number of failed request:  203
  Current serial number in output stream:  234
vdr-sxfe: Kein Prozess gefunden
Restarting Linux Video Disk Recorder: vdr.


...


Thanks for your help.



Greets

Bernd

[Marie.O]

rpis do not work very well with the xine based output.

there are specific output devices for rpi but they work different from xine, in that they act as real output devices starting up with vdr, whereas the xine based output device that we use, is only started when we want to watch.

Things to do to make rpi work with vdr are probably:

* Don't use any xine based vdr plugin on the relevant MD
* Add the rpihddevice plugin
* Make sure to start VDR with the rpihddevice in suspend mode
* Change StartVDRClient.sh to activate the rpihddevice
* Find out what the name of the xwindow is that the rpihddevice creates (xwininfo -tree -root is your friend)
* amend the vdr player device for the rpi to bring that xwindow to the front (web admin change)

[rebelkiller]

Ok, I will try getting this to work. Let's be more specific: 

* Don't use any xine based vdr plugin on the relevant MD
=> Should I remove those packages from MD? Removal vdr-plugin-xineliboutput will result in removing pluto-vdr...

* Add the rpihddevice plugin
=> ok
* Make sure to start VDR with the rpihddevice in suspend mode
=> which conf-file must be edited?
* Change StartVDRClient.sh to activate the rpihddevice
=> we are talking about this line in StartVDRClient.sh, right?

Code: [Select]

/usr/bin/vdr-sxfe $XINE_IP --reconnect --post tvtime:method=use_vo_driver --fullscreen --tcp --syslog --verbose

I must be something like

Code: [Select]

/usr/bin/vdr $XINE_IP -P rpihddevice

* Find out what the name of the xwindow is that the rpihddevice creates (xwininfo -tree -root is your friend)
=> ok
* amend the vdr player device for the rpi to bring that xwindow to the front (web admin change)
=> which web admin device must be added?


Thanks!


Greets
Bernd

[Marie.O]

The requirement in pluto-vdr is  bummer...

I do not have answers for most of your questions, but I am sure putting the question into google will result in the needed information.

For the web admin device, it is the existing vdr player device on the MD. atm it is set at vdr.vdr for the window to be controlled.