Here is a section from an older version of the Fix_clock ( see http://xoshare.org/mi
Getting to the prompt
All these commands are typed on the "other" laptop that is connected serially to the one with the bad clock
Power on the laptop under test. You should see "Page Fault" on the serial terminal, followed by an "ok" prompt. If you don't see "Page Fault", there are several possibilities:
If you don't see anything on the serial terminal, either
The serial terminal is not connected correctly, or
Something else is wrong with the machine - the machine is quite quite dead and it's not an instance of the symptom 1 RTC problem.
If you see a lot of startup messages, but the last one isn't "Page Fault" followed by "ok", then the machine is largely working, but the problem is not symptom 1 RTC problem. If the screen comes on, you should be following the "Developer Key Procedure" below, not this serial procedure.
To set the date, do the following commands at the ok prompt (hitting enter after each one):
ok select /rtc
ok sec min hour day month year set-time
sec, min, hour, day, etc in the previous command should be numbers correlating to the current date. For the current time:
ok 36 01 01 2 12 2009 set-time
As I understand your post, you are getting the startup but it never stops with "Page Fault", so the XO is largely working. This also implies that your serial communication is working.
Supposedly you can type "i" right away to interrupt, but I can rarely get it to stop this way.
I have had an XO that would not stop with "Page Fault", but had other OFW problems that prevented it from booting -- could not fix.
On the second XO, you can "yum install" minicom (as "su"). The setup is given in the above link.
Finally, most serial devices have LED's on the transmit and receive lines. Generally when you press return on the computer running the communication software, the transmit light will flash and is a pretty good indication that you are sending to the XO ( although you could still have a bad hardware connection). I will try to look up your device.
So, it looks like this is not a RTC problem but will still give you the symptom (one very, very brief flash of the microphone LED on power on). Please confirm your symptoms.
A developer key is not need for any of this. minicom should be installed and run while logged in as "su". The drivers for your device may not be included in the XO linux kernel. The drivers for FTDI chips widely used in serial adapters is in the XO kernel. Security disabled or enabled should not be a problem in any of these procedures -- do not understand effect on d6.py .
Does any of this make sense for your situation ?