OESF Portables Forum

Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: Shdwdrgn on October 25, 2004, 12:41:15 pm

Title: Fix for timeclock reset
Post by: Shdwdrgn on October 25, 2004, 12:41:15 pm
Just an FYI for anyone still suffering from the zaurus internal clock resetting every time you reboot.  The hardware clock needs to be manually set before it will start keeping time, and whenever you reboot the system clock is reset to the hw clock.

- Manually set the clock (either through clock settings or by pulling from an online source)
- Go to a command prompt and issue the command "hwclock --systohc"

This was tested under OZ3.5.1 on an SL5500.
Title: Fix for timeclock reset
Post by: zenyatta on October 25, 2004, 04:58:55 pm
I wish there was a similar way to preserve the time during a hard reset

z.
Title: Fix for timeclock reset
Post by: Bundabrg on October 26, 2004, 02:57:23 am
I'm sure slutils does this. Under pdaXrom, there is command in the 'halt' script that is simply:

sltime -set


Anyway, another (probably more primitive way) is to have a cron job that writes the current time to a file every now and then, and on boot, to read that file and set the date.
Title: Fix for timeclock reset
Post by: obscurite on October 26, 2004, 10:27:20 am
FYI (on C860, cacko 1.21b)

# hwclock --systohc
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
# hwclock --debug --systohc
hwclock 2.4c/util-linux-2.10r
hwclock: Open of /dev/rtc failed, errno=16: Device or resource busy.
No usable clock interface found.
Cannot access the Hardware Clock via any known method.

-Daniel
Title: Fix for timeclock reset
Post by: Shdwdrgn on October 26, 2004, 12:54:13 pm
Zenyatta - ah I see that.  Yep clock is also lost on mine during a hard reset.  I wonder why that is?
Title: Fix for timeclock reset
Post by: zenyatta on October 26, 2004, 03:07:13 pm
Shdwdrgn: beats me. I just know that with 3.5.1 being at the stage it is at now, hard resets are waaaay too frequent