A User wants to install yaVDR without customization and relies on full automation. @@ -483,22 +489,22 @@ Several roles are used to tie everything together:
One of the major problems we faced with customized Ubuntu ISO files as installation media for prior yaVDR versions has been the limited hardware support and the time consuming process to create and update them. An interesting alternative to this approach is to enable the user to choose the installation medium himself so point releases, kernel versions and additional drivers can be chosen deliberately. After the basic setup is complete (and a working internet connection is available), a fully customizable install script completes the yaVDR installation.
This is an experimental feature which allows to set up a yaVDR installation based on a normal Ubuntu Server 16.04.x installation using Ansible. @@ -520,8 +526,8 @@ sudo ./install-yavdr.sh
if (( $EUID != 0 )); then @@ -544,12 +550,12 @@ ansible-playbook yavdr07.yml -b -i 'localhost_inventory
The yavdr07.yml playbook sets up a fully-featured yaVDR installation:
@@ -587,6 +593,7 @@ The yavdr07.yml playbook sets up a fully-featured yaVDR installatio
- kodi
- dvd # set up packages and a udev rule to allow kodi and other players
# to play and eject optical media
+ - wakeup # set up wakeup methods for rtc etc.
- grub-config # configure grub
tags:
- always
@@ -597,8 +604,8 @@ The yavdr07.yml playbook sets up a fully-featured yaVDR installatio
For a headless server installation yavdr07-headless.yml is a good choice
@@ -621,6 +628,7 @@ For a headless server installation yavdr07-headless.yml is a good c
- nfs-server
- grub-config
- autoinstall-satip
+ - wakeup
tags:
- always
handlers:
@@ -630,8 +638,8 @@ For a headless server installation yavdr07-headless.yml is a good c
This playbook can either be used to run the installation on the localhost or any other PC in the network that can be accessed via ssh. Simply add the host names or IP addresses to the hosts file in the respective section: @@ -645,12 +653,12 @@ This playbook can either be used to run the installation on the localhost or any
---
@@ -662,8 +670,8 @@ This playbook can either be used to run the installation on the localhost or any
branch: unstable
@@ -679,8 +687,8 @@ This playbook can either be used to run the installation on the localhost or any
# properties of the user vdr and vdr-related options @@ -707,8 +715,8 @@ This playbook can either be used to run the installation on the localhost or any
# dictionary of directories for (shared) files. Automatically exported via NFS and Samba if those roles are enabled @@ -723,8 +731,8 @@ This playbook can either be used to run the installation on the localhost or any
nfs:
@@ -733,8 +741,8 @@ This playbook can either be used to run the installation on the localhost or any
samba:
@@ -744,8 +752,8 @@ This playbook can either be used to run the installation on the localhost or any
# additional packages you want to install @@ -754,20 +762,20 @@ This playbook can either be used to run the installation on the localhost or any - bpython3 - htop - tree - - vdr-addon-acpiwakeup - vim - w-scan
frontend: vdr #system: # shutdown: poweroff +wakeup_method: acpiwakeup grub: timeout: 0 boot_options: quiet nosplash @@ -776,20 +784,20 @@ This playbook can either be used to run the installation on the localhost or any
---
@@ -809,19 +817,19 @@ This playbook can either be used to run the installation on the localhost or any
install nvidia-387 from ppa:graphics-drivers/ppa
---
@@ -847,15 +855,15 @@ install nvidia-387 from ppa:graphics-drivers/ppa
This role is used to set up a basic yaVDR installation. It creates the directories, installs the vdr and other useful packages.
This section is for reference only, please use the files in global_vars for customizations.
@@ -868,7 +876,7 @@ This section is for reference only, please use the files in global_vars
Automatically installed drivers can be very useful, but if you know you need a certain driver, you can simply set it’s value to true. If you don’t want a driver to be installed, set it’s value to false. @@ -898,7 +906,7 @@ Automatically installed drivers can be very useful, but if you know you need a c
Add additional packages you would like to have on your installation to this list @@ -912,7 +920,7 @@ Add additional packages you would like to have on your installation to this list
This section allows you to set the recording directory, the user and group that runs the vdr and it’s home directory. @@ -945,15 +953,15 @@ This section allows you to set the recording directory, the user and group that
yavdr-common executes the following tasks:
- name: add PPAs
@@ -1004,7 +1012,7 @@ This task prevents apt to automatically install all recommended dependencies for
- name: use bash instead of dash
@@ -1016,8 +1024,8 @@ This task prevents apt to automatically install all recommended dependencies for
- name: disable release-upgrade notifications
@@ -1031,7 +1039,7 @@ This task prevents apt to automatically install all recommended dependencies for
- name: apt | install basic packages
@@ -1063,7 +1071,7 @@ This task prevents apt to automatically install all recommended dependencies for
- name: apt | install extra packages
@@ -1077,13 +1085,13 @@ This task prevents apt to automatically install all recommended dependencies for
{{ ansible_managed_file | comment('c') }}
@@ -1095,16 +1103,16 @@ APT::Install-Suggests "0";
- name: get information about usb and pci hardware and loaded kernel modules @@ -1131,16 +1139,16 @@ APT::Install-Suggests "0";
--- @@ -1159,7 +1167,7 @@ APT::Install-Suggests "0";
- name: add svdrp and svdrp-disc to /etc/services @@ -1174,7 +1182,7 @@ APT::Install-Suggests "0";
- name: create vdr recdir @@ -1210,7 +1218,7 @@ APT::Install-Suggests "0";
The additional plugins to install can be set in the variable {{vdr_plugins}} in the group variables
@@ -1228,7 +1236,7 @@ The additional plugins to install can be set in the variable {{vdr_plugins
- name: ensure vdr is stopped
@@ -1261,15 +1269,15 @@ The additional plugins to install can be set in the variable {{vdr_plugins
LIRC.Up KEY_UP @@ -1404,7 +1412,7 @@ XKeySym.Next XF86AudioNext
# Remote control key macros for VDR @@ -1430,12 +1438,12 @@ User0 @osdteletext
install_avahi: true @@ -1443,8 +1451,8 @@ User0 @osdteletext
---
@@ -1514,15 +1522,15 @@ User0 @osdteletext
---
@@ -1551,12 +1559,12 @@ User0 @osdteletext
/srv *(rw,fsid=0,sync,no_subtree_check,all_squash,anongid={{ vdr.gid }},anonuid={{ vdr.uid }})
@@ -1567,7 +1575,7 @@ User0 @osdteletext
<?xml version="1.0" standalone='no'?> @@ -1588,15 +1596,15 @@ User0 @osdteletext
---
@@ -1647,8 +1655,8 @@ User0 @osdteletext
{% if frontend != 'kodi' %} @@ -1659,17 +1667,17 @@ User0 @osdteletext
---
@@ -1691,8 +1699,8 @@ User0 @osdteletext
# Use PulseAudio by default @@ -1714,12 +1722,12 @@ User0 @osdteletext
The X-Server is started by using the two systemd units xlogin@.service and x@.service provided by the package xlogin. The former is enabled (and started) for the vdr user - which results (using the default settings for the user vdr with the uid 666) in the activation of xlogin@vdr.service when reaching the graphical.target.
@@ -1747,11 +1755,11 @@ In order to achive a clean shutdown of the session, x@t7.service is
---
@@ -2008,14 +2016,14 @@ In order to achive a clean shutdown of the session, x@t7.service is
# file: roles/yavdr-xorg/templates/systemd/system/x-verbose@.service.j2
@@ -2031,7 +2039,7 @@ In order to achive a clean shutdown of the session, x@t7.service is
[Unit]
@@ -2052,7 +2060,7 @@ In order to achive a clean shutdown of the session, x@t7.service is
# file: roles/yavdr-xorg/templates/vdr-xorg.conf
@@ -2065,7 +2073,7 @@ In order to achive a clean shutdown of the session, x@t7.service is
#!/bin/bash
@@ -2075,7 +2083,7 @@ In order to achive a clean shutdown of the session, x@t7.service is
Section "Device"
@@ -2402,7 +2410,7 @@ EndSection
-[Service]
@@ -2412,9 +2420,9 @@ EndSection
[Unit] @@ -2428,7 +2436,7 @@ EndSection
[Unit]
@@ -2444,7 +2452,7 @@ EndSection
[Unit]
@@ -2465,7 +2473,7 @@ EndSection
[Unit]
@@ -2486,7 +2494,7 @@ EndSection
[Unit]
@@ -2505,7 +2513,7 @@ EndSection
[Unit]
@@ -2524,9 +2532,9 @@ EndSection
-# forward environment variables to an environment file and the systemd user session @@ -2560,7 +2568,7 @@ systemctl --user isolate yavdr-desktop.target
<?xml version="1.0" encoding="UTF-8"?> @@ -3390,12 +3398,12 @@ systemctl --user isolate yavdr-desktop.target
---
@@ -3417,12 +3425,12 @@ systemctl --user isolate yavdr-desktop.target
---
@@ -3447,14 +3455,14 @@ systemctl --user isolate yavdr-desktop.target
{{ ansible_managed_file | comment }}
@@ -3540,7 +3548,7 @@ systemctl --user isolate yavdr-desktop.target
{% for name, path in media_dirs.iteritems() %}
@@ -3562,7 +3570,7 @@ systemctl --user isolate yavdr-desktop.target
include = /etc/samba/smb.conf.custom @@ -3575,15 +3583,15 @@ systemctl --user isolate yavdr-desktop.target
It would be nice to be able to detect if it is suitable to install those drivers:
Vendor-IDs: @@ -3594,14 +3602,14 @@ Vendor-IDs:
from http://www.vdr-portal.de/board18-vdr-hardware/board102-dvb-karten/120817-treiber-der-cine-ctv6-ddbridge-ci-in-den-kernel-integrieren/
@@ -3610,15 +3618,15 @@ from
-
The tool ubuntu-drivers is used to install the matching driver version for nvidia graphics cards, virtualbox guest additions and Intel and AMD microcode updates.
If a Sat>IP Server responds to a discovery request, the package vdr-plugin-satip is installed.
Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware sollte in yavdr-firmware stecken
This systemd unit for the user session starts (and stops) kodi.
@@ -4028,15 +4038,15 @@ This systemd unit for the user session starts (and stops) kodi.
Those configuration files provide a preconfiguration for kodi which overrides the system wide configuration
This file maps the keys defined in Lircmap.xml to actions within kodi.
This section contains custom modules for the yaVDR Playbooks. They are used to collect facts about the system and configure applications and daemons.
7.14 autoinstall-ubuntu-drivers
+7.14 autoinstall-ubuntu-drivers
7.14.1 tasks
+7.14.1 tasks
---
@@ -3641,15 +3649,15 @@ The tool ubuntu-drivers is used to install the matching driver version for nvidi
7.15 autoinstall-satip
+7.15 autoinstall-satip
7.15.1 tasks
+7.15.1 tasks
---
@@ -3665,6 +3673,7 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
- name: apt | install vdr-plugin-satip if a Sat>IP server has been detected
apt:
name: vdr-plugin-satip
+ state: present
when: satip_devices
notify: [ 'Restart VDR' ]
@@ -3673,12 +3682,12 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
7.16 autoinstall-targavfd
+7.16 autoinstall-targavfd
7.16.1 tasks
+7.16.1 tasks
---
@@ -3694,12 +3703,12 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
7.17 autoinstall-imonlcd
+7.17 autoinstall-imonlcd
7.17.1 tasks
+7.17.1 tasks
---
@@ -3715,12 +3724,12 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
7.18 autoinstall-libcecdaemon
+7.18 autoinstall-libcecdaemon
7.18.1 tasks
+7.18.1 tasks
---
@@ -3736,12 +3745,12 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
7.19 autoinstall-pvr350
+7.19 autoinstall-pvr350
7.19.1 tasks
+7.19.1 tasks
---
@@ -3757,8 +3766,8 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
7.20 autoinstall-hauppauge-pvr
+7.20 autoinstall-hauppauge-pvr
---
@@ -3773,12 +3782,12 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
7.21 autoinstall-dvbsky-firmware
+7.21 autoinstall-dvbsky-firmware
7.21.1 defaults
+7.21.1 defaults
---
@@ -3788,8 +3797,8 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
7.21.2 tasks
+7.21.2 tasks
---
@@ -3840,15 +3849,15 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
7.22 TODO autoinstall-dvbhddevice
+7.22 TODO autoinstall-dvbhddevice
7.22.1 tasks
+7.22.1 tasks
---
@@ -3865,12 +3874,12 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
7.23 autoinstall-dvbsddevice
+7.23 autoinstall-dvbsddevice
7.23.1 tasks
+7.23.1 tasks
---
@@ -3886,12 +3895,12 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
7.24 autoinstall-hardware-irmp
+7.24 autoinstall-hardware-irmp
7.24.1 sasks
+7.24.1 tasks
---
@@ -3900,30 +3909,31 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
- name: apt | install yavdr-hardware-irmp if connected
apt:
name: yavdr-hardware-irmp
+ state: present
when: '"1209:4444" in usb'
7.25 kodi
+7.25 kodi
7.25.1 tasks
+7.25.1 tasks
-
+
-
-
+- import_tasks: install-kodi.yml tags=install,update,kodi:install
- import_tasks: configure-kodi.yml tags=install,update,kodi:configure
@@ -3931,7 +3941,7 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
+
---
@@ -3949,7 +3959,7 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
+
- name: create kodi.service for the user session
@@ -3998,12 +4008,12 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
7.25.2 templates
+7.25.2 templates
-
+
7.25.3 files
+7.25.3 files
+
-
+
<!-- This file contains the mapping of keys (gamepad, remote, and keyboard) to actions within XBMC -->
@@ -4664,17 +4674,17 @@ This file maps the keys defined in Lircmap.xml to actions within kodi.
7.26 dvd
+7.26 dvd
7.26.1 tasks
+7.26.1 tasks
-
-
+---
# file: roles/dvd/tasks/main.yml
@@ -4714,8 +4724,8 @@ This file maps the keys defined in Lircmap.xml to actions within kodi.
7.27 template-test
+7.27 template-test
---
@@ -4956,14 +4966,53 @@ EndSection
7.28 grub-config
+7.28 wakeup
7.28.1 default variables
+7.28.1 defaults
---
+# file roles/wakeup/defaults/main.yml
+wakeup_method: "acpiwakeup"
+
+7.28.2 tasks
+---
+# file roles/wakeup/tasks/main.yml
+
+- name: install and configure vdr-addon-acpiwakeup
+ block:
+ - apt:
+ name: vdr-addon-acpiwakeup
+ state: present
+
+ - lineinfile:
+ path: /etc/vdr/vdr-addon-acpiwakeup.conf
+ regexp: '^ACPI_ENABLED='
+ line: 'ACPI_ENABLED=true'
+
+ when: wakeup_method == "acpiwakeup"
+
+7.29 grub-config
+7.29.1 default variables
+system:
shutdown: poweroff
grub:
@@ -4973,9 +5022,9 @@ EndSection
7.28.2 tasks
-7.29.2 tasks
+---
@@ -4999,9 +5048,9 @@ EndSection
7.28.3 templates
-7.29.3 templates
+#!/bin/sh
exec tail -n +3 $0
@@ -5023,9 +5072,9 @@ menuentry "PowerOff" {
7.28.4 handlers
-7.29.4 handlers
+---
@@ -5042,15 +5091,15 @@ menuentry "PowerOff" {
8 Modules
+8 Modules
8.1 hardware_facts.py
+8.1 hardware_facts.py
# This Module collects the vendor- and device ids for USB- and PCI(e)-devices and currently loaded kernel modules.
@@ -5217,8 +5266,8 @@ This section contains custom modules for the yaVDR Playbooks. They are used to c
8.2 satip_facts.py
+8.2 satip_facts.py
DOCUMENTATION = '''
@@ -5342,8 +5391,8 @@ This section contains custom modules for the yaVDR Playbooks. They are used to c
8.3 xrandr_facts.py
+8.3 xrandr_facts.py
[ ] support multiple screens (-d :0.0 .. :0.n)9 Handlers
+9 Handlers
- name: Reconfigure unattended upgrades with dpkg
@@ -5688,7 +5737,7 @@ This section contains custom modules for the yaVDR Playbooks. They are used to c