Project

General

Profile

Rasp. Pi with Triplestick 292e: DVB-C & Frontend. Configuration failed.

Added by Robin A. Jensen about 9 years ago

Hello all of you.
I hope some one can help me with this problem, that i've spend many hours to solve.
I've have a Triplestick 292e dvb-t/t2/c connectet to my Raspberry Pi 2 and in some way it works fine with tvheadend.
But only with dvb-t and a antenna. I also have cable-tv but headend can't find any service at all.
So many hours used to figure out why?
I've have done a scan with w-scan and it have found channels on my cable-tv, so my attention went back to headend and i found this in the system log window:

Sep 19 05:56:35.280 dvb: Adapter "Silicon Labs Si2168" Enabled
Sep 19 05:56:44.392 dvb: "/dev/dvb/adapter0" tuning to "143,000 kHz" -- Front configuration failed -- Invalid argument, frequency: 143000000

In w_scan:
dumping lists (224 services) : (just a cutout)
Charli;YouSee:143000:M64:C:6875:2860=27:2861=dan;2866:2862:500,5601:2860:65024:1020:0

My provider info: 143000 kHz, QAM64, Symbolrate:6875. Original Network ID: 100.
Raspberry Pi2: Raspbian up to date.
tvheadend version 3.4~wheezy.

So i could really need a little help here.
Is it a bug or is there some thing i've should have done some way down the line?
I been reading many tutorial / instructions and all of them have been followed.


Replies (8)

RE: Rasp. Pi with Triplestick 292e: DVB-C & Frontend. Configuration failed. - Added by Prof Yaffle about 9 years ago

I'd immediately suggest trying a later build - 4.0 or 4.1-master. 3.4 is getting really old now, and all development is going into 4.x, so you're far more likely to (a) be able to find any bugs if it is a bug, plus (b) get them fixed.

My guess is that it isn't the frequency that's wrong - there's probably something else incorrect in the mux definitions for your DVB-C provider, and that's what's choking. You may need to check the mux configurations, and perhaps add them manually (or add one and let the others get discovered automatically) - at least, that's how -S and -T work, so I'm presuming the same for -C.

RE: Rasp. Pi with Triplestick 292e: DVB-C & Frontend. Configuration failed. - Added by Robin A. Jensen about 9 years ago

Prof Yaffle wrote:

I'd immediately suggest trying a later build - 4.0 or 4.1-master. 3.4 is getting really old now, and all development is going into 4.x, so you're far more likely to (a) be able to find any bugs if it is a bug, plus (b) get them fixed.

My guess is that it isn't the frequency that's wrong - there's probably something else incorrect in the mux definitions for your DVB-C provider, and that's what's choking. You may need to check the mux configurations, and perhaps add them manually (or add one and let the others get discovered automatically) - at least, that's how -S and -T work, so I'm presuming the same for -C.

I'm not quit sure hoq to get a newer version. I've used apt-get and ended up with this version.
So i've might to have to compile a newer version - Is that what you are saying..? :-)
I-m not sure how to do that, but are willing to give it a try.

RE: Rasp. Pi with Triplestick 292e: DVB-C & Frontend. Configuration failed. - Added by Robin A. Jensen about 9 years ago

gary tan wrote:

have a look here and see if theres any posts that help

https://tvheadend.org/boards/4/topics/13782

I-ve followed this instruction:
@wget https://github.com/OpenELEC/dvb-firmware/blob/master/firmware/dvb-demod-si2168-02.fw -O /lib/firmware/dvb-demod-si2168-02.fw

Should be

.. https://github.com/OpenELEC/dvb-firmware/blob/master/firmware/dvb-demod-si2168-02.fw?raw=true ...
@
And i also downloaded: dvb-firmware/firmware/dvb-demod-si2168-b40-01.fw
from the same github.
Now tvheadend creates this error, when creating a new MUX:
Sep 19 17:26:02.982 web interface: Unable to create mux on Silicon Labs Si2168: Invalid FEC

This happends for all options: none, auto, 2/3

Is it possible to start all over again, this time with a working set of firmware and tvheadend..?
I've only found instructions where everything a working and no trouble solution at all.

RE: Rasp. Pi with Triplestick 292e: DVB-C & Frontend. Configuration failed. - Added by Mark Clarkstone about 9 years ago

Robin A. Jensen wrote:

Prof Yaffle wrote:

I'd immediately suggest trying a later build - 4.0 or 4.1-master. 3.4 is getting really old now, and all development is going into 4.x, so you're far more likely to (a) be able to find any bugs if it is a bug, plus (b) get them fixed.

My guess is that it isn't the frequency that's wrong - there's probably something else incorrect in the mux definitions for your DVB-C provider, and that's what's choking. You may need to check the mux configurations, and perhaps add them manually (or add one and let the others get discovered automatically) - at least, that's how -S and -T work, so I'm presuming the same for -C.

I'm not quit sure hoq to get a newer version. I've used apt-get and ended up with this version.
So i've might to have to compile a newer version - Is that what you are saying..? :-)
I-m not sure how to do that, but are willing to give it a try.

Quick & Easy guide to building Tvheadend on a RPi2.

sudo apt-get install git build-essential debhelper pkg-config fakeroot
git clone https://github.com/tvheadend/tvheadend.git build/tvheadend/master
cd build/tvheadend/master
./Autobuild.sh 
What each lines does.
  • 1 Installs a few dependencies (you'll need to install some more later on).
  • 2 Clones the Tvheadend master branch from github & places it in build/tvheadend/master.
  • 3 Changes directory to the above path.
  • 4 Runs the Autobuild script that will build a debian package so that you can install it in a nice and neat way.

Other info.
The Autobuild.sh script will complain about other missing dependencies you need to install those (using sudo apt-get install) and then run the script again.
Once the build has completed you'll find the built debian package (E.g tvheadend_4.1-368~geeda7d7_armhf.deb) in build/tvheadend.

You can then install it (and the debug package) using.

cd build/tvheadend
sudo dpkg -i tvheadend*.deb

Also you may want to start a new configuration from scratch so remove /home/hts/.hts before installing to avoid issues later on (configuration issues caused by migration of old 3.4 config).

RE: Rasp. Pi with Triplestick 292e: DVB-C & Frontend. Configuration failed. - Added by Robin A. Jensen about 9 years ago

Thank You Mark.
That was one step closer to my goal.
Your explanation was a great help.
Tvheadend is installed. I have not used it with DVB-t, but i'll think it works.
This solution created a new problem.
In tvheadend under tab for DVB Inputs /dev/adapter0 only shows DVB-T and DVB-T2 / DVB-C is missing.
As i can see there is a solution to it, as it is a driver issue, at least i think.
So i've found, that other user's are pointin at blog.palossaari and driver from his git.

[[http://blog.palosaari.fi/2014/04/naked-hardware-15-pctv-triplestick-292e.html]] <- seems to be some of the first time around with 292e. Not sure about nessacarity to extract firmware from cd..?

So i've found this:
[[http://git.linuxtv.org/cgit.cgi/anttip/media_tree.git/log/?h=pctv_292e]]
And there is si2168: add support for DVB-C (annex A version) <- My provider use that as DVB-C.
Also: si2168: Silicon Labs Si2168 DVB-T/T2/C demod driver.

And as the newbie I am - then i got stuck again.... :-(
How do i obtain this fine piece of driver..?
Do i need to do some compile and what to download..?

RE: Rasp. Pi with Triplestick 292e: DVB-C & Frontend. Configuration failed. - Added by Prof Yaffle about 9 years ago

IF you need it and IF it will help and IF it doesn't break anything, you'd build media_tree as per these instructions:

http://www.linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers

http://git.linuxtv.org/cgit.cgi/media_tree.git/about/

I put the IFs in there deliberately, as I haven't followed the full thread plus links to know if that's likely to be your issue. It's unlikely to break anything, though.

EDIT

Expanding on that - the link you gave was to the stuff that's included in the Linux kernel, so whether they're in yours depends on the kernel version you currently have. If the code is included already, then the links above won't really change anything; if, however, you have an older kernel, then those links will help you build the drivers as an addon to whatever your kernel supports already. The other obvious alternative is to update your kernel to something more recent.

RE: Rasp. Pi with Triplestick 292e: DVB-C & Frontend. Configuration failed. - Added by Robin A. Jensen about 9 years ago

Prof Yaffle wrote:

IF you need it and IF it will help and IF it doesn't break anything, you'd build media_tree as per these instructions:

http://www.linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers

http://git.linuxtv.org/cgit.cgi/media_tree.git/about/

I put the IFs in there deliberately, as I haven't followed the full thread plus links to know if that's likely to be your issue. It's unlikely to break anything, though.

EDIT

Expanding on that - the link you gave was to the stuff that's included in the Linux kernel, so whether they're in yours depends on the kernel version you currently have. If the code is included already, then the links above won't really change anything; if, however, you have an older kernel, then those links will help you build the drivers as an addon to whatever your kernel supports already. The other obvious alternative is to update your kernel to something more recent.

Thank you Prof Yaffle.
I'll look into it, even as I seem to be out on deep water here. :) But i'll give it a try.

To get me self on the way, i did make a new system with OSMC. I've installed tvheadend og got it to work..! (/)
In DVB Tab Adapter0 now shows DVB-T and DVB-C. Further more and most important, there are service's available. :P
It runs with a little pixelering. But is has not yet been able to stream smooth. Very bad lagging while using WLAN. It might been better if use LAN instead, but not sure and haven't testet it yet.

I'm using the exactly same firmware version, so these things are the different:

-----------------------------------------------------------------------------------------------------------<

  1. Raspbian

Linux version 4.1.7-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease) (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #815 SMP PREEMPT Thu Sep 17 18:34:33 BST 2015

  1. Firmware / Driver f.292e
    [ 0.268659] raspberrypi-firmware soc:firmware: Attached to firmware from 2015-09-18 15:20
    [ 21.317955] si2168 4-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
    [ 21.582794] si2168 4-0064: firmware version: 4.0.4
    [ 21.636735] si2157 5-0060: firmware version: 3.0.5
  1. tvheadend
    tvheadend: version 4.1-438~g7b32791
  1. OSMC

Linux version 4.1.5-1-osmc (root@vero) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP PREEMPT Wed Aug 19 18:37:30 UTC 2015

  1. Firmaware / Driver f. 292e
    [ 0.321323] raspberrypi-firmware soc:firmware: Attached to firmware from 2015-08-20 17:56
    [ 19.321749] si2168 4-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
    [ 19.568116] si2168 4-0064: firmware version: 4.0.4
    [ 19.622038] si2157 5-0060: firmware version: 3.0.5
  1. tvheadend
    tvheadend: version 4.0.5

-------------------------------------------------------------------------------------------------------------<

I wunder if is in tvheadend newer version, where something is missing? Apparently as I can read other users have the same experience with lack of DVB-C after an update.
I did consider to compile tvheadend 4.0.5, but got lost in git repository and could't really find the branch. :)

    (1-8/8)