Posted 23 November 2013 - 00:03
It's only an initial issue after setup, due to a driver problem that doesn't initialize the internal clock properly. Once it has a valid date set, the problem is gone.
What you can do is have it start and do a DHCP, lookup the IP issued, telnet into the box, and use the 'date' command to set a valid date (any valid date will do).
Once it's setup, it doesn't have this issue anymore, as it would pick up the correct date from the transponder it tunes into.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.