Still no joy for me
If i type date; sudo hwclock -r i get both times simulaneoulsy but in different formats??
Fri Feb 12 02:30:01 AEST 2016
Fri 12 Feb 2016 02:30:02 AEST .125778 seconds
Do you think this could be the issue somehow? I also cannot find the Internationalisation Options in raspi-config???
Thanks again Radek,
I noticed that when i ran lsmod|grep rtc it brought up details for the ds1307 (i have a ds3231)? I amended the config.txt to show a ds1307 but this still did not work.
I have attached the details
thought i was going crazy so bought another RTC (got a ds3231) this time. Followed the instructions and hey presto!!! Still not working
I flashed another SD card with Raspian and the RTC works perfectly there. So i know the hardware is fine.
There seems to be something somewhere that is forcing the date and time back to Fri Feb 12, 02:28:16 (year 2006). I have looked and looked but cannot find anything anywhere.
Going to GPS isn't an option as it won't give me anything other than a further power drain when i'm out in the field and i'll still have to set my mount manually initially anyway.
Help me Obi Wan you're my only help..........
I think it is probably worth doing the kernel update. This is where i will need some upgrade for dummies instructions.
Hi all, me again.
Still struggling with this RTC. It is recognised by the Pi, i have installed a fresh battery, i can write the correct time to it and it displays the correct time. When i reboot it always defaults to the same date - Fri Feb 12, 02:28:16
Tried removing the RTC and then sudo hwclock -r and it is not found so i am definitely accessing the RTC module.
Do you think i have a faulty RTC module???
Any fresh ideas?
Hi all, still struggling with this RTC.
I have reflashed the SD card just in case and completed the setup. The RTC is being recognised. I let the Pi synch time via the internet and then "sudo hwclock -w" to write the time. "sudo hwclock -r" shows the correct time.
When i restart it still defaults back to Fri Feb 12, 02:28!!!!!
Is there some other clock set or some kind of override in the config that is looking at some kind of pretend hwclock?
After some more searching I have also run:
sudo apt-get -y remove fake-hwclock - this fails as it says fake-hwclock is not installed
sudo update-rc.d -f fake-hwclock remove
sudo systemctl disable fake-hwclock
Any clues? It is starting to drive me wild now
No, still no joy.
Tried the following:
Set the system clock (via control center as i couldn't work it out at the command line)
date returned the correct time
sudo hwclock -w seemed to work, sudo hwclock returned the correct time.
Switched off and back on and the wrong date/time displayed
sudo hwclock -w --systohc changes the hwclock time but it went back to the wrong date after a restart.
Cannot figure out what i'm doing wrong. Even tested the battery which is giving out a healthy 3v.
Thanks Kaczorek, i'll smash a few buttons until it works
I have attached an image of what i see.
Not sure if that means it is recognised?
Hi guys, i'm a bit of a beginner when it comes to linux (which is a bit embarrassing as a manager of an Application support team!).
I have just purchased an RTC for my Pi 3b+ so that i'm not messing around with times when i'm out in the field. I have followed all of the instructions i can find but the RTC still won't work
Is there anybody who would be kind enough to help me out with the config please?
The module is I2C RTC DS1307 purchased from GearBest.
The instructions are at wiki.52pi.com/index.php/DS1307_RTC_Modul...erry_Pi_SKU:_EP-0059
Any help you could offer would be greatly appreciated.