No channel scan on a archlinux raspberry pi 2 system
No channel scan on a archlinux raspberry pi 2 systemReplies (4)
RE: No channel scan on a archlinux raspberry pi 2 system
-
Added by Prof Yaffle almost 10 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 almost 10 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 almost 10 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 almost 10 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!