Tvheadend

Nicola Apicella wrote:

Hey guys!

I wanted to play around a bit with DVB-T2, which should be up and running (a trial run) where I'm living since a week or two. (Just in time for the UEFA Euro 2016!)
So I bought myself a "Hauppauge WinTV-soloHD"—mainly because everywhere it says it should run out of the box. (Cf. Linux TV https://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-soloHD as well as Hauppauge themselves http://www.hauppauge.co.uk/site/products/data_solohd.html#tabs-3 )

First things first: I'm running "HTS Tvheadend 4.0.9" on "Linux 4.4.0-22-generic #40~14.04.1-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux" (which is a Linux Mint 17.3). And yes, to be absolutely sure, I upgrade everything to the latest version; even the kernel.

Anyway, after inserting the stick, this is what I get:

[...]

And that's it. Nothing more. The USB device ID fits (and mtp failing is expected), but from experience I know I should be expecting a bit more after all that!

In fact, when I insert my trusty Hauppauge WinTV-HVR-930C, right after the USB discovery a whole bunch of other stuff "awakes": em28xx, em2884, tveeprom, usbcore, em28xx-audio.c, drxk, xc5000, …
And it instantly pops up in tvheadend. No such luck with the soloHD.

Did I miss a step? Am I forgetting something? Or is there something that needs to be set-up yet?

Any help would be greatly appreciated.
Nicola

Check your kernel has "si2168", "si2157" and "em28xx" modules (it should do if it's 4.0+)

sudo modinfo {si2168,si2157,em28xx}

Mark Clarkstone wrote:

Check your kernel has "si2168", "si2157" and "em28xx" modules (it should do if it's 4.0+)

As a matter of fact, all three of them are present.

Is there a way to "force" the system to load the stick or something? No idea why the other three DVB-USB sticks I own work without a hitch but this one doesn't. :-(

Nicola Apicella wrote:

Mark Clarkstone wrote:

Check your kernel has "si2168", "si2157" and "em28xx" modules (it should do if it's 4.0+)

As a matter of fact, all three of them are present.

Is there a way to "force" the system to load the stick or something? No idea why the other three DVB-USB sticks I own work without a hitch but this one doesn't. :-(

If you have those modules, they should just load and set up the device.. You could install the kernel source package and take a look if the source has the following lines from this patch, https://git.linuxtv.org/media_tree.git/commit/?id=1efc21701d94ed0c5b91467b042bed8b8becd5cc.

Ok, I looked into this on Ubuntu 16.04 (4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux) and the source doesn't have the required lines, 4.6.2 and 4.5.7 on kernel.org have the required lines whereas 4.4.13 doesn't..

Your only option is to upgrade your kernel or install/build the latest media_tree, maybe your apt sources have a newer kernel?

Hello!

Mark Clarkstone wrote:

Check your kernel has "si2168", "si2157" and "em28xx" modules (it should do if it's 4.0+)

As a matter of fact, all three of them are present.

Is there a way to "force" the system to load the stick or something? No idea why the other three DVB-USB sticks I own work without a hitch but this one doesn't. :-(

If you have those modules, they should just load and set up the device.. You could install the kernel source package and take a look if the source has the following lines from this patch, https://git.linuxtv.org/media_tree.git/commit/?id=1efc21701d94ed0c5b91467b042bed8b8becd5cc.

Ok, I looked into this on Ubuntu 16.04 (4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux) and the source doesn't have the required lines, 4.6.2 and 4.5.7 on kernel.org have the required lines whereas 4.4.13 doesn't..

Just to make sure I'm getting this right: Both my sources claim kernel support since 3.16 for the device—which it does, since the stick gets recognized. But to get it running, it also needs to know to load the corresponding modules—which fails because the patch you linked to is not included in kernel 4.4.0. (The patch is in fact way younger than the 4.4.0 release, as far as I can tell…)
Is that correct?

Your only option is to upgrade your kernel or install/build the latest media_tree, maybe your apt sources have a newer kernel?

The newest kernel my system offers is the one I have installed. On the other hand, just yesterday a new beta of Linux Mint (18.0) has been released, based on a much newer version of Ubuntu; the official release should be this month. (And yes, I checked: newer kernel version and everything! \o/ ).

So thanks for helping me understand how stuff works. :-)
I'll try and update to the beta (what could possibly go wrong… ;-) ) or just wait a bit. I've got plenty of projects on the backburner anyway. ^^ (I'll keep you guys posted unless I forget.)

Nicola Apicella wrote:

Hello!

Mark Clarkstone wrote:

Check your kernel has "si2168", "si2157" and "em28xx" modules (it should do if it's 4.0+)

As a matter of fact, all three of them are present.

Is there a way to "force" the system to load the stick or something? No idea why the other three DVB-USB sticks I own work without a hitch but this one doesn't. :-(

If you have those modules, they should just load and set up the device.. You could install the kernel source package and take a look if the source has the following lines from this patch, https://git.linuxtv.org/media_tree.git/commit/?id=1efc21701d94ed0c5b91467b042bed8b8becd5cc.

Ok, I looked into this on Ubuntu 16.04 (4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux) and the source doesn't have the required lines, 4.6.2 and 4.5.7 on kernel.org have the required lines whereas 4.4.13 doesn't..

Just to make sure I'm getting this right: Both my sources claim kernel support since 3.16 for the device—which it does, since the stick gets recognized.

The stick isn't recognised, but rather no drivers (modules) were loaded for it, the kernel sees it but has no clue how to handle it.

But to get it running, it also needs to know to load the corresponding modules—which fails because the patch you linked to is not included in kernel 4.4.0. (The patch is in fact way younger than the 4.4.0 release, as far as I can tell…)
Is that correct?

Yes. It can take a while before a driver/modules gets included, many end up in "staging" (for advanced kernel builders).

Your only option is to upgrade your kernel or install/build the latest media_tree, maybe your apt sources have a newer kernel?

The newest kernel my system offers is the one I have installed. On the other hand, just yesterday a new beta of Linux Mint (18.0)

This doesn't prevent you from building your own (it's easy as hell), while it has many pros, it has just as many cons!

has been released, based on a much newer version of Ubuntu; the official release should be this month. (And yes, I checked: newer kernel version and everything! \o/ ).

If it's based on 16.04 (what I'm running) the kernel may still be 4.4.x, but I could be wrong though.

So thanks for helping me understand how stuff works. :-)
I'll try and update to the beta (what could possibly go wrong… ;-) ) or just wait a bit. I've got plenty of projects on the backburner anyway. ^^ (I'll keep you guys posted unless I forget.)

Hey Guys,

i hope someone here can help me. I have exact the same problem but i want to run the tvheadend-version on my raspberry. Actually just for testing. Later it should work on my Synology DS414 where the tvheadend installation don't see the wintv soloHD-Stick.

So, my raspberry with jessie is up to date to latest kernel, latest dist-version and so on. Raspbian sees the soloHD stick but it don't finds drivers i think.
I wanted to install the dvb device drivers with the basic way like described here https://www.linuxtv.org/wiki/index.php/How_to_install_DVB_device_drivers#Retrieving_and_Building.2FCompiling_the_Latest_V4L-DVB_Source_Code (actually i'm not shure if the drives are in the git-source included or if i have to add these patch https://git.linuxtv.org/media_tree.git/commit/?id=1efc21701d94ed0c5b91467b042bed8b8becd5cc )

But the make-script brings the following error:

make -C /home/pi/media_build/v4l allyesconfig
make[1]: Entering directory '/home/pi/media_build/v4l'
No version yet, using 4.4.11+
make[2]: Entering directory '/home/pi/media_build/linux'
Applying patches for kernel 4.4.11+
patch -s -f -N -p1 -i ../backports/api_version.patch
patch -s -f -N -p1 -i ../backports/pr_fmt.patch
patch -s -f -N -p1 -i ../backports/debug.patch
patch -s -f -N -p1 -i ../backports/drx39xxj.patch
patch -s -f -N -p1 -i ../backports/v4.6_i2c_mux.patch
patch -s -f -N -p1 -i ../backports/v4.5_gpiochip_data_pointer.patch
patch -s -f -N -p1 -i ../backports/v4.5_get_user_pages.patch
patch -s -f -N -p1 -i ../backports/v4.5_uvc_super_plus.patch
patch -s -f -N -p1 -i ../backports/v4.4_gpio_chip_parent.patch
Patched drivers/media/dvb-core/dvbdev.c
Patched drivers/media/v4l2-core/v4l2-dev.c
Patched drivers/media/rc/rc-main.c
make[2]: Leaving directory '/home/pi/media_build/linux'
./scripts/make_kconfig.pl /lib/modules/4.4.11+/build /lib/modules/4.4.11+/build 1
Preparing to compile for kernel version 4.4.11
File not found: /lib/modules/4.4.11+/build/.config at ./scripts/make_kconfig.pl line 33, <IN> line 4.
Makefile:369: recipe for target 'allyesconfig' failed
make[1]: *** [allyesconfig] Error 2
make[1]: Leaving directory '/home/pi/media_build/v4l'
Makefile:26: recipe for target 'allyesconfig' failed
make: *** [allyesconfig] Error 2
can't select all drivers at ./build line 490.

I tried Google for different things but i don't really know what to do now. Which way is the correct one to get this needed files.
Maybe someone of you can help me?
Maybe someone of you also know what to do with my Synology to get it work with the soloHD?

Big thanks,
Florian

You're missing the kernel source..

Try using something like this to install it. https://github.com/notro/rpi-source/wiki

Hello,
Mark, thanks for your Link. I also got it working with this tut http://raspberrypi.stackexchange.com/questions/39284/how-to-setup-tvheadend-on-raspbian-so-that-i-can-record-tv-shows-streamed-by-hdh
Now dmesg says

[   24.581679] si2168 4-0064: found a 'Silicon Labs Si2168-B40'
[   24.582995] si2168 4-0064: Direct firmware load for dvb-demod-si2168-b40-01.fw failed with error -2
[   24.583118] si2168 4-0064: Direct firmware load for dvb-demod-si2168-02.fw failed with error -2
[   24.583149] si2168 4-0064: firmware file 'dvb-demod-si2168-02.fw' not found
[   24.598986] si2157 5-0060: found a 'Silicon Labs Si2157-A30'
[   24.650041] si2157 5-0060: firmware version: 3.0.5
[   24.650180] usb 1-1.2: DVB: adapter 0 frontend 0 frequency 0 out of range (42000000..870000000)
[   24.673885] si2168 4-0064: found a 'Silicon Labs Si2168-B40'
[   24.674009] si2168 4-0064: Direct firmware load for dvb-demod-si2168-b40-01.fw failed with error -2
[   24.674093] si2168 4-0064: Direct firmware load for dvb-demod-si2168-02.fw failed with error -2
[   24.674124] si2168 4-0064: firmware file 'dvb-demod-si2168-02.fw' not found
[   81.594417] TCP: request_sock_TCP: Possible SYN flooding on port 9981. Sending cookies.  Check SNMP counters.
[ 1277.977043] si2168 4-0064: found a 'Silicon Labs Si2168-B40'
[ 1277.977178] si2168 4-0064: Direct firmware load for dvb-demod-si2168-b40-01.fw failed with error -2
[ 1277.981620] si2168 4-0064: Direct firmware load for dvb-demod-si2168-02.fw failed with error -2
[ 1277.981672] si2168 4-0064: firmware file 'dvb-demod-si2168-02.fw' not found

But tvheadend finds 2 adapters:
Silicon Labs Si2168 DVB-C
Silicon Labs Si2168 DVB-T

So we can start.
Next problem, the scan don't find any Services on specified Muxes. Normaly it should find for example the new DVB-T2 HD channels in germany. With same usb-device and same antenna-position it finds the muxes in windows and dvbviewer. Also "old" DVB-T channels are not found.
Scan result always fails.

Any ideas?

Florian Hesse wrote:

Hello,
Mark, thanks for your Link. I also got it working with this tut http://raspberrypi.stackexchange.com/questions/39284/how-to-setup-tvheadend-on-raspbian-so-that-i-can-record-tv-shows-streamed-by-hdh
Now dmesg says
[...]

But tvheadend finds 2 adapters:
Silicon Labs Si2168 DVB-C
Silicon Labs Si2168 DVB-T

So we can start.
Next problem, the scan don't find any Services on specified Muxes. Normaly it should find for example the new DVB-T2 HD channels in germany. With same usb-device and same antenna-position it finds the muxes in windows and dvbviewer. Also "old" DVB-T channels are not found.
Scan result always fails.

Any ideas?

Firmware is missing xD you need to get those firmware files "dvb-demod-si2168-02.fw" is an older backup firmware, don't bother with that. you can find the firmware here https://github.com/LibreELEC/dvb-firmware/tree/master/firmware make sure you get the raw file (click on the filename in the list and press the raw button). https://github.com/LibreELEC/dvb-firmware/raw/master/firmware/dvb-demod-si2168-b40-01.fw

Thanks for that.
I tought media_build will do this things for me. Theses are the times where i know why linux is not consumer user compatible.

Thanks, it works now, finds muxes and so on.
Just Sat>ip is not working for the moment. But i will get it running i think.

Any idea how to get the soloHD also working on my synology NAS?
Maybe i also just need to place a firmware anywhere.

Hello,
I'm using the SoloHD-Stick with Libreelec and it worked from beginning - except DVB-T2.

There's a thread in this forum http://forum.kodi.tv/showthread.php?tid=278293

Does anybody know how to get it working?

today i've updated my raspbian. The updated log says there where some kernel updates.

Since this update and reboot-process, tvheadend don't finds the soloHD again.
The firmware is still present and i reinstalled media_build with the new kernel files.

Does anyone know how i can get it to work again?