Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.
Results 1 to 14 of 14

Thread: Technomate TM-2T box freezing whilst in standby

  1. #1

    Title
    Junior Member
    Join Date
    Sep 2013
    Posts
    4
    Thanks
    0
    Thanked 2 Times in 1 Post

    Technomate TM-2T box freezing whilst in standby

    I have recently purchased a Technomate TM-2T and every so often the box freezes whilst in standby and the clock freezes on the front display.

    No button on the receiver or on the remote will do anything, the only way to get it back working is to do a cold boot and restart with the switch on the back of the receiver.

    Has anybody seen this before?

    Regards
    Glyn

  2. #2
    Larry-G's Avatar
    Title
    V.I.P
    Donated Member
    Join Date
    May 2010
    Posts
    32,542
    Thanks
    7,824
    Thanked 22,935 Times in 12,378 Posts
    Which exact image and build number ?

    you can see this by navigating to Menu> Information> About.
    My posts contain my own personal thoughts and opinions, they do not represent those of any organisation or group but my own.

    If you don't like what I post, Don't read it.

    SIMPLES.

  3. #3
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,363
    Thanks
    6,444
    Thanked 9,160 Times in 6,235 Posts
    I have experienced this on the twin. Unfortunately debug logs were off, so didn't see any point in posting something nobody could check into. Only seems to happen when the last channel viewed was not on 28.2.

  4. #4

    Title
    Junior Member
    Join Date
    Sep 2013
    Posts
    4
    Thanks
    0
    Thanked 2 Times in 1 Post
    The image I'm using is VIX

    Version - 3.0
    Build - 750
    Kernel - 3.5.3
    Drivers - 2013-09-17

  5. #5
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,363
    Thanks
    6,444
    Thanked 9,160 Times in 6,235 Posts
    Done it again today. Time got stuck at 14:00. Log file is showing as 468313 KB in size, so can't upload.

    Last part of log shows a repetitive
    Code:
    --- <exception caught here> ---
      File "/usr/lib/python2.7/site-packages/twisted/internet/base.py", line 1181, in mainLoop
        
      File "/usr/lib/enigma2/python/e2reactor.py", line 158, in doPoll
        
    exceptions.OverflowError: Python int too large to convert to C long
    Unhandled Error
    Traceback (most recent call last):
      File "/usr/lib/enigma2/python/mytest.py", line 695, in <module>
        runScreenTest()
      File "/usr/lib/enigma2/python/mytest.py", line 543, in runScreenTest
        runReactor()
      File "/usr/lib/enigma2/python/mytest.py", line 114, in runReactor
        reactor.run(installSignalHandlers=False)
      File "/usr/lib/python2.7/site-packages/twisted/internet/base.py", line 1169, in run
        
    --- <exception caught here> ---
      File "/usr/lib/python2.7/site-packages/twisted/internet/base.py", line 1181, in mainLoop
        
      File "/usr/lib/enigma2/python/e2reactor.py", line 158, in doPoll
        
    exceptions.OverflowError: Python int too large to convert to C long
    Build 761, USB flash with settings/plugin restore.
    Plugins installed
    Rats Picon updater,
    Autobouquets 28.2
    OnDemand

  6. #6

    Title
    Junior Member
    Join Date
    Sep 2013
    Posts
    4
    Thanks
    0
    Thanked 2 Times in 1 Post
    I got in from work today and the box had got stuck at 14:29, so had to do a cold restart.

    Still on build 750.

    Any ideas what is causing this as I'm getting frustrated now as I'm missing recordings?

  7. #7
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,363
    Thanks
    6,444
    Thanked 9,160 Times in 6,235 Posts
    Quote Originally Posted by ghturbo2000 View Post
    I got in from work today and the box had got stuck at 14:29, so had to do a cold restart.

    Still on build 750.

    Any ideas what is causing this as I'm getting frustrated now as I'm missing recordings?
    Problem will not be resolved unless logs are created/uploaded. Please make sure that the debug logs are enabled.

    Thankfully, this is only affecting a very limited number of people/other people not reporting it.

  8. #8

    Title
    Junior Member
    Join Date
    Sep 2013
    Posts
    4
    Thanks
    0
    Thanked 2 Times in 1 Post
    Ok I have set that up now, if it does it again I will upload to this thread.

  9. The Following 2 Users Say Thank You to ghturbo2000 For This Useful Post:

    abu baniaz (25-10-13),judge (25-10-13)

  10. #9

    Title
    ViX Beta Tester
    Join Date
    Jan 2011
    Posts
    14,099
    Thanks
    3,389
    Thanked 4,102 Times in 3,198 Posts
    Please do an E2 restart or full reboot now in order for debug logs to be generated.

  11. #10
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,363
    Thanks
    6,444
    Thanked 9,160 Times in 6,235 Posts
    It's just done it again, twice on the trot. It is still in this state if any of the devs want to have a telnet session into it. Supposedly 588 MB log saved to PC.

    There is this section which is repeated over and over again, first line is found 851114 times.
    --- <exception caught here> ---
    Code:
      File "/usr/lib/python2.7/site-packages/twisted/internet/base.py", line 1181, in mainLoop
        
      File "/usr/lib/enigma2/python/e2reactor.py", line 158, in doPoll
        
    exceptions.OverflowError: Python int too large to convert to C long
    Unhandled Error
    Traceback (most recent call last):
      File "/usr/lib/enigma2/python/mytest.py", line 695, in <module>
        runScreenTest()
      File "/usr/lib/enigma2/python/mytest.py", line 543, in runScreenTest
        runReactor()
      File "/usr/lib/enigma2/python/mytest.py", line 114, in runReactor
        reactor.run(installSignalHandlers=False)
      File "/usr/lib/python2.7/site-packages/twisted/internet/base.py", line 1169, in run
    TMTwin with upgraded VFD chip, build 775, USB flashed with a restore.
    Plugins:-
    Autobouquest E2
    OnDemand
    Neutrino HD
    Mgcamd

    Vhannibal chanenl list, think it was 01/11/13.
    Attached Images Attached Images

  12. #11
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,363
    Thanks
    6,444
    Thanked 9,160 Times in 6,235 Posts
    Happened again today. I spoke to Technomate, they said to try the 4D image. Any ideas?

  13. #12
    Larry-G's Avatar
    Title
    V.I.P
    Donated Member
    Join Date
    May 2010
    Posts
    32,542
    Thanks
    7,824
    Thanked 22,935 Times in 12,378 Posts
    No idea mate, it's never happened with mine and mine is on 24/7 or in regular standby. has this happened while using a clean ViX image or just when your using the neutrino beta ?.
    My posts contain my own personal thoughts and opinions, they do not represent those of any organisation or group but my own.

    If you don't like what I post, Don't read it.

    SIMPLES.

  14. #13
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,363
    Thanks
    6,444
    Thanked 9,160 Times in 6,235 Posts
    It started doing a few weeks ago. I have started from scratch, bootloader, no restore of settings or plugins, deleted epg from HDD just in case. Without Neutrino (which you have to kill enigma to run anyway).

    The concerning bit is that on one reboot, it got stuck on the red dot that CG121 mentioned. My PSU has always had the browning around the regulator, temp is 42.

  15. #14
    Larry-G's Avatar
    Title
    V.I.P
    Donated Member
    Join Date
    May 2010
    Posts
    32,542
    Thanks
    7,824
    Thanked 22,935 Times in 12,378 Posts
    Quote Originally Posted by abu baniaz View Post

    The concerning bit is that on one reboot, it got stuck on the red dot that CG121 mentioned. My PSU has always had the browning around the regulator, temp is 42.
    That certainly does not sound healthy, maybe a hardware fault rearing it's head ?.
    My posts contain my own personal thoughts and opinions, they do not represent those of any organisation or group but my own.

    If you don't like what I post, Don't read it.

    SIMPLES.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.