PINE64

Full Version: Debian do not remember my time setting.
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
When I start my Pine the time is wrong. So I click the clock in the upper right corner and set it right.

The next time I start the Pine the time is wrong again.
I am in CET and it is set to CET and it is till 2 hours off every time I start it.
Do you have a RTC backup battery connected?
I have been experimenting with the RTC backup battery on my cb&dt Play Box. The pine store has two models (both 3v) the one I'm using which uses AA cells, and the other one which uses CR2032 cells. The RTC batt holds the realtime clock running while the unit is OFF.
No battery. I just assumed that the system connected to a time server on startup like the Raspberry :-$
You can certainly install a ntp client to do that...
Turns out ntp was installed when I ran "apt-get install ntp" What confuses me is that the clock is consistently set 2 hours wrong when I start up.
(08-11-2016, 02:33 PM)xalius Wrote: [ -> ]You can certainly install a ntp client to do that...

yea... this is strange.

I have moved to the ubuntu image so I can replicate the behavior...


but it was either tzselect or timedatectl - and i felt like I didn't experience this same issue
(08-11-2016, 03:00 PM)Wolfenstein Wrote: [ -> ]Turns out ntp was installed when I ran "apt-get install ntp" What confuses me is that the clock is consistently set 2 hours wrong when I start up.

You can start and stop the service and it will straighten up.  This same behavior can be seen on the latest Raspbian on the RPi too.  Its very frustrating... on my RPi (one of my plethora) the clock will be off six hours till I sync up... stop , restart...   it has something to do with systemd service interfering with ntpd or visa versa
There is also a setting somewhere if the hardware clock is set to local time or UTC, that influences how the timezone is applied, can't remember right now where that was... but it could explain the behavior
(08-11-2016, 03:26 PM)xalius Wrote: [ -> ]There is also a setting somewhere if the hardware clock is set to local time or UTC, that influences how the timezone is applied, can't remember right now where that was... but it could explain the behavior

I don't know if this is what you are talking about but this has always fixed my time settings with my pines. this is on my little cheat sheet.

Run 'dpkg-reconfigure tzdata' if you wish to change it. timezone
(date) is the time check command