I checked my Mac & discovered its timeserver was one on our local network. -time-from & edited to reflect the local time server, rather than the ones in the Pi. It can also take a very very long time to adjust the clock, during which period the time is totally wrong; I think that's why ntpd has an extra lower limit (e.g. To make it worse I believe recent builds of Linux 3.17 have a bug on the B (at least) which cause time drift, maybe a few seconds in 24 hours.
However, I have now discovered it must be related to the University network; I tried just now & it didn't update the time/date. I spoke to a colleague, who suggested that it could be the time server. If you're as clueless as me when it comes to linux, I used the LX Terminal & In general if you are using NTP to set the RPi clock you must do it in two steps: 1) Set the clock approximately correct using another program, such as ntpclient; this reads the time from an NTP server (e.g. Some system boots have a 'swclock' approach that reads a datestamp off the file system and applies it to the system clock; this prevents time going backward on the root file system. There are multiple different implementations of ntpd however I believe they all use the kernel 'adjtime' interface and that has hardware specific limitations on how large an adjustment it can make, in addition to whatever limit the ntpd implementation imposes. Enter "org" (no quotes) reboot system and you're good to go!
This HOWTO attempts to provide a simple and cross-distribution one-time solution to the issue, making sure all your distributions know that your hardware clock is set to the local time (or UTC if you prefer it).
This is a one-time procedure to ensure that your hardware clock's time zone is correctly and consistently recognized by all the Linux installations you multiboot on a single machine.
Assuming you are dual-booting Distro X and Y, first boot into Distribution X.
Warm Regards, Sivakumar Hello, If there is internet connection available follow the steps to set the date 1. I haven't proved that yet to my satisfaction but if you are using 3.17 you might want to watch out for the problem; it manifests as ntp continually logging increasing drifts in the time (use dmesg). The firmware has moved on a bit (for example, the zero is "overclocked" to 1GHz by default).
When an update is available, a popup will be displayed to flash the update Warning: This procedure will NOT work on USB 3.0 only systems.
This process is provided as a courtesy, and requires the use of third party utilities to create the bootable USB key.
The Raspberry Pi does not have a RTC (Real Time Clock) module and it is not able to keep the date and time without a power source.
If your Raspberry Pi is not connected to the Internet, you are out of luck and the only option is to buy and install an RTC module.