Re: [QtMoko] hwclock issue
2010/1/26 Joif : > > Hi! > I'm using QtMoko v16b on the NAND and I have other distro on the uSD. > My time is GMT+1 and when I have to choose the correct time on QtMoko I set > it on the Paris time zone. But when I use another distro I see that the time > reported is exactly GMT not GMT+1. I don't really know about this part - but could just be that the other distro doesn't have correct time zone set up. > Also, some time after a reboot (and > specially after using Debian) I see during the boot an error message about > the impossibility to read the hardware clock and to set the time to > 01/01/1970. Recently understood; please see here: http://www.mail-archive.com/community@lists.openmoko.org/msg57473.html > This error disappears from the boot only if I remove the > battery. Ah, that is interesting. That would explain why I have stopped seeing this problem. (I've been trying out SHR testing, and now my RTC is working even when I switch back to Debian. I was struggling to understand why that was.) Regards, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[QtMoko] hwclock issue
Hi! I'm using QtMoko v16b on the NAND and I have other distro on the uSD. My time is GMT+1 and when I have to choose the correct time on QtMoko I set it on the Paris time zone. But when I use another distro I see that the time reported is exactly GMT not GMT+1. Also, some time after a reboot (and specially after using Debian) I see during the boot an error message about the impossibility to read the hardware clock and to set the time to 01/01/1970. This error disappears from the boot only if I remove the battery. This is what I have if I give date and hwclock in the terminal of QtMoko: neo:~# date Tue Jan 26 23:54:02 CET 2010 neo:~# hwclock Cannot access the Hardware Clock via any known method. Use the --debug option to see the details of our search for an access method. neo:~# hwclock --debug hwclock from util-linux-ng 2.13.1.1 hwclock: Open of /dev/rtc0 failed, errno=16: Device or resource busy. No usable clock interface found. Cannot access the Hardware Clock via any known method. -- View this message in context: http://n2.nabble.com/QtMoko-hwclock-issue-tp4464053p4464053.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
