gumball3000

Or: how do I install the open source drivers? Is that another package?

This happened with the OpenPLi from a week ago or so. So it should have the latest closed source driver, I guess? Or do I need to install them manually?

Ahh, cool, thanks a lot!

I have 1.0-rc2 installed. This needs to be pushed to the official repository.

And a little feature request: An option to always set a static *good* date like "2014-01-01 01:00" during boot, before trying to use ntpdate, would be very helpful for those VU Duo2 boxes, so that they will not revert to these strange pre-1970 dates if ntpdate fails.

Okay so I have learned from this thread: http://openpli.org/f...ndpost&p=424638

This is a problem in the VU+ drivers, that do funny things if the date on the box is not correct. And for some reason the box doesn't boot in 1-1-1970 like any other linux machine, but with a date in 1958.

So my guess is: When a VU Duo2 crashes/freezes (of yet unknown cause) it may corrupt the system time / make it revert to the default value of 1923 (for my box, others seem to have 1958 etc). Because if I forcefully plug/unplug it ,it always seems to revert to 1970, not the strange one.

So my fix is:

+) deleted "/etc/rcS.d/S42ntpdate.sh" created by Engima2 SystemTime plugin

+) added "/etc/network/if-up.d/02ntpdate" which calls ntpdate

+) added "/etc/rcS.d/S01date" which points to "/etc/init.d/S01date" which sets the date to a valid one ( /bin/date -s "2014-03-28 09:26" )

Now the date is always set to "2014-03-28 09:26" on each boot, and if a LAN cable is plugged it will use ntpdate during boot.

If no LAN cable is plugged during boot, but afterwards, hopefully the SystemTime E2 plugin will refresh it.

Hopefully this will be useful for others

The date jumps seem to go like that:

*cold boot after power loss*

1970 (epoch 0)

2014 (correct date)

1923 (negative timestamp) 

at this point the box becomes unusable slow because of the low-date timing issues