> > So we have an init script to get the clock in the 'ball park' >
That explains the May-ish date that I keep booting up to, instead of what this dmesg entry implies: [ 1.025090] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800) But I am still unclear as to when Debian is synchronizing /dev/rtc0 to the system clock (seems to me this is happening before boot_scripts.sh is called). I am also stumped as to why /etc/init.d/hwclock.sh is not running (/etc/rcS.d/S05hwclock.sh is symlinked to /etc/init.d/hwclock.sh, and I did perform an rc.d-update hwclock.sh). If hwclock.sh was running, I would expect one of two outcomes (since I did change which RTC the script should be using): - If it ran before boot_scripts.sh, I would expect the system clock and omap_rtc would have the correct time. - If it ran after boot_scripts.sh, I would expect the system clock to have the correct time > > https://github.com/beagleboard/image-builder/blob/master/target/init_scripts/generic-debian.sh#L19 > > > It's located at /etc/init.d/boot_scripts.sh > > You can either remove "/etc/timestamp" and it'll ignore resetting the > clock on bootup. Looking at boot_scripts.sh, it doesn't look like removing this code would solve my problem. /dev/rtc1 is not being reset by anything. It still holds the current time from where I set it yesterday. > > Regards, > > -- > Robert Nelson > http://www.rcn-ee.com/ > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
