From 47061871edfbc54435eef7ba6ca6762950fb2754 Mon Sep 17 00:00:00 2001 From: Alexander Grothe Date: Tue, 11 Sep 2018 14:51:26 +0200 Subject: [PATCH] Update Manual.html --- Manual.html | 1125 ++++++++++++++++++++++++++++----------------------- 1 file changed, 628 insertions(+), 497 deletions(-) diff --git a/Manual.html b/Manual.html index 9a3201f..451aa5f 100644 --- a/Manual.html +++ b/Manual.html @@ -3,7 +3,7 @@ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> - + Ansible Playbooks for yaVDR 0.7 @@ -240,261 +240,262 @@ for the JavaScript code in this tag.

Inhaltsverzeichnis

-
-

1 User Stories

+
+

1 User Stories

-
-

1.1 yavdr-full

+
+

1.1 yavdr-full

A User wants to install yaVDR without customization and relies on full automation. @@ -527,22 +528,22 @@ Several roles are used to tie everything together:

-
-

1.1.1 Using vdr, pulseaudio and xorg together

+
+

1.1.1 Using vdr, pulseaudio and xorg together

-
-

2 Introduction

+
+

2 Introduction

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 by 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.

-
-

3 Installing and configuring yaVDR with Ansible

+
+

3 Installing and configuring yaVDR with Ansible

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. @@ -577,20 +578,23 @@ We use a callback to generate tags for all roles autmatically:

-
-

3.1 Install script for local usage

+
+

3.1 Install script for local usage

-
if (( $EUID != 0 )); then
+
set -e
+if (( $EUID != 0 )); then
     echo "This script must be run using sudo -H or as root"
     exit
 fi
 
-apt-get -y install software-properties-common
 # update packages
-apt-get update
+apt update
+apt -y install software-properties-common
+add-apt-repository -y ppa:ansible/ansible-2.6
+
 # install required packages
-apt-get -y install --no-install-recommends ansible
+apt-get -y install --no-install-recommends ansible python-jmespath
 
 # TODO: run ansible on local host
 ansible-playbook yavdr07.yml -b -i 'localhost_inventory' --connection=local --tags="all" --extra-vars "first_run=True"
@@ -599,12 +603,12 @@ ansible-playbook yavdr07.yml -b -i 'localhost_inventory
-
-

4 Playbooks

+
+

4 Playbooks

-
-

4.1 yavdr07.yml

+
+

4.1 yavdr07.yml

The yavdr07.yml playbook sets up a fully-featured yaVDR installation: @@ -622,9 +626,9 @@ The yavdr07.yml playbook sets up a fully-featured yaVDR installatio - collect-facts # query system facts - autoinstall-ubuntu-drivers # use ubuntu-drivers to install proprietary dirvers # (e.g. nvidia, virtualbox) - - autoinstall-virtualbox-guest # - nvidia-experimental # install very recent nvidia dirver from ppa:graphics-drivers/ppa - vdr # install vdr and related packages + - autoinstall-virtualbox-guest - yavdr-network # enable network client capabilities - samba-install # install samba server - samba-config # configure samba server @@ -636,13 +640,14 @@ The yavdr07.yml playbook sets up a fully-featured yaVDR installatio - autoinstall-satip # install vdr-plugin-satip if a Sat>IP server has been found - autoinstall-targavfd # install vdr-plugin-targavfd if display is connected - autoinstall-imonlcd # install vdr-plugin-imonlcd if a matchind display is connected - - autoinstall-pvr350 # install vdr-plugin-pgvr350 if a matching card is detected + - autoinstall-pvr350 # install vdr-plugin-pvr350 if a matching card is detected - autoinstall-hauppauge-pvr # install vdr-plugin-pvrinput if a matching card is found - autoinstall-dvbsddevice # install vdr-plugin-dvbsddevice if a matching card is detected - autoinstall-hardware-irmp # install yavdr-hardware-irmp if a matching usb device is detected - autoinstall-atric-usb # preconfigure lircd for Atric IR-WakeupUSB receiver - autoinstall-yausbir # preconfigure lircd for yaUsbIR receiver - - autoinstall-dvbsky-firmware # download an install required firmware files for dvbsky cards + - autoinstall-dvbsky-firmware # download and install required firmware files for dvbsky cards + - autoinstall-firmware # download and install firmware files for dvb devices - kodi - dvd # set up packages and a udev rule to allow kodi and other players # to play and eject optical media @@ -655,8 +660,8 @@ The yavdr07.yml playbook sets up a fully-featured yaVDR installatio

-
-

4.2 yavdr07-headless.yml

+
+

4.2 yavdr07-headless.yml

For a headless server installation yavdr07-headless.yml is a good choice @@ -678,7 +683,12 @@ For a headless server installation yavdr07-headless.yml is a good c - samba-config - nfs-server - grub-config - - autoinstall-satip + - autoinstall-satip # install vdr-plugin-satip if a Sat>IP server has been found + - autoinstall-pvr350 # install vdr-plugin-pvr350 if a matching card is detected + - autoinstall-hauppauge-pvr # install vdr-plugin-pvrinput if a matching card is found + - autoinstall-dvbsddevice # install vdr-plugin-dvbsddevice if a matching card is detected + - autoinstall-dvbsky-firmware # download and install required firmware files for dvbsky cards + - autoinstall-firmware # download and install firmware files for dvb devices - wakeup tags: - always @@ -689,8 +699,8 @@ For a headless server installation yavdr07-headless.yml is a good c

-
-

5 Hosts

+
+

5 Hosts

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: @@ -704,12 +714,12 @@ This playbook can either be used to run the installation on the localhost or any

-
-

6 Group Variables

+
+

6 Group Variables

-
-

6.1 PPAs

+
+

6.1 PPAs

---
@@ -727,8 +737,8 @@ This playbook can either be used to run the installation on the localhost or any
-
-

6.2 VDR user, directories, special configuration and plugins

+
+

6.2 VDR user, directories, special configuration and plugins

# properties of the user vdr and vdr-related options
@@ -754,8 +764,8 @@ This playbook can either be used to run the installation on the localhost or any
-
-

6.3 Media directories

+
+

6.3 Media directories

# dictionary of directories for (shared) files. Automatically exported via NFS and Samba if those roles are enabled
@@ -770,8 +780,8 @@ This playbook can either be used to run the installation on the localhost or any
-
-

6.4 NFS

+
+

6.4 NFS

nfs:
@@ -780,8 +790,8 @@ This playbook can either be used to run the installation on the localhost or any
-
-

6.5 Samba

+
+

6.5 Samba

samba:
@@ -791,8 +801,8 @@ This playbook can either be used to run the installation on the localhost or any
-
-

6.6 Additional packages

+
+

6.6 Additional packages

# additional packages you want to install
@@ -808,8 +818,8 @@ This playbook can either be used to run the installation on the localhost or any
-
-

6.7 System pre-configuration

+
+

6.7 System pre-configuration

frontend: vdr
@@ -824,20 +834,20 @@ This playbook can either be used to run the installation on the localhost or any
-
-

7 Roles

+
+

7 Roles

-
-

7.1 install-dependencies

+
+

7.1 install-dependencies

-
-

7.1.1 tasks

+
+

7.1.1 tasks

    -
  1. main.yml
    +
  2. main.yml
    ---
@@ -858,19 +868,19 @@ This playbook can either be used to run the installation on the localhost or any
    -
    -

    7.2 nvidia experimental drivers

    +
    +

    7.2 nvidia experimental drivers

    install nvidia-396 from ppa:graphics-drivers/ppa

    -
    -

    7.2.1 tasks

    +
    +

    7.2.1 tasks

      -
    1. main.yml
      +
    2. main.yml
      ---
@@ -900,15 +910,15 @@ install nvidia-396 from ppa:graphics-drivers/ppa
    -
    -

    7.3 yavdr-common

    +
    +

    7.3 yavdr-common

    This role is used to set up a basic yaVDR installation. It creates the directories, installs the vdr and other useful packages.

    -
    -

    7.3.1 default variables

    +
    +

    7.3.1 default variables

    This section is for reference only, please use the files in global_vars for customizations. @@ -921,7 +931,7 @@ This section is for reference only, please use the files in global_vars

      -
    1. Repositories
      +
    2. Repositories

      You can set a list of package repositories which provide the necessary packages. Feel free to use own PPAs if you need special customization to the VDR and it’s plugins. @@ -938,7 +948,7 @@ You can set a list of package repositories which provide the necessary packages.

    3. -
  3. Drivers
    +
  4. Drivers

    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. @@ -951,7 +961,7 @@ Automatically installed drivers can be very useful, but if you know you need a c

-
  • Additional Packages
    +
  • Additional Packages

    Add additional packages you would like to have on your installation to this list @@ -965,7 +975,7 @@ Add additional packages you would like to have on your installation to this list

    • -
  • VDR
    +
  • VDR

    This section allows you to set the recording directory, the user and group that runs the vdr and it’s home directory. @@ -998,15 +1008,15 @@ This section allows you to set the recording directory, the user and group that

    • -
    -

    7.3.2 tasks

    +
    +

    7.3.2 tasks

    yavdr-common executes the following tasks:

      -
    1. main.yml
      +
    2. main.yml
      ---
@@ -1023,7 +1033,7 @@ yavdr-common executes the following tasks:
        -
      1. Disable default installation of recommended packages
        +
      2. Disable default installation of recommended packages

        This task prevents apt to automatically install all recommended dependencies for packages: @@ -1040,7 +1050,7 @@ This task prevents apt to automatically install all recommended dependencies for

    -
  • Set up package repositories
    +
  • Set up package repositories
    - name: add PPAs
@@ -1060,34 +1070,22 @@ This task prevents apt to automatically install all recommended dependencies for
    • -
  • Use bash instead of dash
    +
  • Use bash instead of dash
    -
    - name: apt | ensure debconf and debconf-utils are installed
-  apt:
-    name: "{{ packages }}"
-  vars:
-    packages:
-    - debconf
-    - debconf-utils
-
-- name: use bash instead of dash by default
-  debconf:
-    name: dash
-    question: dash/sh
-    value: 'false'
-    vtype: select
-  notify: ['Reconfigure unattended upgrades with dpkg']
-
+
    - name: use bash instead of dash
+  shell: |
+    echo "set dash/sh false" | debconf-communicate
+    dpkg-reconfigure -f noninteractive dash
    • -
  • create user vdr
    • -
  • Disable release-upgrade notifications
    +
  • create user vdr
    • +
  • Disable release-upgrade notifications
      -
    1. SOMEDAY move from lineinfile to template
      +
    2. SOMEDAY move from lineinfile to template
      - name: disable release-upgrade notifications
@@ -1109,7 +1107,7 @@ This task prevents apt to automatically install all recommended dependencies for
    • -
  • Install essential packages
    +
  • Install essential packages
    - name: apt | install basic packages
@@ -1141,7 +1139,7 @@ This task prevents apt to automatically install all recommended dependencies for
    • -
  • Install additional packages (user defined)
    +
  • Install additional packages (user defined)
    - name: apt | install extra packages
@@ -1155,14 +1153,14 @@ This task prevents apt to automatically install all recommended dependencies for
    • -
  • create directories
    • -
  • create sudoers drop-in for vdr
    • +
  • create directories
    • +
  • create sudoers drop-in for vdr
    • -
    -

    7.3.3 templates

    +
    +

    7.3.3 templates

    {{ ansible_managed | comment('c') }}
@@ -1173,7 +1171,7 @@ APT::Install-Suggests "0";
      -
    1. yavdr sudoers drop-in
      +
    2. yavdr sudoers drop-in

      Allow the vdr user to restart vdr.service and reboot the system @@ -1188,12 +1186,12 @@ Allow the vdr user to restart vdr.service and reboot the system

    -
    -

    7.4 collect facts about the system with custom modules

    +
    +

    7.4 collect facts about the system with custom modules

    -
    -

    7.4.1 variables

    +
    +

    7.4.1 variables

    first_run: False
@@ -1201,12 +1199,12 @@ Allow the vdr user to restart vdr.service and reboot the system
    -
    -

    7.4.2 tasks

    +
    +

    7.4.2 tasks

      -
    1. main.yml
      +
    2. main.yml
      - name: get information about usb and pci hardware and loaded kernel modules
@@ -1233,6 +1231,15 @@ Allow the vdr user to restart vdr.service and reboot the system
     - amd_detected
     - virtualbox_detected
 
+- name: get detailed PCI device information
+  pci_facts:
+  tags:
+    - always
+
+- debug:
+    var: pci_devices
+    verbosity: 1
+
 - name: known vdr output plugins
   set_fact:
     vdr_output_plugins:    
@@ -1246,16 +1253,16 @@ Allow the vdr user to restart vdr.service and reboot the system
    -
    -

    7.5 vdr

    +
    +

    7.5 vdr

    -
    -

    7.5.1 tasks

    +
    +

    7.5.1 tasks

      -
    1. install the basic vdr packages
      +
    2. install the basic vdr packages
      ---
@@ -1274,7 +1281,7 @@ Allow the vdr user to restart vdr.service and reboot the system
      3. -
    3. Add svdrp/svdrp-disc to /etc/services
      +
    4. Add svdrp/svdrp-disc to /etc/services
      - name: add svdrp and svdrp-disc to /etc/services
@@ -1289,7 +1296,7 @@ Allow the vdr user to restart vdr.service and reboot the system
      5. -
    5. Set up the recording directory for the vdr user
      +
    6. Set up the recording directory for the vdr user
      - name: create vdr recdir
@@ -1324,7 +1331,7 @@ Allow the vdr user to restart vdr.service and reboot the system
      7. -
    7. Install additional vdr plugins
      +
    8. Install additional vdr plugins

      The additional plugins to install can be set in the variable {{vdr_plugins}} in the group variables @@ -1342,7 +1349,7 @@ The additional plugins to install can be set in the variable {{vdr_plugins

    -
  • copy vdr configuration files (if they don’t exist yet)
    +
  • copy vdr configuration files (if they don’t exist yet)
    - name: ensure vdr is stopped
@@ -1373,7 +1380,7 @@ The additional plugins to install can be set in the variable {{vdr_plugins
    • -
  • start vdr after network-online.target
    +
  • start vdr after network-online.target
    - name: create directory for vdr.service systemd drop-in files
@@ -1394,8 +1401,8 @@ The additional plugins to install can be set in the variable {{vdr_plugins
    -
    -

    7.5.2 templates

    +
    +

    7.5.2 templates

    Start after network-online.target @@ -1407,12 +1414,12 @@ Start after network-online.target

    -
    -

    7.5.3 files

    +
    +

    7.5.3 files

      -
    1. remote.conf
      +
    2. remote.conf
      LIRC.Up KEY_UP
@@ -1547,7 +1554,7 @@ XKeySym.Next       XF86AudioNext
      3. -
    3. keymacros.conf
      +
    4. keymacros.conf
      # Remote control key macros for VDR
@@ -1573,12 +1580,12 @@ User0     @osdteletext
    -
    -

    7.6 STARTED yavdr-network

    +
    +

    7.6 STARTED yavdr-network

    -
    -

    7.6.1 default variables

    +
    +

    7.6.1 default variables

    install_avahi: true
@@ -1586,8 +1593,8 @@ User0     @osdteletext
    -
    -

    7.6.2 tasks

    +
    +

    7.6.2 tasks

    ---
@@ -1657,15 +1664,15 @@ User0     @osdteletext
    -
    -

    7.7 nfs-server

    +
    +

    7.7 nfs-server

    -
    -

    7.7.1 TODO avahi-services für NFS beim Stoppen des nfs-kernel-servers depublizieren, beim Start wieder announcen

    +
    +

    7.7.1 TODO avahi-services für NFS beim Stoppen des nfs-kernel-servers depublizieren, beim Start wieder announcen

    -
    -

    7.7.2 tasks

    +
    +

    7.7.2 tasks

    ---
@@ -1694,12 +1701,12 @@ User0     @osdteletext
    -
    -

    7.7.3 templates

    +
    +

    7.7.3 templates

      -
    1. /etc/exports
      +
    2. /etc/exports
      /srv *(rw,fsid=0,sync,no_subtree_check,all_squash,anongid={{ vdr.gid }},anonuid={{ vdr.uid }})
@@ -1710,7 +1717,7 @@ User0     @osdteletext
      3. -
    3. avahi services
      +
    4. avahi services
      <?xml version="1.0" standalone='no'?>
@@ -1732,12 +1739,12 @@ User0     @osdteletext
      -
      -

      7.8 STARTED yavdr-remote

      +
      +

      7.8 STARTED yavdr-remote

      -
      -

      7.8.1 default variables

      +
      +

      7.8.1 default variables

      lircd0_socket: /var/run/lirc/lircd0
@@ -1745,8 +1752,8 @@ User0     @osdteletext
      -
      -

      7.8.2 tasks

      +
      +

      7.8.2 tasks

      ---
@@ -1819,12 +1826,12 @@ User0     @osdteletext
      -
      -

      7.8.3 templates

      +
      +

      7.8.3 templates

        -
      1. Systemd Drop-in to start vdr with lirc support
        +
      2. Systemd Drop-in to start vdr with lirc support
        {% if frontend != 'kodi' %}
@@ -1835,7 +1842,7 @@ User0     @osdteletext
        3. -
      3. Systemd Drop-in to start lircd2uinput with lircd
        +
      4. Systemd Drop-in to start lircd2uinput with lircd
        [Service]
@@ -1845,7 +1852,7 @@ User0     @osdteletext
        5. -
      5. create /etc/rc_maps.cfg
        +
      6. create /etc/rc_maps.cfg
        {{ ansible_managed | comment }}
@@ -2037,17 +2044,17 @@ ati_remote    rc-medion-x10-digitainer   /lib/udev/rc_keymaps/rc-medion-x10-digi
      -
      -

      7.8.4 files

      +
      +

      7.8.4 files

      -
      -

      7.9 pulseaudio

      +
      +

      7.9 pulseaudio

      -
      -

      7.9.1 tasks

      +
      +

      7.9.1 tasks

      ---
@@ -2070,8 +2077,8 @@ ati_remote    rc-medion-x10-digitainer   /lib/udev/rc_keymaps/rc-medion-x10-digi
      -
      -

      7.9.2 templates

      +
      +

      7.9.2 templates

      # Use PulseAudio by default
@@ -2094,12 +2101,12 @@ ati_remote    rc-medion-x10-digitainer   /lib/udev/rc_keymaps/rc-medion-x10-digi
      -
      -

      7.10 yavdr-xorg

      +
      +

      7.10 yavdr-xorg

      -
      -

      7.10.1 About the GUI session

      +
      +

      7.10.1 About the GUI session

      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. To simplify starting and stopping the X-server and the desktop session a yavdr-xorg.service is provided by the package yavdr-xorg, which depends on the two units mentioned before. @@ -2128,8 +2135,8 @@ In order to achive a clean shutdown of the session, x@t7.service is

      -
      -

      7.10.2 default variables

      +
      +

      7.10.2 default variables

      first_run: False
@@ -2152,12 +2159,12 @@ In order to achive a clean shutdown of the session, x@t7.service is
      -
      -

      7.10.3 tasks

      +
      +

      7.10.3 tasks

        -
      1. main.yml
        +
      2. main.yml
        ---
@@ -2170,7 +2177,7 @@ In order to achive a clean shutdown of the session, x@t7.service is
        3. -
      3. setup-xorg.yml
        +
      4. setup-xorg.yml
        ---
@@ -2291,7 +2298,7 @@ In order to achive a clean shutdown of the session, x@t7.service is
        5. -
      5. detect-xorg.yml
        +
      6. detect-xorg.yml
        ---
@@ -2451,7 +2458,7 @@ In order to achive a clean shutdown of the session, x@t7.service is
        7. -
      7. intel.yml
        +
      8. intel.yml

        KMS drivers (like for intel (i915) and amd (radeon)) require additional configuration beneath a customized xorg.conf - for a „static“ output configuration (which works if the TV or AV receiver is not turned on) we need to force loading the display(s) EDID early during the boot process. @@ -2498,12 +2505,12 @@ Please note that rescanning the connected displays works only after removing the

      -
      -

      7.10.4 templates

      +
      +

      7.10.4 templates

        -
      1. grub
        +
      2. grub
        {% set output_flag = 'D' if ("HDMI" in xorg.primary.connector or "DVI" in xorg.primary.connector or "DP" in xorg.primary.connector) else 'e' %} 
@@ -2513,9 +2520,9 @@ Please note that rescanning the connected displays works only after removing the
        3. -
      3. xorg
        +
      4. xorg
          -
        1. x-verbose@.service
          +
        2. x-verbose@.service
          # file: roles/yavdr-xorg/templates/systemd/system/x-verbose@.service.j2
@@ -2531,7 +2538,7 @@ Please note that rescanning the connected displays works only after removing the
          3. -
        3. Drop-in snippet for x@.service
          +
        4. Drop-in snippet for x@.service
          [Unit]
@@ -2557,7 +2564,7 @@ Please note that rescanning the connected displays works only after removing the
          5. -
        5. Drop-in snippet for vdr.service
          +
        6. Drop-in snippet for vdr.service
          {{ ansible_managed | comment }}
@@ -2569,7 +2576,7 @@ Please note that rescanning the connected displays works only after removing the
          7. -
        7. xorg.conf snippets
          +
        8. xorg.conf snippets
          {{ ansible_managed | comment }}
@@ -2583,7 +2590,7 @@ EndSection
          9. -
        9. xorg.conf
          +
        10. xorg.conf
          Section "Device"
@@ -2909,7 +2916,7 @@ EndSection
        5. -
      5. vdr
        +
      6. vdr

        Set environment variables for system locale and user session on startup @@ -2925,12 +2932,12 @@ Set environment variables for system locale and user session on startup

      -
      -

      7.10.5 files

      +
      +

      7.10.5 files

        -
      1. initramfs EDID hook
        +
      2. initramfs EDID hook
        #!/bin/bash
@@ -2956,16 +2963,16 @@ manual_add_modules i915 radeon
        -
        -

        7.11 yavdr-desktop

        +
        +

        7.11 yavdr-desktop

        -
        -

        7.11.1 Tasks

        +
        +

        7.11.1 Tasks

          -
        1. main.yml
          +
        2. main.yml
          ---
@@ -3114,14 +3121,14 @@ manual_add_modules i915 radeon
        -
        -

        7.11.2 Templates

        +
        +

        7.11.2 Templates

          -
        1. xorg configuration
          +
        2. xorg configuration
            -
          1. .Xresources
            +
          2. .Xresources
            xterm*background: Black
@@ -3144,7 +3151,7 @@ XTerm.vt100.font: 7x13
            3. -
          3. .xinitrc
            +
          4. .xinitrc
            #!/bin/bash
@@ -3156,9 +3163,9 @@ XTerm.vt100.font: 7x13
          3. -
        3. openbox
          +
        4. openbox
            -
          1. autostart
            +
          2. autostart
            # forward environment variables to an environment file and the systemd user session
@@ -3194,7 +3201,7 @@ systemctl --user isolate yavdr-desktop.target
            3. -
          3. rc.xml
            +
          4. rc.xml
            <?xml version="1.0" encoding="UTF-8"?>
@@ -3983,6 +3990,12 @@ systemctl --user isolate yavdr-desktop.target
       <!--<skip_pager>yes</skip_pager>-->
       <skip_taskbar>no</skip_taskbar>
     </application>
+    <application title="softhdcuvid">
+      <decor>no</decor>
+      <maximized>yes</maximized>
+      <!--<skip_pager>yes</skip_pager>-->
+      <skip_taskbar>no</skip_taskbar>
+    </application>
     <application title="vaapidevice">
       <decor>no</decor>
       <maximized>yes</maximized>
@@ -4014,7 +4027,7 @@ systemctl --user isolate yavdr-desktop.target
            5. -
          5. rc2.xml
            +
          6. rc2.xml
            <?xml version="1.0" encoding="UTF-8"?>
@@ -4803,6 +4816,12 @@ systemctl --user isolate yavdr-desktop.target
       <!--<skip_pager>yes</skip_pager>-->
       <skip_taskbar>no</skip_taskbar>
     </application>
+    <application title="softhdcuvid">
+      <decor>no</decor>
+      <maximized>yes</maximized>
+      <!--<skip_pager>yes</skip_pager>-->
+      <skip_taskbar>no</skip_taskbar>
+    </application>
     <application title="vaapidevice">
       <decor>no</decor>
       <maximized>yes</maximized>
@@ -4837,9 +4856,9 @@ systemctl --user isolate yavdr-desktop.target
          5. -
        5. Systemd User Session
          +
        6. Systemd User Session
            -
          1. yavdr-desktop.target
            +
          2. yavdr-desktop.target
            [Unit]
@@ -4852,7 +4871,7 @@ systemctl --user isolate yavdr-desktop.target
            3. -
          3. detect-second-display
            +
          4. detect-second-display
            [Unit]
@@ -4868,7 +4887,7 @@ systemctl --user isolate yavdr-desktop.target
            5. -
          5. openbox-second.service
            +
          6. openbox-second.service
            [Unit]
@@ -4890,7 +4909,7 @@ systemctl --user isolate yavdr-desktop.target
            7. -
          7. osd2web.service
            +
          8. osd2web.service
            [Unit]
@@ -4913,7 +4932,7 @@ systemctl --user isolate yavdr-desktop.target
            9. -
          9. tmux.service
            +
          10. tmux.service
            [Unit]
@@ -4932,7 +4951,7 @@ systemctl --user isolate yavdr-desktop.target
            11. -
          11. wm-exit.service
            +
          12. wm-exit.service
            [Unit]
@@ -4951,7 +4970,7 @@ systemctl --user isolate yavdr-desktop.target
          7. -
        7. irexec
          +
        8. irexec

          irexec.service starts irexec for the user session @@ -4985,12 +5004,12 @@ end

        -
        -

        7.12 samba-install

        +
        +

        7.12 samba-install

        -
        -

        7.12.1 tasks

        +
        +

        7.12.1 tasks

        ---
@@ -5012,12 +5031,12 @@ end
        -
        -

        7.13 samba-config

        +
        +

        7.13 samba-config

        -
        -

        7.13.1 tasks

        +
        +

        7.13.1 tasks

        ---
@@ -5042,14 +5061,14 @@ end
        -
        -

        7.13.2 templates

        +
        +

        7.13.2 templates

          -
        1. smb.conf
          +
        2. smb.conf
            -
          1. global settings
            +
          2. global settings
            {{ ansible_managed | comment }}
@@ -5135,7 +5154,7 @@ end
            3. -
          3. media directories
            +
          4. media directories
            {% for name, path in media_dirs.iteritems() %}
@@ -5157,7 +5176,7 @@ end
            5. -
          5. include custom samba exports
            +
          6. include custom samba exports
            include = /etc/samba/smb.conf.custom
@@ -5170,15 +5189,15 @@ end
        -
        -

        7.14 STARTED autoinstall-drivers

        +
        +

        7.14 STARTED autoinstall-drivers

        It would be nice to be able to detect if it is suitable to install those drivers:

        -
        -

        7.14.1 TODO sundtek for Sundtek devices (local or network connection)

        +
        +

        7.14.1 TODO sundtek for Sundtek devices (local or network connection)

        Vendor-IDs: @@ -5189,7 +5208,7 @@ Vendor-IDs:

          -
        1. planned packages
          +
        2. planned packages
          • yavdr-hardware-sundtek
            • @@ -5200,8 +5219,8 @@ Vendor-IDs:
        -
        -

        7.14.2 TODO drivers for TT S2-6400 FF

        +
        +

        7.14.2 TODO drivers for TT S2-6400 FF

        https://github.com/s-moch/linux-saa716x - kann man den relevanten Teil als dkms-Paket bauen? @@ -5209,15 +5228,15 @@ Vendor-IDs:

        -
        -

        7.15 autoinstall-ubuntu-drivers

        +
        +

        7.15 autoinstall-ubuntu-drivers

        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.

        -
        -

        7.15.1 tasks

        +
        +

        7.15.1 tasks

        ---
@@ -5240,8 +5259,8 @@ The tool ubuntu-drivers is used to install the matching driver version for nvidi
        -
        -

        7.16 autoinstall-virtualbox-guest

        +
        +

        7.16 autoinstall-virtualbox-guest

        This role installs the guest additions for virtualbox guests on Ubuntu 16.04 @@ -5286,18 +5305,18 @@ This role installs the guest additions for virtualbox guests on Ubuntu 16.04 - vdrctl enable xineliboutput ignore_errors: yes when: - - ansible_virtualization_type == "virtualbox" + - ansible_virtualization_type == "virtualbox" or ansible_virtualization_type == "VMware" - ansible_virtualization_role == "guest"

        -
        -

        7.17 autoinstall-atric-usb

        +
        +

        7.17 autoinstall-atric-usb

        -
        -

        7.17.1 dependencies

        +
        +

        7.17.1 dependencies

        ---
@@ -5309,8 +5328,8 @@ This role installs the guest additions for virtualbox guests on Ubuntu 16.04
        -
        -

        7.17.2 tasks

        +
        +

        7.17.2 tasks

        ---
@@ -5352,8 +5371,8 @@ This role installs the guest additions for virtualbox guests on Ubuntu 16.04
        -
        -

        7.17.3 templates

        +
        +

        7.17.3 templates

        {{ ansible_managed | comment }}
@@ -5382,12 +5401,12 @@ This role installs the guest additions for virtualbox guests on Ubuntu 16.04
        -
        -

        7.18 autoinstall-yausbir

        +
        +

        7.18 autoinstall-yausbir

        -
        -

        7.18.1 dependencies

        +
        +

        7.18.1 dependencies

        ---
@@ -5398,8 +5417,8 @@ This role installs the guest additions for virtualbox guests on Ubuntu 16.04
        -
        -

        7.18.2 tasks

        +
        +

        7.18.2 tasks

        ---
@@ -5441,8 +5460,8 @@ This role installs the guest additions for virtualbox guests on Ubuntu 16.04
        -
        -

        7.18.3 templates

        +
        +

        7.18.3 templates

        {{ ansible_managed | comment }}
@@ -5470,15 +5489,15 @@ This role installs the guest additions for virtualbox guests on Ubuntu 16.04
        -
        -

        7.19 autoinstall-satip

        +
        +

        7.19 autoinstall-satip

        If a Sat>IP Server responds to a discovery request, the package vdr-plugin-satip is installed.

        -
        -

        7.19.1 tasks

        +
        +

        7.19.1 tasks

        ---
@@ -5503,12 +5522,12 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
        -
        -

        7.20 autoinstall-targavfd

        +
        +

        7.20 autoinstall-targavfd

        -
        -

        7.20.1 tasks

        +
        +

        7.20.1 tasks

        ---
@@ -5524,12 +5543,12 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
        -
        -

        7.21 autoinstall-imonlcd

        +
        +

        7.21 autoinstall-imonlcd

        -
        -

        7.21.1 tasks

        +
        +

        7.21.1 tasks

        ---
@@ -5545,12 +5564,12 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
        -
        -

        7.22 autoinstall-libcecdaemon

        +
        +

        7.22 autoinstall-libcecdaemon

        -
        -

        7.22.1 tasks

        +
        +

        7.22.1 tasks

        ---
@@ -5566,12 +5585,12 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
        -
        -

        7.23 autoinstall-pvr350

        +
        +

        7.23 autoinstall-pvr350

        -
        -

        7.23.1 tasks

        +
        +

        7.23.1 tasks

        ---
@@ -5587,8 +5606,8 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
        -
        -

        7.24 autoinstall-hauppauge-pvr

        +
        +

        7.24 autoinstall-hauppauge-pvr

        ---
@@ -5603,12 +5622,12 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
        -
        -

        7.25 autoinstall-firmware

        +
        +

        7.25 autoinstall-firmware

        -
        -

        7.25.1 dependencies

        +
        +

        7.25.1 dependencies

        ---
@@ -5619,38 +5638,54 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
        -
        -

        7.25.2 tasks

        +
        +

        7.25.2 tasks

        ---
 
 # This role provides easyily downloadable firmware files
 
-- name: Firmware for Hauppauge WinTV HD Solo/Duo, PCTV 292e
+- name: Firmware dvb-demod-si2168-b40-01.fw for Hauppauge WinTV HD Solo/Duo, PCTV 292e
   get_url:
     url: https://github.com/OpenELEC/dvb-firmware/raw/master/firmware/dvb-demod-si2168-b40-01.fw
     checksum: sha256:8507536630d75a316d0719d6b95c04b90c36baa5b457ad457c9bacadafcef134
     dest: /lib/firmware/dvb-demod-si2168-b40-01.fw
   when: '"2040:0264" in usb or "2013:025f" in usb'
 
-- name: Firmware for Hauppauge WinTV-HVR-930C
+- name: Firmware dvb-fe-xc5000-1.6.114.fw for Hauppauge WinTV-HVR-930C
   get_url:
     url: https://github.com/OpenELEC/dvb-firmware/raw/master/firmware/dvb-fe-xc5000-1.6.114.fw
     checksum: sha256:7104bda8df301fe1bd4c09de1708aeb6d0d8e1f9d55505449fecfad82639235f
     dest: /lib/firmware/dvb-fe-xc5000-1.6.114.fw
   when: '"2040:1605" in usb'
+
+- name: Firmware ngenge_18.fw for ngene cards
+  get_url:
+    url: http://l4m-daten.de/downloads/firmware/dvb-s2/linux/all/ngene_18.fw
+    checksum: sha256:213d98ec2cd575eba15d82ee79fed7098e670de43792f8aa773a95cfb7c32060
+    dest: /lib/firmware/ngene_18.fw
+  when: '"ngene" in modules'
+  notify: reboot required
+
+- name: Firmware drxk_a3.mc for drxk
+  get_url:
+     url: https://github.com/OpenELEC/dvb-firmware/raw/master/firmware/drxk_a3.mc
+     checksum: sha256:f8956ad6f92a4ce90a6ab94ed23e2f9a27e9317e936fd3e0119778dd28e7e294
+     dest: /lib/firmware/drxk_a3.mc
+  when: '"ngene" in modules or "drxk" in modules'
+  notify: reboot required
        -
        -

        7.26 autoinstall-dvbsky-firmware

        +
        +

        7.26 autoinstall-dvbsky-firmware

        -
        -

        7.26.1 dependencies

        +
        +

        7.26.1 dependencies

        ---
@@ -5661,8 +5696,8 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
        -
        -

        7.26.2 defaults

        +
        +

        7.26.2 defaults

        ---
@@ -5672,8 +5707,8 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
        -
        -

        7.26.3 tasks

        +
        +

        7.26.3 tasks

        ---
@@ -5723,15 +5758,15 @@ If a Sat>IP Server responds to a discovery request, the package vdr-plugin-sa
        -
        -

        7.27 TODO autoinstall-dvbhddevice

        +
        +

        7.27 TODO autoinstall-dvbhddevice

        Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware sollte in yavdr-firmware stecken

        -
        -

        7.27.1 dependencies

        +
        +

        7.27.1 dependencies

        ---
@@ -5742,8 +5777,8 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
        -
        -

        7.27.2 tasks

        +
        +

        7.27.2 tasks

        ---
@@ -5760,12 +5795,12 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
        -
        -

        7.28 autoinstall-dvbsddevice

        +
        +

        7.28 autoinstall-dvbsddevice

        -
        -

        7.28.1 dependencies

        +
        +

        7.28.1 dependencies

        ---
@@ -5776,8 +5811,8 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
        -
        -

        7.28.2 tasks

        +
        +

        7.28.2 tasks

        ---
@@ -5795,12 +5830,12 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
        -
        -

        7.29 autoinstall-hardware-irmp

        +
        +

        7.29 autoinstall-hardware-irmp

        -
        -

        7.29.1 dependencies

        +
        +

        7.29.1 dependencies

        ---
@@ -5811,8 +5846,8 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
        -
        -

        7.29.2 tasks

        +
        +

        7.29.2 tasks

        ---
@@ -5828,19 +5863,19 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
        -
        -

        7.30 kodi

        +
        +

        7.30 kodi

        -
        -

        7.30.1 tasks

        +
        +

        7.30.1 tasks

          -
        1. Install KODI
          +
        2. Install KODI
            -
          • main.yml
            -
            +
          • main.yml
            +
            - import_tasks: install-kodi.yml tags=install,update,kodi:install
 - import_tasks: configure-kodi.yml tags=install,update,kodi:configure
@@ -5848,7 +5883,7 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
            • -
          • install-kodi.yml
            +
          • install-kodi.yml
            ---
@@ -5861,12 +5896,26 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
   with_items:
     - kodi
     - kodi-pvr-vdr-vnsi
-    - kodi-eventclients-kodi-send # for ubuntu packages, team-xbmc uses "kodi-eventclients-xbmc-send for some reason
+
+- name: apt | install kodi-send (team-xbmc PPA)
+  apt:
+    name: "kodi-eventclients-xbmc-send" # team-xbmc uses "kodi-eventclients-xbmc-send for some reason
+    state: present
+    install_recommends: no
+  register: team_xbmc_ppa
+  ignore_errors: True
+
+- name: apt | install kodi-send (Ubuntu package)
+  apt:
+    name: "kodi-eventclients-kodi-send" # fallback to ubuntu package
+    state: present
+    install_recommends: no
+  when: team_xbmc_ppa.failed
            • -
          • configure-kodi.yml
            +
          • configure-kodi.yml
            - name: create kodi.service for the user session
@@ -5915,12 +5964,12 @@ Problem: woher kommt der Treiber (AFAIK noch nicht im Kernel)? Die Firmware soll
        -
        -

        7.30.2 templates

        +
        +

        7.30.2 templates

          -
        1. kodi.service
          +
        2. kodi.service

          This systemd unit for the user session starts (and stops) kodi. @@ -5936,7 +5985,7 @@ This systemd unit for the user session starts (and stops) kodi. ExecStart=/usr/bin/kodi -l /run/lirc/lircd ExecStop=/bin/bash -c "/usr/bin/kodi-send --action=QUIT; while ps -p $MAINPID -o comm=; do sleep .25; done" TimeoutStopSec=10 -SuccessExitStatus=0 127 +SuccessExitStatus=0 127 SIGKILL Restart=on-failure

          @@ -5945,15 +5994,15 @@ This systemd unit for the user session starts (and stops) kodi.
        -
        -

        7.30.3 files

        +
        +

        7.30.3 files

        Those configuration files provide a preconfiguration for kodi which overrides the system wide configuration

          -
        1. Lircmap.xml
          +
        2. Lircmap.xml

          This file allows to map keys sent by remotes via eventlircd (which uses the name devinput) to kodi key names. @@ -6024,14 +6073,14 @@ This file allows to map keys sent by remotes via eventlircd (which uses the name

        3. -
      3. keymaps
        +
      4. keymaps

        This file maps the keys defined in Lircmap.xml to actions within kodi.

          -
        1. remote.xml
          +
        2. remote.xml
          <?xml version="1.0" encoding="UTF-8"?>
@@ -6583,17 +6632,17 @@ This file maps the keys defined in Lircmap.xml to actions within kodi.
      -
      -

      7.31 dvd

      +
      +

      7.31 dvd

      -
      -

      7.31.1 tasks

      +
      +

      7.31.1 tasks

        -
      • install libdvd-pkg, allow programs to eject optical media
        -
        +
      • install libdvd-pkg, allow programs to eject optical media
        +
        ---
 # file: roles/dvd/tasks/main.yml
@@ -6626,6 +6675,7 @@ This file maps the keys defined in Lircmap.xml to actions within kodi.
   shell: sed 's/--lock-media //' /lib/udev/rules.d/60-cdrom_id.rules > /etc/udev/rules.d/60-cdrom_id.rules
   args:
     creates: /etc/udev/rules.d/60-cdrom_id.rules
+    warn: false
        @@ -6633,15 +6683,15 @@ This file maps the keys defined in Lircmap.xml to actions within kodi.
      -
      -

      7.32 install-sundtek

      +
      +

      7.32 install-sundtek

      -
      -

      7.32.1 variables

      +
      +

      7.32.1 variables

      -
      -

      7.32.2 tasks

      +
      +

      7.32.2 tasks

      ---
@@ -6690,8 +6740,8 @@ This file maps the keys defined in Lircmap.xml to actions within kodi.
      -
      -

      7.32.3 templates

      +
      +

      7.32.3 templates

      # ----- GLOBAL SECTION -----
@@ -6797,8 +6847,8 @@ This file maps the keys defined in Lircmap.xml to actions within kodi.
      -
      -

      7.33 template-test

      +
      +

      7.33 template-test

      ---
@@ -7039,12 +7089,12 @@ EndSection
      -
      -

      7.34 wakeup

      +
      +

      7.34 wakeup

      -
      -

      7.34.1 defaults

      +
      +

      7.34.1 defaults

      ---
@@ -7054,8 +7104,8 @@ EndSection
      -
      -

      7.34.2 tasks

      +
      +

      7.34.2 tasks

      ---
@@ -7076,8 +7126,8 @@ EndSection
      -
      -

      7.34.3 templates

      +
      +

      7.34.3 templates

      {{ ansible_managed | comment }}
@@ -7103,12 +7153,12 @@ ACPI_START_AHEAD=5
      -
      -

      7.35 grub-config

      +
      +

      7.35 grub-config

      -
      -

      7.35.1 default variables

      +
      +

      7.35.1 default variables

      system:
@@ -7120,8 +7170,8 @@ ACPI_START_AHEAD=5
      -
      -

      7.35.2 tasks

      +
      +

      7.35.2 tasks

      ---
@@ -7146,8 +7196,8 @@ ACPI_START_AHEAD=5
      -
      -

      7.35.3 templates

      +
      +

      7.35.3 templates

      #!/bin/sh
@@ -7170,8 +7220,8 @@ menuentry "PowerOff" {
      -
      -

      7.35.4 handlers

      +
      +

      7.35.4 handlers

      ---
@@ -7194,15 +7244,15 @@ menuentry "PowerOff" {
      -
      -

      8 Modules

      +
      +

      8 Modules

      This section contains custom modules for the yaVDR Playbooks. They are used to collect facts about the system and configure applications and daemons.

      -
      -

      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.
@@ -7380,10 +7430,87 @@ This section contains custom modules for the yaVDR Playbooks. They are used to c
      -
      -

      8.2 satip_facts.py

      +
      +

      8.2 pci_facts.py

      +
      +# This module parses the output of lspci for detailed information about available (sub) devices.
+DOCUMENTATION = '''
+  ---
+  module: pci_facts
+  short_description: parses lspci output for detailed (sub) devices data
+  description:
+      - This module parses the output of lspci for detailed information about available (sub) devices.
+      - returns a list with a dict for each device
+
+notes:
+    - requires lspci (package pciutils)
+
+'''
+
+EXAMPLES = '''
+- name: get detailled pci device infos
+  pci_facts:
+
+- debug:
+    var: pci_devices
+'''
+
+
+import argparse
+import shlex
+import subprocess
+from collections import namedtuple
+
+from ansible.module_utils.basic import *
+
+def convert2hex(arg):
+    arg = arg.strip('"')
+    if arg:
+        return int(arg, 16)
+    else:
+        return None
+
+def parse_lspci_data():
+    parser = argparse.ArgumentParser()
+    parser.add_argument('-r', '--revision', help='revision', type=convert2hex)
+    parser.add_argument('-p', '--progif', help='proginf', type=convert2hex)
+    parser.add_argument('slot')
+    parser.add_argument('device_class', type=convert2hex)
+    parser.add_argument('vendor_id', type=convert2hex)
+    parser.add_argument('device_id', type=convert2hex)
+    parser.add_argument('sub_vendor_id', type=convert2hex)
+    parser.add_argument('sub_device_id', type=convert2hex)
+    parser.add_argument('other', nargs='*', default=[])
+
+    devices = []
+    for line in subprocess.check_output(['lspci', '-nm'], universal_newlines=True).splitlines():
+        args = parser.parse_args(args=shlex.split(line))
+        devices.append(vars(args))
+    return devices
+
+
+def main():
+    arg_specs = {}
+    module = AnsibleModule(argument_spec=arg_specs, supports_check_mode=True,)
+    try:
+        pci_devices = parse_lspci_data()
+    except:
+        module.fail_json(msg="Something fatal happened")
+    data = {'pci_devices': pci_devices}
+    module.exit_json(changed=False, ansible_facts=data, msg=data)
+
+if __name__ == '__main__':
+    main()
+
      +
      +
      +
      +
      +

      8.3 satip_facts.py

      +
      +
      DOCUMENTATION = '''
 ---
 module: hardware_facts
@@ -7505,9 +7632,9 @@ This section contains custom modules for the yaVDR Playbooks. They are used to c
      -
      -

      8.3 xrandr_facts.py

      -
      +
      +

      8.4 xrandr_facts.py

      +
      • [ ] support multiple screens (-d :0.0 .. :0.n)
      @@ -7733,6 +7860,7 @@ This section contains custom modules for the yaVDR Playbooks. They are used to c def output_data(data, write_edids=True): + result = {} if data: modes = [] for _, screen_data in data.items(): @@ -7744,7 +7872,6 @@ This section contains custom modules for the yaVDR Playbooks. They are used to c for refreshrate in refreshrates: modes.append(Mode(connector, resolution, refreshrate)) if modes: - result = {} try: gpu_name, bus_id = collect_nvidia_data() except ValueError: @@ -7793,8 +7920,8 @@ This section contains custom modules for the yaVDR Playbooks. They are used to c
      -
      -

      9 Handlers

      +
      +

      9 Handlers

      - name: Reconfigure unattended upgrades with dpkg
@@ -7876,6 +8003,10 @@ This section contains custom modules for the yaVDR Playbooks. They are used to c
     name: x@vt7.service
     state: stopped
   register: x_stop
+
+- name: reboot required
+  debug:
+    msg: PLEASE REBOOT YOUR SYSTEM.
      @@ -7883,7 +8014,7 @@ This section contains custom modules for the yaVDR Playbooks. They are used to c

      Autor: Alexander Grothe <seahawk1986@gmx.de>

      -

      Created: 2018-08-05 So 14:04

      +

      Created: 2018-09-11 Di 14:50

      Validate