TBS6984 works with Media Portal => TVheadend no services

Speager Rowland

Hello,

I am using TVHeadend 2.99.53.4502158 with card TBS6984 with same settings like in Media Portal in Windows, where it works perfectly, but in TVheadend I can't get any services from transponders..

Can any one help??

Info:
OS: Ubuntu 12.04
TVHeadend: 2.99.53.4502158
Satellite Card: TBS6984
Driver: tbs-linux-drivers_TBS6284_v120814
Output for: "dmesg |grep DVB"
[ 2.628596] DVB: registering new adapter (SAA716x dvb adapter)
[ 2.721220] TurboSight TBS6984 DVB-S2 card port0 MAC=00:22:ab:90:1a:0c
[ 2.721224] DVB: registering adapter 0 frontend 0 (TurboSight TBS 6984 DVBS/S2 frontend)...
[ 2.721293] DVB: registering new adapter (SAA716x dvb adapter)
[ 2.811995] TurboSight TBS6984 DVB-S2 card port1 MAC=00:22:ab:90:1a:0d
[ 2.811998] DVB: registering adapter 1 frontend 0 (TurboSight TBS 6984 DVBS/S2 frontend)...
[ 2.812079] DVB: registering new adapter (SAA716x dvb adapter)
[ 2.899945] TurboSight TBS6984 DVB-S2 card port2 MAC=00:22:ab:90:1a:0e
[ 2.899948] DVB: registering adapter 2 frontend 0 (TurboSight TBS 6984 DVBS/S2 frontend)...
[ 2.900035] DVB: registering new adapter (SAA716x dvb adapter)
[ 2.987793] TurboSight TBS6984 DVB-S2 card port3 MAC=00:22:ab:90:1a:0f

[ 2.987796] DVB: registering adapter 3 frontend 0 (TurboSight TBS 6984 DVBS/S2 frontend)...

Log:
....

....

Aug 21 10:19:00 dvb: New mux "12,629,000 kHz Vertical (Default (Port 0, Universal LNB))" created by built-in configuration from "Astra-28.2E"

Aug 21 10:19:00 dvb: New mux "12,692,000 kHz Vertical (Default (Port 0, Universal LNB))" created by built-in configuration from "Astra-28.2E"

Loglevel debug: enabled

Aug 21 10:19:04 dvb: "12,344,000 kHz Horizontal (Default (Port 0, Unive" on adapter "TurboSight TBS 6984 DVBS/S2 frontend", status changed to Faint signal

Aug 21 10:19:05 dvb: "11,720,000 kHz Horizontal (Default (Port 0, Unive" on adapter "TurboSight TBS 6984 DVBS/S2 frontend", status changed to No signal

Aug 21 10:19:06 dvb: "11,778,000 kHz Vertical (Default (Port 0, Univers" on adapter "TurboSight TBS 6984 DVBS/S2 frontend", status changed to Bad signal

Aug 21 10:19:07 dvb: "11,778,000 kHz Vertical (Default (Port 0, Univers" on adapter "TurboSight TBS 6984 DVBS/S2 frontend", status changed to Faint signal

Aug 21 10:19:11 dvb: "/dev/dvb/adapter2" tuning via s2api to "12,324,000 kHz Vertical (Default (Port 0, Universal LNB))" (1724000, 29500000 Baud, 3/4, SYS_UNDEFINED, QPSK)

Aug 21 10:19:14 dvb: "/dev/dvb/adapter3" tuning via s2api to "10,803,000 kHz Horizontal (Default (Port 0, Universal LNB))" (1053000, 22000000 Baud, 5/6, SYS_UNDEFINED, QPSK)

Aug 21 10:19:20 dvb: "/dev/dvb/adapter0" tuning via s2api to "11,740,000 kHz Vertical (Default (Port 0, Universal LNB))" (1140000, 27500000 Baud, 2/3, SYS_UNDEFINED, QPSK)

Aug 21 10:19:25 dvb: "11,740,000 kHz Vertical (Default (Port 0, Univers" on adapter "TurboSight TBS 6984 DVBS/S2 frontend", status changed to No signal

Aug 21 10:19:28 dvb: "12,324,000 kHz Vertical (Default (Port 0, Univers" on adapter "TurboSight TBS 6984 DVBS/S2 frontend", status changed to Bad signal

Aug 21 10:19:29 dvb: "12,324,000 kHz Vertical (Default (Port 0, Univers" on adapter "TurboSight TBS 6984 DVBS/S2 frontend", status changed to Faint signal

Aug 21 10:19:30 dvb: "10,803,000 kHz Horizontal (Default (Port 0, Unive" on adapter "TurboSight TBS 6984 DVBS/S2 frontend", status changed to Bad signal

Aug 21 10:19:31 dvb: "/dev/dvb/adapter2" tuning via s2api to "10,921,000 kHz Horizontal (Default (Port 0, Universal LNB))" (1171000, 22000000 Baud, 5/6, SYS_UNDEFINED, QPSK)

Aug 21 10:19:33 dvb: "10,803,000 kHz Horizontal (Default (Port 0, Unive" on adapter "TurboSight TBS 6984 DVBS/S2 frontend", status changed to Faint signal

Aug 21 10:19:34 dvb: "/dev/dvb/adapter3" tuning via s2api to "11,307,000 kHz Vertical (Default (Port 0, Universal LNB))" (1557000, 27500000 Baud, 2/3, SYS_UNDEFINED, QPSK)

Aug 21 10:19:38 dvb: "10,921,000 kHz Horizontal (Default (Port 0, Unive" on adapter "TurboSight TBS 6984 DVBS/S2 frontend", status changed to Bad signal

Aug 21 10:19:39 dvb: "10,921,000 kHz Horizontal (Default (Port 0, Unive" on adapter "TurboSight TBS 6984 DVBS/S2 frontend", status changed to Faint signal

Aug 21 10:19:39 dvb: "11,307,000 kHz Vertical (Default (Port 0, Univers" on adapter "TurboSight TBS 6984 DVBS/S2 frontend", status changed to Faint signal

....
....

Adam Sutton

There was a problem with my own TBS6981 (dual tuner) variant of this card. The driver failed to accept SYS_UNDEFINED and a bug in the code meant it didn't properly set SYS_DVBS.

This looks like the exact same problem your having here. I fixed the problem some time ago, but it won't be in that version you have.

I would recommend building from latest git or picking up the 3.0 deb (which will be a bit more stable than git master).

Adam

Speager Rowland

Problem, finally solved by using new version TVheadend 3.0 and good know numbering of adapters "adapter3 = TunerA".

Thanks for help to Adam Sutton

Richard Lloyd

I also have the TBS6984 running under Ubuntu 12.04 (64-bit). tvheadend 2.12 in that setup was virtually unusable (very frequent crashes), but the git version (and subsequent 3.0 release) are very solid now. The only issues I tend to have are signal ones (I see that if you monitor signal quality with the git version, anything under 10% quality will be ignored now).

I don't know if any Windows-based media centre software has such a comprehensive Web backend (i.e one that does tuner card config, EPG grabbing, EIT detection, recorder scheduling and playback) - tvheadend seems to be almost unique in that respect on Linux at least. On Windows, almost all media centre software I've seen uses a native UI.

Adam Sutton

I have to admit I usually disable signal quality monitoring. I'm not 100% convinced by the implementation as I've definitely seen issues with TVH rejecting perfectly good muxes in the past.

Andreas did consider completely removing the signal monitoring, but I didn't think that necessary since there is already an option to disable it. Though I think I slightly tweaked things to ensure it was properly ignored.

There are definitely several users with TBS6981/4 cards using TVH without problems.

Adam

Kjell A. Stormo

Hello, i'm also experiensing problems with Tvheadend and TBS 6984.
I have been using tvheadend and TBS several month now, and it have been working ok, it was working ok after i added a TBS 6981 card.
Then i changed the TBS 6981 card with a secound TBS 6984 card, and now i have problems with the two cards together.
I have also updated tvheaden almost every month.

Now i have reverted back to a 2.99 version to see if the problem is in that version.(HTS Tvheadend 2.99.44.g4ef72.dirty)

Here i get some of these errors:

Oct 26 08:29:06 TS: TBS 6984 frontend3/Telenor: 10,747,000 kHz Vertical (LNB 1): H264

#514: Continuity counter error Oct 26 08:29:28 TS: TBS 6984 frontend3/Telenor: 10,747,000 kHz Vertical (LNB 1): H264

#514: Continuity counter error

But the muxes are still here.

With the tvheadend 3.2xxx and 3.3xx the muxes are ok afer scanning, and running ok for some hours, then starting to get Faint signal and then No signal. This happends first to two out of eight adapters, and when trying to watch tv, tvheadend only picks the adapters with no signal.

then after a few more minits the rest of the adapters looses their signal to. The only way to get them working again is to reinstall tvheaden, clean all configs and start over from scratch, then it's workong for a few hours again before i hav to do the reinstall again.

I have moved the TBS 6981 card to another machine, this one is working good and have been for a few days since i installed the system, no errors, all muxes is ok(HTS Tvheadend 3.3.78~g3236c4a). This is with the same version that crashes with TBS6984.

I have a friend that also have the same system with two TBS 6984 cards, he is also experiencing problems with signal loss.

Please would someone take a look at this problem.
For any more regarding this problem, please PM me or send me a mail.

Adam Sutton

I need to give this some thought. This sounds very familiar to another user I've talked to.

Can you confirm, 100%, that <3.0 is absolutely fine, no problems at all? but 3.2+ causes problems with the 6984, to the point that even a TVH restart will not solve the problem?

I had seen this on a user system and had put it down to a firmware issue, since I cannot see how/why TVH could be responsible for the hardware failing permanently (i.e. restarting TVH had no effect, nor did switching to another software package once things started to fail).

Adam

Kjell A. Stormo

Right now i'm running the 3.3.77 Ver, because the 3.3.78 started to fail. i'm running the signal scan, on all adapters, (two at a time). Reinstalled the drivers , tvhe 3.3.77 and is now running and have been for a few hours. I have to drive the machine a bit to know the result, recording 3 -4 channels, live tv on two or three units, then ill get you the results of this ver.

I have started another thread on this subjekt: https://www.lonelycoder.com/redmine/boards/5/topics/6050

I'll post the result on that thread.

If this one is starting to fail, i'll try the 3.0 release, and give you the results. to be shore i'll ne a few days, since the crashes normally takes 12 -24 hours.

Kjell A. Stormo

Ok, it was up for 3 hours, now the adapters 4-7 is failing, adapter 0-3 still working, but as long as the muxes are mapped from the failing card i only get the No input message when trying to watch live tv.
I will now remove all muxes from the failing card, without restarting tvheadend and see if the first card breaks down.