Ubuntu time not updating
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.
Some people prefer setting their hardware clock to UTC (Universal Coordinated Time) instead of local time.
Remember that the Raspberry Pi doesn't have a real-time clock (unless you add one yourself) so unless you're connected to the internet you'll have to set the time every time you power on or restart.
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!
Now boot into Distro Y and follow the same steps as above.
It doesn't matter that the hardware clock is now set correctly, you can still reset the clock once to make sure that every distribution you multi-boot recognizes the hardware clock as set to the local time.
For example, assume you are dual-booting two Linux distributions, Distro X and Distro Y.
This process will not be supported by Dell Technical Support. Note: This procedure may not work on systems that were not capable of having Linux factory installed.
This process will not be supported by Dell Technical Support.
I've got the Pi on the network - both using Ethernet & Wifi, and that's fine. I've used the suggestion of setting the time zone (or, more to the point, tried changing it to another & back again); and have left it for about an hour, in case it needed time to think about the whole business ...
Warm Regards, Sivakumar I've had problems with this too ...
Use the image below as a sample of what the UNetbootin screen should look like.