Project

General

Profile

Bug #2346

TVH has a mux frequency that does not exist according to satellite data website

Added by Crazy Fin about 10 years ago. Updated about 10 years ago.

Status:
Invalid
Priority:
Normal
Category:
Muxers
Target version:
-
Start date:
2014-10-05
Due date:
% Done:

0%

Estimated time:
Found in version:
3.9.1721
Affected Versions:

Description

I see a lot of these messages in the log when I have disabled the mux 12053.5H on 0.8W Thor satellite:
2014-10-05 17:47:09.145 mpegts: 12053.5H in THOR - not enabled
2014-10-05 17:48:13.145 mpegts: 12053.5H in THOR - not enabled
2014-10-05 17:49:17.145 mpegts: 12053.5H in THOR - not enabled
2014-10-05 17:50:21.145 mpegts: 12053.5H in THOR - not enabled
2014-10-05 17:51:25.145 mpegts: 12053.5H in THOR - not enabled
2014-10-05 17:52:29.145 mpegts: 12053.5H in THOR - not enabled

However, there is no 12.0535 (or even 12.053) mux on this satellite as far as I can see when looking through http://www.telenorsat.com/broadcast/tv-radio-channel-listings/ as well as http://www.telenorsat.com/satellites-teleports/satellite-service-data/satellites/ (and from here choose both THOR5 and THOR6).

I can see that this much contains 31 services according TVH webgui and all these services are from provider "ST" and I only need to access services from provider "Telenor".

Problem is that if I disable all the services from this mux and then disable this mux I start to get those error messages in the TVH log.

If I disable that mux but do not enable any services from that mux I do not get those error messages in the TVH log anymore. However, when I have this mux enabled I see a constant tuner being used for this mux?! It looks like an EPG scan being performed but not all the time but still this mux is causing one tuner to be occupied by this mux constantly.

See attached screenshot as well.


Files

Mux 12053.5 causes constant tuning.jpg (69.6 KB) Mux 12053.5 causes constant tuning.jpg Crazy Fin, 2014-10-05 19:43
tvh.log (41.1 KB) tvh.log Crazy Fin, 2014-10-05 23:19
tvh.log (33.7 KB) tvh.log Crazy Fin, 2014-10-05 23:36

History

#1

Updated by Crazy Fin about 10 years ago

I realised now that could this be the reason that I see this in the TVH-log on every startup of TVH?

Everytime I start TVH I see the following error message for the adapters:

Oct 1 22:03:41 tvserver tvheadend24555: linuxdvb: adapter added /dev/dvb/adapter7
Oct 1 22:03:41 tvserver tvheadend24555: linuxdvb: adapter added /dev/dvb/adapter6
Oct 1 22:03:41 tvserver tvheadend24555: linuxdvb: adapter added /dev/dvb/adapter5
Oct 1 22:03:41 tvserver tvheadend24555: linuxdvb: adapter added /dev/dvb/adapter4
Oct 1 22:03:41 tvserver kernel: [19957.745013] ddbridge 0000:05:00.0: DVB: adapter 4 frontend 0 frequency 0 out of range (950000..2150000)
Oct 1 22:03:41 tvserver tvheadend24555: linuxdvb: adapter added /dev/dvb/adapter3
Oct 1 22:03:41 tvserver kernel: [19957.782155] ddbridge 0000:03:00.0: DVB: adapter 3 frontend 0 frequency 0 out of range (950000..2150000)
Oct 1 22:03:41 tvserver tvheadend24555: linuxdvb: adapter added /dev/dvb/adapter2
Oct 1 22:03:41 tvserver kernel: [19957.821679] ddbridge 0000:03:00.0: DVB: adapter 2 frontend 0 frequency 0 out of range (950000..2150000)
Oct 1 22:03:41 tvserver tvheadend24555: linuxdvb: adapter added /dev/dvb/adapter1
Oct 1 22:03:41 tvserver kernel: [19957.844220] ddbridge 0000:03:00.0: DVB: adapter 1 frontend 0 frequency 0 out of range (950000..2150000)
Oct 1 22:03:41 tvserver tvheadend24555: linuxdvb: adapter added /dev/dvb/adapter0
Oct 1 22:03:41 tvserver kernel: [19957.884211] ddbridge 0000:03:00.0: DVB: adapter 0 frontend 0 frequency 0 out of range (950000..2150000)

Tuning in XBMC and TVH works fine though and it works perfectly fine to watch LiveTV via XBMC.

#2

Updated by Crazy Fin about 10 years ago

I deleted ALL the muxes I do not need and I was able to get rid of the messages
2014-10-05 17:47:09.145 mpegts: 12053.5H in THOR - not enabled
2014-10-05 17:48:13.145 mpegts: 12053.5H in THOR - not enabled
from the log

However, I still get the error message
Oct 1 22:03:41 tvserver kernel: [19957.884211] ddbridge 0000:03:00.0: DVB: adapter 0 frontend 0 frequency 0 out of range (950000..2150000)
when starting TVH.

#3

Updated by Jaroslav Kysela about 10 years ago

Provide 'mpegts' and 'linuxdvb' traces... It's not clear what your tvh config tries to do..

#4

Updated by Crazy Fin about 10 years ago

Attached the tvh.log file that I get when starting TVH with:
./build.linux/tvheadend -l tvh.log --trace linuxdvb,mpegts

However, I do not see those "frequency out of range" messages in the tvh.log. They seem to only appear in the syslog and they look more like kernel-related messages?

Oct 5 23:16:29 tvserver tvheadend17114: main: Log started
Oct 5 23:16:30 tvserver tvheadend17114: linuxdvb: adapter added /dev/dvb/adapter7
Oct 5 23:16:30 tvserver tvheadend17114: linuxdvb: adapter added /dev/dvb/adapter6
Oct 5 23:16:30 tvserver tvheadend17114: linuxdvb: adapter added /dev/dvb/adapter5
Oct 5 23:16:30 tvserver tvheadend17114: linuxdvb: adapter added /dev/dvb/adapter4
Oct 5 23:16:30 tvserver tvheadend17114: linuxdvb: adapter added /dev/dvb/adapter3
Oct 5 23:16:30 tvserver kernel: [34269.287161] ddbridge 0000:03:00.0: DVB: adapter 3 frontend 0 frequency 0 out of range (950000..2150000)
Oct 5 23:16:30 tvserver tvheadend17114: linuxdvb: adapter added /dev/dvb/adapter2
Oct 5 23:16:30 tvserver kernel: [34269.326781] ddbridge 0000:03:00.0: DVB: adapter 2 frontend 0 frequency 0 out of range (950000..2150000)
Oct 5 23:16:30 tvserver tvheadend17114: linuxdvb: adapter added /dev/dvb/adapter1
Oct 5 23:16:30 tvserver tvheadend17114: linuxdvb: adapter added /dev/dvb/adapter0
Oct 5 23:16:30 tvserver kernel: [34269.377017] ddbridge 0000:03:00.0: DVB: adapter 0 frontend 0 frequency 0 out of range (950000..2150000)
Oct 5 23:16:30 tvserver tvheadend17114: dvr: Creating new configuration ''
Oct 5 23:16:30 tvserver tvheadend17114: CSA: Using SSE2 128bit parallel descrambling

I did a fresh and new clean install on Saturday and downloaded the latest drivers from http://linuxtv.org/hg/~endriss/media_build_experimental and followed instructions found at http://shop.digital-devices.de/epages/62357162.sf/?ObjectPath=/Shops/62357162/Categories/DownloadsNew1/Linux_Unterstuetzung_fuer_Digital_Devices_Produkte

I might have had these error messages all the time but I have not noticed them until recently when I looked at the syslog instead of the "on screen" log showing when starting TVH with ./build.linux/tvheadend.

I can see now though that these error messages has been reduced down to 3 instead of 5 after that I deleted all the muxes I do not need anymore.

#5

Updated by Crazy Fin about 10 years ago

Nope, I was too quick on my comment above. I rebooted the server and now I got 7 rows with "freq out of range" messages.

#6

Updated by Crazy Fin about 10 years ago

I've added a more "cleaner" log without any XBMC clients running and trying to connect.

#7

Updated by Crazy Fin about 10 years ago

Hmmm maybe we should move this discussion out of the "issues" since this does not seem to be a TVH issue anymore?

If I stop TVH and do "femon -H -a 0" or any other frontend from 0 to 7 (I have 8 tuners) I get no signal.
However, if I have TVH running and for example start XBMC and tune in to any channel and then do "femon -H -a x" (where x is the same tuner number that TVH is utilizing to display the channel to XBMC) I get nice signal and FE lock message.

This is what it looks like when TVH is stopped and I do "femon":

root@tvserver:/home/tvserver# femon -H -a 7
FE: STV090x Multistandard (DVBS)
Problem retrieving frontend information: Resource temporarily unavailable
status SC | signal 0% | snr 0% | ber 0 | unc 1 |

and when I start TVH and XBMC:

root@tvserver:/home/tvserver# femon -H -a 7
FE: STV090x Multistandard (DVBS)
status SCVYL | signal 76% | snr 81% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 76% | snr 82% | ber 0 | unc 0 | FE_HAS_LOCK

Is there something wrong with my channel conf:s "outside" TVH causing the tuner cards trying to tune in to a zero freq when TVH is starting? Everything works fine as soon as TVH has done its startup sequence and I have no issues at all to watch Live TV via XBMC clients connected to TVH.

#8

Updated by Jaroslav Kysela about 10 years ago

  • Status changed from New to Invalid

Your messages 'DVB: adapter 3 frontend 0 frequency 0 out of range (950000..2150000)' are from the kernel. I'm not sure, if there are not other tasks sharing the DVB adapters on your system and from provided log, tvh sets correct frequencies. I'm closing it as "invalid". Perhaps, you may discuss this in the forum with other DD users..

#9

Updated by Crazy Fin about 10 years ago

Agreed but what is confusing me is that this kernel message only shows up when I start TVH... :-(

I´ll dig around in the Digital Devices forum and ask DD for help via their support ticket system as well.

#10

Updated by Crazy Fin about 10 years ago

Could it be something in TVH startup procedure causing the adapters trying to tune to frequency 0 before TVH properly starts to tune in to correct frequencies when the muxes has been initialized?

I do not use diseq-switches but another person with similar error messages at this thread http://www.vdr-portal.de/board16-video-disk-recorder/board8-vdr-grundlagen/p1190931-frequency-out-of-range-issue-with-some-channel/ fixed it by setting proper frequency bands.

So I am still thinking that something is going wrong with the adapter tuning during TVH startup since I do not see any of these error messages in syslog until I start TVH. The error messages from kernel in the syslog appears when TVH is initializing the frontends.

#11

Updated by Crazy Fin about 10 years ago

Sorry to keep chatting in this thread that was changed from "New" to "Invalid".

I still believe it is TVH doing something strange during the startup sequence that causes these "adapter 2 frontend 0 frequency 0 out of range (950000..2150000)" messages from kernel in the syslog:

Oct 5 23:16:30 tvserver tvheadend17114: linuxdvb: adapter added /dev/dvb/adapter4
Oct 5 23:16:30 tvserver tvheadend17114: linuxdvb: adapter added /dev/dvb/adapter3
Oct 5 23:16:30 tvserver kernel: [34269.287161] ddbridge 0000:03:00.0: DVB: adapter 3 frontend 0 frequency 0 out of range (950000..2150000)
Oct 5 23:16:30 tvserver tvheadend17114: linuxdvb: adapter added /dev/dvb/adapter2
Oct 5 23:16:30 tvserver kernel: [34269.326781] ddbridge 0000:03:00.0: DVB: adapter 2 frontend 0 frequency 0 out of range (950000..2150000)
Oct 5 23:16:30 tvserver tvheadend17114: linuxdvb: adapter added /dev/dvb/adapter1
Oct 5 23:16:30 tvserver tvheadend17114: linuxdvb: adapter added /dev/dvb/adapter0
Oct 5 23:16:30 tvserver kernel: [34269.377017] ddbridge 0000:03:00.0: DVB: adapter 0 frontend 0 frequency 0 out of range (950000..2150000)
Oct 5 23:16:30 tvserver tvheadend17114: dvr: Creating new configuration ''

I downloaded dvb-apps. I shutdown TVH and did a SCAN according to the info at http://www.linuxtv.org/wiki/index.php/Scan to create a complete channel list for the satellite THOR 1.0W (actually it is 0.8W).
After that I tuned each adapter to a channel and then I started TVH again and voilaaaa! No more messages in the syslog about "frequency 0 out of range"! :-)

So it looks like that when TVH starts it initiates the adapters without having a valid frequency set?

Also available in: Atom PDF