2024-02-08, 12:16 AM
I’ll recheck it.
2024-02-08, 12:16 AM
I’ll recheck it.
2024-02-08, 12:27 AM
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
2024-02-08, 12:32 AM
(2024-02-08, 12:13 AM)mvallevand Wrote: 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.
2024-02-08, 12:36 AM
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:
Quote:2024-02-08 13:34:24:438 [DEBUG] No more streams active. and then dvbv5-scan could run (even though DeviceHostLinux was still running)
2024-02-08, 01:15 AM
Perhaps after failure it is different. In any case ShadowMask's logs show that stop followed by the failure to lock after resume
Martin
2024-02-08, 01:39 AM
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.
2024-02-08, 01:57 AM
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.
2024-02-08, 02:09 AM
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
2024-02-08, 07:52 AM
(This post was last modified: 2024-02-08, 07:52 AM by mvallevand.)
(2024-02-07, 03:06 PM)ShadowMask Wrote: 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: 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
2024-02-08, 09:08 AM
(This post was last modified: 2024-02-08, 09:08 AM by ShadowMask.)
(2024-02-08, 07:52 AM)mvallevand Wrote: 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? |
|