Probs after standby "Disconnected from hts tvheadend"

Peter Ludwig

Hello,
I am new in this forum and just trying openelec with tvheadend. I am quite happy with this nice and fast system.
But I have problem. After a start TV watching is nice, but after going to standby (S3) and resume later I cannot watch TV. So it is very difficult to schedule recording unless I run the system permanently.
After resume I get the message "working" followed by "Disconnected from hts tvheadend" when trying to watch TV and then nothings happens. Even when I then try to shut down or sleep or reboot the system is hanging. I tried to unload the modules before standby but no success.
After resume there are a lot of messages in the log file like this "ngene: Command timeout". I attached the file.
Has anybody an idea what to do? I googled at lot and finally I am completely confused...
Many thanks in advance

Gaper

This is my system: Openelec v 3.2.4, tvheadend v 3.1.4, intel x86_64, tv-card: dual tuner cine S2 (v4)

ProfYaffle

Those are v4l dvb calls from what I can see - so the errors are coming from the dvb OS subsystem rather than tvheadend. The question is why...

From your comments, you've looked at unloading and reloading the modules as you go to suspend... as well as the OE interface, though, you can edit the specific scripts. That would allow you to do some testing from the command line as well (i.e. run the scripts to simulate standby/resume).

You can see the script kicking in here in your log:

Feb 15 22:29:13 openelec user.notice Boot: ### running addon sleep script /storage/.xbmc/addons/service.multimedia.tvheadend/sleep.d/tvheadend.power (suspend)... ###

and

Feb 15 22:29:37 openelec user.notice Boot: ### running addon sleep script /storage/.xbmc/addons/service.multimedia.tvheadend/sleep.d/tvheadend.power (resume)... ###

Does debug logging tell you any more, either in XBMC or tvheadend?

What does the tvheadend web interface look like after resume - is that available, what does the adapter status say, does it look like the adapters are there (so it's an XBMC/addon problem) or not (so it's an OS problem)?

What happens if you manually restart tvheadend again after the system is fully up (in case it's a firmware/module reload issue - timing - tvheadend/XBMC being ready before the tuner has restarted properly)?

I run tvh on a separate system, so I can't really do any testing for you.

I suppose you could try the OE beta with or without the updated tvheadend (3.9) addon, see if that's any better.

Peter Ludwig

Hello,

Sorry, I just found the notice-mail of your answer in my spam-folder:( therefore I didn't answer for a long time).

First of all, thank you for giving a fast answer and offering support.

I tried the tvheadend web interface and found, when I am connected via web-interface before suspend no resume is possible (that was reproduceable). When I close the browser before suspend resume is possible but I get no access to the web interface so it seems to be an OS prob (following your comments).

I enabled logging and attached the xbmc.log and all other log.file. I am not able to find something in the log-files.

Sorry, but I don't know how to restart tvheadend manually (I run tvheadend.start in the folder ~/.xbmc/addons/service.multimedia.tvheadend/sleep.d, but no success)

To use OE 4.0beta do I have to make a full new installation? What happens with my settings and data?

So, a lot of questions...
BR
Gaper

ProfYaffle

I'm not really sure what to suggest... it's definitely coming from the ngene driver (or, at least, that's my best guess). To test this, you'd need to see what syslog says on resume - can you see the tuners re-initialising; also, do you have the /dev/dvb files you'd expect (or whatever the OE equivalents are).

You could try Ubuntu instead of OE, but that's major surgery; the OE beta is safer. Simply copy the SYSTEM and KERNEL files into your Update SMB share and reboot - I did it with my systems last week, and I don't recall losing any of my configuration (but it's always wise to take a backup first).

The linuxtv web page says something about an external power supply - is that true? Is it plugged into a decent power source?

Peter Ludwig

Hmm, really difficult.
There is no external power supply, the power supply should be ok.
Where do I find the syslog? How can I see if the tuners are re-initialising? I looked into dev/dvb, it contains both adapters (see attachment) , no change after resume. What kind of files should I find in dev/dvb?
To move to Ubuntu is not a real option, I like the fast booting, slim OE. Maybe I will try OE beta, but this takes time because I want to backup first. Do have an proposal how to do it simple?
Many thanks

Gaper

Peter Ludwig

Hmm,
first of all I made I back-up with the backup-addon (nice tool).
Than I updated to OE 3.95.2 and... TV is not more running. Error messages are: "Tvheadend disconnected" and "No PVR-client started", but I activated everything in the menu. Access via web-interface is not possible (no connection to the server), but ssh is running.
So, what could I do?
Many thanks
Gaper

ProfYaffle

tvheadend clearly didn't survive the upgrade... you can easily downgrade again by going through the same processes but with an earlier version.

Have you checked that the tvheadend addon is installed, enabled and configured correctly?

Peter Ludwig

Surprise, surprise,
I got at least tvheadend running. I deactivated the MCE-client and a DVB-client (they occurred after the upgrade), some rebooting and I am able to watch TV again (Access via web-interface is also possible). But the original prob is still there :( after going to standby (S3) and resume later I cannot watch TV. The only difference is, that when I shut down or sleep or reboot the system this is possible now later after resume.
I like this slim OE also with this simple backup and upgrade function so I would be really happy to get sleep/resume issue solved.
So, Prof Yaffle, any idea how to solve the issue?
Many thanks
Gaper

ProfYaffle

I'm afraid I'll have to abandon you here... you'd maybe be better off fighting this on the OpenElec forum, as I don't think this is tvheadend-specific. As above, the ngene errors suggest it's a driver problem.

Sorry :(

Peter Ludwig

Nevertheless, thank you for your support.
I will try to get support from the oe-forum.
Thanks again
Gaper