[mythtv-users] haupauge

Stephen Worthington stephen_agent at jsw.gen.nz
Wed Jun 3 08:30:34 UTC 2020

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
>[   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:


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.

More information about the mythtv-users mailing list