channelscanner can not added the found channels

[lars.schmohl@…]

I am trying to use the new MythTV 0.25 for a new htpc.

I have installed mythbuntu 12.04, so far everything is running.

When I am scanning for channels, they are found but not insert in the table after the scan.

log file with the error messages are attached

myth

[lars.schmohl@…]

mythtv setup channel scan

[dekarl@…]

Lets see... Google hints that you might be in Switzerland.

Apr  6 11:28:15 HTPC-core mythtv-setup[11341]: E Scanner dvbchannel.cpp:797 (Tune) DVBChan(1:/dev/dvb/adapter0/frontend0): Tune(): Setting Frontend tuning parameters failed.#012#011#011#011eno: Invalid argument (22)
Apr  6 11:28:15  mythtv-setup[11341]: last message repeated 73 times

looks like your DVB card is unable to automatically guess one of the parameters and you have to manually scan one transport and learn the others from the network_information_section (NIT).

Looking further it appears that you might be on DVB-C with CableCom? and got a welcome letter with a network_id in it. The manual network_id setting is not yet hooked up to the GUI, see #7486, which enables MythTV to find the correct NIT and realize that your signal follows the DVB SI standard.

Apr  6 13:05:13 HTPC-core mythtv-setup[12526]: E CoreContext mythdbcon.cpp:648 (exec) Original query failed, but resend with empty strings in place of NULL strings worked. #012DB Error (MSqlQuery):#012Query was:#012INSERT INTO channelscan_dtv_multiplex  (  scanid,     mplexid,            frequency,       inversion,      symbolrate,         fec,             polarity,       hp_code_rate,       lp_code_rate,    modulation,     transmission_mode,  guard_interval,  hierarchy,      mod_sys,            rolloff,                         bandwidth,          sistandard,      tuner_type   ) VALUES  ( ?,    ?,           ?,      ?,     ?,        ?,            ?,      ?,      ?,   ?,    ?, ?, ?,     ?,           ?,                        ?,         ?,     ?   );#012Bindings were:#012:BANDWIDTH="a", :FEC="none", :FREQUENCY="538000000", :GUARD_INTERVAL="auto",#012:HIERARCHY="a", :HP_CODE_RATE="auto", :INVERSION="a", :LP_CODE_RATE="auto",#012:MODULATION="qam_64", :MOD_SYS="UNDEFINED", :MPLEXID=0, :POLARITY="v",#012:ROLLOFF="0.35", :SCANID=1, :SISTANDARD=NULL, :SYMBOLRATE="6900000",#012:TRANSMISSION_MODE="a", :TUNER_TYPE=1#012Driver error was [2/1048]:#012QMYSQL3: Unable to execute statement#012Database error was:#012Column 'sistandard' cannot be null

Ohh, and the channel.conf parser is known broken at the moment, see #7701

Apr  6 12:51:58 HTPC-core mythtv-setup[12448]: I CoreContext dtvconfparser.cpp:317 (AddChannel) Imported channel:  10001 -1  on 538000000 qam_64 a auto auto a a auto a v fec: none msys: UNDEFINED rolloff: 0.35

Looking further it appears that CableCom? is only providing CI+ cards, but no CI cards, which do not work with Linux at all. Knowing some details on country/provider would help alot as especially DVB-C providers often need special handling.

[lars.schmohl@…]

I have a local provider, all channels are unencrypted, except for Teleclub (NDS). No transponder has a NIT (except for the Teleclub transponder, which is unusable).

I have got it to work by manually scanning every transponder.

The other thing is that the internal scanner of version 0.24.2 worked correctly and the internal scanner of version 0.25 does not.

[dekarl@…]

So if I understand correctly, the real issue is that the full scan can't tune any channels anymore due to

Tune(): Setting Frontend tuning parameters failed.
eno: Invalid argument (22)

which makes it similar to #8758...

[Jussi Lehtola <jussi.lehtola@…>]

I am experiencing the very same issue on Fedora 17. I can scan for channels and that works properly, but the channels aren't added anywhere.

Running

$ mythtv-setup --loglevel debug

I see that the error is

2012-07-07 19:33:14.154926 E Original query failed, but resend with empty strings in place of NULL strings worked. DB Error (MSqlQuery): Query was: INSERT INTO channelscan_dtv_multiplex ( scanid, mplexid, frequency, inversion, symbolrate, fec, polarity, hp_code_rate, lp_code_rate, modulation, transmission_mode, guard_interval, hierarchy, mod_sys, rolloff, bandwidth, sistandard, tuner_type ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ); Bindings were: :BANDWIDTH="a", :FEC="none", :FREQUENCY="154000000", :GUARD_INTERVAL="auto", :HIERARCHY="a", :HP_CODE_RATE="auto", :INVERSION="a", :LP_CODE_RATE="auto", :MODULATION="qam_128", :MOD_SYS="UNDEFINED", :MPLEXID=0, :POLARITY="v", :ROLLOFF="0.35", :SCANID=2, :SISTANDARD=NULL, :SYMBOLRATE="6900000", :TRANSMISSION_MODE="a", :TUNER_TYPE=1 Driver error was [2/1048]: QMYSQL3: Unable to execute statement Database error was: Column 'sistandard' cannot be null

I have an 8-year old Terratec Cinergy dvb-c card.

[dekarl@…]

Lets see...

Original query failed, but resend with empty strings in place of NULL strings worked.
...
Database error was: Column 'sistandard' cannot be null

While the error only means that somewhere NULL and "" are not properly handled it still hints at an issue, namely that the SDT could not be found, leading to sistandard being NULL instead of the correct "dvb".

Jussi, the OP has posted a version string that indicates his version is newer then [778d8111e]. Can you verify that you have 0.25 newer than March 23rd, too? (output of mythbackend --version)

Also knowing your country/provider would help lots to narrow down the possible issue. (maybe you need #7486)

Googling your name hints at Finland where the patch from #7486 should not be necessary based on specs. Unified Requirements of HDTV DVB-C and DVB-T2 digital receiver for Finnish market, 6.3.1:

When IRD locks to the first transmitting multiplex, the IRD shall read the NIT actual table and install the network and channels accordingly. The IRD should not scan the other remaining frequencies in the network.

The other issue is that the channels are not added after the scan. (even though they are scanned wrong they should still be added IMHO)

I suggest to make a ticket for "channel scan in <country> on DVB-C provider <provider> does not work" or similar so we can track the different networks in separate tickets.