Page 1 of 1

Firmware 1.21 + MuMuDVB = Segmentation fault

PostPosted: Tue Aug 27, 2013 12:32 am
by Traveler
Hello to everybody,

After upgrading my MOI Box with latest release of Firmware 1.2.1, each time when I start MuMuDVB 1.7.1 on MOI I have segmentation fault. Does anybody have any kind of solution, because this is really annoying :(

Here is my log:

Code: Select All Code
# mumudvb -d -c /home/mumudvb/Tuner2-HotBird.conf
MuMuDVB Version 1.7.1
 --- Build information ---
Built with CAM support.
Built without transcoding support.
Built with ATSC support.
Built with ATSC long channel names support.
Built with support for DVB API Version 5.
---------
Originally based on dvbstream 0.6 by (C) Dave Chapman 2001-2004
Released under the GPL.
Latest version available from http://mumudvb.braice.net/
Project from the cr@ns (http://www.crans.org)
by Brice DUBOST (mumudvb@braice.net)

Info:  Main:  Full autoconfiguration, we activate SAP announces. if you want to deactivate them see the README.
Info:  Main:  Full autoconfiguration, we activate PAT rewritting. if you want to deactivate it see the README.
Info:  Main:  Full autoconfiguration, we activate SDT rewritting. if you want to deactivate it see the README.
Info:  Main:  Full autoconfiguration, we activate sorting of the EIT PID. if you want to deactivate it see the README.
Info:  Main:  ========== End of configuration, MuMuDVB version 1.7.1 is starting ==========
Info:  Autoconf:  The autoconfiguration auto update is enabled. If you want to disable it put "autoconf_pid_update=0" in your config file.
Info:  Main:  Streaming. Freq 12596000
Info:  Tune:  Using DVB card "TurboSight TBS 2991 DVBS/S2 frontend" tuner 0
Info:  Tune:  Tuning DVB-S to Freq: 1996000 kHz, LO frequency 10600000 kHz Pol:V Srate=27500000, LNB number: 4
Info:  Tune:  LNB voltage 13V
Info:  Tune:  DISEQC SETTING SUCCEDED
Info:  Tune:  FE_STATUS:
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:       FE_HAS_CARRIER : found a DVB signal
Info:  Tune:       FE_HAS_VITERBI : FEC is stable
Info:  Tune:       FE_HAS_SYNC : found sync bytes
Info:  Tune:       FE_HAS_LOCK : everything's working...
Info:  Tune:  Event:  Frequency: 12596000 (or 8604000)
Info:  Tune:          SymbolRate: 2848000
Info:  Tune:          FEC_inner:  2
Info:  Tune:  Bit error rate: 67108863
Info:  Tune:  Signal strength: 33975
Info:  Tune:  SNR: 4369
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:       FE_HAS_CARRIER : found a DVB signal
Info:  Tune:       FE_HAS_VITERBI : FEC is stable
Info:  Tune:       FE_HAS_SYNC : found sync bytes
Info:  Tune:       FE_HAS_LOCK : everything's working...
Info:  Main:  Card 1, tuner 0 tuned
Info:  Autoconf:  Autoconfiguration Start
Segmentation fault
#

Re: Firmware 1.21 + MuMuDVB = Segmentation fault

PostPosted: Tue Dec 31, 2013 3:25 pm
by 0blar
Hello

I have similar problem using 2.0.2 firmware

Did you find a solution ?

Thanks

Re: Firmware 1.21 + MuMuDVB = Segmentation fault

PostPosted: Fri Feb 14, 2014 10:19 am
by mdx
Me too. Segmentation fault after autoconfiguration starts.

Re: Firmware 1.21 + MuMuDVB = Segmentation fault

PostPosted: Thu Oct 16, 2014 2:03 am
by pispi
i have this problem too, anybody its solve this?

Re: Firmware 1.21 + MuMuDVB = Segmentation fault

PostPosted: Sun Oct 19, 2014 2:22 pm
by diabloss
Guys

Make the mumu binary 755 permission wise and fill the .conf file with care.
Each mumu version have some slight small changes.
1 bad parameter in the conf file and voila ... segmentation fault.