Login at Kodi Home

charlie0440 · (This post was last modified: 2013-06-23, 19:18 by charlie0440.)

@FernetMenta, sorry for yet another thread, I can't help but tinker

I wanted to upgrade my server to VDR 2.0. I did a fresh install of ubuntu server 13.04 and installed the yavdr unstable-vdr ppa (https://launchpad.net/~yavdr/+archive/un...ter=raring) as it had raring packages.

The vnsi plugin appears to have compiled without an error (terminal output here: http://pastebin.com/EKzL9bM0 )

Problem is on issuing a vdr -V it does not list the plugin, also the plugin is not showing up in the plugin folders.

history:

Code:
1  sudo apt-add-repository ppa:yavdr/unstable-vdr

    2  sudo apt-get update

    3  sudo apt-get install vdr vdr-dev python-software-properties git pkg-config

    4  mkdir Downloads

    5  cd Downloads/

    6  git clone git://github.com/opdenkamp/xbmc-pvr-addons.git 

    7  ls

    8  cd xbmc-pvr-addons/addons/pvr.vdr.vnsi/vdr-plugin-vnsiserver

    9  sudo make

   10  history

Note - I had to install pkg-config otherwise I get an error message about it when compiling vnsi

syslog:

/usr/lib/vdr/plugins is empty
/var/lib/vdr/plugins is empty
/usr/include/vdr/plugins contains: dvbhddevice dvbsddevice
/etc/vdr/plugins contains: nano order.conf

Code:
charlie@Server:/usr/include/vdr/plugins$ vdr -V

vdr (2.0.1/2.0.0) - The Video Disk Recorder

cat /var/log/syslog | grep vdr

Code:
Jun 23 15:57:32 Server vdr: [10215] VDR version 2.0.1 started

Jun 23 15:57:32 Server vdr: [10215] switched to user 'vdr'

Jun 23 15:57:32 Server vdr: [10215] codeset is 'UTF-8' - known

Jun 23 15:57:32 Server vdr: [10215] found 28 locales in /usr/share/locale

Jun 23 15:57:32 Server vdr: [10215] loading /var/lib/vdr/sources.conf

Jun 23 15:57:32 Server vdr: [10215] loading /var/lib/vdr/diseqc.conf

Jun 23 15:57:32 Server vdr: [10215] loading /var/lib/vdr/scr.conf

Jun 23 15:57:32 Server vdr: [10215] loading /var/lib/vdr/channels.conf

Jun 23 15:57:32 Server vdr: [10215] loading /var/lib/vdr/commands.conf

Jun 23 15:57:32 Server vdr: [10215] loading /var/lib/vdr/reccmds.conf

Jun 23 15:57:32 Server vdr: [10215] loading /var/lib/vdr/svdrphosts.conf

Jun 23 15:57:32 Server vdr: [10215] loading /var/lib/vdr/keymacros.conf

Jun 23 15:57:32 Server vdr: [10233] video directory scanner thread started (pid=10215, tid=10233, prio=high)

Jun 23 15:57:32 Server vdr: [10233] video directory scanner thread ended (pid=10215, tid=10233)

Jun 23 15:57:32 Server vdr: [10215] registered source parameters for 'A - ATSC'

Jun 23 15:57:32 Server vdr: [10215] registered source parameters for 'C - DVB-C'

Jun 23 15:57:32 Server vdr: [10215] registered source parameters for 'S - DVB-S'

Jun 23 15:57:32 Server vdr: [10215] registered source parameters for 'T - DVB-T'

Jun 23 15:57:32 Server vdr: [10215] probing /dev/dvb/adapter0/frontend0

Jun 23 15:57:32 Server vdr: [10215] creating cDvbDevice

Jun 23 15:57:32 Server vdr: [10215] new device number 1

Jun 23 15:57:32 Server vdr: [10234] video directory scanner thread started (pid=10215, tid=10234, prio=high)

Jun 23 15:57:32 Server vdr: [10234] video directory scanner thread ended (pid=10215, tid=10234)

Jun 23 15:57:32 Server vdr: [10235] epg data reader thread started (pid=10215, tid=10235, prio=high)

Jun 23 15:57:32 Server vdr: [10235] epg data reader thread ended (pid=10215, tid=10235)

Jun 23 15:57:32 Server vdr: [10215] DVB API version is 0x0509 (VDR was built with 0x0509)

Jun 23 15:57:32 Server vdr: [10215] frontend 0/0 provides DVB-S,DVB-S2,DSS with QPSK ("STV090x Multistandard")

Jun 23 15:57:32 Server vdr: [10237] tuner on frontend 0/0 thread started (pid=10215, tid=10237, prio=high)

Jun 23 15:57:32 Server vdr: [10237] cTimeMs: using monotonic clock (resolution is 1 ns)

Jun 23 15:57:32 Server vdr: [10215] probing /dev/dvb/adapter1/frontend0

Jun 23 15:57:32 Server vdr: [10238] section handler thread started (pid=10215, tid=10238, prio=low)

Jun 23 15:57:32 Server vdr: [10215] creating cDvbDevice

Jun 23 15:57:32 Server vdr: [10215] new device number 2

Jun 23 15:57:32 Server vdr: [10215] frontend 1/0 provides DVB-S,DVB-S2,DSS with QPSK ("STV090x Multistandard")

Jun 23 15:57:32 Server vdr: [10240] tuner on frontend 1/0 thread started (pid=10215, tid=10240, prio=high)

Jun 23 15:57:32 Server vdr: [10215] found 2 DVB devices

Jun 23 15:57:32 Server vdr: [10215] setting primary device to 1

Jun 23 15:57:32 Server vdr: [10215] device 1 has no MPEG decoder

Jun 23 15:57:32 Server vdr: [10215] assuming manual start of VDR

Jun 23 15:57:32 Server vdr: [10215] SVDRP listening on port 6419

Jun 23 15:57:32 Server vdr: [10241] section handler thread started (pid=10215, tid=10241, prio=low)

Jun 23 15:57:32 Server vdr: [10215] setting current skin to "lcars"

Jun 23 15:57:32 Server vdr: [10215] loading /var/lib/vdr/themes/lcars-default.theme

Jun 23 15:57:32 Server vdr: [10215] ERROR (lirc.c,45): /var/run/lirc/lircd: No such file or directory

Jun 23 15:57:32 Server vdr: [10215] ERROR: remote control LIRC not ready!

Jun 23 15:57:32 Server vdr: [10215] setting watchdog timer to 60 seconds

Jun 23 15:57:32 Server vdr: [10215] OSD size changed to 720x480 @ 1

Jun 23 15:57:32 Server vdr: [10215] ERROR: no OSD provider available - using dummy OSD!

Jun 23 15:57:38 Server vdr: [10215] max. latency time 1 seconds

FernetMenta · 2013-06-23, 17:31

compile the plugin with
make (no sudo, run sudo make clean, if you compiled with sudo)

install with
sudo make install

You still need to tell vdr to load the plugin, not sure how ya-vdr handles this.

charlie0440 · 2013-06-23, 17:54

worked perfect thanks. VDR loads the plugin without me having to do anything else.

Minor moan, every time I compile the plugin I have to create the vnsiserver4 folder and the allowed_hosts file. Could / Should this not happen during compilation?

Again thanks for the great work and support!!

FernetMenta · 2013-06-23, 19:20

Quote:every time I compile the plugin I have to create the vnsiserver4 folder and the allowed_hosts file

Why? I have my config files in /var/vdr and neither vdr build nor vnsi build touches them.

Quote:Should this not happen during compilation?

How should the build know about the content of your config? Those files can't be created automatically.

axelgenus · 2013-06-23, 21:51

Configuration files are added automatically if you install the DEB package from yaVDR repository and it has nothing to do with compilation of the plugin. Wink

FernetMenta · 2013-06-23, 22:05

Even the yaVDR packagers don't know what clients you would like to give access in allowed_hosts. This file should not be deleted/overwritten by any install script.

charlie0440 · 2013-06-23, 22:16

I understand what your saying and its no trouble to create one. I just meant if during compile could it check if a allowed_hosts file exists and if it does not it creates one.

axelgenus · 2013-06-24, 16:28

(2013-06-23, 22:05)FernetMenta Wrote: Even the yaVDR packagers don't know what clients you would like to give access in allowed_hosts. This file should not be deleted/overwritten by any install script.

Initial allowed_hosts.conf allows only localhost to be connected to VNSI. When the package is updated or removed configuration is left as it is: apt just ask you what you want to do if the file differs from the package "safe" one.