Project

General

Profile

Bug #4094

Failure to tune DVB-T2 using Panasonic MN88472, dvbv5-scan OK

Added by Mark Clarkstone almost 5 years ago. Updated almost 5 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
2016-11-22
Due date:
% Done:

0%

Estimated time:
Found in version:
git master
Affected Versions:

Description

There appears to be an issue with Tvheadend git master and the Panasonic MN88472 when tuning to DVB-T2 muxes. dvbv5-scan has no problems scanning both delivery systems.

I logged the output from both tvheadend (linuxdvb) & dvbv5-scan for comparison

  • Tvheadend log - The 698mhz mux is a DVB-T mux (which works fine), the 770mhz is a DVB-T2 mux and that fails on the Panasonic, but the Sony (CXD2820R) has no problems tuning to it.
  • dvbv5-scan log

it's a weird one!

History

#1

Updated by Jaroslav Kysela almost 5 years ago

It seems that TVH is requesting PID 8192 (full mux) for your DVB-T tuners. It looks like an issue. The Panasonic probably cannot receive full mux or there's a bug in the driver. Could you add '--trace mpegts' and provide a new log for one tune request ?

#2

Updated by Mark Clarkstone almost 5 years ago

Jaroslav Kysela wrote:

It seems that TVH is requesting PID 8192 (full mux) for your DVB-T tuners. It looks like an issue. The Panasonic probably cannot receive full mux or there's a bug in the driver. Could you add '--trace mpegts' and provide a new log for one tune request ?

Yep, no problem: https://clbin.com/iJfkw. I also tried playing a single service & that fails with poll timeout. dvbv5-zap in monitor mode on both amd64 & arm appear OK.

This did previously work fine with Tvheadend using an older kernel, I think it was 4.3. which used the older MN88472 staging driver.

I've also asked crope (the guy who wrote the driver) to comment & see if he has any ideas :)

#3

Updated by Jaroslav Kysela almost 5 years ago

The PID 8192 is really (wrongly?) used:

2016-11-23 05:58:00.522 [  DEBUG]:mpegts: 770MHz in DVB-T - Waltham - started
2016-11-23 05:58:00.522 [  TRACE]:mpegts: table: mux 0x56327a6b6040 add bat 00/00 (0) pid 0BBA (3002)
2016-11-23 05:58:00.522 [  DEBUG]:mpegts: 770MHz in DVB-T - Waltham - open PID 0BBA (3002) [16/0x7fba4800ea80]
2016-11-23 05:58:00.522 [  TRACE]:mpegts: table: mux 0x56327a6b6040 add uk_freesat 00/00 (0) pid 0BBB (3003)
2016-11-23 05:58:00.522 [  DEBUG]:mpegts: 770MHz in DVB-T - Waltham - open PID 0BBB (3003) [16/0x7fba480031b0]
2016-11-23 05:58:00.522 [  TRACE]:mpegts: table: mux 0x56327a6b6040 add eit 00/00 (0) pid 0012 (18)
2016-11-23 05:58:00.522 [  DEBUG]:mpegts: 770MHz in DVB-T - Waltham - open PID 0012 (18) [20/0x7fba4805dd60]
2016-11-23 05:58:00.522 [  DEBUG]:mpegts: 770MHz in DVB-T - Waltham - open PID fullmux subscription [0003/0x7fba1cfe7d40]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2016-11-23 05:58:01.789 [  TRACE]:linuxdvb: Panasonic MN88472 : DVB-T #1 - open PID 2000 (8192) fd 38
#4

Updated by Mark Clarkstone almost 5 years ago

Jaroslav Kysela wrote:

The PID 8192 is really (wrongly?) used:

[...]

The Sony does the same thing..

2016-11-24 07:42:13.517 [  DEBUG]:mpegts: 770MHz in DVB-T - Waltham - started
2016-11-24 07:42:13.517 [  TRACE]:mpegts: table: mux 0x561055a511f0 add bat 00/00 (0) pid 0BBA (3002)
2016-11-24 07:42:13.517 [  DEBUG]:mpegts: 770MHz in DVB-T - Waltham - open PID 0BBA (3002) [16/0x7f9eac02aa80]
2016-11-24 07:42:13.517 [  TRACE]:mpegts: table: mux 0x561055a511f0 add uk_freesat 00/00 (0) pid 0BBB (3003)
2016-11-24 07:42:13.517 [  DEBUG]:mpegts: 770MHz in DVB-T - Waltham - open PID 0BBB (3003) [16/0x7f9eac02cf60]
2016-11-24 07:42:13.517 [  TRACE]:mpegts: table: mux 0x561055a511f0 add eit 00/00 (0) pid 0012 (18)
2016-11-24 07:42:13.517 [  DEBUG]:mpegts: 770MHz in DVB-T - Waltham - open PID 0012 (18) [20/0x7f9eac023f10]
2016-11-24 07:42:13.517 [  DEBUG]:mpegts: 770MHz in DVB-T - Waltham - open PID fullmux subscription [0003/0x7f9e98030670]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2016-11-24 07:42:13.517 [   INFO]:subscription: 0016: "HTTP" subscribing to mux "770MHz", weight: 10, adapter: "Sony CXD2820R : DVB-T #0", network: "DVB-T - Waltham", service: "Raw PID Subscription", hostname="192.168.1.40", client="VLC$
2016-11-24 07:42:13.567 [  TRACE]:linuxdvb: Sony CXD2820R : DVB-T #0 - checking FE status (ready)
2016-11-24 07:42:14.661 [  DEBUG]:linuxdvb: Sony CXD2820R : DVB-T #0 - status    GOOD (SIGNAL | CARRIER | VITERBI | SYNC | LOCK)
2016-11-24 07:42:14.661 [  DEBUG]:linuxdvb: Sony CXD2820R : DVB-T #0 - locked
2016-11-24 07:42:14.661 [  TRACE]:mpegts: table: mux 0x561055a511f0 add pat 00/00 (0) pid 0000 (0)
2016-11-24 07:42:14.662 [  DEBUG]:mpegts: 770MHz in DVB-T - Waltham - open PID 0000 (0) [20/0x7f9eac025390]
2016-11-24 07:42:14.662 [  TRACE]:mpegts: table: mux 0x561055a511f0 add cat 01/FF (1) pid 0001 (1)
2016-11-24 07:42:14.662 [  DEBUG]:mpegts: 770MHz in DVB-T - Waltham - open PID 0001 (1) [16/0x7f9eac0269b0]
2016-11-24 07:42:14.662 [  TRACE]:mpegts: table: mux 0x561055a511f0 add nit 00/00 (0) pid 0010 (16)
2016-11-24 07:42:14.662 [  DEBUG]:mpegts: 770MHz in DVB-T - Waltham - open PID 0010 (16) [16/0x7f9eac027e30]
2016-11-24 07:42:14.662 [  TRACE]:mpegts: table: mux 0x561055a511f0 add sdt 40/F8 (64) pid 0011 (17)
2016-11-24 07:42:14.662 [  DEBUG]:mpegts: 770MHz in DVB-T - Waltham - open PID 0011 (17) [20/0x7f9eac0292b0]
2016-11-24 07:42:14.662 [  TRACE]:mpegts: table: mux 0x561055a511f0 add bat 48/F8 (72) pid 0011 (17)
2016-11-24 07:42:14.662 [  DEBUG]:mpegts: 770MHz in DVB-T - Waltham - open PID 0011 (17) [16/0x7f9eac003ff0]
2016-11-24 07:42:14.662 [  TRACE]:linuxdvb: Sony CXD2820R : DVB-T #0 - open PID 2000 (8192) fd 44
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2016-11-24 07:42:14.670 [  TRACE]:linuxdvb: Sony CXD2820R : DVB-T #0 - checking FE status (ready)
2016-11-24 07:42:14.672 [  TRACE]:linuxdvb: Sony CXD2820R : DVB-T #0 - status 1 (001F)

I've tried using dvblast with the astrometa and it fails with that too.

I've checked /dev/dvb/adapter0/ & there is no dvr1, tvheadend appears to be using dvr0. which is correct?

[email protected]:~$ ls /dev/dvb/adapter0/
demux0  dvr0  frontend0  frontend1  net0

This is making my head hurt :p

Also available in: Atom PDF