Date Keeping Problem

[louigi600]

I'm not sure if this afflicts any other rom but it certainly afflicts pxaXrom beta4 and above.
Even if you set up the date correctly at each reboot or reset you loose the date. I'm not sure if the hardware has a hardware clock and even if it does I would not be able to write code to manage it in a reasonable amount of time ... so this is the work around I made:
I wrote a simple script in /etc/rc.d/init.d/fixdate that was able to save current time at shutdown and restore it at startup.
Unfortunately the /etc/rc.d/rc script is not working exactly as one would expect (one of the next things I'll try to fix) so I was unable to make the Kxxfixdate links in the desired runlevel directories ... but to get it working I added at the beginning of /etc/rc.d/init.d/halt a line that would run /etc/rc.d/init.d/fixdate stop.

Naturally if the PDA remains shutdown (not suspended) for a long period the time would be way off but still better that "Jan 1 1970".

Here is the script:

#!/bin/sh

. /etc/rc.d/init.d/functions

case "$1" in
  start)
    [ -r /var/tmp/savedate ] && \
      /bin/date -s "$(/bin/cat /var/tmp/savedate)"
  ;;
  stop) /bin/date > /var/tmp/savedate ;;
  *)
    echo "Usage: $0 {start|stop}"
    exit 1
  ;;
esac

exit 0

[mathemajikian]

I don't think the Zaurus has a hardware clock like a normal computer. This is why ROM's like Cacko ask you for the correct time each time you reboot. The script you provide is fine but why not run ntpd at startup? If you have internet access your time will be correct each time you reboot and will be checked periodically throughout the day.If you don't have internet access then you can use the following command to set the date:

Code: [Select]

# date 8506131627
This sets the date to ``June 13, 1985, 4:27 PM''.

[louigi600]

I don't think the Zaurus has a hardware clock like a normal computer. This is why ROM's like Cacko ask you for the correct time each time you reboot. The script you provide is fine but why not run ntpd at startup? If you have internet access your time will be correct each time you reboot and will be checked periodically throughout the day.If you don't have internet access then you can use the following command to set the date:

Code: [Select]

# date 8506131627
This sets the date to ``June 13, 1985, 4:27 PM''.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=149122\"][{POST_SNAPBACK}][/a][/div]

Ntpd date only works when you are connected to net ... so ntpd would be as good as leaving the date to the default (beginning of unix time) il all other cases.
Setting the date blindly is ok but my script reloads the last date saved which I think is better. When you are connected you could just run "ntpdate -b -s <your_ntpserver>" to sync the date immediately.

In any case to your command you would at least haveto add the -s option to tell date that you want to set the date ;-)

[InSearchOf]

In any case to your command you would at least haveto add the -s option to tell date that you want to set the date ;-)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=149136\"][{POST_SNAPBACK}][/a][/div]

No you dont... that command is fine....

Late

[koen]

I don't think the Zaurus has a hardware clock like a normal computer.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=149122\"][{POST_SNAPBACK}][/a][/div]

It has a rtc, but it isn't battery backed, and to make it worse the stock bootloader (and the 2.4.crappix kernel!) resets it on reboot.

[louigi600]

In any case to your command you would at least haveto add the -s option to tell date that you want to set the date ;-)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=149136\"][{POST_SNAPBACK}][/a][/div]

No you dont... that command is fine....

Late
[div align=\"right\"][a href=\"index.php?act=findpost&pid=149138\"][{POST_SNAPBACK}][/a][/div]

Well on my 760 running r121 when I issue

date 8506131627

I get "invalid date" ... same on my slackware linux x86 ... so I guess really something is wrong with the command.
The correct format is: MMDDhhmm[[CC]YY][.ss]
So maybe

date 0613162785

would be the right command  for the desigred date ;-)

[InSearchOf]

In any case to your command you would at least haveto add the -s option to tell date that you want to set the date ;-)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=149136\"][{POST_SNAPBACK}][/a][/div]

No you dont... that command is fine....

Late
[div align=\"right\"][a href=\"index.php?act=findpost&pid=149138\"][{POST_SNAPBACK}][/a][/div]

Well on my 760 running r121 when I issue

date 8506131627

I get "invalid date" ... same on my slackware linux x86 ... so I guess really something is wrong with the command.
The correct format is: MMDDhhmm[[CC]YY][.ss]
So maybe

date 0613162785

would be the right command  for the desigred date ;-)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=149146\"][{POST_SNAPBACK}][/a][/div]

date 1226142706

that is now... well when I typed it...

but the reason you get the invalid date is is because there is no 85th month... I think he put the wrong #'s in the wrong place... I wrote that it is good meaning with out the "-s"

Late

[mathemajikian]

Sorry for the confusion. The date/time format I listed is correct for BSD distros,  but for Linux distros it's in a different format.

[louigi600]

Ok ...

Well whatever I still think that setting and saving with a human readable format is the most convenient.

The following command speaks for it self as to what the date is being set to:

date -s "Tue Dec 26 20:56:33 CET 2006"

And should work on all linux systems

[Drake01]

I'm not sure if this afflicts any other rom but it certainly afflicts pxaXrom beta4 and above.
Even if you set up the date correctly at each reboot or reset you loose the date.
...
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

I don't know if you're running atd, but the thread below mentions some issues you need to address if you are.  The atd daemon will lock the hardware clock and prevent you from setting it properly.

[a href=\"https://www.oesf.org/forums/index.php?showtopic=17326#]https://www.oesf.org/forums/index.php?showtopic=17326#[/url]

[dinorex]

I don't know my experience can be helpful to you or not, but it is my findings.

If you make use of the matchbox and use the 'Settings -> Date & Time' or equivalently : datentime.py in console prompt (for all other windows manager), you can adjust the date time PERMANENTLY before you have taken the battery out on reboot (i.e. warm boot the zaurus you still keep the date / time upon kernel initialization)...

Maybe there are some tricks in the datentime.py applied in housekeeping the date/time, you can investigate that further inside....  

About the timezone, isn't it to be kept by the env'tal var "TZ"? I am quite confused....  

[louigi600]

I don't know if you're running atd, but the thread below mentions some issues you need to address if you are.  The atd daemon will lock the hardware clock and prevent you from setting it properly.
https://www.oesf.org/forums/index.php?showtopic=17326#
[div align=\"right\"][a href=\"index.php?act=findpost&pid=149174\"][{POST_SNAPBACK}][/a][/div]

No I'm not using atd and the time gets set correctly by the script I suggested.
I have'nt tryed what happens with atd active though.

I don't know my experience can be helpful to you or not, but it is my findings.
If you make use of the matchbox and use the 'Settings -> Date & Time' or equivalently : datentime.py in console prompt (for all other windows manager), you can adjust the date time PERMANENTLY before you have taken the battery out on reboot (i.e. warm boot the zaurus you still keep the date / time upon kernel initialization)...
Maybe there are some tricks in the datentime.py applied in housekeeping the date/time, you can investigate that further inside.... 
About the timezone, isn't it to be kept by the env'tal var "TZ"? I am quite confused.... 
[div align=\"right\"][a href=\"index.php?act=findpost&pid=149237\"][{POST_SNAPBACK}][/a][/div]

Using the r121 on c760 at each reboot  the time gets lost even if I use the gui tool.
I agree with KOEN ... i'ts a hardware design flaw that may not afflict all zaurii ... maybe the c1000 and c3x00 have a battery backed hardware clock.

[mathemajikian]

maybe the c1000 and c3x00 have a battery backed hardware clock.

I know that the C3100 and C3200 don't.  Not sure about the c1000.

[koen]

maybe the c1000 and c3x00 have a battery backed hardware clock.

I know that the C3100 and C3200 don't.  Not sure about the c1000.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=149302\"][{POST_SNAPBACK}][/a][/div]

AFAIK only collie has a battery backed RTC

[InSearchOf]

Using the r121 on c760 at each reboot  the time gets lost even if I use the gui tool.
I agree with KOEN ... i'ts a hardware design flaw that may not afflict all zaurii ... maybe the c1000 and c3x00 have a battery backed hardware clock.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=149300\"][{POST_SNAPBACK}][/a][/div]

I believe the issue with the c760's is that there is a script that runs at shutdown... that syncs system clock to hardware clock (RTC)... well for some reason "hwclock" wasn't include in that model sets rom... I will have to talk to sash to confirm... but if that is the issue it will be included in the next release...

Late