tvheadend does not find any muxes

Jakob Pinterits

Hello everyone!

I'm trying to set up Tvheadend on my HTPC. Installation was without any problems, but I cannot get Tvheadend to find any muxes/channels.

My card is a DVBSKY S960.

Steps taken:
* Install OS (Tried Ubuntu, Fedora, Debian and, currently Archlinux. Ubuntudid work, but I would prefer to use arch instead. The problem is the same for all operating systems, except Ubuntu, obviously.)
* Install drivers from website, or on those Systems with linux >= 3.18, do nothing, as linux already comes with the drivers. (Though I did also try with the drivers.)
* Install "linux firmware" package
* Install Tvheadend
* Enable the adapter in the web interface and use "Add DVB Network by location..."

Since the card did work under Ubuntu I know its not a Hardware or Signal problem.

I have no knowledge whatsoever when it comes to DVB, so this is very confusing for me. Any help is greatly appreciated.

Thanks

ProfYaffle

Difficult to say without seeing some logs/messages. I'd offer similar pointers as I just did on a different thread, e.g.

* check you have the firmware (not just that the package is installed)
* see what syslog/dmesg tells you as the card is initialised
* check that '... location' is giving you valid information (frequencies, configuration) for your transmitter
* see if w_scan can see the tuner and use it
* see what errors/messages appear as you try to use it in tvh (bottom right of web screen, little arrows, cog)

Jakob Pinterits

Thank you for your reply.

> check you have the firmware (not just that the package is installed)
dmesg reported errors before installing the firmware packages. These are gone now. Is there any other way to check whether the firmware is ok?
dmesg output: http://pastebin.com/hmvKvTGn

(What is the preferred way of posting long output?)

> see what syslog/dmesg tells you as the card is initialised

It does. (See the dmesg output.)

> check that '... location' is giving you valid information (frequencies, configuration) for your transmitter

Could you be more specific please?

> see if w_scan can see the tuner and use it
w_scan runs into problems. I'll do some recherche on this, but here is the output for now:
w_scan --frontend c --country AT: http://pastebin.com/B5GtLspQ

w_scan --frontend s --satellite S19E2: http://pastebin.com/FxYMr7Fa

> see what errors/messages appear as you try to use it in tvh (bottom right of web screen, little arrows, cog)

There are no messages besides things like "Apr 02 13:04:13.282 dvb: Adapter "Silicon Labs Si2168" Disabled" when I toggle options.

I'll try to get w_scan to work, but given my lack of experience with this topic I'm not exaclty optimistic.

ProfYaffle

You can check the firmware is there by looking in /lib/firmware - looks like you need dvb-fe-ds3103.fw. dmesg should show a successful firmware load as well.

My 'location' comment - you're selecting a location that defines the muxes you'll look for (e.g. what DVB-T transmitter, what DVB-C carriers, what DVB-S satellite). When you select that, you should get a pre-populated list of muxes... it's worth checking one or two to see if they're valid, as the open-source lists do go out of date.

If w_scan is struggling, then the problem is before tvh ever starts, which suggests hardware (including USB port/hub?) or driver (including kernel/modules).

And pastebin is fine for logs - better than cluttering up the forum.

EDIT

Just looked at your dmesg in detail - you have a lot of messages such as:

[16260.696799] si2168 8-0064: firmware file 'dvb-demod-si2168-a30-01.fw' not found
[16260.704049] si2157 12-0060: firmware file 'dvb-tuner-si2158-a20-01.fw' not found

[18180.277209] i2c i2c-9: m88ds3103: firmare file 'dvb-demod-m88ds3103.fw' not found

... which suggests your problem. A good source for specific firmwares is OpenElec, as you can download them as raw files or wget them and install them one at a time.

https://github.com/OpenELEC/dvb-firmware/tree/master/firmware

Jakob Pinterits

Yay, I've made progress!

After getting the firmware and (3 files were missing) w_scan started printing very promising output:
w_scan --frontend c --country AT: http://pastebin.com/fnjBRe2p

w_scan --frontend s --satellite S19E2: http://pastebin.com/PuKBUuDY

However, my original problem remains: I still haven't any muxes in Tvheadend.
> My 'location' comment - you're selecting a location that defines the muxes you'll look for (e.g. what DVB-T transmitter, what DVB-C carriers, what DVB-S satellite). When you select that, you should get a pre-populated list of muxes... it's worth checking one or two to see if they're valid, as the open-source lists do go out of date.
Using "Add DVB Network by location..." does not actually add any muxes. The "Multiplexes" tab doesn't show anything and the "Information and capabilities" window on the right also says "Muxes: 0", as well as "Muxes awaiting initial scan: 0". I've tried several locations now, not only the one I'll actually use. (The log on the bottom does not show any error though.)

ProfYaffle

Okay, so it sounds like your tuner is closer to working (the w_scan) result but the muxes are missing.

How to set it up from here depends on what tvh version you're using, but (assuming this is a DVB-S tuner) it's broadly pick a satellite and sit back. If that isn't working, look up a couple of specific muxes on your target satellite and add them by hand - most settings can be auto beyond the base frequency/bandwidth/carrier mode - and then idle scanning should find everything else over time.

It's odd that you're not getting anything, though, as satellite frequencies don't go out of date that radically, that quickly. Can you post a screenshot of the 'by location' setup and tuner config?

Jakob Pinterits

I've looked up some muxes and added them to tvh. Initially, this did nothing at all, but after a reboot all but one of them were gone and lo! Tvh suddenly started finding muxes on its own, just as you said it would.

I've mapped the channels and have not yet encountered any problems.

> How to set it up from here depends on what tvh version you're using
Eh, this is a strange one. "tvheadend --version" returns "tvheadend: version" and I can't spot any version information on the "about" page in the web interface.

For what it's worth, the package version is 3.4.27 (https://aur.archlinux.org/packages/tvheadend/).

> assuming this is a DVB-S tuner
Apparently I wasn't clear enough. This is a DVBSKY S960, which sports a satellite as well as a cable tuner. The satellite tuner is working now, thanks to you, but I still cannot get anything from the cable tuner.

Since I couldn't find any mux data for the cable tuner I ran "w_scan --frontend c --country AT --output-initial" which gave me a list with entries like this one:

C 314000000 6900000 AUTO QAM256 # Kabelplus

I then tried the same method as before and added a few muxes with the data from this list, but to no avail.

> Can you post a screenshot of the 'by location' setup and tuner config?
Your wish is my command. The screenshots are of the cable tuner, as the other one does work now.
!screenshot_overview.png!

!screenshot_add_network.png!

My sincere thanks for getting the Satellite part to run. Still, I do want to make the cable tuner work, so I can watch the encrypted "ORF" channels. Also this will allow me to watch one channel while recording on a second one (I hope).

ProfYaffle

Glad that half of it is working, but I'm perhaps going to have to let you down on the other part - DVB-C is a closed book to me.

The screenshots look okay to my naïve eyes... all I can suggest is double-checking the frequencies and parameters of the 7 muxes you have (especially units - anything that may be baud versus kilobaud and similar) - after that, it's back to log files to check that side of the tuner has initialised properly and w_scan to see if something else can lock on to any services/channels.

EDIT

Found what appear to be updated details for Salzburg - DVB-C seems to be location-independent in many countries, though, and you did have at_All as the location, so these may be valid for you. It's simply possible that 3.4.x is shipped with/downloading out-of-date information for the muxes.

EDIT2

<Seufz...>

http://forum.team-mediaportal.com/threads/new-tuningdetails-f%C3%BCr-dvbc-austria-salzburgag.128501/<<

Jakob Pinterits

Thank you pal.

This HTPC is actually for my parents and as I'll be heading to my flat again tomorrow it was very important for me to get it at least 'mostly running' as long as I have physical access to it. Thanks to you I am in such a semi-working state and getting DVB-C to work is not a priority - I'm sure I'll manage to get it running at some point.

Jan Smith

Hi!

Any news on resolving this problem (dvb-c)?

I have the same problem with my usb-stik from MyGica.

It shows up in TVH but it will not scan any muxes. I inserted a mux which I now work, since I´ve tried on similar system with a Sundtek dvb-c stick.

I´ve tested on openelec with tvh 3.9.2765, on Ubuntu (kernel 3.19) - with tvh 3.9 - 4.0.5.

Shows up in both systems, but the mux will not scan.

I guess this is a TVH issue since it´s the same problem on different systems.

Jakob Pinterits

Greetings!
I fear there isn't anything new. I haven't had much time to work on this though and hope to change that in the comming weeks.

I'll let you know should I come upon anything interesting.

I also intend to try MythTV to see whether this issue is TVH specific.

Jan Smith

Got it working in OpenElex 5.0.8 with kernel 3.17.8 and TVH 3.9.2765.

I didn´t know what I did, but suddenly all muxes where installed. Have been trying for a long time now, after that, to make it work on my ubuntu server.

Still not working on Ubuntu. Tried with most combination.

Found out that when this stick is inserted along with other usb-sticks, ie. Sundtek, they will not scan on OpenElec, but when I unplugged the Sundtek stick, and deleted all settings before setting up new one, it started working. (ps. did try to delete all settings when both sticks where inserted. No Muxes scanned)
<<

Jan Smith

Tried my working TVH settings from OpenElec system, onto my ubuntu system.

All muxes fails.

Does anyone know what logs I can provide, so that the team can implement this stick. It runs fine on TVH compiled for OpenElec.

ProfYaffle

You can start with syslog. You can switch debugging on via the web interface (lower right, arrows, cog) and get a bit more, or you can set DEBUG in /etc/defaults/tvheadend - that will output a bit more.

You can also trace trace logging - I believe you need to build a version with --enable-trace, though, but I can give you an Ubuntu deb if necessary. That will then generatea lot of information to see what's going on.

What kernel is you Ubuntu system, though (uname -a)?

And what precise stick is it?

I'd like to see what syslog/dmesg says as the stick is inserted - it sounds like a firmware/initialisation issue to me.

Jan Smith

http://www.mygica.com/TV-Tuner/DVB_T2_tv_Stick_63.html

http://www.aliexpress.com/item/dvb-t2-receiver-GENIATECH-Mygica-USB-TV-Stick-T220-DVB-T2-Tuner-DVB-C-DVB-T/699124717.html

OpenElec system with uname -a:
Linux TVHeadend 3.17.8 #1 SMP Tue Mar 31 21:18:50 CEST 2015 x86_64 GNU/Linux

See pics for TVH details.

TVHeadend:~ # dmesg | grep usb
[ 0.000000] Kernel command line: root=/dev/ram0 rdinit=/init usbcore.autosuspend=-1 BOOT_IMAGE=/KERNEL boot=LABEL=System disk=LABEL=Storage ssh quiet
[ 0.376846] usbcore: registered new interface driver usbfs
[ 0.376846] usbcore: registered new interface driver hub
[ 0.376846] usbcore: registered new device driver usb
[ 0.653355] usbcore: registered new interface driver rtsx_usb
[ 0.846195] usbcore: registered new interface driver uas
[ 0.846236] usbcore: registered new interface driver usb-storage
[ 0.848310] usbcore: registered new interface driver usbhid
[ 0.848312] usbhid: USB HID core driver
[ 1.380126] usb 3-5: new low-speed USB device number 2 using ohci-pci
[ 2.123373] usb 4-1: new full-speed USB device number 2 using ohci-pci
[ 2.628488] usb 4-1.1: new full-speed USB device number 3 using ohci-pci
[ 2.818545] usb 4-1.2: new full-speed USB device number 4 using ohci-pci
[ 2.933998] input: HID 05ac:820a as /devices/pci0000:00/0000:00:06.0/usb4/4-1/4-1.2/4-1.2:1.0/0003:05AC:820A.0002/input/input3
[ 2.934144] hid-generic 0003:05AC:820A.0002: input,hidraw0: USB HID v1.11 Keyboard [HID 05ac:820a] on usb-0000:00:06.0-1.2/input0
[ 3.005559] usb 4-1.3: new full-speed USB device number 5 using ohci-pci
[ 3.116954] input: HID 05ac:820b as /devices/pci0000:00/0000:00:06.0/usb4/4-1/4-1.3/4-1.3:1.0/0003:05AC:820B.0003/input/input4
[ 3.117157] hid-generic 0003:05AC:820B.0003: input,hidraw1: USB HID v1.11 Mouse [HID 05ac:820b] on usb-0000:00:06.0-1.3/input0
[ 7.662592] usbcore: registered new interface driver btusb
[ 7.695585] usb 4-1.2: USB disconnect, device number 4
[ 7.941474] usb 4-1.3: USB disconnect, device number 5
[ 263.873428] usb 1-7: new high-speed USB device number 3 using ehci-pci
[ 263.999006] usb 1-7: string descriptor 0 malformed (err = -61), defaulting to 0x0409
[ 264.015943] dvb-usb: found a 'Mygica T230 DVB-T/T2/C' in warm state.
[ 264.253462] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 264.269802] usb 1-7: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)...
[ 264.270987] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:04.1/usb1/1-7/input/input9
[ 264.271189] dvb-usb: schedule remote query interval to 100 msecs.
[ 264.272196] dvb-usb: Mygica T230 DVB-T/T2/C successfully initialized and connected.
[ 264.272230] usbcore: registered new interface driver dvb_usb_cxusb
[ 266.376299] usb 1-7: DVB: adapter 0 frontend 0 frequency 0 out of range (110000000..862000000)
[ 1536.873477] usb 1-7: USB disconnect, device number 3
[ 1536.920118] Modules linked in: si2157 si2168 i2c_mux dvb_usb_cxusb dib0070 dvb_usb rc_core dvb_core snd_hda_codec_realtek snd_hda_codec_generic nvidia(PO) b43 bcma mac80211 firewire_ohci cfg80211 firewire_core crc_itu_t btusb bluetooth snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm uvesafb
[ 1536.920200] [<ffffffffa0053eb7>] ? dvb_usb_fe_sleep+0x2d/0x44 [dvb_usb]

[ 1536.920489] usb 1-7: dvb_frontend_stop: warning: thread ffff8800b9f33560 won't exit

Ubuntu system with uname -a:
Linux PlexMediaServer 3.19.0-22-generic #22~14.04.1-Ubuntu SMP Wed Jun 17 10:03:13 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Further information will come, when I insert the stick to this system.

ProfYaffle

Quick thought - the link you gave lists "T230/T220A", but the linuxtv page (http://www.linuxtv.org/wiki/index.php/Geniatech_T230) says "Don't confuse this with Geniatech T220 or T220A that are the earlier models of the same product". So we need to dig alittle further to know which it is.

Next thought is that perhaps it isn't supported by 3.19 as a result. As such, you need the drivers - which OE almost certainly has, as it has a later version of the media_tree or some other custom drivers. Example: https://bitbucket.org/CrazyCat/linux-tbs-drivers/, "baca66b cxusb: Geniatech T230 support".

That's where I'd start looking. I suspect you'll see that syslog on your Ubuntu system isn't initialising the stick properly despite the kernel version, but let's see...

Jan Smith

PlexMediaServer:~$ dmesg | grep usb
[ 0.188287] usbcore: registered new interface driver usbfs
[ 0.188292] usbcore: registered new interface driver hub
[ 0.188304] usbcore: registered new device driver usb
[ 0.482614] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 0.482883] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber= 1
[ 0.483417] usb usb1: Product: xHCI Host Controller
[ 0.483683] usb usb1: Manufacturer: Linux 3.19.0-22-generic xhci-hcd
[ 0.483954] usb usb1: SerialNumber: 0000:00:14.0
[ 0.488487] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[ 0.488783] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber= 1
[ 0.489299] usb usb2: Product: xHCI Host Controller
[ 0.489561] usb usb2: Manufacturer: Linux 3.19.0-22-generic xhci-hcd
[ 0.489823] usb usb2: SerialNumber: 0000:00:14.0
[ 0.508983] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[ 0.509266] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber= 1
[ 0.509807] usb usb3: Product: EHCI Host Controller
[ 0.510082] usb usb3: Manufacturer: Linux 3.19.0-22-generic ehci_hcd
[ 0.510356] usb usb3: SerialNumber: 0000:00:1a.0
[ 0.524965] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
[ 0.525237] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber= 1
[ 0.525756] usb usb4: Product: EHCI Host Controller
[ 0.525993] usb usb4: Manufacturer: Linux 3.19.0-22-generic ehci_hcd
[ 0.526233] usb usb4: SerialNumber: 0000:00:1d.0
[ 0.820649] usb 3-1: new high-speed USB device number 2 using ehci-pci
[ 0.836640] usb 4-1: new high-speed USB device number 2 using ehci-pci
[ 0.953009] usb 3-1: New USB device found, idVendor=8087, idProduct=8008
[ 0.953346] usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 0.968835] usb 4-1: New USB device found, idVendor=8087, idProduct=8000
[ 0.969196] usb 4-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1.240663] usb 4-1.6: new high-speed USB device number 3 using ehci-pci
[ 1.333555] usb 4-1.6: language id specifier not provided by device, defaulti ng to English
[ 1.336442] usb 4-1.6: New USB device found, idVendor=0572, idProduct=c688
[ 1.336443] usb 4-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber =3
[ 1.602679] dvb-usb: found a 'Mygica T230 DVB-T/T2/C' in warm state.
[ 1.836302] dvb-usb: will pass the complete MPEG2 transport stream to the sof tware demuxer.
[ 1.843011] usb 4-1.6: DVB: registering adapter 0 frontend 0 (Silicon Labs Si 2168)...
[ 1.843294] input: IR-receiver inside an USB DVB receiver as /devices/pci0000 :00/0000:00:1d.0/usb4/4-1/4-1.6/input/input12
[ 1.843431] dvb-usb: schedule remote query interval to 100 msecs.
[ 1.843501] dvb-usb: Mygica T230 DVB-T/T2/C successfully initialized and conn ected.
[ 1.843523] usbcore: registered new interface driver dvb_usb_cxusb
[ 6.175488] usb 4-1.6: DVB: adapter 0 frontend 0 frequency 0 out of range (11 0000000..862000000)
[ 387.109983] dvb-usb: bulk message failed: -71 (1/0)
[ 387.195027] usb 4-1.6: USB disconnect, device number 3
[ 387.218444] Modules linked in: des3_ede_x86_64 des_generic md4 si2157 si2168 i2c_mux snd_hda_codec_hdmi dvb_usb_cxusb dib0070 dvb_usb dvb_core rc_core intel_ rapl iosf_mbi x86_pkg_temp_thermal dcdbas intel_powerclamp coretemp kvm_intel kv m crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw g f128mul glue_helper ablk_helper cryptd snd_hda_codec_realtek snd_hda_codec_gener ic i915 serio_raw snd_hda_intel snd_hda_controller snd_hda_codec drm_kms_helper snd_hwdep snd_pcm lpc_ich drm snd_timer mei_me snd mei soundcore i2c_algo_bit 82 50_fintek video mac_hid nls_utf8 cifs fscache lp parport e1000e psmouse ahci ptp libahci pps_core
[ 387.220428] [<ffffffffc025c4d7>] dvb_usb_fe_sleep+0x37/0x60 [dvb_usb]
[ 387.231162] usb 4-1.6: dvb_frontend_stop: warning: thread ffff8800d9a5bae0 wo n't exit
[ 4857.097589] Modules linked in: des3_ede_x86_64 des_generic md4 si2157 si2168 i2c_mux snd_hda_codec_hdmi dvb_usb_cxusb dib0070 dvb_usb dvb_core rc_core intel_ rapl iosf_mbi x86_pkg_temp_thermal dcdbas intel_powerclamp coretemp kvm_intel kv m crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw g f128mul glue_helper ablk_helper cryptd snd_hda_codec_realtek snd_hda_codec_gener ic i915 serio_raw snd_hda_intel snd_hda_controller snd_hda_codec drm_kms_helper snd_hwdep snd_pcm lpc_ich drm snd_timer mei_me snd mei soundcore i2c_algo_bit 82 50_fintek video mac_hid nls_utf8 cifs fscache lp parport e1000e psmouse ahci ptp libahci pps_core

Jan Smith

The dmesg above shows what happens when initializing on startup. As you can see I also unplugged the device later on.

The dvb module seems to be initialzed as normal.

ProfYaffle

Hmmmm. You have a few errors in there, but the OE and Ubuntu logs look broadly similar, don't they.

Dumb question time: the adapter isenabled in tvheadend, isn't it? And associated with the right network definition?

Tvheadend doesn't try to do much with the adapters other than 'use them' - everything else is an OS issue.

The logs don't mention firmware - do you have both dvb-demod-si2168-b40-01.fw and dvb-tuner-si2158-a20-01.fw installed? (ref: http://www.linuxtv.org/wiki/index.php/Geniatech_T230).

After that... I'd try w_scan or similar (to see if any other application can access the tuner) and/or update V4L (just to make sure it's not a kernel/driver dependency issue: http://www.linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers#Retrieving_and_Building.2FCompiling_the_Latest_V4L-DVB_Source_Code).

Jan Smith

Found a solution :)

Tried first with the original git from linux.tv but got compilation errors. Then next I tried with the git from CrazyCat which also gave me compilation errors. I also did not want to install all unnecessary drivers from both those git´s. The "make menuconfig" command did not work either.

I noticed from this page http://www.linuxtv.org/wiki/index.php/Geniatech_T230 the following lines:
"Firmware for both the demodulator and tuner are necessary. OpenELEC dvb-firmware collection includes firmwares for this device too.
dvb-demod-si2168-b40-01.fw
dvb-tuner-si2158-a20-01.fw

Place the 2 firmware files in /lib/firmware."

When I placed those 2 files taken from: https://github.com/OpenELEC/dvb-firmware/tree/master/firmware I got an error saying "Could not download dvb-tuner-si2158-a20-01.fw"

Then I came up with this good idea.

After a lot testing and compiling I went for the drivers in OE. I just copied them out of my working OE setup and into /lib/firmware on my Ubuntu.

And VOILA, all muxes scanned.

Maybe OE makes their own fw files, or have a more up to date driver collection?
<<