Project

General

Profile

Forums » Tutorial and setups »

After switching back from 3.9 to 3.4: No muxes found

Added by Bjoern Franke almost 10 years ago

Hi,

after upgrading my 3.9-git-installation yesterday, nothing worked any more. Also deleting all configs and reinstalling the git-version did not help. Muxes are found, but no recordingprofiles exist and it seems to be unstable.
So I decided to delete every config again and installed 3.4.27. But now, no muxes are found. Both DVB-S cards are enabled and set to "autodetect muxes" and "idle scanning". After adding the network (Astra 19.2E / Default (Port 0 / Universal LNB)) just nothing happens. I find this quite confusing because month ago I used 3.4.27 and had no issues detecting muxes and services.


Replies (1)

RE: After switching back from 3.9 to 3.4: No muxes found - Added by Daisy Reiss almost 10 years ago

Hi Björn,

for my Setup (TvHeadend 3.9.2407~gabea248, headless xubuntu 14.04.1 LTS, 3x DVB-T Tuner, Hannover Area) I learned for similar situations, that I have to:
  1. disable all autorec entries (cause they will disturb next steps)
  2. delete the whole Netwoks+Muxes+Services+Channels
  3. disable all DVB Tuners
  4. reboot (sic!) the linux
  5. then enable the tuners (all at once or one after the other)
  6. force full scans
  7. drink some coffee
  8. map the services
  9. [optionally now or later] assin the picons
  10. test everything
  11. enable autorec entries back again
  12. see, it's far past midnight and there will remain 4h until next workday starts :(

This worked all times for me, but I got some trouble with my wife since it consumes a lot of my rare spare time :(

Sometimes it was okay to just disable / enable some networks (I use DVB-T/DE-Niedersachsen or DVB-T/generic-default (not the 168kHz steps one)), or to disable/enable some/all DVB-T tuners with a 'service stop tvheadend;sleep 3;service start tvheadend' between disabling/enabling. But most times this lead me to not finishing the scans or much more often to 'linuxdvb: Realtek RTL2832 (DVB-T) : DVB-T #2 - poll TIMEOUT' (tail -f /var/log/syslog)

Another lesson I learned by trial and error was, "idle scanning" is not my friend when restarting / reinstalling something. I feel it also does disturb something.

all the above written may not be a problem from tvheadend but from linuxdvb - I can't be sure, which is true. Please refer to [[http://forums.openmediavault.org/index.php/Thread/7385-How-to-fix-this-Kernel-bug-manually/]]. I hope some of the active tvheadend coders will read this and give a statement, please.

    (1-1/1)