Go to file
2019-04-08 22:20:34 +02:00
filter_plugins Add inital i18n translation support 2017-12-18 17:55:53 +01:00
group_vars Add more configuration variables and explanations to group_vars 2019-04-08 21:59:16 +02:00
handlers Add handler to indicate a reboot is required 2018-08-10 08:12:49 +02:00
library Add error handling for incomplete Timing information on Modelines 2019-04-07 17:43:14 +02:00
plugins/callbacks add automatic tagging for roles 2018-01-01 23:05:40 +01:00
roles Don't create 20-intel.conf if nvidia_detected 2019-04-08 22:20:34 +02:00
ansible.cfg use ansible_managed instead of own variable ansible_managed_file 2018-01-16 13:07:58 +01:00
displays.yml Update displays.yml 2017-08-28 18:13:08 +02:00
hosts update README and hosts 2017-02-19 14:06:11 +01:00
install-yavdr-headless.sh Add install script for headless installation 2018-12-31 19:42:02 +01:00
install-yavdr.sh Run dpkg-reconfigure for libdvd-pkg package using a library module 2019-03-09 17:44:35 +01:00
LICENSE Initial commit 2017-02-19 13:53:08 +01:00
localhost_inventory change group name for inventory file 2017-11-12 21:17:44 +01:00
Manual.html Update Manual.html 2019-03-26 14:27:22 +01:00
Manual.org Don't create 20-intel.conf if nvidia_detected 2019-04-08 22:20:34 +02:00
README.md Adds information on waiting for dvb adapters before starting vdr 2019-03-25 19:35:20 +01:00
yavdr07-headless.yml Add role for epgd 2019-03-10 20:40:01 +01:00
yavdr07.yml Add role for epgd 2019-03-10 20:40:01 +01:00

yavdr-ansible

ansible playbooks for yaVDR

What can yavdr-ansible do for me?

Ansible is an automation tool which can be used to configure systems and deploy software. yavdr-ansible uses Ansible to set up a yaVDR System on top of an Ubuntu 18.04 Server installation (see below for details) and allows the user to fully customize the installation - have a look at the Ansible documentation if you want to learn how it works.

Please note that this is still work in progress and several features of yaVDR 0.6 haven't been implemented (yet).

System Requirements and Compatiblity Notes

  • RTC must be set to UTC in order for vdr-addon-acpiwakeup to work properly
  • 32 Bit Installations are untested, but should work
  • You need an IGP/GPU with support for VDPAU or VAAPI if you want to use software output plugins for VDR like softhddevice or vaapidevice
  • xineliboutput/vdr-sxfe works with software rendering, too
  • Can be used in a VirtualBox VM (VirtualBox 5.22 works better than Version 6.0.0)

Usage:

Set up a Ubuntu Server 18.04.x Installation

NOTE: it is important to use the alternative server installer or the mini.iso, otherwise the boot splash and Xorg won't work properly.

Download yavdr-ansible

Run the following commands to download the current version of yavdr-ansible:

sudo apt-get install git
git clone https://github.com/yavdr/yavdr-ansible
cd yavdr-ansible
git checkout bionic

Customizing the Playbooks and Variables

You can choose the roles run by the playbooks yavdr07.yml or yavdr07-headless.yml.

If you want to customize the variables in group_vars/all, copy the file to host_vars/localhost before changing it. This way you can change the PPAs used and choose which extra vdr plugins and packages should be installed by default.

Run the Playbook

If you want a system with Xorg output run:

sudo -H ./install-yavdr.sh

NOTE: on systems with a nvidia card unloading the noveau driver after installing the proprietary nvidia driver can fail (in this case ansible throws an error). If this happens please reboot your system to allow the nvidia driver to be loaded and run the install script again.

If you want a headless vdr server run:

sudo -H ./install-yavdr-headless.sh

First Steps after the installation:

Wait for local dvb adapters

The yaVDR VDR Package provides a systemd service wait-for-dvb@.service which allows to delay the start of vdr until all given locally connected dvb adapters have been initalized - e.g. to wait for /dev/dvb/adapter0 .. /dev/dvb/adapter3you can enable the required instances of this service like this:

systemctl enable wait-for-dvb@{0..3}.service

Please remember to adapt the enabled service instances if you change your configuration.

This should work foll all DVB adaptors for which udev events are generated. Note that devices with userspace drivers (e.g. by Sundtek) won't emit such events.

Add a /var/lib/vdr/channels.conf

You can use the wirbelscan-Plugin, w_scan, t2scan (especially useful for DVB-T2) or ready-to-use channellists from http://channelpedia.yavdr.com/gen/

Important: vdr.service must be stopped if you want to edit VDR configuration files: sudo stop vdr.service