Date is 1970 on Utilite
Home › Forums › GeeXboX on ARM SoCs › Date is 1970 on Utilite
This topic contains 14 replies, has 3 voices, and was last updated by
peduro 2 months ago.
-
AuthorPosts
-
Hello
Why is it when I put a devel tar image on a SD card and boot it on my Utilite Pro the date is 1970? I can set the time using the date command but I just wonder why it does not use RTC or NTP?
Would you like me to look for something in system messages?
Peter
hum, same here
we have to enable ntpd with networkmanagerBesides that: Do we know anything about the RTC in the Utilite? Are there two RTCs like it is in CuBox-i or is the on-chip RTC battery backed?
one rtc enabled with CONFIG_RTC_DRV_EM3027=y
edit :
if I use ntp manually and store date using hwclock, at next reboot, i have the correct date and timeone rtc enabled with CONFIG_RTC_DRV_EM3027=y
Nope. Then it has two. One inside the iMX.6 (i.e. on-chip) and one external (accessed via I2C). I guess the on-chip one will loose it’s time when the device is powered off, while the external EM3027 has a backup battery. The question is which one maps to /dev/rtc…
BTW, rtc-em3027.c lacks support for device table and there is no mention of it in imx6q-cm-fx6.dtsi. So I’m not so sure that this driver will be loaded at all on a 3.14.xx kernel.
snvs_rtc 20cc034.snvs-rtc-lp: rtc core: registered 20cc034.snvs-rtc-lp as rtc0
snvs_rtc 20cc034.snvs-rtc-lp: setting system clock to 2015-02-10 19:27:57 UTC (1423596477)
if it can help
dmesg | grep -e em3027 shows nothing. I guess you are right. It does not work on 3.14
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/315533.html seems promising
edit
with http://lxr.free-electrons.com/source/arch/arm/boot/dts/tegra20-trimslice.dts#L306Yup. That’s the way to go…
ok got EM3027 working, now have to prepare a patch for this
@peduro : please test this version :
http://download.openbricks.org/utilite/geexbox-devel-20150211-r110437a.utilite.tar.xz
ETL to upload : 35 minIf your are at this, you might add a proper:
.owner = THIS_MODULEto the em3027_driver struct… Also we need to check why the fallback to NTP didn’t work.
Edit: I just saw that your patch changed the *.dtb name. So it will not work when the system is installed onto the internal harddrive.
Done
Will retest the kernel with this
Thanks Rudiedit :
Yes, I need to recreate a proper file for thisfor ntp, I think the problem is related to networkmanager (connman won’t work with this new kernel, something is bad in config file for linux, but didn’t found what)
Thanks, I will try the new image tonight. Meanwhile i found how to do it using commandline just to make sure I have no connection problems. I am connecting using SSH so I cannot cut the power to see if time is kept.
root@geexbox:~# hwclock -r
Thu Jan 1 15:31:19 1970 0.000000 seconds
root@geexbox:~# date
Thu Jan 1 16:31:45 BST 1970
root@geexbox:~# ntpd -q -p ntp.fullrate.dk
root@geexbox:~# date
Thu Feb 12 09:22:24 GMT 2015
root@geexbox:~# hwclock -r
Thu Jan 1 15:47:33 1970 0.000000 seconds
root@geexbox:~# hwclock -w
root@geexbox:~# hwclock -r
Thu Feb 12 09:24:35 2015 0.000000 seconds
root@geexbox:~# shutdown -r now
………….logging in again:
root@geexbox:~# date
Thu Feb 12 09:35:26 GMT 2015please use this one : http://download.openbricks.org/utilite/geexbox-devel-20150212-r2a02cd6.utilite.tar.xz , install it to your µsdcard.
ntpd should work just fine, better support for high videos, no more log in dmesg about usb
(ETL 20 min)then if you want to install it to your internal drive, please, do remotely :
wget http://download.openbricks.org/utilite/geexbox-devel-20150212-r2a02cd6.utilite.tar.xz install-utilite /root/geexbox-devel-20150212-r2a02cd6.utilite.tar.xzI tried your new image and it solves the RTC and time sync problem! And yes I am exited to try Kodi in the comming days. Thank you for being so fast at solving the date problem and putting it up.
-
AuthorPosts
You must be logged in to reply to this topic.