Vu+ Duo VIX crashes not recognising recording timer clash

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • tonythekiwi
    Newbie
    • Jan 2015
    • 2

    #1

    Vu+ Duo VIX crashes not recognising recording timer clash

    Latest VIX image - and few previous, have started crashing the box when recordings are scheduled and it appears the multiple timers
    are not recognising a timer clash as earlier images did.
    Anyone got any clues or suggestions to remedy.
  • ontherack
    DK Veteran
    • Apr 2011
    • 1080

    #2
    reflash working image, and submit crash logs to vix team, assuming vu genuine box.

    Comment

    • tonythekiwi
      Newbie
      • Jan 2015
      • 2

      #3
      Vu+ Duo genuine model.
      Doesn't generate a crash log. It freezes up and won't respond to any commands from remote until powered off and on again. Just a cycling VIX label in the corner but the current channel still running normally.
      I have a dual LNB with twin cables to the VU tuners.

      Comment

      • digicon
        V.I.P. Member
        • Jul 2009
        • 8261

        #4
        Sounds like the Memory Leak problem i could be wrong though, Have you tried setting up a Swap File on a USB stick to see if that helps

        Comment

        • cactikid
          V.I.P. Member
          • Sep 2008
          • 12017

          #5
          duo needs swapfile on usb stick and run cacheflush plugin get that from download plugins.i have a duo with vix also

          Comment

          • philly
            Top Poster
            • Nov 2008
            • 119

            #6
            crash vu duo outcome

            Originally posted by tonythekiwi
            Vu+ Duo genuine model.
            Doesn't generate a crash log. It freezes up and won't respond to any commands from remote until powered off and on again. Just a cycling VIX label in the corner bidut the current channel still running normally.
            I have a dual LNB with twin cables to the VU tuners.
            Did you get your problem fixed. I upgraded to the latest vix 4.0 image and am having the same issues.

            Comment

            Working...