[mythtv-users] DVB-S2 scan fails (0.29)

Sat Dec 23 21:56:59 UTC 2017

On 23 December 2017 at 15:09, Stephen Worthington <stephen_agent at jsw.gen.nz>
wrote:

>
> That sounds like you may need to increase the tuning timeouts.  But
> take a look in your logs to see what is actually happening.  You may
> want to run mythtv-setup.real with the extra logging option "-v
> chanscan" for more detail.
>

Good suggestion, thanks. Here is the output of
 mythtv-setup.real -v chanscan --loglevel debug --logpath /tmp
just after re-entering the freesat HD parameters and asking it to scan:

2017-12-23 21:45:52.361357 I [3624/3624] CoreContext scanwizard.cpp:70
(Scan) - SWiz: Scan(): type(10) cardid(1) inputname(DVBInput)
2017-12-23 21:45:54.872105 E [3624/3624] CoreContext diseqc.cpp:838
(SetVoltage) - DiSEqCDevTree: FE_SET_VOLTAGE failed
            eno: No such file or directory (2)
2017-12-23 21:46:02.351881 E [3624/3624] CoreContext diseqc.cpp:676
(send_diseqc) - DiSEqCDevTree: send_diseqc FE_DISEQC_SEND_MASTER_CMD failed
            eno: Connection timed out (110)
2017-12-23 21:46:02.351899 E [3624/3624] CoreContext diseqc.cpp:740
(SendCommand) - DiSEqCDevTree: DiSEqC command failed
            eno: Connection timed out (110)
2017-12-23 21:46:02.351909 E [3624/3624] CoreContext diseqc.cpp:787
(ResetDiseqc) - DiSEqCDevTree: DiSEqC reset failed
            eno: Connection timed out (110)
2017-12-23 21:46:02.354792 W [3624/3624] CoreContext
recorders/dvbsignalmonitor.cpp:91 (DVBSignalMonitor) -
DVBSigMon[-1](/dev/dvb/adapter0/frontend0): Cannot measure Signal Strength
            eno: No such file or directory (2)
2017-12-23 21:46:02.357351 I [3624/3624] CoreContext
channelscan/channelscan_sm.cpp:180 (ChannelScanSM) -
ChannelScanSM(/dev/dvb/adapter0/frontend0): Connecting up DTVSignalMonitor
2017-12-23 21:46:02.358815 I [3624/3624] CoreContext
channelscan/channelscan_sm.cpp:198 (ChannelScanSM) -
ChannelScanSM(/dev/dvb/adapter0/frontend0): Setting NIT-ID to 4294967295
2017-12-23 21:46:02.375781 I [3624/3624] CoreContext
channelscan/channelscanner.cpp:134 (Scan) - ChScan: Scan()
2017-12-23 21:46:02.375840 I [3624/3624] CoreContext
channelscan/channelscanner.cpp:176 (Scan) - ChScan: ScanTransports()
2017-12-23 21:46:02.375967 I [3624/3755] Scanner
channelscan/channelscan_sm.cpp:1532 (run) -
ChannelScanSM(/dev/dvb/adapter0/frontend0): run -- begin
2017-12-23 21:46:02.376000 I [3624/3755] Scanner
channelscan/channelscan_sm.cpp:1766 (ScanTransport) -
ChannelScanSM(/dev/dvb/adapter0/frontend0): ScanTransport Tuning to
Frequency 10847000 mplexid(0)
2017-12-23 21:46:02.376145 D [3624/3755] Scanner portchecker.cpp:84
(checkPort) - PortChecker::checkPort(): host localhost port 3306 timeLimit
30000 linkLocalOnly 1
2017-12-23 21:46:02.377509 E [3624/3755] Scanner diseqc.cpp:529 (Execute) -
DiSEqCDevTree: No root device tree node!
2017-12-23 21:46:02.377520 E [3624/3755] Scanner
recorders/dvbchannel.cpp:734 (Tune) -
DVBChan[1](/dev/dvb/adapter0/frontend0): Tune(): Failed to setup DiSEqC
devices
2017-12-23 21:46:02.377537 E [3624/3755] Scanner
channelscan/channelscan_sm.cpp:1774 (ScanTransport) -
ChannelScanSM(/dev/dvb/adapter0/frontend0): Failed to tune Frequency
10847000 mplexid(0) at offset 0
2017-12-23 21:46:02.415303 I [3624/3624] CoreContext
channelscan/channelscan_sm.cpp:1798 (StopScanner) -
ChannelScanSM(/dev/dvb/adapter0/frontend0): StopScanner
2017-12-23 21:46:02.417864 I [3624/3755] Scanner
channelscan/channelscan_sm.cpp:1542 (run) -
ChannelScanSM(/dev/dvb/adapter0/frontend0): run -- end
2017-12-23 21:46:02.418094 I [3624/3624] CoreContext
channelscan/channelscan_sm.cpp:1798 (StopScanner) -
ChannelScanSM(/dev/dvb/adapter0/frontend0): StopScanner
2017-12-23 21:46:02.418105 I [3624/3624] CoreContext
channelscan/channelscan_sm.cpp:223 (~ChannelScanSM) -
ChannelScanSM(/dev/dvb/adapter0/frontend0): ChannelScanSM Stopped
2017-12-23 21:46:02.419544 I [3624/3624] CoreContext
channelscan/channelimporter.cpp:45 (Process) - ChanImport: No channels to
process..

A majority of this is incomprehensible to me but I can spot "no such file
of directory" (OK mythsetup, WHICH file please?)

Also, all of these diseq commands fail, and further down there' s a mention
of
DiSEqCDevTree: No root device tree node!

All this is somewhat at odds with having recently recreated the capture
card.

It would be useful to have a way to check if the card hardware and drivers
work that was independent from myth.
At the moment all I can say is that the cards show up in dmesg, which is a
step up from when they don't but I guess is still some way away from saying
that they are actually working:

$ dmesg | fgrep frontend
[    5.096451] cx23885: cx23885_dvb_register() allocating 1 frontend(s)
[    5.098506] i2c i2c-1: cx24117: Attaching frontend 0
[    5.098510] cx23885 0000:04:00.0: DVB: registering adapter 0 frontend 0
(Conexant CX24117/CX24132)...
[    5.098768] cx23885: cx23885_dvb_register() allocating 1 frontend(s)
[    5.098772] i2c i2c-1: cx24117: Attaching frontend 1
[    5.098774] cx23885 0000:04:00.0: DVB: registering adapter 1 frontend 0
(Conexant CX24117/CX24132)...

Further clues welcome, especially if you can read more into this log than I
can, or if you can guess which file or directory it's telling me is missing.

> Are you running v29, or v29+fixes?  If you are just running v29 from
> the main repositories, it would be a good idea to add in the ppa and
> get the latest fixes version.
>

That's what I had already done. The main repositories for 16.04 only seem
to have 0.28, so I installed the ppa with
  sudo add-apt-repository ppa:mythbuntu/0.29

The following shows it' s with fixes:

apt-cache policy mythtv
mythtv:
  Installed: 2:29.0+fixes.20171223.68e982e-0ubuntu0mythbuntu4
  Candidate: 2:29.0+fixes.20171223.68e982e-0ubuntu0mythbuntu4
  Version table:
[etc]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20171223/18dea6bc/attachment.html>