No channel scan on a archlinux raspberry pi 2 system

Problem:
I want to set up Tvheadend on a Raspberry Pi 2 with Archlinux because Archlinux is the fastest system booting and running. IMHO all hardware and drivers are ok. The log files and protocols are below. Tvheadend is unable to do a channel scan. When I choose the satellite Astra 19.2 and set the other suggested options and click the Save button nothing happens. Nothing appears under "Currently tuned to" or "Muxes" or "Muxes awaiting initial scan"!

A test with LXDE/Kaffeine was succesfull. Kaffeine finds all the needed channels. I've tested the same Pi Board with Raspbian and it runs Tvheadend without any problem. I don't know whether Archlinux or Tvheadend is the problem. Maybe anayone has some experiences with that combination and can help. What is wrong?

Hardware:
Raspberry Pi 2
Tevii S660 USB S2 Revćeiver

OS:
Linux alarmpi 3.18.6-2-ARCH #1 SMP PREEMPT Sun Feb 8 09:40:23 MST 2015 armv7l GNU/Linux

Tvheadend version:
at Pi 2 compiled tvheadend-3.4.27-2-armv7h.pkg.tar.xz
using this Howto: http://kodi.wiki/view/HOW-TO:Install_Tvheadend_on_Arch_Linux

Content of lsusb:

Bus 001 Device 004: ID 9022:d660 TeVii Technology Ltd. DVB-S2 S660
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Content of lsmod:

Module                  Size  Used by
rpcsec_gss_krb5        21136  0 
evdev                   9464  0 
rc_tevii_nec            1180  0 
ts2020                  4274  1 
ds3000                 11971  1 
dvb_usb_dw2102         40541  0 
dvb_usb                18283  1 dvb_usb_dw2102
dvb_core               90917  1 dvb_usb
rc_core                21274  4 dvb_usb,rc_tevii_nec,dvb_usb_dw2102
leds_gpio               3530  0 
led_class               4035  1 leds_gpio
uio_pdrv_genirq         3281  0 
uio                     8710  1 uio_pdrv_genirq
sch_fq_codel            7252  2 
snd_bcm2835            20881  2 
snd_pcm                86661  2 snd_bcm2835
snd_timer              19608  1 snd_pcm
snd                    60836  6 snd_bcm2835,snd_timer,snd_pcm
bcm2708_rng             1143  0 
rng_core                5666  1 bcm2708_rng
ipv6                  342650  40

Content of dmesg | grep dvb

[    9.625954] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
[    9.716657] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
[    9.849739] dvb-usb: found a 'TeVii S660 USB' in warm state.
[    9.856621] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[    9.955173] dvb-usb: MAC address: 00:18:bd:5b:61:d1
[   10.104610] dvb-usb: schedule remote query interval to 150 msecs.
[   10.112744] dvb-usb: TeVii S660 USB successfully initialized and connected.

Content of journalctl | grep tvheadend

Feb 12 12:08:40 alarmpi systemd[1]: Started tvheadend.
Feb 12 12:08:40 alarmpi tvheadend[271]: charset: 71 entries loaded
Feb 12 12:08:40 alarmpi tvheadend[271]: dvb: Found adapter /dev/dvb/adapter0 (Montage Technology DS3000) via USB (480 Mbit/s)
Feb 12 12:08:40 alarmpi tvheadend[271]: dvb: Adapter /dev/dvb/adapter0 will run in filtered mode
Feb 12 12:08:40 alarmpi tvheadend[271]: CSA: Using 32bit parallel descrambling
Feb 12 12:08:40 alarmpi tvheadend[271]: epggrab: module eit created
Feb 12 12:08:40 alarmpi tvheadend[271]: epggrab: module uk_freesat created
Feb 12 12:08:40 alarmpi tvheadend[271]: epggrab: module uk_freeview created
Feb 12 12:08:40 alarmpi tvheadend[271]: epggrab: module viasat_baltic created
Feb 12 12:08:40 alarmpi tvheadend[271]: epggrab: module opentv-ausat created
Feb 12 12:08:40 alarmpi tvheadend[271]: epggrab: module opentv-skyit created
Feb 12 12:08:40 alarmpi tvheadend[271]: epggrab: module opentv-skyuk created
Feb 12 12:08:40 alarmpi tvheadend[271]: epggrab: module pyepg created
Feb 12 12:08:40 alarmpi tvheadend[271]: epggrab: module xmltv created
Feb 12 12:08:40 alarmpi tvheadend[271]: epgdb: loaded v2
Feb 12 12:08:40 alarmpi tvheadend[271]: epgdb:   channels   0
Feb 12 12:08:40 alarmpi tvheadend[271]: epgdb:   brands     0
Feb 12 12:08:40 alarmpi tvheadend[271]: epgdb:   seasons    0
Feb 12 12:08:40 alarmpi tvheadend[271]: epgdb:   episodes   0
Feb 12 12:08:40 alarmpi tvheadend[271]: epgdb:   broadcasts 0
Feb 12 12:08:40 alarmpi tvheadend[271]: dvr: Creating new configuration ''
Feb 12 12:08:40 alarmpi tvheadend[271]: START: HTS Tvheadend version  started, running as PID:271 UID:1337 GID:91, settings located in '/home/hts/.hts/tvheadend'
Feb 12 12:08:41 alarmpi tvheadend[271]: AVAHI: Service 'Tvheadend' successfully established.

Content of Web-Interface Tvheadend
Main Window: Configuration -> TV Adapters - General
Sub-Window: Information and Capabilities shows:

Hardware
Device path:
/dev/dvb/adapter0
Device name:
Montage Technology DS3000
Host connection:
USB (480 Mbit/s)
Intermediate Frequency range:
950000 kHz - 2150000 kHz, in steps of 1011 kHz
Symbolrate range:
1000000 Baud - 45000000 Baud
Status
Currently tuned to:

Services:
0
Muxes:
0
Muxes awaiting initial scan:
0
Signal Strength:
0%
Bit Error Rate:
0/s
Uncorrected Bit Errors:
0/s

Any idea?

Replies (4)

RE: No channel scan on a archlinux raspberry pi 2 system - Added by Prof Yaffle over 9 years ago

Try manually adding a known mux - you need the first couple of parameters but the rest can be left on 'auto'. Given that as a 'seed' then tvh should find the other muxes on that network and then can scan for services.

RE: No channel scan on a archlinux raspberry pi 2 system - Added by J_ oergZ over 9 years ago

Much Obliged! That was the crucial clue. Do you know why a problem that has been known for more than two years ([https://tvheadend.org/boards/4/topics/6326?r=6970#message-6970]), isn't still resolved? It is not possible to create manually a mux using the web interface using Archlinux/Tvheadend. In my case, I edited /usr/share/tvheadend/data/dvb-scan/dvb-s/Astra-19.2E as root and inserted a line which I found in the Raspbian installation in the same file:

S 12551500 V 22000000 5/6

and disabled the section

#[CHANNEL]
#       DELIVERY_SYSTEM = DVBS
#       FREQUENCY = 12551500
#       POLARIZATION = VERTICAL
#       SYMBOL_RATE = 22000000
#       INNER_FEC = 5/6
#       INVERSION = AUTO

and the scan started immediately! I guess for other regions and other satellites you have to edit the corresponding (satellite) file.

Maybe that it has something to do with (write) permissions? But why does it run under Raspbian and not under Archlinux? Strange... Is there any log file from the web interface or is there a switch to start TVH with to see what happens if I change something?

RE: No channel scan on a archlinux raspberry pi 2 system - Added by Prof Yaffle over 9 years ago

To a great extent, 3.4 is old news and all effort for the past year or more has been going into 3.9.x as a development branch. If the problem has been there for some time, that may be the issue - or it may be that it was never logged as a formal bug and got lost - or that it was simply overlooked in the DVB rewrite - or, or, or...

It's odd that it's not possible to create a mux from the web interface... that does suggest something's up with saving the config. On Debian (and thus Raspbian), the installation .deb creates an hts user with all the correct permissions... maybe that's related, as the Arch installation could well be a much simpler 'move the binary to /usr/bin' (I don't know, I'm not an Arch man). That doesn't explain why you don't get valid satellite frequencies to start with, though, as they're pretty constant; DVB-T signals have been re-arranged in many countries, but satellite much less so.

tvh logs to syslog, so it's that or journalctl if you're on a systemd architecture. Again, on Debian distros there's /etc/default/tvheadend, to which you can add a TVH_DEBUG = 1 to get more verbose logging, so you may have that; you can also enable basic logging to the web interface by clicking the up arrows in the bottom right, and enable debug logging by then clicking the little cog/wheel. Or you can start with command-line options, but I forget what they are on 3.4 - -s, I think (for 'syslog') - although 3.9 allows specific module debugging and tracing.

RE: No channel scan on a archlinux raspberry pi 2 system - Added by J_ oergZ over 9 years ago

I've tried out 3.9.x before. It didn't work. I'll try it again later. Maybe ther was another mistake...

Archlinux/systemd has no /etc/default/tvheadend file. So I can't switch on the debug mode on this way. I found out that adding (as root) some switches in the file

/usr/lib/systemd/system/tvheadend.service

is the right way and changed this line:

ExecStart=/usr/bin/tvheadend -f -p  /run/tvheadend.pid -C -u hts -g video -d -s -l /home/hts/tvheadend.log

The new content is behind the group name video and means: -d for enabeling debug mode, (-s for protocol mode with syslog), -l with the following path and file name for writing the logs into that file and not using the standard syslog.

Unfortunately will the web interface activities not to be recorded, even if the switch --uidebug is activated. Because the debug mode is very verbosely I'll switch it off. It tells a lot about what is happening at the sat receiver but not about the subject I'm interested in. All the switches you can set are reported when you type

tvheadend -h

Just another step forward... Thanks!

(1-4/4)

Project

General

Profile

Tvheadend