[_Michael_]

Hello,

I try now since a while to get my HTPC running under KodiBuntu and MythTV. I think I'm near to success but the last step seems impossible for me...
1) I use a DVB-C dual tuner card.
2) I have an working EPG (with EIT data) for all of my 32 TV channels.
2.0) I have almost 20 TV channels working (live TV).
2.1) For the remaining 12 channels I only get "channel unavailable".
2.3) During my different tries (means MythTV setups) the not working channels changed.
3.0) I already increased the "signal timeout" for each tuner on backend from 1000 ms to 10000 ms.
3.1) "Tuning delay (sec)" is set to 30 in pvr.mythtv addon.
I have a Kodi.log here
Kodi log (_Michael_)
'RTL' is as good case present and 'ProSieben MAXX' as bad case.
(btw.: "xmbclogs.com" is a dead link in the kodi.wiki)

Any help is appreciated!

Michael

[MikeB2013]

I have looked at the Kodi log file, but it only confirms the Channel Unavailable you are seeing after 30 seconds.

Can you repeat the tests and provide a new Kodi log, with the "Include more debug information in the log" selected in the pvr.mythtv addon Advanced tab. This will give a lot more data on what the mythtvbackend is doing, including the mythbackend version data.

Mike

[_Michael_]

Thank you Mike, I already did this setting but may be I need a reboot to get it working. I will be back soon.

Michael

[_Michael_]

OK, now much more data (too much -> 3 links required):
log 1 of 3
log 2 of 3
log 3 of 3

Michael

[MikeB2013]

From log 1 of 3 your mythbackend version is "v0.27-193-g8ee257c" which was released 23 March 2014 and is far too old, there have been many changes/improvements since then. Current version is 3783dc8 released 26 June 2016, so you need to update and retest, if you still have problems new Kodi log(s) will be required.

Here is how I do it , in a terminal on the mythbackend machine :

sudo add-apt-repository ppa:mythbuntu/0.27
sudo apt-get update
sudo apt-get dist-upgrade
sudo reboot

After this any usual sudo apt-get update followed by sudo apt-get upgrade will always get you the latest version.

The reboot may not be strictly necessary, but I do just to ensure a clean start (I have been caught out in the past where everything worked until a reboot)

Mike

[_Michael_]

I understand (and agree) that I should not use a outdated version BUT why the hell is the KodiBuntu package maintenance app telling that this '2014 MythTV version' is the latest (supported) version?! These are my 1st steps with Linux and I already almost h...e it (sorry):
How can it be that I have to start a manual update with the command line?

Back to my problem: Thanks for the advice, Mike. Pl. ignore my text above, it is not a real question and it makes no sense to discuss this (here).

[_Michael_]

1) It was not solving the issue and now the channel search gets less results :-(.
2) I searched again and now found this post. I tried the mentioned "limit channel tuning attempt = off" and now it works. I have partly huge delays (around 10 seconds) between channel changes and it seems that my system hangs during this time.

Michael

[MikeB2013]

For 1) I am not sure what is meant "...channel search gets less results"?



For 2) The "limit channel tuning attempts = off" only masks the problem, which I now think maybe on the mythbackend. One of your tuners is having problems tuning to certain channels. The pvr.mythtv addon asks the mythbackend for a list of available tuners for the channel you want, which the pvr.mythtv addon then goes through in a specific order, with "limit channel tuning attempts=on" only the first tuner in the specific order is tried. New Kodi log(s) would be useful. Note that attempting to tune to encrypted (copy protected) channels will result in "Channel Unavailable"

From your previous logs channel tuning when it worked was around 2 seconds, so you might want to adjust signal timeout in the mythbackend to 5000. The Tuning Delay in pvr.mythtv addon can be set to default of 5 seconds (the delay is automatically cancelled if tuning works).

Can you provide more details on your DVB-C tuner card ?

Mike

[_Michael_]

It means that I have now less detected TV channels at channel scan.
Encrypted channels: skipped during channel scan -> cannot be the problem
My card is from Digital Devices, model 'Cine C/T (V6)'.
I cannot provide a new log because at the moment I'm busy with different things ... may be this evening.
Thank you.

Michael

[_Michael_]

here is the new log file:
log 1 of 2
log 2 of 2

[MikeB2013]

From the logs channel ProSieben MAXX does not work with recorder 1, but does work with recorder 3. Channel RTL works with recorder 1.

This appears to be a problem with mythbackend, rather than Kodi with pvr.mythtv addon.

Can you from a terminal run the "dmesg" command and copy the output to pastebin, this may give some clues as to what is happening with the linux driver for the Digital Devices, model 'Cine C/T (V6)' card, which unfortunately I don't know anything about.

Can you run mythtv frontend and see if it also has problems ?

Mike

[_Michael_]

"This appears to be a problem with mythbackend" I think you are right: I wrote above that I have now less TV stations found by channel scan. I did it again but this time not in step "6. Channel Editor" but dedicated for each tuner in step "5. Input connections". For tuner two the result was different to tuner one, tuner two found 12 TV stations more! (Could it be that my tuner card goes wrong? It was and is working since 3 years under my Win7 system, therefore I cannot believe that I have a HW issue.)
The real problem is the MythTV backend setup, I think. I found nowhere an installation example for my HW and there are to many setting options present! (see above: Is 5. and 6. required or only one of both?)
You wrote "... recorder 1, ... recorder 3" how is this meant? I have only two tuners (or only one tuner with two DVB-C demodulators???).

output of 'dmesg | grep DVB':
...
[ 4.181577] DDBridge driver detected: Digital Devices DVBCT V6.1 DVB adapter
[ 4.194364] Port 0: Link 0, Link Port 0 (TAB 1): DUAL DVB-C/T
[ 4.198763] DVB: registering new adapter (DDBridge)
[ 4.198764] DVB: registering new adapter (DDBridge)
[ 4.772807] ddbridge 0000:01:00.0: DVB: registering adapter 0 frontend 0 (STV0367 DVB-C DVB-T)...
[ 5.310250] ddbridge 0000:01:00.0: DVB: registering adapter 1 frontend 0 (STV0367 DVB-C DVB-T)...
[ 7.710609] ddbridge 0000:01:00.0: DVB: adapter 1 frontend 0 frequency 0 out of range (47125000..865000000)
[ 7.717597] ddbridge 0000:01:00.0: DVB: adapter 0 frontend 0 frequency 0 out of range (47125000..865000000)

addendum for dmesg:
[ 4.687062] Installing knfsd (copyright © 1996 [email protected]).
[ 4.849271] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 4.874820] mei_me 0000:00:16.0: irq 47 for MSI/MSI-X
[ 4.917912] dvb_core: module verification failed: signature and/or required key missing - tainting kernel
[ 4.931111] ACPI Warning: 0x0000000000001828-0x000000000000182f SystemIO conflicts with Region \PMIO 1 (20131115/utaddress-251)
[ 4.931117] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 4.931120] ACPI Warning: 0x0000000000001c30-0x0000000000001c3f SystemIO conflicts with Region \GPRL 1 (20131115/utaddress-251)
[ 4.931122] ACPI Warning: 0x0000000000001c30-0x0000000000001c3f SystemIO conflicts with Region \GPR_ 2 (20131115/utaddress-251)
[ 4.931124] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 4.931125] ACPI Warning: 0x0000000000001c00-0x0000000000001c2f SystemIO conflicts with Region \GPRL 1 (20131115/utaddress-251)
[ 4.931126] ACPI Warning: 0x0000000000001c00-0x0000000000001c2f SystemIO conflicts with Region \GPR_ 2 (20131115/utaddress-251)
[ 4.931128] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 4.931129] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 4.950266] Digital Devices PCIE bridge driver 0.9.22, Copyright © 2010-15 Digital Devices GmbH
[ 4.950410] DDBridge driver detected: Digital Devices DVBCT V6.1 DVB adapter
[ 4.950431] DDBridge: HW 0001000c REGMAP 00010004
[ 4.950456] ddbridge 0000:01:00.0: irq 48 for MSI/MSI-X
[ 4.955751] Port 0: Link 0, Link Port 0 (TAB 1): DUAL DVB-C/T
[ 4.956719] Port 1: Link 0, Link Port 1 (TAB 2): NO MODULE
[ 4.957745] Port 2: Link 0, Link Port 2 (TAB 3): NO MODULE
[ 4.957887] 0 netstream channels
[ 4.957889] DVB: registering new adapter (DDBridge)
[ 4.957890] DVB: registering new adapter (DDBridge)
[ 5.002300] stv0367 found
...
Here is "dvb_core: module verification failed: ..." and "Resource conflict(s)" listed, should I care on these issues? If yes: How? Thanks a lot.

Michael

[MikeB2013]

It is unlikely that your card is faulty.

Sorry my error in recorder 1 and 3, these are the internal numbers in mythtvbackend, from a tuner point of view it is just the first or second tuner.

The only thing I have seen about your tuner card is that frontend0 is to be configured if using DVB-T, frontend1 for DVB-C.

Your best option is to ask on mythtv forum (Troubleshooting) at https://forum.mythtv.org/index.php


Mike

[_Michael_]

Thanks, Mike.
1) Your post was in parallel to my update of Post #12, may be you can also say something to my extended dmseg info.
2) Where have you seen that "frontend0 is to be configured if using DVB-T"?

Michael

[MikeB2013]

Whoops, Got the frontends wrong way round see http://palatum.org/2013/01/digital-devic...-cablecom/

"dvb_core: module verification failed: ..." and "Resource conflict(s)" listed, These are very common and can be ignored.


Mike