Project

General

Profile

14.04 (32bit) After some time: No input detected. Where is the problem?

Added by A T over 10 years ago

Hi,

i changed with a clean install to 14.04.

Using 2x terratec htc usb dvb-C with the following firmware:
https://github.com/OpenELEC/dvb-firmware/blob/master/firmware/dvb-usb-terratec-htc-stick-drxk.fw
Its the same firmware that worked fine until now.

I tried with stable and unstable repo.

Problem:
After quite some time (a few h up to ~12h) i get in XBMC the "no signal detected". It seems as is starts with one programm but after a few tries none work.

A reboot is required to fix. W-scan can still acces the devices btw, not sure if that means its not my devices..

Here is the log output:
Loglevel debug: enabled
Apr 28 13:01:06.037 Service: 2/122,000 kHz/RTL: Status changed to [Graceperiod expired]
Apr 28 13:01:06.278 subscription: "192.168.1.102 [ dertester | XBMC Media Center ]" unsubscribing from "RTL"
Apr 28 13:01:06.287 Service: Subscription "192.168.1.102 [ dertester | XBMC Media Center ]": Adding adapter "_dev_dvb_adapter1_DRXK_DVB_C_DVB_T394000000" for service "2/394,000 kHz/RTL II"
Apr 28 13:01:06.288 Service: Subscription "192.168.1.102 [ dertester | XBMC Media Center ]": Adding adapter "_dev_dvb_adapter0_DRXK_DVB_C_DVB_T394000000" for service "1/394,000 kHz/RTL II"
Apr 28 13:01:06.288 Service: Subscription "192.168.1.102 [ dertester | XBMC Media Center ]": Probing adapter "_dev_dvb_adapter1_DRXK_DVB_C_DVB_T394000000" without stealing for service "2/394,000 kHz/RTL II"
Apr 28 13:01:06.288 dvb: /dev/dvb/adapter1 stopping thread
Apr 28 13:01:06.288 dvb: /dev/dvb/adapter1 stopped thread
Apr 28 13:01:06.288 dvb: "/dev/dvb/adapter1" tuning to "Kabel Deutschland: 394,000 kHz" (Transport start)
Apr 28 13:01:06.288 subscription: "192.168.1.102 [ dertester | XBMC Media Center ]" subscribing on "RTL II", weight: 150, adapter: "2", network: "Kabel Deutschland", mux: "Kabel Deutschland: 394,000 kHz", provider: "Digital Free", service: "RTL II", quality: 100
Apr 28 13:01:06.521 dvb: /dev/dvb/adapter1 started dvr thread
Apr 28 13:01:06.521 viasat_baltic: install table handlers
Apr 28 13:01:06.521 uk_freesat: install table handlers
Apr 28 13:01:06.521 eit: install table handlers
Apr 28 13:01:06.923 eit: processing complete
Apr 28 13:01:16.037 Service: 2/394,000 kHz/RTL II: Status changed to [Graceperiod expired]

More here:
http://pastebin.com/PsFyNhJk

Can you help pls?


Replies (2)

RE: 14.04 (32bit) After some time: No input detected. Where is the problem? - Added by Prof Yaffle over 10 years ago

I would guess at power saving... either the OS powering the USB tuners down and not waking them up again or tvheadend doing something similar. Emphasis on "guess".

I don't have 14.04, but see what power management options you have in the OS. You can also look at the 'keep FE open' option in tvheadend; I've never been 100% certain as to what it does, but I think it locks the front end and doesn't return control of it to the operating system.

The other area I'd explore is whether tvheadend is losing sight of the adapters or is it XBMC-related. You say that you're seeing the error in XBMC, but go to the tvheadend web interface and see if you can either record a programme or stream something to (e.g.) VLC once XBMC starts complaining. It's not impossible that the back end is fine, it's perhaps an addon/front-end problem.

RE: 14.04 (32bit) After some time: No input detected. Where is the problem? - Added by A T over 10 years ago

Hmm...

About energy savings:
-At least on the status page of tvheadend webpage it shows that its actually tuning to freq but no values for bitrate.. just the frequency and channelname
-w-scan can access the device normally and finds muxes
-global standby is disabled and i didnt change usb settings with powertop etc.

About XBMC:
-My recordings wont work also...

=> my conclusion of this would be its something tvh related as the other things work..
I dont understand why tvh cant grab the device again but w-scan has no problem..

Additional:
I reverted back to 13.10 and everything works as usual.
=> Cant try your option atm, but im not sure where to find or that is saw this at my devices.

I often read about this and it was stated its somewhere in the hardware but im not so sure with this ..

    (1-2/2)