Project

General

Profile

Bug #3215

Subscribe channel/San muxes only once after reboot

Added by Stefan Strobel about 9 years ago. Updated about 9 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
Category:
DVB
Target version:
-
Start date:
2015-10-27
Due date:
% Done:

0%

Estimated time:
Found in version:
4.0.5
Affected Versions:

Description

Hi,

My System:
  • raspberry pi 2 with osmc-latest
  • DVBSky S960
  • Tvheadend-4.0.5

I'm not sure, if it's a tvheadend problem.
When i boot my system and choose a channel (like DMAX first) all works fine.
If i swith to another channel and come back to DMAX, no subscription is possible.
Adding the Mux for DMAX was the same. Only after reboot and first switch the DMAX-Mux to PEND, the state changed to OK.
All Services I add this way, i can only watch first time after reboot.
Restarting tvheadend does not help, so it might be a kernel/firmware-problem?

I've attached a logfile where i switch to DMAX, then to 3Sat and back to DMAX.


Files

tvh.log (288 KB) tvh.log Tvheadend logfile Stefan Strobel, 2015-10-27 23:40

History

#1

Updated by Jaroslav Kysela about 9 years ago

Try to play in tuner settings, disable power save, increase tune repeats, increase buffering. The driver doesn't give data do TVH for a reason.

#2

Updated by Stefan Strobel about 9 years ago

Playing with tuner settings does not help.
I also compiled from master but same behavior.
I will do some other tests.

#3

Updated by Jaroslav Kysela about 9 years ago

Also note that some linux 4.x kernels were broken (linuxdvb).

#4

Updated by Stefan Strobel about 9 years ago

I swiched temporary to OpenElec and all works fine (TVH-4.0.3).
Kernel version from OpenElec 5.95.5 is 4.1.6.
Kernel version from OSMC 2015.10-1 is 4.2.3-3.
So i guess something is broken in kernel > 4.1.6.

After next release i will give osmc another chance (if kernel is upgraded).

So no problem with tvheadend so far.

thx

#5

Updated by Jaroslav Kysela about 9 years ago

  • Status changed from New to Invalid

Closing as invalid - it seems like a kernel bug.

Also available in: Atom PDF