[TM-NANO-3T COMBO] Unresponsive box after installing mgcamd & update 55 [Archive] - Satellite Support Forum .: Home of OpenViX Team:.

View Full Version : [TM-NANO-3T COMBO] Unresponsive box after installing mgcamd & update 55

chris16v

13-10-14, 11:32

ViX Apollo
build 55

ViX Night HD skin

plugins installed
* CCcam 2.3.1 ( installed via the feeds )
* mgcamd ( installed via the feeds )
* multiquick ( installed via the feeds )
* RED HD skin downloaded (from feeds but not installed)

After a random amount of time (maybe 30 mins to 5 hours) i find the box has locked up completely and totally unresponsive. No video output to tv, remote does nothing, no network connection for ftp/telnet etc. nothing.... and needs a power off back on to get it working again., then some hours later it does it again.

* I have owned the T3 for 5 days now. First 3 days it ran fine and no problems using CCam softcam.
* I then went for a software update to 55 and also installed MGCAMD, multiquick and RED HD skin.
* I also disabled CCcam and enabled MGCAMD

From there i have noticed the problems described above begin.

To troubleshoot i have reverted back the box back as follows:

* changed skin back to VIX night HD (but not removed red hd plugin)
* disabled MGCAMD and enabled CCcam. (but not removed mgcamd plugin)

The problem persists

thanks

grahammcm1888

13-10-14, 16:46

I am still on v54. Isn't 55 unstable at the moment?

Sent from my iPhone using Tapatalk

chris16v

13-10-14, 19:50

I am still on v54. Isn't 55 unstable at the moment?

it might be, i have no idea. since no one else has commented i am thinking of rolling back to 54 and see if its the solution for now. i just presumed i install the updates when i saw it flashing green.

grahammcm1888

13-10-14, 19:54

I done a fresh flash to v54 today. However when I went to plugins the feeds were not available unless I selected unstable downloads. When I selected the option the feeds became available but the update icon was flashing red to indicate there was an unstable upgrade available(i think). I chose not to update until its stable. I might be wrong on this , not sure. I would rollback to v54 if I was you.

Sent from my iPhone using Tapatalk

judge

13-10-14, 20:10

No need to roll back. A bug was found in ABM after release, will be fixed on the next build.
A badly configured mgcamd can cause these issues, when you say you disabled mgcamd, are you 100% sure it stopped running?

cactikid

13-10-14, 20:23

as you mentioned cams i see there are newer ones for Cccam AND Mgcamd is there a difference in 213 and 230 and 1.35a and 1.38:confused:

judge

13-10-14, 20:33

as you mentioned cams i see there are newer ones for Cccam AND Mgcamd is there a difference in 213 and 230 and 1.35a and 1.38:confused:
Just newer versions. I don't know the change logs though...
Compatible cams can be found in the ViX plugin feeds.

chris16v

14-10-14, 09:11

A badly configured mgcamd can cause these issues,
Judge, are you refering to the config of the mg_cfg & newcamd.list files or the compile of the softcam when its installed?

when you say you disabled mgcamd, are you 100% sure it stopped running?
in softcams i unchecked autostart and i also disabled it, then enabled cccam.

I am on build 55 and maybe i should remove the mgcamd plugin as a test. failing that, which image should i roll back to, as known to be stable?

abu baniaz

14-10-14, 11:49

He is referring to mg_cfg

chris16v

14-10-14, 12:30

think i might use oscam softcam instead. but was thinking to re-flash the box but i am not sure which version is the current stable image? its definately not 55 i presume..

chris16v

15-10-14, 10:16

right,

* i have reflashed the box and downgraded to build 54
* i have installed the oscam plugin
* i have added basic server/config/user oscam files
* the T3 is working fine, clears channels

BUT the box total lock up persists. In 12 hours it has twice locked up, and needed a hard power off/on to get it started again.

Could this be a hardware fault to speak to the world of satellte shop about? any further troubleshooting advice is greatly appreciated.

grahammcm1888

15-10-14, 10:18

chris16v

15-10-14, 11:30

is there anyone from the Vix support team who can also comment here as well.

So after downgrading from rev55 to rev54 i get this:

random amount of time working (say 30mins to 8hrs)
black screen, no network, display on lcd showing channel but box is completely unresponsive.

I need to establish if this is software/hardware. Is there a certain log i can check before deciding this is a faulty unit?

abu baniaz

15-10-14, 16:37

You can enable debug logs in the logs menu. You will need to reboot for this change to take effect.

Can you alos upload yout mg_cfg please. Just want to check something.

chris16v

15-10-14, 16:44

i can do that tonight abu baniaz but since imaging the T3 again i havent reinstalled mgcamd, now i am runing only oscam. so do you still wan the mg_cfg file?
(its still locking up mind you)

Larry-G

15-10-14, 16:47

i can do that tonight abu baniaz but since imaging the T3 again i havent reinstalled mgcamd, now i am runing only oscam. so do you still wan the mg_cfg file?
(its still locking up mind you)

In that case it's even more important that you upload some debug logs from these incidents.

nsw9154

15-10-14, 19:20

V57 appears to be the latest update. Why dont you give this a try. I am still on v54 but the update via my duo2 will only go to v55 which I think should be avoided. I will update via USB to v57 when I get a chance.

Sent from my iPhone using Tapatalk

why not update through Image Manager it's easy-er than using USB, I used to upload with USB all the time now I do it through Image Manager
just press the yellow Button to Download the image to your Hard Drive then press the Blue Button to install it :D

Rob van der Does

15-10-14, 21:06

Do you have a mountpoint that is not available?

chris16v

15-10-14, 22:43

Do you have a mountpoint that is not available?

afraid not. when i downgraded to rev54 i only installed the oscam plugin and stopped there. i did not configure anything else for it. thats why i am concerned there is either a hardware or software fault.
i have switched on debugging and now waiting for it to fail. When it does and you want me to post the log, i presume you are just gonna want the last few lines of the log and not the whole thing.

judge

15-10-14, 23:09

When it does and you want me to post the log, i presume you are just gonna want the last few lines of the log and not the whole thing.
Attach the full log, easier to see anything else that might cause it.
Hit the 'Go Advanced' button under the post area & then the paperclip icon above the resulting post area to attach any logs.
Not sure if anything will be spotted in the logs though as a random lockup rarely does, but worth a look anyway.

abu baniaz

15-10-14, 23:36

May be worth checking all cables on motherboard are seated firmly.

Rob van der Does

16-10-14, 05:44

Did you restart the box after enabling debug logs?
If the issue persists please disconnect any storage devices ((internal)HDD, USB-stick) and indeed LAN-cable as well.

chris16v

16-10-14, 09:27

right then, i enabled debugging and rebooted the box, and waited. so some time in the night it locked up... yippee..
but after powering the box back up there is only one log in home/root/logs and it looks to me that the log data prior to the lockup has been overwritten because the only log data i have in the /logs folder is pretty short... posted below:

(out of interest, looking at the log name, if after a reboot the log file starts again with the same time/date stamp, i am guessing this is a problem?)
log name Enigma2-01-01-1970_1-00-16.log

+ (1) Background File Eraser
+ (5) Tuxtxt
+ (8) graphics acceleration manager
+ (9) GFBDC
10800k video mem
- double buffering available!
7560kB available for acceleration surfaces.
resolution: 720 x 576 x 32 (stride: 2880)
+ (9) gLCDDC
found OLED display!
lcd buffer 0x779ca8 8448 bytes, stride 132
LCD resolution: 132 x 64 x 8 (stride: 132)
+ (9) Font Render Class
[FONT] initializing lib...
[FONT] loading fonts...
PYTHONPATH: /usr/lib/enigma2/python
[FONT] Intializing font cache, using max. 4MB...
+ (10) gRC
RC thread created successfully
+ (15) eWindowStyleManager
+ (20) DVB-CI UI
+ (20) UHF Modulator
couldnt open /dev/rfmod0!!!!
+ (20) RC Input layer
+ (20) misc options
+ (20) AVSwitch Driver
+ (21) input device driver
Input device "FORCE1-PLUS remote control (native)" is a remotecontrol
Found 1 input devices.
+ (22) Hdmi CEC driver
eHdmiCEC: detected physical address change: 1000 --> 4000
eHdmiCEC: send message 84 40 00 03
+ (30) eActionMap
+ (35) CI Slots
scanning for common interfaces..
cannot open /proc/stb/tsmux/input2
eDVBCIInterfaces->setInputSource(0, 0)
eDVBCIInterfaces->setInputSource(1, 1)
done, found 1 common interface slots
+ (35) CA handler
+ (40) eServiceCenter
settings instance.
+ (41) eServiceFactoryDVD
+ (41) eServiceFactoryHDMI
+ (41) eServiceFactoryM2TS
+ (41) eServiceFactoryMP3
+ (41) eServiceFactoryFS
+ (41) eServiceFactoryDVB
+ (41) Stream server
reached rl 70
---- opening lame channel db
reading services (version 4)
loaded 130 channels/transponders and 1120 services
scanning for frontends..
opening frontend 0
close frontend 0
opening frontend 1
close frontend 1
opening frontend 2
close frontend 2
found 1 adapter, 3 frontends(3 sim) and 9 demux, boxtype 4
RTC not ready... wait for transponder time
[EPGC] Initialized EPGCache (wait for setCacheFile call now)
Loading spinners...
[ePNG] couldn't open /usr/share/enigma2/spinner/wait20.png
found 19 spinner!
setIoPrio best-effort level 3 ok
couldn't open /proc/stb/misc/12V_output
[Harddisk] enumerating block devices...
[Harddisk] enumerating network mounts...
Reading satellites.xml
main thread is non-idle! display spinner!
Reading cables.xml
Reading terrestrial.xml
removing internal link on frontend id 1
sec config cleared
setSlotInfo for dvb frontend 0 to slotid 0, descr BCM7356 (internal), need rotorworkaround No, enabled Yes, DVB-S2 Yes
setSlotInfo for dvb frontend 1 to slotid 1, descr BCM7356 (internal), need rotorworkaround No, enabled Yes, DVB-S2 Yes
setSlotInfo for dvb frontend 2 to slotid 2, descr Panasonic SP9680PVB (external), need rotorworkaround No, enabled Yes, DVB-S2 No
slot: 0 configmode: simple
diseqcmode: diseqc_a_b_c_d
slot: 1 configmode: simple
diseqcmode: single
sec config completed
[Time By]: Transponder
[EPGC] time updated.. but cache file not set yet.. dont start epg!!
[Ipkg] Added to OPKG destinations: /
[FONT] adding font /usr/share/fonts/Roboto-Bold.ttf...executing main
OK (Regular)
[FONT] adding font /usr/share/fonts/Roboto-BoldItalic.ttf...OK (Italic)
[FONT] adding font /usr/share/fonts/Roboto-Black.ttf...OK (Bold)
[FONT] adding font /usr/share/fonts/Roboto-BlackItalic.ttf...OK (Boldit)
[FONT] adding font /usr/share/fonts/nmsbd.ttf...OK (Subtitlefont)
[FONT] adding font /usr/share/fonts/lcd.ttf...OK (LCD)
[FONT] adding font /usr/share/fonts/ae_AlMateen.ttf...OK (Replacement)
[FONT] adding font /usr/share/fonts/tuxtxt.ttf...OK (Console)
- double buffering available!
3600kB available for acceleration surfaces.
resolution: 1280 x 720 x 32 (stride: 5120)
[SKIN] loading include: /usr/share/enigma2/ViX-Common/CommonSkin.xml
[FONT] adding font /usr/share/fonts/nmsbd.ttf...OK (Subs)
[FONT] adding font /usr/share/fonts/nmsbd.ttf...OK (FdLcD)
[iInputDevices] getInputDevices <ERROR: ioctl(EVIOCGNAME): [Errno 25] Inappropriate ioctl for device >
Activating keymap: Default (US)
Activating language English (UK)
[VideoMode] setting aspect: 16:9
[VideoMode] setting wss: auto
[VideoMode] setting policy: panscan
[VideoMode] setting policy2: letterbox
[VideoMode] setting scaler_sharpness to: 0000000D
[VideoMode] setMode - port: HDMI, mode: 1080p, rate: multi
[EPGC Load] Poller disabled.
[EPGC Save] Poller disabled.
[EPGC] setCacheFile read/write epg data from/to '/etc/enigma2/epg.dat'
setLCDBrightness 25
setLCDBrightness 127
setLCDScrollspeed 150
setLCDRepeat 3
setLCDMode 1
Setting OSD position: 27 667 22 534
Setting OSD alpha: 255
Setting 3D mode: auto
Setting 3D depth: 50
[EPGC Save] Poller disabled.
[EPGC Load] Poller disabled.
FIXME: request for unknown slot
FIXME: request for unknown slot
FIXME: request for unknown slot
Plugin Extensions/WebInterface failed to load: No module named plugin
[XMLTVImport] autostart (0) occured at 1413443626.76
[AutoTimer] Auto Poll Enabled
[SoftcamManager] AutoStart Enabled
[CI_Assignment] activating ci configs:
[CI_Activate] FOUND 1 CI Slots
[CI_Activate_Config_CI0] no config file found
[CI_Activate_Config_CI0] error parsing xml...
starting hotplug handler
[CrossEPG_Auto] AutoStart Enabled
[CrossEPG_Auto] Schedule Disabled at Thu 16 Oct 2014 08:13:46 IST
[ImageManager] AutoStart Enabled
[ImageManager] Backup Schedule Disabled at (now=Thu 16 Oct 2014 08:13:46 IST)
[BackupManager] AutoStart Enabled
[BackupManager] Backup Schedule Disabled at (now=Thu 16 Oct 2014 08:13:46 IST)
[AutoBouquetsMaker] AutoStart Enabled
[AutoBouquetsMaker] AutoBouquetsMaker Schedule Disabled at Thu 16 Oct 2014 08:13:46 IST
[XMLTVImport] autostart (0) occured at 1413443626.91
[XMLTVImport] WakeUpTime now set to -1 (now=1413443626)
warning, skin is missing element state in <class 'Screens.PVRState.TimeshiftState'>
RemovePopup, id = ZapError
[Skin] Attribute not implemented: alphatest value: blend
setValue 100
Setvolume: 100 100 (raw)
Setvolume: 0 0 (-1db)
Setvolume: 100 100 (raw)
Setvolume: 0 0 (-1db)
[LogManager] Trim Poll Started
[LogManager] Trash Poll Started
[LogManager] probing folders
[LogManager] found following log's: ['/home/root/logs']
[LogManager] looking in: /home/root/logs
[LogManager] /home/root/logs: bytesToRemove -13601739
[NTP]: setting E2 time: 1413443628.96
[EPGC] time updated.. start EPG Mainloop
playing 1:0:1:517:7DB:2:11A0000:0:0:0:
[EPGC] 339 events read from /etc/enigma2/epg.dat
not enough diskspace for timeshift! (less than 1GB)
not enough diskspace for timeshift! (less than 1GB)
not enough diskspace for timeshift! (less than 1GB)
not enough diskspace for timeshift! (less than 1GB)
not enough diskspace for timeshift! (less than 1GB)
not enough diskspace for timeshift! (less than 1GB)
RemovePopup, id = ZapError
allocate channel.. 07db:0002
opening frontend 0
(0)tune
RotorCmd ffffffff, lastRotorCmd ffffffff
prepare_sat System 0 Freq 11914500 Pol 0 SR 27500000 INV 2 FEC 2 orbpos 282 system 0 modulation 1 pilot 2, rolloff 0
tuning to 1314 mhz
OURSTATE: tuning
allocate Channel: res 0
[eDVBCIInterfaces] addPMTHandler 1:0:1:517:7DB:2:11A0000:0:0:0:
allocate demux
CI Slot 0: reset requested
ci flush
ci inserted in slot 0
poll: unhandled POLLERR/HUP/NVAL for fd 31(16)
poll: unhandled POLLERR/HUP/NVAL for fd 35(16)
job Components.Task.Job name=LogManager #tasks=1 completed with [] in None
[SEC] set static current limiting
0.0.0.0
192.168
ER plugin not found
[OpenWebif] no plugins to load
[OpenWebif] started on 80
executing opkg --add-dest /:/ update
[OpenWebif] started on 443
poll: unhandled POLLERR/HUP/NVAL for fd 34(16)
job Components.Task.Job name=OnlineVersionCheck #tasks=1 completed with [] in None
set sequence pos 3
set sequence pos 4
[SEC] setVoltage 2
[SEC] sleep 200ms
[SEC] invalidate current switch params
[SEC] sendDiseqc: e00000(DiSEqC reset)
[SEC] sleep 50ms
[SEC] sendDiseqc: e00003(DiSEqC peripherial power on)
[SEC] sleep 150ms
[SEC] sendDiseqc: e01038ff(?)
[SEC] sleep 50ms
set sequence pos 3
[SEC] setTone 1
[SEC] sleep 10ms
[SEC] update current switch params
[SEC] startTuneTimeout 5000
[SEC] setFrontend 1
setting frontend 0
(0)fe event: status 0, inversion off, m_tuning 1
(0)fe event: status 19, inversion off, m_tuning 2
OURSTATE: ok
[eDVBLocalTimerHandler] channel 0x1ea31b0 running
[eEPGCache] channel 0x1ea31b0 running
stop release channel timer
ok ... now we start!!
[EPGC] next update in 2 sec
RemovePopup, id = ZapError
[SEC] sleep 500ms
PATready
use pmtpid 0102 for service_id 0517
[Dish] tuning failed
eventNewProgramInfo 0 0
have 1 video stream(s) (0202), and 2 audio stream(s) (0287, 0282), and the pcr pid is 1ffe, and the text pid is 0244
allocate demux
decoder state: play, vpid=514, apid=647
DMX_SET_PES_FILTER(0x1ffe) - pcr - ok
DEMUX_START - pcr - ok
DMX_SET_PES_FILTER(0x287) - audio - ok
DEMUX_START - audio - ok
AUDIO_SET_BYPASS(1) - ok
AUDIO_PAUSE - ok
AUDIO_PLAY - ok
Video Device: /dev/dvb/adapter0/video0
demux device: /dev/dvb/adapter0/demux0
VIDEO_SET_STREAMTYPE 0 - ok
DMX_SET_PES_FILTER(0x202) - video - ok
DEMUX_START - video - ok
VIDEO_FREEZE - ok
VIDEO_PLAY - ok
DMX_SET_PES_FILTER(0x244) - ttx - ok
DEMUX_START - ttx - ok
VIDEO_SLOWMOTION(0) - ok
VIDEO_FAST_FORWARD(0) - ok
VIDEO_CONTINUE - [EPGC] start caching events(1413443632)
ok
AUDIO_CONTINUE - ok
AUDIO_CHANNEL_SELECT(0) - ok
disable teletext subtitles page ffffffffffffffff (und)
not enough diskspace for timeshift! (less than 1GB)
not enough diskspace for timeshift! (less than 1GB)
not enough diskspace for timeshift! (less than 1GB)
not enough diskspace for timeshift! (less than 1GB)
not enough diskspace for timeshift! (less than 1GB)
[eDVBCAService] new service 1:0:1:517:7DB:2:11A0000:0:0:0:
[eDVBCAService] add demux 0 to slot 0 service 1:0:1:517:7DB:2:11A0000:0:0:0:
[eDVBCIInterfaces] gotPMT
[SEC] set dynamic current limiting
executing opkg --add-dest /:/ list-upgradable
poll: unhandled POLLERR/HUP/NVAL for fd 35(16)
not enough diskspace for timeshift! (less than 1GB)
not enough diskspace for timeshift! (less than 1GB)
[OnlineVersionCheck] 57 Updates available
poll: unhandled POLLERR/HUP/NVAL for fd 70(16)
sdt update done!
[SoftcamManager] Couldn't find oscam running, Starting oscam
poll: unhandled POLLERR/HUP/NVAL for fd 68(16)
[eDVBLocalTimerHandler] dont have correction.. set Transponder Diff
[eDVBLocalTimerHandler] set RTC Time
[eDVBLocalTimerHandler] update RTC
[eDVBLocalTimerHandler] time update to 08:13:58
[eDVBLocalTimerHandler] m_time_difference is 0
poll: unhandled POLLERR/HUP/NVAL for fd 57(16)
[EPGC] abort non avail nownext reading
[EPGC] abort non avail schedule reading
[EPGC] abort non avail netmed schedule reading
[EPGC] abort non avail netmed schedule other reading
[EPGC] abort non avail FreeSat schedule_other reading
[EPGC] abort non avail viasat reading
VIDEO_GET_EVENT - ok
[VideoMode] setting aspect: 16:9
[VideoMode] setting wss: auto
[VideoMode] setting policy: panscan
[VideoMode] setting policy2: letterbox
job Components.Task.Job name=SoftcamCheck #tasks=1 completed with [] in None

Rob van der Does

16-10-14, 11:11

1- Please post logs as attachement, not as text. This is unworkable.
2- The log name shows your box has an issue getting the time. What is your time settings? Getting time happens once after a reboot.

chris16v

16-10-14, 11:36

sorry Rob van der does, i couldnt find the Go advanced button as suggested by the Judge.
The log didnt seem too long in order to post its total contents.

My image is as default out of the box, nothing has been configured apart from oscam so if it looks like the time is an issue then i will take a look and see if i can edit this, and start the debugging process again.

Where is the go advanced button for posting/inserting files? thanks

Rob van der Does

16-10-14, 11:42

'Go advanced' is right beneath the 'Post Quick Reply' button.

Regarding time: is an LNB connected? And is Internet available to your box?

chris16v

16-10-14, 12:04

'Go advanced' is right beneath the 'Post Quick Reply' button.

Regarding time: is an LNB connected? And is Internet available to your box?

i can see why you might ask this, the answer to both is yes. Although the lnb is reached via a diseq switch but that shouldnt make a difference.

chris16v

16-10-14, 12:12

ah, found it and now the log file is attached.
thanks

Rob van der Does

16-10-14, 12:21

First of all the get-time issue should be taken care off.
Please restart Enigma (so not a reboot), and see if the new log gets the correct time.

chris16v

17-10-14, 09:55

ok guys, i have a log that was live when the machine locked up.
After checking that the time from the lnb was right, i restarted enigma and could see the log being written to, so hopefully there are some clues in the attached log.

cheers

judge

17-10-14, 10:15

Have you timeshift enabled with no HDD or USB attached?
Also, saving EPG to internal flash?

chris16v

17-10-14, 10:40

normally i would have all these features set up and configured but as the box is a new purchase and with this lockup issue i havent sorted the HDD, timeshift, usb pen drive, epg etc yet until i resolve this.

The image is in a "default" state from flashed (apart from oscam softcam). So if the default image settings after a reflash have these features switched on then maybe there is an issue there? I cant check till i get home tonight.

Does the log suggest the features you have listed to be the root cause of the lockups? For the lock up tests i am not using the box, i am leaving it switched on and dormant.

Rob van der Does

17-10-14, 11:23

The only (for me) clear issue I found is "not enough diskspace for timeshift! (less than 1GB)".
1- Did you enable Timeshift? If so, please disable.
2- What plugins have you installed, apart from Oscam?
3- What service settings do you use?
4- Did you restore settings?

chris16v

17-10-14, 12:43

The only (for me) clear issue I found is "not enough diskspace for timeshift! (less than 1GB)".

1- Did you enable Timeshift? If so, please disable.
I havent touched timeshift settings at all since flashing the image, so whatever settings are set as the default in the image is what i have. But i dont yet have a usb or hdd mounted either. its bog standard default, no other devices plugged in. i cant confirm what those settings actually are but can post them tonight

2- What plugins have you installed, apart from Oscam?
Nothing at all. totally untouched and default apart from oscam.

3- What service settings do you use?
do u mean how are my tuners set up? ok her we go
Tuner A) simple, set to DiSEqC a/b/c/d. only port d is configured to 28e so that i can get out past my 4 port switch to a multi lnb. 9this configuration worked well with my vusolo.
Tuner B) not configured
Tuner C) Active ( i will need to check later for specific settings used but its working fine)

4- Did you restore settings?
no, defo not.

hope that helps :confused:

DaMacFunkin

17-10-14, 13:29

As everybody says you need to make sure that time shift is disabled, it should be by default but I would still toggle it and save the setting, time shift can cause crashes in certain circumstances and your log is full of incomplete time shift requests.

chris16v

17-10-14, 13:50

DaMacFunkin yes i agree it should be disabled by defaut and i can confirm if it is by defaul tonight. However the log file is littered with:
"not enough diskspace for timeshift! (less than 1GB)"
and when there are several of them in a row there is always the following error:
RemovePopup, id = ZapError

But i think this might be a red herring because if timeshift is the offender then why doesnt the box lock up sooner when the timeshift lines appear in the log?

Rob van der Does

17-10-14, 17:18

Timeshift is disabled by default.
And as I said: apart from that no clue from the log.
With settings I actually meant your service settings (channel list); how did you obtain it?

chris16v

17-10-14, 18:02

confirmed: timeshift is set to disabled

my services/bouquets have been created solely by the autobouquetsmaker, both 28e and uk cable provider. both appear to be correct and work fine.

so what do we think guys, dodgy reciever or flakey image? ( i can always download an earlier build revisions if anyone can confirm which one to download, 41,43,47,54,57?)
My day job is a windows regression tester, so i am happy to follow any suggestions, but my gut feeling is its the box especially if no one else is reporting similar problems.

DaMacFunkin

17-10-14, 19:16

chris16v

17-10-14, 21:30

But did you toggle disabled to something else, save it then toggle it back to disabled, reason i ask is if i don't do this on a fresh flash with no settings restore, i can sometimes get a enigma2 reboot which i can trace to auto resolution, even though auto resolution is disabled, turning it on, saving settings, then turning it off again and saving solves the problem.

thanks for the suggestion but thats news to me mate cos I have always done fresh flashes without settings restores. I was gonna say you lost me there because i have never known that to be a linked issue that i have ever seen. Personally i think if the image has timeshift set as disabled by default and i havent touched it then it shouldnt be an issue should it?. Has what you are describing been raised as a known bug cos i cant see many people knowing about what you have described.

Apart from DaMacFunkins idea (i will try it), do we have any other suggstions? older image,, or maybe send the box back as faulty?

Rob van der Does

17-10-14, 21:34

Is there any other image available for the box? 4Od or so?

judge

17-10-14, 21:51

You really are going to have to try a few suggestions made for yourself. All we can look at is one log, you have control of the box.
Also try putting a 4GB+ stick in the box & format it in the box so it's in ext4 & mounted as /hdd
This might help us tell if it's a timeshift issue, and no, it's not a known issue.

Rob van der Does

18-10-14, 06:30

Could you please stop all softcams and see if the issue is there (obviously using FTA services)?

Sicilian

18-10-14, 06:32

Just been reading thru this thread. Imo something is being setup wrong and you need to track down what.

I'd suggest the following.

1) Disconnect ALL storage devices even Internal HDD is you have one.
2) Do a complete fresh and setup of latest ViX Build here http://www.openvix.co.uk/index.php?dir=TM-Nano-3T/ DO NOT RESTORE ANY BACKUPS.
3) Setup ONLY for FREESAT using Autobouquetsmaker, set for your area. Menu > Setup > Service Searching > AutobouqetsMaker.

Do not setup or add ANYTHING extra, no softcams, nothing, run exactly as free to air for at least 24 hours. Use EXACTLY as default, do not setup and EPG import settings, nothing.

lemi

18-10-14, 07:42

Are you using cs or sub?
Like Rob said,disable softcam and try FTA channel.

chris16v

18-10-14, 09:53

ok as instructed by the judge i have initialsied a stick in ext4, mounted it as /media/hdd in order to test the timeshift errors we are seeing in the log. ( tested by making sure i could pause tv)

this means from a new flash i only have oscam, a hdd stick mounted and bouquets from autobouqetmaker configured, but yes it locked up again

the log is attached.

37831

as for the suggested tests by rob van der does, sicilian & lemi i will do those logically one at a time over the next few days and keep the posting here to a minimum (apart from test results & log) to avoid too much noise for anyone reading this. (thanks for your help so far)

chris16v

18-10-14, 20:52

this log is up to the point of the lastest lockup.
The test was default image: rev 54, cccam plugin, usb stick as hdd, left on a premium 28e service.

37861

next: test will be default image, all softcams removed, usb stick as hdd left on fta service.

ronand

18-10-14, 21:06

Are you reflashing the receiver or just doing a factory reset?

chris16v

19-10-14, 00:07

Are you reflashing the receiver or just doing a factory reset?

reflashing ronand

Sicilian

19-10-14, 06:00

chris16v

20-10-14, 10:37

Sicilian, i will be starting your suggetsed test tonight once i get home tonight.

(btw, it took 36 hours over the weekend for a lockup of the box running rev54, all softcams removed, no plugins installed, left on fta channel)

chris16v

20-10-14, 20:59

Sicilians test is underway.

-fresh flash of Apollo.62
-no storage devices attached
-Freesat using autobouquetsmaker
-NOTHING else set up at all, completely default

Sicilian, if after 24/36 hours it appears stable & for the benefit of this test, which order would you want me to add additional configuration ? (ie: my desired softcams, epg, samba, usb/hdd devices, etc). I know how to add them all but purely for this test i imagine you have a preffered order?

chris16v

21-10-14, 08:48

Morning all, here we are my 3T still locks up after a few hours of use after following the prescribed test plan.
I switched on debugging around 9pm last night, left on an fta channel and found it had locked up this morning. Hopefully there is a clue in the log but having parsed it quickly i dont see a giveaway.

log file here>>> 37889

what did i configure, what did i install/set:
-fresh flash of Apollo.62
-no storage devices attached
-Freesat (only) using autobouquetsmaker
-NOTHING else set up at all, completely default, nothing at all

So there we are chaps, completely default flash, do we have a faulty box that i should now go back to WOS with? Its no good other members telling me theres is working fine cos that doesnt appear to matter now. I have been testing all different scenarios for 10 days and i am obviously feeling a bit frustrated.

Sicilian

21-10-14, 08:55

So there we are chaps, completely default flash, do we have a faulty box that i should now go back to WOS with? Its no good other members telling me theres is working fine cos that doesnt appear to matter now. I have been testing all different scenarios for 10 days and i am obviously feeling a bit frustrated.

Yes email WoS.

Humbucker

28-10-14, 17:23

Hello.
Chris 16v have you fixed the problem or did you return the receiver.
I am having the same / similar problem, it came with the vix 054 image and I was only watching free view on cable and the tv screen goes black and no function from the remote, so after speaking to WOS I flashed the receiver with vix 064 and its still the same on free view with nothing extra installed, no cams no plugins no hard drives.
It still does the same with no softcams installed, no internet, no cable, only power lead and HDMI lead and mine still goes to a black screen with the remote not functioning. Only way to get it going again is to power it down then up again.
It seems to me a hardware issue either a faulty component on the main board or possibly a dry joint on a component.
The receiver is in the open and is not hot.

world-of-satellite.co.uk

28-10-14, 19:43

Humbucker

28-10-14, 21:50

Thanks. World of Satellite
I have emailed you the details.

jwok

28-10-14, 21:50

I'm experiencing the same problem. First with the supplied 4D image and now with the latest Vix image. Even tried running with the lid off but still getting random blackouts that can only be resolved by power off & restart. Order ID 18263. I'll email the details to WoS.

tony97568

04-11-14, 03:18

tony97568

04-11-14, 06:36

Chris16v / Humbucker, jwok
I'm also seeing random blackouts on my TM-Nano-3T, 1-2 per day. I thought it might be an issue with mgcam1.38a (that was the issue I was looking to cure until I saw this thread) as the FTA channels continued to work. Restarting the softcam usually cured the problem although I do recall having to power the box down on at least one occasion to get rid of the black screen and the cam back up and running. Don't recall losing the FTA channels yet but will look out for it. Only had my box 4 days but coming from a iBox2 am used to having my box freeze but wasn't expecting it from this one. WOS Order ID 18812, looks like I need to get in touch.
Firmware:Apollo.071
Driver date:20141017
No HDD, server storage
USB for Image storage and a separate one for time shift.

WoS have got back to me already with some things to try. Thanks for the quick response

"Re-flash your receiver and setup for free to air only. Do not restore any backups.

How to flash process is the same as the Nano-2T
http://www.openvix.co.uk/index.php?dir=Guides%20and%20Tutorials/Flashing%20Guides/&file=How%20to%20flash%20a%20TM-Nano-2T.pdf

Images here
http://www.openvix.co.uk/index.php?dir=TM-Nano-3T/

Set up as FREE TO AIR ONLY.
DO NOT INSTALL ANY EXTRA PLUGINS.
TEST FOR AT LEAST 24 HOURS.

Please advise if the receiver locks up or looses HDMI output."

Will give it a go and report back. Thanks again WoS

irfyd

05-11-14, 15:41

WoS have got back to me already with some things to try. Thanks for the quick response

"Re-flash your receiver and setup for free to air only. Do not restore any backups.

How to flash process is the same as the Nano-2T
http://www.openvix.co.uk/index.php?dir=Guides%20and%20Tutorials/Flashing%20Guides/&file=How%20to%20flash%20a%20TM-Nano-2T.pdf

Images here
http://www.openvix.co.uk/index.php?dir=TM-Nano-3T/

Set up as FREE TO AIR ONLY.
DO NOT INSTALL ANY EXTRA PLUGINS.
TEST FOR AT LEAST 24 HOURS.

Please advise if the receiver locks up or looses HDMI output."

Will give it a go and report back. Thanks again WoS

Hi guys I jus rec'd mine today from WoS pre-installed 1tb HD.. everything was going so well then the box froze hav to power off from back.
came with v 070 done software update to 073...I hope this gets fixed quick

Humbucker

05-11-14, 19:51

Just a quick thank you to The World of Satellite team for sorting my out my issues with the Technomate Nano 3T Combo.
New receiver up and running and has been on for 10 hours with no glitches.
Thanks again for your prompt attention and excellent service.:thumbsup:

irfyd

05-11-14, 20:04

Humbucker

05-11-14, 20:38

I would try this first. flash with latest image but don't install anything just set up the screen so you can see the vix page .
Remove the Ethernet and any other cables and drives and just have power lead and the Hdmi cable in.
Make sure the receiver is in the open for this test. Keep checking every hour to see if the vix screen is still there and the remote is still working.
Mine stopped after 5 hours then once it went black it would do it quicker.
If yours does the same get in touch with your supplier.
I think mine must have been hardware, my new replacement seems good after 11 hours

tony97568

06-11-14, 03:51

Update on my black screen issue - In my case I think it was cam related, and not a hardware.

-Since following the recommendations from WoS my box has been working fine (FTA only). I don't put the box into standby over night and its still displaying BBC1 in the morning, just as I left it. Its been 2 days now without a glitch so I'm now going to start to use Mgcam again with a concious effort to check that if I get the black screen, I check the screen is still being driven (press "ok" or "menu"), just to check I get a response from the box and the HDMI still outputs.

Really pleased with my purchase so far. Thanks again to WoS for the support.

chris16v

01-12-14, 11:53

guys, an update to my experience. WOS kindly replaced my 3T and i got a new one 2 weeks ago.

however i am still seeing the same issue where the box randomly locks up. This surely suggests a local install issue? So I have reduced the test down to FTA only, no cams, nothing else running and still it locks up on latest image rev.

WOS have suggested it could be a short on my lnb feed so i moved to the box into another room and onto a different lnb feed. But the same issue persists. Plus i also have a VUsolo plugged into the same cables and this doesnt lock up on either of the two lnb feeds i have tried the 3T on.

Failing taking the box to another address and leaving it plugged into someone elses dish, i dont know what other test i can do. i honestly dont want this box anymore. Maybe its tuner is too sensitive by design?

i am really mystified and dispondant. Out of interest, the other members who are having issues what kind of setups do they have? i am using a multi lnb system & a 28e dish all going into a diseqc switch. But never had a shorting issue with any other box.

s2tephen

01-12-14, 17:43

Re flash with the original technomate image and see if it locks up on it or at least try another.
leave it running free to air and see.

tony97568

01-12-14, 19:19

Chris
Just been experiencing what I thought was a lock up on mine, but only since updating to ApolloHD90 (Box has been stable since 06-11). I have occasionally been getting black screen again so went back to vix 89 (which had been stable for me) but still got the issue, very puzzling. I would restart the box and it would start working ok. However, with my issue I noticed yesterday that the menu function was still working on the front screen so the box hadn't locked up, it had just stopped outputting through HDMI. Using the screen on the box I navigated through to the restart option and restarted the box and all worked fine again. After a bit of digging around in the settings I found that my default output had changed from HDMI to scart. If I restarted the box it seem that there is some wake up function between my tv and the nano and the HDMI would output ok. When I switched my TV to terrestrial TV output then back to the HDMI channel the nano was plugged into I got the black screen again. I have now reflashed my box with HDMI as the default output and have not had a problem since. Fingers crossed.

(Still on VIX 89, will give it a few days then update to the latest image. ),
Hope this is of some help.

chris16v

02-12-14, 16:37

irfyd

04-12-14, 23:56

tony97568 thanks for your feedback its interesting what you have highlighted.

In my case not only is HDMI output dead but the front screen is fronzen as well (no front panel buttons working), as well as ethernet not working either, so in my case the box is totally dead when it locks up.

This is exactly same issue I had with my first 3T box.. Either its a hardware issue or software/driver related. Really need this to be sorted as the 3T I can see has potential and will be very popular once the kinks are worked out. Picture on 3T is better than VU+ Ultimo IMO

I have left the 3T at parents place so not sure if the issue still exists but I have a bad feeling its still there.

irfyd

30-12-14, 15:00

This is exactly same issue I had with my first 3T box.. Either its a hardware issue or software/driver related. Really need this to be sorted as the 3T I can see has potential and will be very popular once the kinks are worked out. Picture on 3T is better than VU+ Ultimo IMO

I have left the 3T at parents place so not sure if the issue still exists but I have a bad feeling its still there.

Just update have tested 2 more 3T both have no issue at all..Either software has sorted this issue or maybe a few boxes were affected.

All in all very good box just wish the remote was better but PQ is great.