[SOLVED]Help please with drivers for TBS6981 DVB-S2 on Ubuntu

Have a MythTV related problem? Ask for help from other MythTV users here.

Moderator: Forum Moderators

georgep56
Newcomer
Posts: 10
Joined: Thu May 10, 2018 2:33 pm
Great Britain

[SOLVED]Help please with drivers for TBS6981 DVB-S2 on Ubuntu

Post by georgep56 »

I'm building a new system to replace my ageing 0.27-fixes on Ubuntu 12.04 system which has been (and is still) giving great service but is getting a little tired and unreliable

I've put together my new 0.29-fixes system using Lubuntu 16.04 (tried later versions but niggles over versions of (eg) php led me to go back to a solid version.

Previously I have used Tevii PCI-e and USB S660 tuners (DVB-S2), and I have tried the S660 USB tuner on my new box and everything is fine.These tuners are no longer available and so I've picked up a dual tuner PCI-e TBS6981 on ebay for a good price.

First of all I just "plugged it in and turned it on" and MythTV straight away found 2x Conexant cx23885 tuners so I thought things were all going OK, but soon the logs started filling up with diseqc and tuning errors (I only have simple LNBs). A bit of searching revealed that I needed to build some drivers for this card so I downloaded driver code from github-dot-com/tbsdtv/linux_media following instructions at tbsdtv-dot-com/forum/viewtopic.php?f=86&t=9960

These drivers built and installed OK and MythTV then found 2x "TurboSight TBS6981" tuners. This time no strings of errors in the logs but trying to tune / record any stations results in signal timeouts and recording failures.

I've also tried driver code from the "official" TBS site but these seem very old and fail to build with my 4.13.0-41 kernel.

Here are a couple of snippets from my dmesg output:

Code: Select all

george@tvbox:~$ dmesg | grep dvb
[    4.648951] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
[    4.652743] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
[    4.763946] dvb-usb: found a 'TeVii S660 USB' in warm state.
[    4.764023] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[    4.764106] dvbdev: DVB: registering new adapter (TeVii S660 USB)
[    4.851016] dvb-usb: MAC address: 00:18:bd:5b:61:cb
[    4.944518] dvb-usb: schedule remote query interval to 150 msecs.
[    4.944520] dvb-usb: TeVii S660 USB successfully initialized and connected.
[    6.431531] cx23885: cx23885_dvb_register() allocating 1 frontend(s)
[    6.431532] cx23885: cx23885[0]: cx23885 based dvb card
[    6.445759] dvbdev: DVB: registering new adapter (cx23885[0])
[    6.445947] cx23885: cx23885_dvb_register() allocating 1 frontend(s)
[    6.445948] cx23885: cx23885[0]: cx23885 based dvb card
[    6.445953] dvbdev: DVB: registering new adapter (cx23885[0])

Code: Select all

george@tvbox:~$ dmesg | grep front
[    4.917580] usb 3-10: DVB: registering adapter 0 frontend 0 (Montage Technology DS3000)...
[    6.431531] cx23885: cx23885_dvb_register() allocating 1 frontend(s)
[    6.445757] i2c i2c-8: cx24117: Attaching frontend 0
[    6.445761] cx23885 0000:01:00.0: DVB: registering adapter 1 frontend 0 (TurboSight TBS 6981 DVB-S/S2)...
[    6.445947] cx23885: cx23885_dvb_register() allocating 1 frontend(s)
[    6.445952] i2c i2c-8: cx24117: Attaching frontend 1
[    6.445954] cx23885 0000:01:00.0: DVB: registering adapter 2 frontend 0 (TurboSight TBS 6981 DVB-S/S2)...
[  367.105634] cx23885 0000:01:00.0: DVB: adapter 1 frontend 0 frequency limits undefined - fix the driver
[  367.105670] cx23885 0000:01:00.0: DVB: adapter 1 frontend 0 frequency limits undefined - fix the driver
[  635.633616] cx23885 0000:01:00.0: DVB: adapter 1 frontend 0 frequency limits undefined - fix the driver
[  635.633674] cx23885 0000:01:00.0: DVB: adapter 1 frontend 0 frequency limits undefined - fix the driver
[  635.697543] cx23885 0000:01:00.0: DVB: adapter 1 frontend 0 frequency limits undefined - fix the driver
george@tvbox:~$



Can anyone suggest the best drivers and firmware to use with this card on Ubuntu 16.04?

Thanks in anticipation.
George
(Somerset, UK)
Last edited by georgep56 on Sun May 13, 2018 9:49 am, edited 1 time in total.
MikeB2013
Senior
Posts: 519
Joined: Mon Jul 25, 2016 4:16 pm
Great Britain

Re: Help please with drivers for TBS6981 DVB-S2 on Ubuntu

Post by MikeB2013 »

"cx23885 0000:01:00.0: DVB: adapter 1 frontend 0 frequency limits undefined - fix the driver" indicates problem with the build of the drivers.

The drivers (https://github.com/tbsdtv/linux_media) should be built using instructions at https://github.com/tbsdtv/linux_media/wiki (the tbs forum post is out of date).

Also for TBS 6981 you need firmware from https://github.com/tbsdtv/linux_media/w ... 7-firmware this is linked from More Info near bottom of page at https://github.com/tbsdtv/linux_media/wiki
georgep56
Newcomer
Posts: 10
Joined: Thu May 10, 2018 2:33 pm
Great Britain

Re: Help please with drivers for TBS6981 DVB-S2 on Ubuntu

Post by georgep56 »

Thanks Mike.
There is indeed a difference in the instructions you linked and those I followed initially.
I'm about to build and reinstall drivers and firmware from your links.
I'll post again with the outcome.
George
georgep56
Newcomer
Posts: 10
Joined: Thu May 10, 2018 2:33 pm
Great Britain

Re: Help please with drivers for TBS6981 DVB-S2 on Ubuntu

Post by georgep56 »

OK- I just rebuilt the driver and reinstalled the firmware and the result is slightly different - but still not good!

((NOTE)) it seems I can't post URLs so I'm having to use -dot-com type notation as a work around :-)

First of all I got a similar boot-time output from dmesg:

Code: Select all

george@tvbox:~$ dmesg | grep front
[    5.341968] usb 3-10: DVB: registering adapter 0 frontend 0 (Montage Technology DS3000)...
[    6.936818] cx23885: cx23885_dvb_register() allocating 1 frontend(s)
[    6.991786] i2c i2c-8: cx24117: Attaching frontend 0
[    6.991791] cx23885 0000:01:00.0: DVB: registering adapter 1 frontend 0 (TurboSight TBS 6981 DVB-S/S2)...
[    6.991986] cx23885: cx23885_dvb_register() allocating 1 frontend(s)
[    6.991991] i2c i2c-8: cx24117: Attaching frontend 1
[    6.991993] cx23885 0000:01:00.0: DVB: registering adapter 2 frontend 0 (TurboSight TBS 6981 DVB-S/S2)...
[  442.575775] cx23885 0000:01:00.0: DVB: adapter 1 frontend 0 frequency limits undefined - fix the driver
This time I tried running w_scan - firstly on my [good] Tevii S660 USB tuner:

Code: Select all

george@tvbox:~$ w_scan -f s -c GB -a 0 -s S28E2
w_scan -f s -c GB -a 0 -s S28E2 
w_scan version 20141122 (compiled for DVB API 5.10)
using settings for 28.2 east Astra 2A/B/C/D + EuroBird 1 28.5
scan type SATELLITE, channellist 61
output format vdr-2.0
WARNING: could not guess your codepage. Falling back to 'UTF-8'
output charset 'UTF-8', use -C <charset> to override
-_-_-_-_ Getting frontend capabilities-_-_-_-_ 
Using DVB API 5.11
frontend 'Montage Technology DS3000' supports
INVERSION_AUTO
DVB-S
DVB-S2
FREQ (0.95GHz ... 2.15GHz)
SRATE (1.000MSym/s ... 45.000MSym/s)
using LNB "UNIVERSAL"
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ 
trying 'S  f = 10714 kHz H SR = 22000  5/6 0,35  QPSK  (0:0:0)'
(time: 00:00.439)         signal ok:	S  f = 10714 kHz H SR = 22000  5/6 0,35  QPSK  (0:0:0)
        S  f = 10714 kHz H SR = 22000  5/6 0,35  QPSK  (0:0:0) : updating transport_stream_id: -> (0:0:2041)
        S  f = 10714 kHz H SR = 22000  5/6 0,35  QPSK  (0:0:2041) : updating network_id -> (0:32:2041)
        S  f = 10714 kHz H SR = 22000  5/6 0,35  QPSK  (0:32:2041) : updating original_network_id -> (2:32:2041)
        new transponder: (S  f = 10964 kHz H SR = 22000  5/6 0,35  QPSK  (2:32:2057)) 0x4043
        new transponder: (S  f = 10994 kHz H SR = 22000  5/6 0,35  QPSK  (2:32:2059)) 0x4043
All looking good OK there - but I know that this tuner is fine.

Now the first tuner on the TBS card:

Code: Select all

george@tvbox:~$ w_scan -f s -c GB -a 1 -s S28E2
w_scan -f s -c GB -a 1 -s S28E2 
w_scan version 20141122 (compiled for DVB API 5.10)
using settings for 28.2 east Astra 2A/B/C/D + EuroBird 1 28.5
scan type SATELLITE, channellist 61
output format vdr-2.0
WARNING: could not guess your codepage. Falling back to 'UTF-8'
output charset 'UTF-8', use -C <charset> to override
-_-_-_-_ Getting frontend capabilities-_-_-_-_ 
Using DVB API 5.11
frontend 'TurboSight TBS 6981 DVB-S/S2' supports
INVERSION_AUTO
DVB-S
DVB-S2
This dvb driver is *buggy*: the frequency limits are undefined - please report to linuxtv-dot-org
This dvb driver is *buggy*: the symbol rate limits are undefined - please report to linuxtv-dot-org
using LNB "UNIVERSAL"
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ 
trying 'S  f = 10714 kHz H SR = 22000  5/6 0,35  QPSK  (0:0:0)'
(time: 00:05.743) set_frontend:2133: ERROR: Setting frontend parameters failed
: 22 Invalid argument

initial_tune:2710: Setting frontend failed S  f = 10714 kHz H SR = 22000  5/6 0,35  QPSK  (0:0:0)
trying 'S  f = 10729 kHz V SR = 22000  5/6 0,35  QPSK  (0:0:0)'
(time: 00:06.887) set_frontend:2133: ERROR: Setting frontend parameters failed
: 22 Invalid argument

initial_tune:2710: Setting frontend failed S  f = 10729 kHz V SR = 22000  5/6 0,35  QPSK  (0:0:0)
trying 'S  f = 10744 kHz H SR = 22000  5/6 0,35  QPSK  (0:0:0)'
(time: 00:08.035) set_frontend:2133: ERROR: Setting frontend parameters failed
: 22 Invalid argument
I realised there was no LNB plugged in to that card so I swapped the cable from the Tevii USB tuner to the internal card and tried again, but this time on the other tuner:

Code: Select all

george@tvbox:~$ w_scan -f s -c GB -a 2 -s S28E2
w_scan -f s -c GB -a 2 -s S28E2 
w_scan version 20141122 (compiled for DVB API 5.10)
using settings for 28.2 east Astra 2A/B/C/D + EuroBird 1 28.5
scan type SATELLITE, channellist 61
output format vdr-2.0
WARNING: could not guess your codepage. Falling back to 'UTF-8'
output charset 'UTF-8', use -C <charset> to override
-_-_-_-_ Getting frontend capabilities-_-_-_-_ 
Using DVB API 5.11
frontend 'TurboSight TBS 6981 DVB-S/S2' supports
INVERSION_AUTO
DVB-S
DVB-S2
FREQ (0.95GHz ... 2.15GHz)
SRATE (1.000MSym/s ... 45.000MSym/s)
using LNB "UNIVERSAL"
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ 
trying 'S  f = 10714 kHz H SR = 22000  5/6 0,35  QPSK  (0:0:0)'
(time: 00:00.035)         signal ok:	S  f = 10714 kHz H SR = 22000  5/6 0,35  QPSK  (0:0:0)
        Info: no data from PAT after 2 seconds
^C^C^C^C^C
This time I get frequency range and symbol rates reported and a "signal OK" back from the tuner but then the driver crashes and hangs the w_scan session completely - I can't even kill it with "sudo kill -9" .

Meantime the syslog reports this...

Code: Select all

May 11 16:54:01 tvbox kernel: [  608.493582] cx23885 0000:01:00.0: DVB: adapter 1 frontend 0 frequency limits undefined - fix the driver
May 11 16:54:14 tvbox kernel: [  622.300395] BUG: unable to handle kernel paging request at ffff99b083b06000
May 11 16:54:14 tvbox kernel: [  622.300515] IP: dvb_dmx_swfilter+0xe4/0x1a0 [dvb_core]
May 11 16:54:14 tvbox kernel: [  622.300569] PGD 11b936067 
May 11 16:54:14 tvbox kernel: [  622.300570] P4D 11b936067 
May 11 16:54:14 tvbox kernel: [  622.300601] PUD 11b937067 
May 11 16:54:14 tvbox kernel: [  622.300631] PMD 834a3067 
May 11 16:54:14 tvbox kernel: [  622.300660] PTE 0
May 11 16:54:14 tvbox kernel: [  622.300688] 
May 11 16:54:14 tvbox kernel: [  622.302372] Oops: 0000 [#1] SMP PTI
The full kernel backtrace is at https://pastebin.com/tymxdS1C

So to my eye this suggests that the driver is crashing - but only when it receives a signal from the tuner??

At this point I really feel like putting the TBS card back onto ebay and getting something that I can get to work with a little less effort !!!
Any suggestions?
Last edited by Steve Goodey on Sun May 13, 2018 9:16 am, edited 1 time in total.
Reason: URL corrected.
MikeB2013
Senior
Posts: 519
Joined: Mon Jul 25, 2016 4:16 pm
Great Britain

Re: Help please with drivers for TBS6981 DVB-S2 on Ubuntu

Post by MikeB2013 »

I use the tbsdtv drivers all the time ( as the old tbs closed source drivers only work on kernels upto 4.10). Your Lubuntu 16.04 should have a 4.13 series kernel

It is possible that your previous install of the drivers has left some files which are causing problems with the drivers.
There is some trouble shooting info in the FAQ section https://github.com/tbsdtv/linux_media/wiki

Specifically 5 which states

"If you find module load errors like "module has wrong symbol version", this means that there still are old modules from your previous Media Tree installation (usually duplicated modules in two different places).

sudo rm -rf /lib/modules/``uname -r``/kernel/drivers/media/*"

Of course it forgets to tell you how to find the symbol conflicts ("dmesg |grep -i sym" should do it)

So in a terminal session run (I always do this anyway just in case)
sudo rm -rf /lib/modules/``uname -r``/kernel/drivers/media/*

followed by
in media_build directory of wherever you put the tbsdtv drivers
sudo make install
now you must reboot the machine
sudo reboot

There is also a possibility that the driver source code tree in media_build needs to be cleaned (gets rid of any remnants from previous builds), so
cd media_build
make distclean
make dir DIR=../media
make allyesconfig
make -j4
sudo rm -rf /lib/modules/``uname -r``/kernel/drivers/media/*
sudo make install
sudo reboot

Here is a sample output from my tbs 6981 (it is adapter 4 on my setup) from w_scan. Note I interrupted the scan - it takes a very long time to complete!

Code: Select all

mike@myth-server-1:~$ w_scan -f s -c GB -a 4 -s S28E2
w_scan -f s -c GB -a 4 -s S28E2 
w_scan version 20170107 (compiled for DVB API 5.10)
using settings for 28.2 east Astra 2E/F + Eutelsat 28A
scan type SATELLITE, channellist 62
output format vdr-2.0
WARNING: could not guess your codepage. Falling back to 'UTF-8'
output charset 'UTF-8', use -C <charset> to override
-_-_-_-_ Getting frontend capabilities-_-_-_-_ 
Using DVB API 5.11
frontend 'TurboSight TBS 6981 DVB-S/S2' supports
INVERSION_AUTO
DVB-S
DVB-S2
FREQ (0.95GHz ... 2.15GHz)
SRATE (1.000MSym/s ... 45.000MSym/s)
using LNB "UNIVERSAL"
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ 
trying 'S  f = 10714 kHz H SR = 22000  5/6 0,35  QPSK  (0:0:0)'
(time: 00:00.035)         signal ok:	S  f = 10714 kHz H SR = 22000  5/6 0,35  QPSK  (0:0:0)
        S  f = 10714 kHz H SR = 22000  5/6 0,35  QPSK  (0:0:0) : updating network_id -> (0:32:0)
        already known: (S  f = 10714 kHz H SR = 22000  5/6 0,35  QPSK  (0:32:0)), but not found by pids
        S  f = 10714 kHz H SR = 22000  5/6 0,35  QPSK  (0:32:0) : updating tp ids -> (2:32:2041)
        new transponder: (S  f = 10964 kHz H SR = 22000  5/6 0,35  QPSK  (2:32:2057)) 0x4043
        new transponder: (S  f = 10994 kHz H SR = 22000  5/6 0,35  QPSK  (2:32:2059)) 0x4043
        new transponder: (S2 f = 10832 kHz H SR = 23000  3/4 0,25  8PSK  (2:32:2049)) 0x4043
        new transponder: (S  f = 10891 kHz H SR = 22000  5/6 0,35  QPSK  (2:32:2053)) 0x4043
        new transponder: (S  f = 10906 kHz V SR = 22000  5/6 0,35  QPSK  (2:32:2054)) 0x4043
        new transponder: (S  f = 10759 kHz V SR = 22000  5/6 0,35  QPSK  (2:32:2044)) 0x4043
        new transponder: (S  f = 12304 kHz H SR = 27500  5/6 0,35  QPSK  (2:32:2031)) 0x4043
        new transponder: (S  f = 11568 kHz V SR = 22000  5/6 0,35  QPSK  (2:32:2096)) 0x4043
        new transponder: (S  f = 11343 kHz V SR = 27500  5/6 0,35  QPSK  (2:32:2112)) 0x4043
        new transponder: (S2 f = 11612 kHz H SR = 23000  2/3 0,25  8PSK  (2:32:2099)) 0x4043
        new transponder: (S  f = 11671 kHz H SR = 22000  5/6 0,35  QPSK  (2:32:2103)) 0x4043
        new transponder: (S  f = 11523 kHz H SR = 22000  5/6 0,35  QPSK  (2:32:2093)) 0x4043
        new transponder: (S  f = 11224 kHz H SR = 27500  2/3 0,35  QPSK  (2:32:2105)) 0x4043
        new transponder: (S  f = 10729 kHz V SR = 22000  5/6 0,35  QPSK  (2:32:2042)) 0x4043
        new transponder: (S  f = 11597 kHz V SR = 22000  5/6 0,35  QPSK  (2:32:2098)) 0x4043
        new transponder: (S  f = 11582 kHz H SR = 22000  5/6 0,35  QPSK  (2:32:2097)) 0x4043
        new transponder: (S  f = 11307 kHz H SR = 27500  5/6 0,35  QPSK  (2:32:2109)) 0x4043
        new transponder: (S  f = 11307 kHz V SR = 27500  5/6 0,35  QPSK  (2:32:2110)) 0x4043
        new transponder: (S2 f = 11387 kHz H SR = 29500  8/9 0,35  QPSK  (2:32:2113)) 0x4043
        new transponder: (S  f = 11038 kHz V SR = 22000  5/6 0,35  QPSK  (2:32:2062)) 0x4043
        new transponder: (S2 f = 11097 kHz V SR = 23000  3/4 0,25  8PSK  (2:32:2066)) 0x4043
        new transponder: (S2 f = 11068 kHz V SR = 23000  3/4 0,25  8PSK  (2:32:2064)) 0x4043
        Info: no data from NIT(actual )after 11 seconds
10729: skipped (already known transponder)
trying 'S  f = 10744 kHz H SR = 22000  5/6 0,35  QPSK  (0:0:0)'
(time: 00:13.235) 
10758: skipped (already known transponder)
trying 'S  f = 10773 kHz H SR = 22000  5/6 0,35  QPSK  (0:0:0)'
(time: 00:18.907)         signal ok:	S  f = 10773 kHz H SR = 22000  5/6 0,35  QPSK  (0:0:0)
        S  f = 10773 kHz H SR = 22000  5/6 0,35  QPSK  (0:0:0) : updating network_id -> (0:32:0)
        new transponder: (S2 f = 12461 kHz H SR = 29500  8/9 0,35  QPSK  (2:32:2039)) 0x4043
        new transponder: (S2 f = 12344 kHz H SR = 29500  8/9 0,35  QPSK  (2:32:2033)) 0x4043
        new transponder: (S2 f = 12266 kHz H SR = 29500  8/9 0,35  QPSK  (2:32:2029)) 0x4043
        new transponder: (S2 f = 12363 kHz V SR = 29500  8/9 0,35  QPSK  (2:32:2034)) 0x4043
        new transponder: (S2 f = 12012 kHz V SR = 29500  8/9 0,35  QPSK  (2:32:2016)) 0x4043
        new transponder: (S2 f = 12246 kHz V SR = 29500  8/9 0,35  QPSK  (2:32:2028)) 0x4043
        new transponder: (S2 f = 12168 kHz V SR = 29500  8/9 0,35  QPSK  (2:32:2024)) 0x4043
        new transponder: (S2 f = 11856 kHz V SR = 29500  8/9 0,35  QPSK  (2:32:2008)) 0x4043
        new transponder: (S2 f = 11739 kHz V SR = 29500  8/9 0,35  QPSK  (2:32:2002)) 0x4043
        new transponder: (S2 f = 12324 kHz V SR = 29500  8/9 0,35  QPSK  (2:32:2032)) 0x4043
        new transponder: (S2 f = 12090 kHz V SR = 29500  8/9 0,35  QPSK  (2:32:2020)) 0x4043
        new transponder: (S2 f = 12227 kHz H SR = 29500  8/9 0,35  QPSK  (2:32:2027)) 0x4043
        new transponder: (S2 f = 11759 kHz H SR = 29500  8/9 0,35  QPSK  (2:32:2003)) 0x4043
        new transponder: (S  f = 11778 kHz V SR = 27500  2/3 0,35  QPSK  (2:32:2004)) 0x4043
        new transponder: (S  f = 12110 kHz H SR = 27500  5/6 0,35  QPSK  (2:32:2021)) 0x4043
        new transponder: (S  f = 11934 kHz V SR = 27500  5/6 0,35  QPSK  (2:32:2012)) 0x4043
        new transponder: (S  f = 12149 kHz H SR = 27500  5/6 0,35  QPSK  (2:32:2023)) 0x4043
        new transponder: (S  f = 11837 kHz H SR = 27500  5/6 0,35  QPSK  (2:32:2007)) 0x4043
        new transponder: (S  f = 12071 kHz H SR = 27500  5/6 0,35  QPSK  (2:32:2019)) 0x4043
        new transponder: (S  f = 12207 kHz V SR = 27500  5/6 0,35  QPSK  (2:32:2026)) 0x4043
        new transponder: (S  f = 11915 kHz H SR = 27500  5/6 0,35  QPSK  (2:32:2011)) 0x4043
        new transponder: (S  f = 12188 kHz H SR = 27500  5/6 0,35  QPSK  (2:32:2025)) 0x4043
        already known: (S  f = 10773 kHz H SR = 22000  5/6 0,35  QPSK  (0:32:0)), but not found by pids
        S  f = 10773 kHz H SR = 22000  5/6 0,35  QPSK  (0:32:0) : updating tp ids -> (2:32:2045)
        new transponder: (S  f = 10803 kHz H SR = 22000  5/6 0,35  QPSK  (2:32:2047)) 0x4043
        new transponder: (S2 f = 10847 kHz V SR = 23000  2/3 0,25  8PSK  (2:32:2050)) 0x4043
        new transponder: (S  f = 10788 kHz V SR = 22000  5/6 0,35  QPSK  (2:32:2046)) 0x4043
        new transponder: (S  f = 10818 kHz V SR = 22000  5/6 0,35  QPSK  (2:32:2048)) 0x4043
        new transponder: (S2 f = 11023 kHz H SR = 23000  2/3 0,25  8PSK  (2:32:2061)) 0x4043
        new transponder: (S  f = 11895 kHz V SR = 27500  2/3 0,35  QPSK  (2:32:2010)) 0x4043
        new transponder: (S2 f = 11686 kHz V SR = 23000  2/3 0,25  8PSK  (2:32:2104)) 0x4043
        new transponder: (S  f = 11427 kHz V SR = 27500  5/6 0,35  QPSK  (2:32:2116)) 0x4043
        new transponder: (S2 f = 11387 kHz V SR = 29500  3/4 0,20  QPSK  (2:32:2114)) 0x4043
        new transponder: (S  f = 11112 kHz H SR = 22000  5/6 0,35  QPSK  (2:32:2067)) 0x4043
        new transponder: (S  f = 11082 kHz H SR = 22000  5/6 0,35  QPSK  (2:32:2065)) 0x4043
        new transponder: (S  f = 11553 kHz H SR = 22000  5/6 0,35  QPSK  (2:32:2095)) 0x4043
        new transponder: (S2 f = 11225 kHz V SR = 23000  2/3 0,25  8PSK  (2:32:2106)) 0x4043
        new transponder: (S  f = 11171 kHz H SR = 22000  5/6 0,35  QPSK  (2:32:2071)) 0x4043
        new transponder: (S  f = 11141 kHz H SR = 22000  5/6 0,35  QPSK  (2:32:2069)) 0x4043
        new transponder: (S  f = 11479 kHz V SR = 22000  5/6 0,35  QPSK  (2:32:2090)) 0x4043
        new transponder: (S  f = 11127 kHz V SR = 22000  5/6 0,35  QPSK  (2:32:2068)) 0x4043
        new transponder: (S  f = 12129 kHz V SR = 27500  2/3 0,35  QPSK  (2:32:2022)) 0x4043
        new transponder: (S  f = 12383 kHz H SR = 27500  5/6 0,35  QPSK  (2:32:2035)) 0x4043
        new transponder: (S  f = 11345 kHz H SR = 27500  5/6 0,35  QPSK  (2:32:2111)) 0x4043
        new transponder: (S2 f = 11053 kHz H SR = 23000  3/4 0,25  8PSK  (2:32:2063)) 0x4043
        new transponder: (S  f = 11265 kHz V SR = 27500  2/3 0,35  QPSK  (2:32:2108)) 0x4043
        new transponder: (S  f = 11656 kHz V SR = 22000  5/6 0,35  QPSK  (2:32:2102)) 0x4043
        new transponder: (S2 f = 11509 kHz V SR = 23000  2/3 0,25  8PSK  (2:32:2092)) 0x4043
        new transponder: (S  f = 11464 kHz H SR = 22000  5/6 0,35  QPSK  (2:32:2089)) 0x4043
        new transponder: (S  f = 11627 kHz V SR = 22000  5/6 0,35  QPSK  (2:32:2100)) 0x4043
        new transponder: (S  f = 11538 kHz V SR = 22000  5/6 0,35  QPSK  (2:32:2094)) 0x4043
        new transponder: (S  f = 11954 kHz H SR = 27500  2/3 0,35  QPSK  (2:32:2013)) 0x4043
        new transponder: (S  f = 11494 kHz H SR = 22000  5/6 0,35  QPSK  (2:32:2091)) 0x4043
^C
ERROR: interrupted by SIGINT, dumping partial result...
(time: 00:29.727) dumping lists (0 services)
Mike
georgep56
Newcomer
Posts: 10
Joined: Thu May 10, 2018 2:33 pm
Great Britain

Re: Help please with drivers for TBS6981 DVB-S2 on Ubuntu

Post by georgep56 »

MikeB2013 wrote:
Fri May 11, 2018 5:08 pm

Of course it forgets to tell you how to find the symbol conflicts ("dmesg |grep -i sym" should do it)
Nothing significant reported there:

Code: Select all

george@tvbox:/raid/firmware/drivers/media_build$ dmesg |grep -i sym
[    0.785669] Key type asymmetric registered
[    0.785670] Asymmetric key parser 'x509' registered
[    5.393808] lirc_dev: Unknown symbol rc_open (err 0)
[    5.393835] lirc_dev: Unknown symbol rc_close (err 0)
MikeB2013 wrote:
Fri May 11, 2018 5:08 pm
There is also a possibility that the driver source code tree in media_build needs to be cleaned (gets rid of any remnants from previous builds), so
cd media_build
make distclean
make dir DIR=../media
make allyesconfig
make -j4
sudo rm -rf /lib/modules/``uname -r``/kernel/drivers/media/*
sudo make install
sudo reboot
Done that - everything appears to build fine.

I'm wondering if it could be firmware related? I have found before that different versions of firmware - with ostensibly the same name - can produce very different behaviour.

My /lib/firmware directory does appear to have a real mixture of firmwares relating to Conexant chipsets :

Code: Select all

george@tvbox:/raid/firmware/drivers/media_build$ ls -l /lib/firmware/*cx*
-rw-r--r-- 1 george george  32674 Jun 21  2013 /lib/firmware/dvb-fe-cx24116.fw
-rw-r--r-- 1 george george  55352 Oct 29  2013 /lib/firmware/dvb-fe-cx24117.fw
-rw-r--r-- 1 root   root    55352 May  9 19:43 /lib/firmware/dvb-fe-cx24117.fw.1
-rw-r--r-- 1 george george  16382 Mar 23  2009 /lib/firmware/v4l-cx231xx-avcore-01.fw
-rw-r--r-- 1 george george 141200 Mar 23  2009 /lib/firmware/v4l-cx23418-apu.fw
-rw-r--r-- 1 george george 158332 Mar 23  2009 /lib/firmware/v4l-cx23418-cpu.fw
-rw-r--r-- 1 george george  16382 Mar 23  2009 /lib/firmware/v4l-cx23418-dig.fw
-rw-r--r-- 1 root   root   262144 Feb  9 13:50 /lib/firmware/v4l-cx2341x-dec.fw
-rw-r--r-- 1 root   root   376836 Feb  9 13:50 /lib/firmware/v4l-cx2341x-enc.fw
-rw-r--r-- 1 root   root   155648 Feb  9 13:50 /lib/firmware/v4l-cx2341x-init.mpg
-rw-r--r-- 1 george george  16382 Mar 23  2009 /lib/firmware/v4l-cx23885-avcore-01.fw
-rw-r--r-- 1 george george  16382 Jun 23  2010 /lib/firmware/v4l-cx23885-enc-broken.fw
-rw-r--r-- 1 george george  16382 Mar 23  2009 /lib/firmware/v4l-cx23885-enc.fw
-rw-r--r-- 1 george george  16382 Mar 23  2009 /lib/firmware/v4l-cx25840.fw
And PLEASE don't ask me how an mpg file got to be in there! :-o

The two versions of cx24117.fw (referred to specifically in the "Getting firmware from the Linux driver" section are identical (same md5sum).
How does that compare with your firmware directory?

Thanks Mike.
George
MikeB2013
Senior
Posts: 519
Joined: Mon Jul 25, 2016 4:16 pm
Great Britain

Re: Help please with drivers for TBS6981 DVB-S2 on Ubuntu

Post by MikeB2013 »

In my /lib/firmware
-rw-r--r-- 1 root root 55K May 2 10:39 dvb-fe-cx24117.fw


which is a different file size to yours.
md5 00bb54e462c84c71c052b1812a1c7190

I just ran the instructions
Edit: on a local directory not /lib/firmware/
Getting firmware from the Linux driver

Code: Select all

wget http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v130901.zip
unzip -p tbs-linux-drivers_v130901.zip linux-tbs-drivers.tar.bz2 | tar jxOf - linux-tbs-drivers/v4l/tbs6981fe_driver.o.x86_64 | dd bs=1 skip=10144 count=55486 of=dvb-fe-cx24117.fw
and it gives
-rw-rw-r-- 1 mike mike 55486 May 11 20:36 dvb-fe-cx24117.fw
md5 0bb54e462c84c71c052b1812a1c7190
and copied it to /lib/firmware/


I have never tried Getting the firmware from the Windows driver

Mike
georgep56
Newcomer
Posts: 10
Joined: Thu May 10, 2018 2:33 pm
Great Britain

Re: Help please with drivers for TBS6981 DVB-S2 on Ubuntu

Post by georgep56 »

Hmm .. that corresponds exactly to what I did, and the results (and md5sum) are the same.

The only other firmware that seems to be being loaded is this:

May 11 16:43:59 tvbox kernel: [ 6.922148] cx25840 9-0044: loaded v4l-cx23885-avcore-01.fw firmware (16382 bytes)

-rw-r--r-- 1 george george 16382 Mar 23 2009 /lib/firmware/v4l-cx23885-avcore-01.fw

a9f8f5d901a7fb42f552e1ee6384f3bb /lib/firmware/v4l-cx23885-avcore-01.fw

Running out of ideas here :-s
George
MikeB2013
Senior
Posts: 519
Joined: Mon Jul 25, 2016 4:16 pm
Great Britain

Re: Help please with drivers for TBS6981 DVB-S2 on Ubuntu

Post by MikeB2013 »

For dvb-fe-cx24117 your file size 55352 mine is 55486 with md5sum 0bb54e462c84c71c052b1812a1c7190

However your -rw-r--r-- 1 george george 16382 Mar 23 2009 /lib/firmware/v4l-cx231xx-avcore-01.fw

md5sum /lib/firmware/v4l-cx231xx-avcore-01.fw
a9f8f5d901a7fb42f552e1ee6384f3bb

is different from mine
-rw-r--r-- 1 root root 16382 Mar 30 2017 v4l-cx231xx-avcore-01.fw
md5sum 7d3bb956dc9df0eafded2b56ba57cc42

Mike
georgep56
Newcomer
Posts: 10
Joined: Thu May 10, 2018 2:33 pm
Great Britain

Re: Help please with drivers for TBS6981 DVB-S2 on Ubuntu

Post by georgep56 »

In a last desperate bid to achieve something tonight I just did another reboot *with the cable attached to the card* (I know it seems bizarre that it should make any difference at all) and .....

george@tvbox:~$ w_scan -f s -c GB -a 2 -s S28E2
w_scan -f s -c GB -a 2 -s S28E2
w_scan version 20141122 (compiled for DVB API 5.10)
using settings for 28.2 east Astra 2A/B/C/D + EuroBird 1 28.5
scan type SATELLITE, channellist 61
output format vdr-2.0
WARNING: could not guess your codepage. Falling back to 'UTF-8'
output charset 'UTF-8', use -C <charset> to override
-_-_-_-_ Getting frontend capabilities-_-_-_-_
Using DVB API 5.11
frontend 'TurboSight TBS 6981 DVB-S/S2' supports
INVERSION_AUTO
DVB-S
DVB-S2
FREQ (0.95GHz ... 2.15GHz)
SRATE (1.000MSym/s ... 45.000MSym/s)
using LNB "UNIVERSAL"
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
trying 'S f = 10714 kHz H SR = 22000 5/6 0,35 QPSK (0:0:0)'
(time: 00:05.703) signal ok: S f = 10714 kHz H SR = 22000 5/6 0,35 QPSK (0:0:0)
S f = 10714 kHz H SR = 22000 5/6 0,35 QPSK (0:0:0) : updating transport_stream_id: -> (0:0:2041)
S f = 10714 kHz H SR = 22000 5/6 0,35 QPSK (0:0:2041) : updating network_id -> (0:32:2041)
new transponder: (S2 f = 12461 kHz H SR = 29500 8/9 0,35 QPSK (2:32:2039)) 0x4043
new transponder: (S2 f = 12344 kHz H SR = 29500 8/9 0,35 QPSK (2:32:2033)) 0x4043
new transponder: (S2 f = 12266 kHz H SR = 29500 8/9 0,35 QPSK (2:32:2029)) 0x4043
new transponder: (S2 f = 12363 kHz V SR = 29500 8/9 0,35 QPSK (2:32:2034)) 0x4043
new transponder: (S2 f = 12012 kHz V SR = 29500 8/9 0,35 QPSK (2:32:2016)) 0x4043
new transponder: (S2 f = 12246 kHz V SR = 29500 8/9 0,35 QPSK (2:32:2028)) 0x4043
new transponder: (S2 f = 12168 kHz V SR = 29500 8/9 0,35 QPSK (2:32:2024)) 0x4043
new transponder: (S2 f = 11856 kHz V SR = 29500 8/9 0,35 QPSK (2:32:2008)) 0x4043
new transponder: (S2 f = 11739 kHz V SR = 29500 8/9 0,35 QPSK (2:32:2002)) 0x4043
new transponder: (S2 f = 12324 kHz V SR = 29500 8/9 0,35 QPSK (2:32:2032)) 0x4043
new transponder: (S2 f = 12090 kHz V SR = 29500 8/9 0,35 QPSK (2:32:2020)) 0x4043
new transponder: (S2 f = 12227 kHz H SR = 29500 8/9 0,35 QPSK (2:32:2027)) 0x4043
new transponder: (S2 f = 11759 kHz H SR = 29500 8/9 0,35 QPSK (2:32:2003)) 0x4043
new transponder: (S f = 11778 kHz V SR = 27500 2/3 0,35 QPSK (2:32:2004)) 0x4043
new transponder: (S f = 12110 kHz H SR = 27500 5/6 0,35 QPSK (2:32:2021)) 0x4043
new transponder: (S f = 11934 kHz V SR = 27500 5/6 0,35 QPSK (2:32:2012)) 0x4043


I'm now going to go to bed before it decides not to work any more :-D
Thanks for your help.
George
georgep56
Newcomer
Posts: 10
Joined: Thu May 10, 2018 2:33 pm
Great Britain

Re: Help please with drivers for TBS6981 DVB-S2 on Ubuntu

Post by georgep56 »

Well I configured the 2 "new" tuners in my backend while 2 separate "w_scan" instances found a whole load of channels.

I then kicked off a mythtv-setup channel scan and around 1000 new channels were found.

Then the weirdness started again...

Having found all the new channels, the backend couldn't tune to any of them! This is what appeared in the backend log....

Code: Select all

May 11 22:14:36 tvbox mythbackend: mythbackend[7888]: N CoreContext main_helpers.cpp:597 (run_backend) MythBackend: Starting up as the master server.
May 11 22:14:38 tvbox mythbackend: mythbackend[7888]: E CoreContext diseqc.cpp:941 (CreateById) DiSEqCDevTree: CreateById failed to find dtv dev 1
May 11 22:14:39 tvbox mythbackend: mythbackend[7888]: I CoreContext channelutil.cpp:1911 (GetChannelData) No visible channels for 100
May 11 22:14:39 tvbox mythbackend: mythbackend[7888]: E CoreContext channelutil.cpp:1925 (GetChannelData) GetChannelData() failed because it could not#012#011#011#011find channel number '100' in DB for source '1'.
May 11 22:14:39 tvbox mythbackend: mythbackend[7888]: E CoreContext recorders/dtvchannel.cpp:219 (SetChannelByString) DTVChan[1](/dev/dvb/adapter0/frontend0): SetChannelByString(100): Unable to find channel in database.
May 11 22:14:39 tvbox mythbackend: mythbackend[7888]: E CoreContext diseqc.cpp:529 (Execute) DiSEqCDevTree: No root device tree node!
May 11 22:14:39 tvbox mythbackend: mythbackend[7888]: E CoreContext recorders/dvbchannel.cpp:734 (Tune) DVBChan[1](/dev/dvb/adapter0/frontend0): Tune(): Failed to setup DiSEqC devices
May 11 22:14:39 tvbox mythbackend: mythbackend[7888]: E CoreContext recorders/dtvchannel.cpp:311 (SetChannelByString) DTVChan[1](/dev/dvb/adapter0/frontend0): SetChannelByString(1-4751): Tuning to frequency.
May 11 22:14:39 tvbox mythbackend: mythbackend[7888]: E CoreContext recorders/channelbase.cpp:134 (Init) ChannelBase[1]: Setting start channel '100' failed, #012#011#011#011and we failed to find any suitible channels on any input.
May 11 22:14:41 tvbox mythbackend: mythbackend[7888]: I CoreContext channelutil.cpp:1911 (GetChannelData) No visible channels for 100
May 11 22:14:41 tvbox mythbackend: mythbackend[7888]: E CoreContext channelutil.cpp:1925 (GetChannelData) GetChannelData() failed because it could not#012#011#011#011find channel number '100' in DB for source '1'.
May 11 22:14:41 tvbox mythbackend: mythbackend[7888]: E CoreContext recorders/dtvchannel.cpp:219 (SetChannelByString) DTVChan[2](/dev/dvb/adapter0/frontend0): SetChannelByString(100): Unable to find channel in database.
May 11 22:14:41 tvbox mythbackend: mythbackend[7888]: E CoreContext diseqc.cpp:529 (Execute) DiSEqCDevTree: No root device tree node!
May 11 22:14:41 tvbox mythbackend: mythbackend[7888]: E CoreContext recorders/dvbchannel.cpp:734 (Tune) DVBChan[1](/dev/dvb/adapter0/frontend0): Tune(): Failed to setup DiSEqC devices
May 11 22:14:41 tvbox mythbackend: mythbackend[7888]: E CoreContext recorders/dtvchannel.cpp:311 (SetChannelByString) DTVChan[2](/dev/dvb/adapter0/frontend0): SetChannelByString(1-4751): Tuning to frequency.
May 11 22:14:41 tvbox mythbackend: mythbackend[7888]: E CoreContext recorders/channelbase.cpp:134 (Init) ChannelBase[2]: Setting start channel '100' failed, #012#011#011#011and we failed to find any suitible channels on any input.
May 11 22:14:41 tvbox mythbackend: mythbackend[7888]: E CoreContext diseqc.cpp:941 (CreateById) DiSEqCDevTree: CreateById failed to find dtv dev 3
May 11 22:14:43 tvbox mythbackend: mythbackend[7888]: I CoreContext channelutil.cpp:1911 (GetChannelData) No visible channels for 0
I just don't get all the references to diseqc - the tuners are set up with a single LNB!
And 'DTVChan[2]' as well as 'DVBChan[2]' ... erm, what???

It's all so unpredictable .. I just don't get it at all!

In the meantime, amidst all this chaos and nonsense, my single USB tuner continues to work solidly (it's a good job too otherwise I'd be doubting my sanity!).

Aside from ditching this card completely I just don't know where to go?
I guess the card itself *could* be faulty? (although the very friendly and communicative ebay seller insists he's had it working reliably for several years).

George
MikeB2013
Senior
Posts: 519
Joined: Mon Jul 25, 2016 4:16 pm
Great Britain

Re: Help please with drivers for TBS6981 DVB-S2 on Ubuntu

Post by MikeB2013 »

I doubt the card is faulty as w_scan finds channels.
It is more likely mythbackend configuration requires adjustment.
I need to see details of how your tuners are configured.
A simple (but not the only) way is to use mythtv services API to get the required data.

In your favorite web browser run the following:

http://192.168.0.20:6544/Capture/GetCaptureCardList

replacing the 192.168.0.20 with the IP address of your mythtv backend
and paste the resulting output, which will be large.

Mike
MikeB2013
Senior
Posts: 519
Joined: Mon Jul 25, 2016 4:16 pm
Great Britain

Re: Help please with drivers for TBS6981 DVB-S2 on Ubuntu

Post by MikeB2013 »

George,

Just in case you are not aware, there is a little bug in mythtv-setup in that it does not stop mythbackend from running. mythtv-setup requires exclusive access to tuners and database whilst being used, strange things do happen if mythbackend is still running.

So until the bug is fixed, you should use the following in a terminal session:

sudo systemctl stop mythtv-backend
mythtv-setup
sudo systemctl start mythtv-backend

Mike
georgep56
Newcomer
Posts: 10
Joined: Thu May 10, 2018 2:33 pm
Great Britain

Re: Help please with drivers for TBS6981 DVB-S2 on Ubuntu

Post by georgep56 »

I'm aware of that one Mike; I've manually patched my mythtv-setup until an official fix appears.

Here is the output you asked for in your previous post. I'm afraid the XML formatting has been lost.
Cardids 1 and 2 are my USB tuner (set to record 2 simultaneous streams) 3 and 4 are the TBS card.

At this point in time the 2 inputs of the TBS card have no LNB connected.

Code: Select all

<CaptureCardList version="1.0" serializerVersion="1.1"><CaptureCards><CaptureCard><CardId>1</CardId><VideoDevice>/dev/dvb/adapter0/frontend0</VideoDevice><AudioDevice/><VBIDevice/><CardType>DVB</CardType><AudioRateLimit>0</AudioRateLimit><HostName>tvbox</HostName><DVBSWFilter>0</DVBSWFilter><DVBSatType>0</DVBSatType><DVBWaitForSeqStart>true</DVBWaitForSeqStart><SkipBTAudio>false</SkipBTAudio><DVBOnDemand>true</DVBOnDemand><DVBDiSEqCType>0</DVBDiSEqCType><FirewireSpeed>0</FirewireSpeed><FirewireModel/><FirewireConnection>0</FirewireConnection><SignalTimeout>7000</SignalTimeout><ChannelTimeout>10000</ChannelTimeout><DVBTuningDelay>1</DVBTuningDelay><Contrast>0</Contrast><Brightness>0</Brightness><Colour>0</Colour><Hue>0</Hue><DiSEqCId>1</DiSEqCId><DVBEITScan>true</DVBEITScan></CaptureCard><CaptureCard><CardId>2</CardId><VideoDevice>/dev/dvb/adapter0/frontend0</VideoDevice><AudioDevice/><VBIDevice/><CardType>DVB</CardType><AudioRateLimit>0</AudioRateLimit><HostName>tvbox</HostName><DVBSWFilter>0</DVBSWFilter><DVBSatType>0</DVBSatType><DVBWaitForSeqStart>true</DVBWaitForSeqStart><SkipBTAudio>false</SkipBTAudio><DVBOnDemand>true</DVBOnDemand><DVBDiSEqCType>0</DVBDiSEqCType><FirewireSpeed>0</FirewireSpeed><FirewireModel/><FirewireConnection>0</FirewireConnection><SignalTimeout>7000</SignalTimeout><ChannelTimeout>10000</ChannelTimeout><DVBTuningDelay>1</DVBTuningDelay><Contrast>0</Contrast><Brightness>0</Brightness><Colour>0</Colour><Hue>0</Hue><DiSEqCId>1</DiSEqCId><DVBEITScan>true</DVBEITScan></CaptureCard><CaptureCard><CardId>3</CardId><VideoDevice>/dev/dvb/adapter1/frontend0</VideoDevice><AudioDevice/><VBIDevice/><CardType>DVB</CardType><AudioRateLimit>0</AudioRateLimit><HostName>tvbox</HostName><DVBSWFilter>0</DVBSWFilter><DVBSatType>0</DVBSatType><DVBWaitForSeqStart>true</DVBWaitForSeqStart><SkipBTAudio>false</SkipBTAudio><DVBOnDemand>true</DVBOnDemand><DVBDiSEqCType>0</DVBDiSEqCType><FirewireSpeed>0</FirewireSpeed><FirewireModel/><FirewireConnection>0</FirewireConnection><SignalTimeout>7000</SignalTimeout><ChannelTimeout>10000</ChannelTimeout><DVBTuningDelay>1</DVBTuningDelay><Contrast>0</Contrast><Brightness>0</Brightness><Colour>0</Colour><Hue>0</Hue><DiSEqCId>2</DiSEqCId><DVBEITScan>true</DVBEITScan></CaptureCard><CaptureCard><CardId>4</CardId><VideoDevice>/dev/dvb/adapter2/frontend0</VideoDevice><AudioDevice/><VBIDevice/><CardType>DVB</CardType><AudioRateLimit>0</AudioRateLimit><HostName>tvbox</HostName><DVBSWFilter>0</DVBSWFilter><DVBSatType>0</DVBSatType><DVBWaitForSeqStart>true</DVBWaitForSeqStart><SkipBTAudio>false</SkipBTAudio><DVBOnDemand>true</DVBOnDemand><DVBDiSEqCType>0</DVBDiSEqCType><FirewireSpeed>0</FirewireSpeed><FirewireModel/><FirewireConnection>0</FirewireConnection><SignalTimeout>7000</SignalTimeout><ChannelTimeout>10000</ChannelTimeout><DVBTuningDelay>1</DVBTuningDelay><Contrast>0</Contrast><Brightness>0</Brightness><Colour>0</Colour><Hue>0</Hue><DiSEqCId>3</DiSEqCId><DVBEITScan>true</DVBEITScan></CaptureCard></CaptureCards></CaptureCardList>
georgep56
Newcomer
Posts: 10
Joined: Thu May 10, 2018 2:33 pm
Great Britain

Re: Help please with drivers for TBS6981 DVB-S2 on Ubuntu

Post by georgep56 »

Well I think I may have somehow sorted the problem.

I wondered if the diseqc messages could somehow be related to MythTV 'thinking' that the tuners were sharing an LNB (when in fact each tuner attaches to a separate port of a multi-lnb), so last night I reconfigured the tuners and labelled the three tuners' LNB connections (with the 'optional name' function) as LNB1,2 and 3.

And things now seem to be working. I have removed the USB tuner (I currently only have 2 lnb ports available) and the two TBS tuners are now behaving;
((text copied from mythweb))

Code: Select all

Encoder 3 [ DVB : /dev/dvb/adapter1/frontend0 ] is local on tvbox and is watching Live TV 'SUV Superbuild' on QUEST. This recording is scheduled to end at 09:00.
Encoder 4 [ DVB : /dev/dvb/adapter2/frontend0 ] is local on tvbox and is recording 'Zoe Ball on Sunday' on ITV West. This recording is scheduled to end at 09:25.
Based on past experience this is probably not the end of the story, but it is at least progress in the right direction :-D
George
Post Reply