Re: Chumby One Time

chumby:~# ntpdate -q; hwclock -r -u; date
server, stratum 2, offset -6.520513, delay 0.10034
server, stratum 2, offset -6.528184, delay 0.13609
server, stratum 2, offset -6.524852, delay 0.13974
9 Jan 10:35:23 ntpdate[11759]: step time server offset -6.520513 sec
Sat Jan  9 10:35:23 2010  0.000000 seconds
Sat Jan  9 10:35:23 EST 2010

Re: Chumby One Time

I believe ntpd is already included.  If not, it'll definitely be included in the next release.

We're also going to tune the driver so that it's more accurate for the next release.

Re: Chumby One Time

BTW, does the Chumby use the NTP server information the DHCP server hands out (dhcp option 42)? I'd say it should...

C1 user in Germany

Re: Chumby One Time

There is a script that syncs the chumby's time.

Script /usr/chumby/scripts/ already exists:

# Options:
# -b   Boot option - allow for large jump in time

if [ ! -e /psp/use_ntp ]; then
    echo 1 >/psp/use_ntp

if [ `cat /psp/use_ntp` -eq 1 ]; then
    # rdate is deprecated - use only if /psp/use_rdate is present
    if [ -e /psp/use_rdate ]; then
    rdate -s
    [ -f /psp/ntp_server ] && NTPSERVER=$(cat /psp/ntp_server)
    ntpdate ${NTPSERVER}
    echo `date +%s >/tmp/time_update`


This script is run via crond, I believe the default is once per day, I've changed mine and I can't remember how it started sad

crontab -l

to see how your cron is setup

I've edited my crontab to

0 0,3,6,9,12,15,18,21 * * * /usr/chumby/scripts/

This change means it will sync time on the 3 hour marks.

Be careful in the crontabs as that is also what causes the flashplayer_watchdog to run every minute (the thing that should fix your chumby if the control panel crashes).

Chumby Classic (White) user.  Be forewarned my comments reflect my knowledge of this device.

Re: Chumby One Time

What ever happened to Chumby providing a firmware update for the time drift problem?

Re: Chumby One Time

The fix for this is in QA.

Re: Chumby One Time

chumby:~# ntpdate -q; hwclock -r -u; date
server, stratum 2, offset -289.788059, delay 0.05844
server, stratum 2, offset -289.787880, delay 0.05539
server, stratum 2, offset -289.788712, delay 0.05461
30 Jan 13:59:38 ntpdate[9366]: step time server offset -289.788712 sec
Sat Jan 30 13:59:38 2010  0.000000 seconds
Sat Jan 30 13:59:38 CET 2010

My C1 has drifted even five minutes ahead. That's quite annoying when getting waked up too early in the morning wink


Re: Chumby One Time

Having this problem as well.  Good thing I've never trusted my Chumby as a true replacement alarm clock. 

Hope to see a fix soon, but I don't think I'll ever be confident that the time is without fault.

Re: Chumby One Time

Another Chumby One user with a 5 minute drift.

Tar, feathers, congress. Some assembly required.

Re: Chumby One Time

After some days....

Stevefalco's patch working fine for me! smile

Re: Chumby One Time

Adding this line to crontab should sort of fix it:

15 0/6 * * * /usr/bin/ntpdate

@Chumbians, what's the good of anyway?


Re: Chumby One Time gets run as part of the network startup process.  So as soon as you have a network connection, you'll get the time.

I believe it's also responsible for setting the hardware clock, which gets used if you start up without a network connection.

Re: Chumby One Time

We're releasing a beta firmware that uses ntpd.  Please try it and see if that addresses the issue.