Wake after Suspend issue with dvbt devices (LE12 Kodi 21)

[sub]

I’ll recheck it.

[mvallevand]

You might need to make it optional, if you release it fully the firmware might get uninstalled and need to be reinstalled with each use.

Martin

[sub]

Sub, it is definitely not released. I don't have tuner's primed but if I want to use dvbv5-scan I have to kill the child process.

Do you know if there was anything more to it?

I just started DeviceHostLinux, started a stream. Confirmed dvbv5-scan indicated the device was busy/unavailable. Stopped the stream, leaving DeviceHostLinux running. dvbv5-scan was able to correctly scan and find the channels.

[sub]

I also checked by starting multiple channels (from the same frequency) at the same time, then slowly stopped each. After getting to the last one, it gave me these messages:

2024-02-08 13:34:24:438 [DEBUG] No more streams active.
2024-02-08 13:34:24:438 [DEBUG] Stopping device...
2024-02-08 13:34:24:438 [DEBUG] ~Adapter()
2024-02-08 13:34:24:438 [DEBUG] Adapter::Stop()
2024-02-08 13:34:24:438 [DEBUG] Stopped@1
2024-02-08 13:34:24:438 [DEBUG] Stopped

and then dvbv5-scan could run (even though DeviceHostLinux was still running)

[mvallevand]

Perhaps after failure it is different. In any case ShadowMask's logs show that stop followed by the failure to lock after resume

Martin

[sub]

I can least reproduce this issue: start channel, stop channel, DeviceHostLinux still running, "sudo systemctl suspend", wait 30 seconds, wake machine, attempt to start channel fails.

[sub]

Actually, I'm not convinced this is anything to do with NextPVR. I notice I can do a dvbv5-scan successfully a couple of times, then "sudo systemctl suspend", then try running dvbv5-scan again, and it has the same issue with not locking onto any signal. ie, no NextPVR in the mix.

If I unplug the stick, wait a few seconds, then plug it back in, the device appears to be working again, and dvbv5-scan can find channels.

[sub]

I know OP was using a PCIe card, so info might not help them (unless they find a PCI equivalent lspci etc), but...

I found comments from other users online saying their tuners weren't working after standby (using kodi with tvheadend), and they used usb-reset to get them working. I tried the same thing here, and it got my tuner working again.

Code:

graeme@Ubuntu-NUC11i3:~$ sudo systemctl suspend

graeme@Ubuntu-NUC11i3:~$ dvbv5-scan /usr/share/dvb/dvb-t/nz-WellingtonKaukau
Scanning frequency #1 578000000
       (0x00) Signal= 0.00dBm C/N= 30.00dB UCB= 0 postBER= 273x10^-3
Scanning frequency #2 562000000
       (0x00) Signal= 0.00dBm C/N= 30.00dB UCB= 0 postBER= 273x10^-3
Scanning frequency #3 594000000
       (0x00) Signal= 0.00dBm C/N= 30.00dB UCB= 0 postBER= 273x10^-3

graeme@Ubuntu-NUC11i3:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2040:0265 Hauppauge
Bus 001 Device 003: ID 8087:0026 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

graeme@Ubuntu-NUC11i3:~$ sudo usb-reset 2040:0265

graeme@Ubuntu-NUC11i3:~$ dvbv5-scan /usr/share/dvb/dvb-t/nz-WellingtonKaukau
Scanning frequency #1 578000000
Lock   (0x1f) C/N= 28.25dB UCB= 0 postBER= 1.00
Service TVNZ 1, provider TVNZ: reserved
Service TVNZ 2, provider TVNZ: reserved
Service TVNZ DUKE, provider TVNZ: reserved
Service TVNZ 1 +1, provider TVNZ: reserved
Service TVNZ 2 +1, provider TVNZ: reserved
Service TVNZ DUKE+1, provider TVNZ: reserved
...

[mvallevand]

I removed my kodi service addon to make sure that wasn't doing the restarts then created /storage/.config/sleep.d and put the following script in there as nextpvr.power:

Code:

#!/bin/sh

SERVICE="service.nextpvr"

case "$1" in
  pre)
    if systemctl is-active "$SERVICE" &>/dev/null ; then
      systemctl stop "$SERVICE"
    fi
    ;;
  post)
    if systemctl is-enabled "$SERVICE" &>/dev/null ; then
      systemctl start "$SERVICE"
    fi
    ;;
esac

The power script works fine and I can now playback and record after suspend. I will try it with timed recordings throughout the week.

Interestingly, despite having tvheadend installed and it working fine with suspend, I had no sleep.d and had to create it, but it all seems to be working now.

Great that is the script i hoped would work and I will include it.  I am not sure where TVHeadend.power is ending up.  I will need to check with LE team once I have access to Slack etc after my vacation where it goes during packaging.

Martin

[ShadowMask]

Great that is the script i hoped would work and I will include it. I am not sure where TVHeadend.power is ending up.  I will need to check with LE team once I have access to Slack etc after my vacation where it goes during packaging.

Yes, that works for sorting the suspend/resume on my system, thank you for pointing me in the right direction.

I can see sleep.d in addons\service.tvheadend43\sleep.d within kodi, I'm not sure where else to look in linux itself but is it possible it is being run directly from there somehow?