Mailing List Archive

On 03/06/2020 07:57, jam@tigger.ws wrote:
> I have long used (upto 30) a pair. of haupauge usb tuners
>
> I recenty upgraded to 31, and after a few fumbles
>
> I can scan channels
> I get resonable. results
> dmesg shows cards found, firmware loaded
> epg gets reasonable results
>
> record a channel results in the red no later by X symbol
> Watch live TV shows signal strengh of 90% but no lock
> Record has the unable to get lock pop-up
>
> What can I be looking for. Using my lucky-packet cards does work, these cards used to work
> James
>
> PS
>
> [ 11.726855] rc rc1: Hauppauge WinTV-dualHD DVB as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/rc/rc1
> [ 11.726879] rc rc1: lirc_dev: driver em28xx registered at minor = 1, scancode receiver, no transmitter
> [ 11.726912] input: Hauppauge WinTV-dualHD DVB as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/rc/rc1/input14
> [ 11.726940] em28xx 1-4:1.0: Input extension successfully initialized
> [ 11.726941] em28xx 1-4:1.0: Remote control support is not available for this card.
> [ 11.726942] em28xx: Registered (Em28xx Input Extension) extension
> [ 11.733792] No iBFT detected.
> [ 16.762855] e1000e 0000:00:1f.6 eno1: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
> [ 16.856437] NET: Registered protocol family 17
> [ 19.946724] fuse: init (API version 7.31)
> [ 20.076264] si2168 12-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
> [ 20.284000] si2168 12-0064: firmware version: B 4.0.11
> [ 20.288097] si2157 17-0060: found a 'Silicon Labs Si2157-A30'
> [ 20.335988] si2157 17-0060: firmware version: 3.0.5
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

That device is working fine for me on both Ubuntu 20.04 and Rasbian with
version 31 of Mythtv.

Check the aerial connections


_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On Wed, 3 Jun 2020 14:57:36 +0800, you wrote:

>I have long used (upto 30) a pair. of haupauge usb tuners
>
>I recenty upgraded to 31, and after a few fumbles
>
>I can scan channels
> I get resonable. results
> dmesg shows cards found, firmware loaded
> epg gets reasonable results
>
>record a channel results in the red no later by X symbol
>Watch live TV shows signal strengh of 90% but no lock
>Record has the unable to get lock pop-up
>
>What can I be looking for. Using my lucky-packet cards does work, these cards used to work
>James
>
>PS
>
>[ 11.726855] rc rc1: Hauppauge WinTV-dualHD DVB as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/rc/rc1
>[ 11.726879] rc rc1: lirc_dev: driver em28xx registered at minor = 1, scancode receiver, no transmitter
>[ 11.726912] input: Hauppauge WinTV-dualHD DVB as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/rc/rc1/input14
>[ 11.726940] em28xx 1-4:1.0: Input extension successfully initialized
>[ 11.726941] em28xx 1-4:1.0: Remote control support is not available for this card.
>[ 11.726942] em28xx: Registered (Em28xx Input Extension) extension
>[ 11.733792] No iBFT detected.
>[ 16.762855] e1000e 0000:00:1f.6 eno1: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
>[ 16.856437] NET: Registered protocol family 17
>[ 19.946724] fuse: init (API version 7.31)
>[ 20.076264] si2168 12-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
>[ 20.284000] si2168 12-0064: firmware version: B 4.0.11
>[ 20.288097] si2157 17-0060: found a 'Silicon Labs Si2157-A30'
>[ 20.335988] si2157 17-0060: firmware version: 3.0.5

Check your tuning timeouts. If your database was originally created a
long time ago, the tuning timeouts will be much smaller than the
recommended 10 seconds (10000 milliseconds) that gets set when
creating new DVB tuners today. I think the tuning code takes a little
longer to tune now, and it may be going over your tuning timeouts.

There should be some error messages in mythbackend.log to show you
what the problem is. If not, try adding "-v record" to your
mythbackend command line. In Ubuntu, add this put in an
/etc/mythtv/additional.args file:

ADDITIONAL_ARGS=-v record

and then restart mythbackend:

sudo systemctl restart mythtv-backend

Or you can run this command from any command prompt:

mythbackend --setverbose record

which tells the running copy of mythbackend to set the verbose record
logging option. Be careful to cut and paste that command, rather than
typing it. Getting it wrong can lead to you having two copies of
mythbackend running at once.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On Wed, 3 Jun 2020 at 09:01, jam@tigger.ws <jam@tigger.ws> wrote:

> I have long used (upto 30) a pair. of haupauge usb tuners
>
> I recenty upgraded to 31, and after a few fumbles
>
> I can scan channels
> I get resonable. results
> dmesg shows cards found, firmware loaded
> epg gets reasonable results
>
> record a channel results in the red no later by X symbol
> Watch live TV shows signal strengh of 90% but no lock
> Record has the unable to get lock pop-up
>
> What can I be looking for. Using my lucky-packet cards does work, these
> cards used to work
> James
>
>
> I suggest to do a channel scan as follows:
- delete the capture cards
- create new capture cards; they will now have the latest default timeout
values
- create a new video source
- connect the capture cards to the new video source
- do a channel scan, for receiving with an antenna the "Full Scan" is best
and then everything should work.

One possible reason is that the transports (transport stream multiplexes,
stored in table dtv_multiplex) can have old/incorrect values and these
values are not updated with a channel scan in v31. This is recently fixed
in master.
Deleting the channels does not help for this because that does not delete
the transports.

Another possible reason is that there are, in addition to new channels
found with the channel scan, also old channels with the same name/callsign
but with incorrect tuning data. Duplicate channels can greatly confuse the
guide and the scheduler.

Both possibilities are eliminated by using a new video source.

The old video source can be deleted when you are happy with the new one.
In v31 the guide will only show channels from video sources that are
connected to capture cards.

Creating new capture cards is the way to make sure that you have the actual
default values for timeouts. The default timeout values are in v31 bigger
than they used to be in v30 but maybe not yet big enough. Feedback on this
is appreciated.

Klaas.

> On 3 Jun 2020, at 7:08 pm, Klaas de Waal <klaas.de.waal@gmail.com> wrote:
>
> I suggest to do a channel scan as follows:
> - delete the capture cards
> - create new capture cards; they will now have the latest default timeout values
> - create a new video source
> - connect the capture cards to the new video source
> - do a channel scan, for receiving with an antenna the "Full Scan" is best
> and then everything should work.

This is exeactly what I've done.

> One possible reason is that the transports (transport stream multiplexes, stored in table dtv_multiplex) can have old/incorrect values and these values are not updated with a channel scan in v31. This is recently fixed in master.
> Deleting the channels does not help for this because that does not delete the transports.
>
> Another possible reason is that there are, in addition to new channels found with the channel scan, also old channels with the same name/callsign but with incorrect tuning data. Duplicate channels can greatly confuse the guide and the scheduler.
>
> Both possibilities are eliminated by using a new video source.
>
> The old video source can be deleted when you are happy with the new one.
> In v31 the guide will only show channels from video sources that are connected to capture cards.
>
> Creating new capture cards is the way to make sure that you have the actual default values for timeouts. The default timeout values are in v31 bigger than they used to be in v30 but maybe not yet big enough. Feedback on this is appreciated.

There is a subtle entry in the log

2020-06-03 10:27:29.993036 W [27922/27922] CoreContext dtvmultiplex.cpp:340 (ParseDVB_T2) - DTVMux: Undefined modulation system, using DVB-T2.

What is. even more frustrating I put my lucky-packet cards in (Leadteck that pixcelate on HD) and everything works perfectly with no further setup.

I'm now trying John's setup with 'buntu 20.04 (and people hate 'me too' type posts, but sheesh they help lots)

I'll post what happens

Thanks
James
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

>
>
> There is a subtle entry in the log
>
> 2020-06-03 10:27:29.993036 W [27922/27922] CoreContext
> dtvmultiplex.cpp:340 (ParseDVB_T2) - DTVMux: Undefined modulation system,
> using DVB-T2.
>
> What is. even more frustrating I put my lucky-packet cards in (Leadteck
> that pixcelate on HD) and everything works perfectly with no further setup.
>
>
> You can also check the "Delivery system" setting for the capture cards.
You have the choice between all that your card supports and it should be
set to DVB-T2 if you card can do that.
With that setting you can also receive the DVB-T multiplexes.

Klaas.

> On 3 Jun 2020, at 8:13 pm, Klaas de Waal <klaas.de.waal@gmail.com> wrote:
>
>
> There is a subtle entry in the log
>
> 2020-06-03 10:27:29.993036 W [27922/27922] CoreContext dtvmultiplex.cpp:340 (ParseDVB_T2) - DTVMux: Undefined modulation system, using DVB-T2.
>
> What is. even more frustrating I put my lucky-packet cards in (Leadteck that pixcelate on HD) and everything works perfectly with no further setup.
>
>
> You can also check the "Delivery system" setting for the capture cards. You have the choice between all that your card supports and it should be set to DVB-T2 if you card can do that.
> With that setting you can also receive the DVB-T multiplexes.
>
> Klaas.
>

Opinion please
could we be looking at kernel versions. (again: running this on open-suse leap 15.1 on version 30 DOES work)

Running ubuntu, which works for someone ...

2020-06-05 16:19:14.514575 I CardUtil[1]: Set delivery system: DVB-T2
2020-06-05 16:19:14.516633 W DVBSigMon[1](/dev/dvb/adapter0/frontend0): Cannot measure S/N
eno: Unknown error 524 (524)
2020-06-05 16:19:14.516656 W DVBSigMon[1](/dev/dvb/adapter0/frontend0): Cannot measure Bit Error Rate
eno: Unknown error 524 (524)
2020-06-05 16:19:14.516675 W DVBSigMon[1](/dev/dvb/adapter0/frontend0): Cannot count Uncorrected Blocks
eno: Unknown error 524 (524)
2020-06-05 16:19:47.424934 C 'SignalMonitor': MThread prolog was never run!


jam@venus:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 006: ID 045e:0750 Microsoft Corp. Wired Keyboard 600
Bus 001 Device 005: ID 04b3:310b IBM Corp. Red Wheel Mouse
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 002: ID 2040:0265 Hauppauge dualHD

James

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On 05/06/2020 10:04, jam wrote:
>
>
>> On 3 Jun 2020, at 8:13 pm, Klaas de Waal <klaas.de.waal@gmail.com> wrote:
>>
>>
>> There is a subtle entry in the log
>>
>> 2020-06-03 10:27:29.993036 W [27922/27922] CoreContext dtvmultiplex.cpp:340 (ParseDVB_T2) - DTVMux: Undefined modulation system, using DVB-T2.
>>
>> What is. even more frustrating I put my lucky-packet cards in (Leadteck that pixcelate on HD) and everything works perfectly with no further setup.
>>
>>
>> You can also check the "Delivery system" setting for the capture cards. You have the choice between all that your card supports and it should be set to DVB-T2 if you card can do that.
>> With that setting you can also receive the DVB-T multiplexes.
>>
>> Klaas.
>>
>
> Opinion please
> could we be looking at kernel versions. (again: running this on open-suse leap 15.1 on version 30 DOES work)
>
> Running ubuntu, which works for someone ...
>
> 2020-06-05 16:19:14.514575 I CardUtil[1]: Set delivery system: DVB-T2
> 2020-06-05 16:19:14.516633 W DVBSigMon[1](/dev/dvb/adapter0/frontend0): Cannot measure S/N
> eno: Unknown error 524 (524)
> 2020-06-05 16:19:14.516656 W DVBSigMon[1](/dev/dvb/adapter0/frontend0): Cannot measure Bit Error Rate
> eno: Unknown error 524 (524)
> 2020-06-05 16:19:14.516675 W DVBSigMon[1](/dev/dvb/adapter0/frontend0): Cannot count Uncorrected Blocks
> eno: Unknown error 524 (524)
> 2020-06-05 16:19:47.424934 C 'SignalMonitor': MThread prolog was never run!
>
>
> jam@venus:~$ lsusb
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 004: ID 8087:0a2b Intel Corp.
> Bus 001 Device 006: ID 045e:0750 Microsoft Corp. Wired Keyboard 600
> Bus 001 Device 005: ID 04b3:310b IBM Corp. Red Wheel Mouse
> Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
> Bus 001 Device 002: ID 2040:0265 Hauppauge dualHD
>
> James

How about 'dmesg | grep adapter' or 'dmesg | grep firmware' or 'dmesg |
grep -i dvb' ?

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

> On 5 Jun 2020, at 5:56 pm, John Pilkington <johnpilk222@gmail.com> wrote:
>
> On 05/06/2020 10:04, jam wrote:
>>
>>> On 3 Jun 2020, at 8:13 pm, Klaas de Waal <klaas.de.waal@gmail.com> wrote:
>>>
>>>
>>> There is a subtle entry in the log
>>>
>>> 2020-06-03 10:27:29.993036 W [27922/27922] CoreContext dtvmultiplex.cpp:340 (ParseDVB_T2) - DTVMux: Undefined modulation system, using DVB-T2.
>>>
>>> What is. even more frustrating I put my lucky-packet cards in (Leadteck that pixcelate on HD) and everything works perfectly with no further setup.
>>>
>>>
>>> You can also check the "Delivery system" setting for the capture cards. You have the choice between all that your card supports and it should be set to DVB-T2 if you card can do that.
>>> With that setting you can also receive the DVB-T multiplexes.
>>> Klaas.

Although dmesg does not mention firmware *and* /dev/dvb entries are instatiated putting a firmware file (in /lib/firmware) does result in working cards!
This happens on ubuntu but not on my SuSE system!

Just for the record I was unable to get
# apt-get install mythtv
to give me a working system, so I built from src

James

>>>
>> Opinion please
>> could we be looking at kernel versions. (again: running this on open-suse leap 15.1 on version 30 DOES work)
>> Running ubuntu, which works for someone ...
>> 2020-06-05 16:19:14.514575 I CardUtil[1]: Set delivery system: DVB-T2
>> 2020-06-05 16:19:14.516633 W DVBSigMon[1](/dev/dvb/adapter0/frontend0): Cannot measure S/N
>> eno: Unknown error 524 (524)
>> 2020-06-05 16:19:14.516656 W DVBSigMon[1](/dev/dvb/adapter0/frontend0): Cannot measure Bit Error Rate
>> eno: Unknown error 524 (524)
>> 2020-06-05 16:19:14.516675 W DVBSigMon[1](/dev/dvb/adapter0/frontend0): Cannot count Uncorrected Blocks
>> eno: Unknown error 524 (524)
>> 2020-06-05 16:19:47.424934 C 'SignalMonitor': MThread prolog was never run!
>> jam@venus:~$ lsusb
>> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>> Bus 001 Device 004: ID 8087:0a2b Intel Corp.
>> Bus 001 Device 006: ID 045e:0750 Microsoft Corp. Wired Keyboard 600
>> Bus 001 Device 005: ID 04b3:310b IBM Corp. Red Wheel Mouse
>> Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
>> Bus 001 Device 002: ID 2040:0265 Hauppauge dualHD
>> James
>
> How about 'dmesg | grep adapter' or 'dmesg | grep firmware' or 'dmesg | grep -i dvb' ?
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On 5 Jun 2020, at 5:56 pm, John Pilkington <johnpilk222@gmail.com> wrote:
>
> How about 'dmesg | grep adapter' or 'dmesg | grep firmware' or 'dmesg | grep -i dvb' ?

Triumphntly I did that, then choked on results.
I must assume that with no-firmware nothing was logged.
Sorry for being an idiot
James

jam@venus:~$ dmesg |grep adapter
[ 6.896489] dvbdev: DVB: registering new adapter (1-2:1.0)
[ 6.896492] em28xx 1-2:1.0: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)...
[ 6.907562] dvbdev: DVB: registering new adapter (1-2:1.0)
[ 6.907566] em28xx 1-2:1.0: DVB: registering adapter 1 frontend 0 (Silicon Labs Si2168)...

jam@venus:~$ dmesg |grep firmware
[ 0.119090] Spectre V2 : Enabling Restricted Speculation for firmware calls
[ 3.769394] iwlwifi 0000:01:00.0: loaded firmware version 36.77d01142.0 op_mode iwlmvm
[ 3.843877] iwlwifi 0000:01:00.0: Allocated 0x00400000 bytes for firmware monitor.
[ 3.891291] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
[ 6.892368] si2168 7-0064: firmware version: B 4.0.2
[ 6.905480] si2168 11-0067: firmware version: B 4.0.2
[ 5307.010799] si2168 7-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
[ 5307.242697] si2168 7-0064: firmware version: B 4.0.11
[ 5307.295137] si2157 12-0060: firmware version: 3.0.5
[ 7505.270651] si2168 11-0067: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
[ 7505.488074] si2168 11-0067: firmware version: B 4.0.11
[ 7505.540194] si2157 13-0063: firmware version: 3.0.5

jam@venus:~$ dmesg | grep -i dvb
[ 3.898789] em28xx 1-2:1.0: DVB interface 0 found: isoc
[ 5.276656] em28xx 1-2:1.0: Identified as Hauppauge WinTV-dualHD DVB (card=99)
[ 5.305434] tveeprom: TV standards PAL(B/G) NTSC(M) PAL(I) SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xfc)
[ 5.305440] em28xx 1-2:1.0: dvb set to isoc mode.
[ 6.672782] em28xx 1-2:1.0: Identified as Hauppauge WinTV-dualHD DVB (card=99)
[ 6.674504] tveeprom: TV standards PAL(B/G) NTSC(M) PAL(I) SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xfc)
[ 6.674508] em28xx 1-2:1.0: dvb ts2 set to isoc mode.
[ 6.885649] em28xx 1-2:1.0: Binding DVB extension
[ 6.896489] dvbdev: DVB: registering new adapter (1-2:1.0)
[ 6.896492] em28xx 1-2:1.0: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)...
[ 6.896495] dvbdev: dvb_create_media_entity: media entity 'Silicon Labs Si2168' registered.
[ 6.897031] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
[ 6.898682] em28xx 1-2:1.0: DVB extension successfully initialized
[ 6.898685] em28xx 1-2:1.0: Binding DVB extension
[ 6.907562] dvbdev: DVB: registering new adapter (1-2:1.0)
[ 6.907566] em28xx 1-2:1.0: DVB: registering adapter 1 frontend 0 (Silicon Labs Si2168)...
[ 6.907569] dvbdev: dvb_create_media_entity: media entity 'Silicon Labs Si2168' registered.
[ 6.907897] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
[ 6.910842] em28xx 1-2:1.0: DVB extension successfully initialized
[ 6.910845] em28xx: Registered (Em28xx dvb Extension) extension
[ 6.949051] rc rc0: Hauppauge WinTV-dualHD DVB as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/rc/rc0
[ 6.949208] input: Hauppauge WinTV-dualHD DVB as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/rc/rc0/input12
[ 5307.010799] si2168 7-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
[ 7505.270651] si2168 11-0067: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
jam@venus:~$
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org