systemd-sleep/yavdr shows unload dvb-drivers but not restore

  • I haven't noticed anything wrong but I'm wondering if everything is correct: /lib/systemd/system-sleep/yavdr has been generated and it looks fine to me:

    Code
    1. case $1 in
    2. pre)
    3. [...]
    4. echo "unload dvb drivers"
    5. [...]
    6. ;;
    7. post)
    8. [...]
    9. echo "restore dvb drivers"
    10. [...]

    but

    1. I see only the "pre/unload" message and not the "post/restore" one in sudo journalctl | grep 'dvb drivers'.
    2. similarly I see only the `rename /etc/avahi/services/xxx.service to /etc/avahi/services/xxx.disabled`, but not the other way around, and indeed ll /etc/avahi/services/*.* shows only "disabled" file

    So that I have the strong impression that the script isn't called when waking up. Is this normal?


    I have defined vdr_shutdown_command: "/usr/bin/systemctl hibernate" but according to systemd-suspend.service(8) it shouldn't make a difference.

    Gehäuse: Antec Fusion Remote
    Netzteil: Seasonic S12II-430GB
    Mainboard: ASUS P8H67-M EVO R.3.0
    CPU: Intel® Core™ i5-2405S
    CPU-Kühler: Scythe Samurai ZZ
    RAM: Corsair DIMM 4 GB DDR3-1600 Kit
    HD-Adapter: Scythe Twin Mounter 2.5 Rev.C
    HD root: Corsair Force F60 2,5" SSD 60 GB
    HD data: Western Digital WD5000BUCT 500 GB
    Laufwerk: Sony Optiarc AD-7283S-0S
    DVB-Karte: Digital Devices Cine CT V6, Dual DVB-C/DVB-T PCIe

    Fernbedienung: Andoer® Universal Fernbedienung, MX3 (Ersatz)

    Distro: YaVDR 0.7 on Ubuntu 20.04.3 LTS

  • Yep, i added echo "YAVDR called as $0 with $*" before the case-statement in the script and I get only in journalctl | grep YAVDR the pre-message: systemd-sleep[2307]: YAVDR called as /usr/lib/systemd/system-sleep/yavdr with pre hibernate, meaning the script really doesn't seem to be called on wake-up.

    Gehäuse: Antec Fusion Remote
    Netzteil: Seasonic S12II-430GB
    Mainboard: ASUS P8H67-M EVO R.3.0
    CPU: Intel® Core™ i5-2405S
    CPU-Kühler: Scythe Samurai ZZ
    RAM: Corsair DIMM 4 GB DDR3-1600 Kit
    HD-Adapter: Scythe Twin Mounter 2.5 Rev.C
    HD root: Corsair Force F60 2,5" SSD 60 GB
    HD data: Western Digital WD5000BUCT 500 GB
    Laufwerk: Sony Optiarc AD-7283S-0S
    DVB-Karte: Digital Devices Cine CT V6, Dual DVB-C/DVB-T PCIe

    Fernbedienung: Andoer® Universal Fernbedienung, MX3 (Ersatz)

    Distro: YaVDR 0.7 on Ubuntu 20.04.3 LTS

  • I can confirm this fails on a Ubuntu Server 20.04 installation without further customization - by default the system is not able to resume from hibernation properly if a swapfile is used - according to https://wiki.archlinux.org/tit…and_hibernate#Hibernation this requires at least additional configuration of boot parameters and the initramfs to use the resume data stored to the swap file.


    I tried https://rephlex.de/blog/2019/1…ing-full-disk-encryption/ but ran into a problem with the nvidia driver that causes hung kernel tasks when hibernating, so maybe if is necessary to order the operations more strictly.

    yaVDR-Dokumentation (Ceterum censeo enchiridia esse lectitanda.)

  • Thanks, very good catch. I'll try to see if I can add something to the Ansible code of YaVDR but someone is too busy to merge my Pull Requests :-P

    Gehäuse: Antec Fusion Remote
    Netzteil: Seasonic S12II-430GB
    Mainboard: ASUS P8H67-M EVO R.3.0
    CPU: Intel® Core™ i5-2405S
    CPU-Kühler: Scythe Samurai ZZ
    RAM: Corsair DIMM 4 GB DDR3-1600 Kit
    HD-Adapter: Scythe Twin Mounter 2.5 Rev.C
    HD root: Corsair Force F60 2,5" SSD 60 GB
    HD data: Western Digital WD5000BUCT 500 GB
    Laufwerk: Sony Optiarc AD-7283S-0S
    DVB-Karte: Digital Devices Cine CT V6, Dual DVB-C/DVB-T PCIe

    Fernbedienung: Andoer® Universal Fernbedienung, MX3 (Ersatz)

    Distro: YaVDR 0.7 on Ubuntu 20.04.3 LTS