#10367 NORM -: [CL1B] Moon activity cannot open.
Zarro Boogs per Child
bugtracker at laptop.org
Tue May 24 20:11:55 EDT 2011
#10367: [CL1B] Moon activity cannot open.
-----------------------------------+----------------------------------------
Reporter: Andy Pei | Owner: Quozl
Type: defect | Status: new
Priority: normal | Milestone:
Component: hardware | Version: 1.5-C2
Resolution: | Keywords:
Next_action: communicate | Verified: 0
Deployment_affected: | Blockedby:
Blocking: |
-----------------------------------+----------------------------------------
Comment(by Quozl):
G'day Garysu,
Not sure if this will answer you.
The RTC is most easily set using OpenFirmware ''ntp-set-clock'' command,
like this:
{{{
ok wifi olpc
ok ntp-set-clock
Scan for: olpc found
Associate with: olpc
DHCP got 10.0.0.2
2011-05-24 23:58:30 UTC
ok
}}}
(''olpc'' above was the SSID provided by the wireless access point).
The current value in the RTC can be shown using OpenFirmware:
{{{
ok .clock
2011-05-25 00:01:33
ok
}}}
The update progress of the RTC can be tested using OpenFirmware:
{{{
ok watch-clock
}}}
To set the RTC in Sugar, using the internet:
{{{
sudo ntpdate pool.ntp.org
sudo hwclock --systohc
}}}
I expect there is already a step in the manufacturing process where the
RTC is being set, since most units have it set. The units that did not
have it set may have either bypassed that step, or may have lost power to
the RTC after that step.
There is no automatic network synchronisation of the RTC by Sugar or our
operating system builds, as far as I can recall. I think there are
security system considerations, since NTP is not trusted and an attacker
can easily set up an NTP server that shows the wrong time.
--
Ticket URL: <http://dev.laptop.org/ticket/10367#comment:13>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list