Tvheadend

Hello Vitaly,

any luck with your issue?
I am having the same problem. I cannot find any services related to S2 muxes.
Status unknown as well.

I am on a Tevii S660 USB. I start doubting the drivers and their capability of locking on S2 Muxes...

Thanks for any update!

Went one step further,

this might be a good clue:

more _dev_dvb_adapter0_Montage_Technology_DS3000_TS2020 {
"type": "DVB-S",
"displayname": "Montage Technology DS3000/TS2020",
"autodiscovery": 1,
"idlescan": 1,
"qmon": 1,
"dump_muxes": 0,
"nitoid": 0,
"diseqc_version": 0
}

it seems Tnheadend sees my DVB adapter as just DVB-S not S2.

Same thing

"type": "DVB-S",
        "displayname": "STB0899 Multistandard",

I just started with TVheadend and luckily found this thread, because I think I have the same problem. I have a TechniSat Skystar HD2 card. It is registered with lcpci as:

01:07.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV PCI Bridge Controller [Ver 1.0] (rev 01)

TVheadend recognizes it as _dev_dvb_adapter0_STB0899_Multistandard:

{
    "type": "DVB-S",
    "displayname": "Skystar HD2",
    "autodiscovery": 1,
    "idlescan": 1,
    "qmon": 0,
    "dump_muxes": 0,
    "nitoid": 0,"diseqc_version": 0
}

When I do "Add DVB network by location" it will add about 37 muxes and start to scan those. However, "Muxes awaiting initial scan" never drops below 5 and every entry on the "Multiplexes" tab has a signal quality of 100%, but with frontend status no signal or unknown. My debug output looks like this:

Loglevel debug: enabled

Nov 26 10:58:26 dvb: "/dev/dvb/adapter0" tuning via s2api to "10,802,000 kHz Horizontal (No satconf)" (1052000, 22000000 Baud, 5/6, SYS_UNDEFINED, QPSK)
Nov 26 10:58:47 dvb: "/dev/dvb/adapter0" tuning via s2api to "11,675,000 kHz Horizontal (No satconf)" (1925000, 27500000 Baud, 3/4, SYS_UNDEFINED, QPSK)
Nov 26 10:59:06 dvb: "/dev/dvb/adapter0" tuning via s2api to "12,630,000 kHz Vertical (No satconf)" (2030000, 6000000 Baud, 3/4, SYS_UNDEFINED, QPSK)
Nov 26 10:59:26 dvb: "/dev/dvb/adapter0" tuning via s2api to "12,565,000 kHz Horizontal (No satconf)" (1965000, 27500000 Baud, 2/3, SYS_UNDEFINED, QPSK)
Nov 26 10:59:46 dvb: "/dev/dvb/adapter0" tuning via s2api to "10,758,000 kHz Vertical (No satconf)" (1008000, 22000000 Baud, 7/8, SYS_UNDEFINED, QPSK)
Nov 26 11:00:07 dvb: "/dev/dvb/adapter0" tuning via s2api to "11,739,000 kHz Vertical (No satconf)" (1139000, 27500000 Baud, 3/4, SYS_UNDEFINED, QPSK)
Nov 26 11:00:26 dvb: "/dev/dvb/adapter0" tuning via s2api to "12,685,000 kHz Vertical (No satconf)" (2085000, 27500000 Baud, 3/4, SYS_UNDEFINED, QPSK)
Nov 26 11:00:46 dvb: "/dev/dvb/adapter0" tuning via s2api to "12,631,000 kHz Horizontal (No satconf)" (2031000, 6666000 Baud, 7/8, SYS_UNDEFINED, QPSK)
Nov 26 11:01:06 dvb: "/dev/dvb/adapter0" tuning via s2api to "12,168,000 kHz Vertical (No satconf)" (1568000, 27500000 Baud, 3/4, SYS_UNDEFINED, QPSK)
Nov 26 11:01:26 dvb: "/dev/dvb/adapter0" tuning via s2api to "10,862,000 kHz Horizontal (No satconf)" (1112000, 22000000 Baud, 5/6, SYS_UNDEFINED, QPSK)
Nov 26 11:01:47 dvb: "/dev/dvb/adapter0" tuning via s2api to "11,475,000 kHz Vertical (No satconf)" (1725000, 27500000 Baud, 3/4, SYS_UNDEFINED, QPSK)
<pre>

Is there a solution for this or has it been logged as a bug? Or am I maybe missing something altogether different? I also tried with dvbstream with the example from Vitaly and that did work.

First, what version of tvheadend are you running?

Version 2.12, got it from the repository with apt-get

Okee, in the latest git version some changes are made to handle dvb-s2 better. So if you can compile a version based on the latest git you might have better results.

Hein

Thanks! I will give it a shot and report back.

No improvement I'm afraid. But the fact that the "Muxes awaiting initial scan" stops at 5 is probably related to the last 5 log messages that mention "Front configuration failed -- Invalid argument, frequency: 140733195449032". I don't know if it is relevant, but I'm using a duo lnb from CanalDigitaal (Netherlands). I created one extra satellite config entry. Both are set to "Universal" LNB type, one for switchport 0, the other for port 1. But my guess is only one is correctly working as I only Astra 23.5 yields multiple muxes, Astra 19.2 only one.

This is the log from the console (the output in the browser is not different from earlier):

whiskey@Mythbox:~/tvheadend-build/andoma-tvheadend-9075408/build.Linux$ ./tvheadend -C[WARNING]:accesscontrol: Created default wide open access controle entry
[INFO]:dvb: Found adapter /dev/dvb/adapter0 (STB0899 Multistandard) via PCI
[INFO]:dvr: Creating new configuration ''
[WARNING]:dvr: Output directory for video recording is not yet configured for DVR configuration "". Defaulting to to "/home/whiskey/Videos". This can be changed from the web user interface.
[INFO]:CSA: Using SSE2 128bit parallel descrambling
[NOTICE]:START: HTS Tvheadend version 2.12.99 started, running as PID:5146 UID:1000 GID:1000, settings located in '/home/whiskey/.hts/tvheadend'
[INFO]:AVAHI: Service 'Tvheadend' successfully established.
[NOTICE]:dvb: Adapter "STB0899 Multistandard" mux autodiscovery set to: On
[NOTICE]:dvb: New mux "12,551,500 kHz Vertical (No satconf)" created by built-in configuration from "Astra-19.2E" 
[NOTICE]:dvb: New mux "10,758,000 kHz Vertical (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "10,788,000 kHz Vertical (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "10,802,000 kHz Horizontal (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "10,842,000 kHz Vertical (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "10,862,000 kHz Horizontal (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "11,475,000 kHz Vertical (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "11,515,000 kHz Horizontal (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "11,675,000 kHz Horizontal (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "11,739,000 kHz Vertical (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "11,798,000 kHz Horizontal (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "11,836,000 kHz Horizontal (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "11,875,000 kHz Horizontal (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "11,914,000 kHz Horizontal (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "11,992,000 kHz Horizontal (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "12,012,000 kHz Vertical (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "12,070,000 kHz Horizontal (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "12,168,000 kHz Vertical (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "12,525,000 kHz Horizontal (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "12,525,000 kHz Vertical (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "12,565,000 kHz Horizontal (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "12,565,000 kHz Vertical (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "12,630,000 kHz Vertical (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "12,631,000 kHz Horizontal (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "12,636,000 kHz Vertical (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "12,641,000 kHz Horizontal (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "12,644,000 kHz Horizontal (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "12,649,000 kHz Horizontal (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "12,661,000 kHz Horizontal (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "12,685,000 kHz Vertical (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "12,696,000 kHz Horizontal (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "12,711,000 kHz Horizontal (No satconf)" created by built-in configuration from "Astra-23.5E" 
[NOTICE]:dvb: New mux "12,725,000 kHz Vertical (No satconf)" created by built-in configuration from "Astra-23.5E" 
[ERROR]:dvb: "/dev/dvb/adapter0" tuning to "12,636,000 kHz Vertical (No satconf)" -- Front configuration failed -- Invalid argument, frequency: 140733195424032
[ERROR]:dvb: "/dev/dvb/adapter0" tuning to "12,641,000 kHz Horizontal (No satconf)" -- Front configuration failed -- Invalid argument, frequency: 140733195429032
[ERROR]:dvb: "/dev/dvb/adapter0" tuning to "12,644,000 kHz Horizontal (No satconf)" -- Front configuration failed -- Invalid argument, frequency: 140733195432032
[ERROR]:dvb: "/dev/dvb/adapter0" tuning to "12,661,000 kHz Horizontal (No satconf)" -- Front configuration failed -- Invalid argument, frequency: 140733195449032
[ERROR]:dvb: "/dev/dvb/adapter0" tuning to "12,696,000 kHz Horizontal (No satconf)" -- Front configuration failed -- Invalid argument, frequency: 140733195484032

Please let me know if there is anything else I can try and thanks for the help.

Remove the muxes that are not valid and then stop and start tvheadend.

I removed the five with the unknown status and restarted. Now the counter does go to zero, but the button "Map DVB services to channels" is still not enabled. Also all the entries in Multiplexes give "No signal" as status with 100% signal quality. The columns Network and MuxID remain empty, the column Satellite config shows "unset" for each entry.

Are there maybe other (console) command I can try to confirm or deny this is an issue with tvheadend? I'm new to the "watch-tv-on-linux" world so any pointers are much appreciated.

You can try these instructions:
http://linuxtv.org/wiki/index.php/Testing_your_DVB_device

Hein

Thanks for the pointer. I played around with it a bit and with scan I was able to create a channels.conf. Dvbscan wouldn't work ("Failed to set frontend"). I was then able to watch a channel with szap and mplayer. However, no HD channels were found (the linuxtv wiki mentions scan is not capable of that) so this might still be related to a dvb-s2 issue, but maybe not specific to tvheadend. Is tvheadend using its own code to scan or does it make use of existing utilities like (dvb)scan?

there is also scan-s2:
http://linuxtv.org/wiki/index.php/Scan-s2

Tvheadend is using it's own code to obtain the frequencies using the information that is contained in the dvb-stream. Based on that information tvheadend can get a list of frequencies where other muxes can be found. To avoid the "chicken-egg" problem at least one frequency needs to be known. That is what the "initial tuning files" are used for. Those are contained inside tvheadend and you can select them using the "select dvb network" option. Or you can manually add the first mux, and then it will use that to get the details.

I hope things are getting clear for you.

Hein

Thanks for the comments. I've tried different tracks the past week and although I couldn't get scan-s2 to work, I did make some progress. I never mentioned that I was running the latest Ubuntu (11.10) and it turns out that scanning success depends on the kernel you're using. I also tried scanning on a backup partition with an older kernel (I think it was 2.6.32-33) with which tvheadend did scan channels successfully (after installing s2-liplianin).

However, with kernel 3.0 I was able to scan perfectly with w_scan and that also got the HD channels which seemed to be missing in the tvheadend scan on the older kernel. I did not have to install additional drivers either as the liplianin were moved into the kernel.

I never got scanning in tvheadend with kernel 3.0 to work, but adding the muxes manually turned out to work just fine so I did that.

I'm now toying with oscam to get descrambling working and just found OpenElec which seems to be a perfect solution (and includes tvheadend) so I'll also give that a go to. Thanks for the help.

I Have the same problem with a TeviiS660 i build tvheadend from git.

hav can I fix this?

Hello,

I have exact the same error, 5 times a mux isn't valid with a line like:
Sep 26 18:59:27 dvb: "/dev/dvb/adapter0" tuning to "12,661,000 kHz Horizontal (Astra 23)" -- Front configuration failed -- Invalid argument, frequency: 206100
And i will not get "map DVB services to channels" button to enable.

I looked up all 5 frequencies and de-selected them from the Multiplexes page,saved the settings like that and restarted tvheadend ( sudo /etc/init.d/tvheadend restart ), it rescans the whole range again ( 4 sats is a very long wait )
To tell you upfront, i am not a linux wiz, i know the basics but that's it.

At the moment the system is again rescanning the whole range ( there goes another hour or two ) but my guess will be that the button won't get enabled again.
I'll add comments on that outcome as soon it is finished, in the meantime a request to have some error detection placed to skip over these time consuming errors.

Setup on which it runs :
MSI Ms-7529 motherboard ( intel chipset ) 1.9Ghz core 2 Duo with 2GB DDR2 ram.
Nvidia GT610 using the HDMI + audio to feed my TV.
Technisat 2HD PCI card connected to a DiSEqC switch with 4 LMB's

Software:
XBMCbuntu 11.0 downloaded 26-sep.
after which i ran :
sudo apt-get install nvidia-current-updates ( nvidia card update )

sudo add-apt-repository ppa:pulse-eight/pulse
sudo apt-get update
sudo apt-get install xbmc tvheadend xbmc-bin (getting the tvheadend version : HTS Tvheadend 2.99.53.4502158 )

score atm :

MUX's: 215

Muxes to scan : 137

As i suspected, the scan is done but the map DVB services to channels" button stays grayed out.
I noticed that "Currently tuned to:" keeps skipping over to all my LMB's : Astra 19, Astra 28, Astra 23 and Hotbird.
I do not get any -- Front configuration failed errors.
So what could be wrong ?
Added a screen shot of my General tab and my sat config tab.

This is a known bug and fixed in latest code and possibly 3.0, but I'm on phone and can't easily check.

Adam

Hi Adam,
Thanks for the quick reply.
Hope to see a solution to my problem as soon as you have the time ( won't keep you from work/private stuff )

PS: found one more strange thing which maybe be a part of the issue.
Scanning all 4 satellites i've only got one hit on the Astra 19 ( diseqc 0 ) while the other 3 are showing multiple frequencies.

Cheers.
Bart Smith

I think you misunderstood me, there is nothing to do. The problem is already fixed I just can't remember whether it was in the 3.0 release. But it is definitely in master.

Not sure about the second issue.

Adam

I'll to re-install tvheadend tomorrow, got to get some sleep first :)
if you can point me to the install i need to grab, I am new at this github since installing tvheadend acually.

Cheers,
Bart

There are currently no available packages, you'll have to build one yourself, see Packaging and Building

However if you're willing to wait we've now entered beta phase for 3.2 and I will hopefully be generating some beta packages today / tomorrow.

Adam

I am currently re-installing the system while writing a howto for the linux impared for myself and will post the final in this forum.
So i go for the packaging option and install it that way, waiting on the 3.2 beta which i will install on a clean re-install ( i don't mind re-installing as it help me learning Linux )
I'll keep you posted on the progress.

Cheers,
Bart