Messages

1

Zaurus - pdaXrom / Kathrin RC8 Is Out..

« on: December 30, 2004, 05:18:53 pm »

Good news! (at least for me)
I solved my own problem (for now).

Looking at datetime.py I found the difference in calling the applet to change time
compared to calling date or ntpdate are the commands 'sethwclock' and 'sltime -set'
issued by the applet after changing the time.
When I issued these commands manually after calling ntpdate my susepnd/wakeup
problems were gone as well!

I have now added these commands to my 'apm' script calling them the Z is going to suspend
(just before the 'suspend' command itself and this works!
I now can call ntpdate anytime I want (or have ntpd) update the time.

Is this something to add to the standard distrib or is it a little too crude?

2

Zaurus - pdaXrom / Kathrin RC8 Is Out..

« on: December 30, 2004, 03:31:45 pm »

I tested with NTPD running and the effects are identical as with running ntpdate from the commandline.

At boot NTPD will sync my systemtime (if I have the Wifi inserted of course) but after I start up the GUI and suspend and attempt to wakeup the input is frozen again.
This all in case the systemtime is more than a few seconds off from the synced time (I guess it has to be minutes).

The problem here is that this makes NTPD essentially useless for me.
I my case it could easily be that the Z lies around suspended for more than a day and after so long a time the systemtime will be substantially off from 'real' (NTP synced) time when I wake it up.
Everytime this is the case NTPD would nicely sync the time at some point and at the next suspend/wakeup cycle my input would freeze again.

The datetime applet however manages to change the time without causing the freezing effect.
What's different here and could this method also be used with NTPD, date and ntpdate?

3

Zaurus - pdaXrom / Kathrin RC8 Is Out..

« on: December 30, 2004, 07:36:19 am »

Hi,

I have a persistent problem with Rc8.
...

When X is running you can currently only change the date/time using the Date & Time application because it has to restart openbox afterwards (due to the way timing is handled in the matchbox applications and applets).  Setting the time when X isn't running (i.e. from the console before you run startx) is fine.  ntpd is also not affected because it doesn't "set" the clock it adjusts its speed to gently shift to the correct time (except in the ntpd script that runs at bootup, it "sets" the clock).  If you need to periodically use date or ntpdate to set your clock then have a look in /usr/bin/datentime.py (lines 53-57) to see what it does after setting the clock.

Matt

Sorry I did not mention this in the original post but I *did* change the date/time when X was not running (since I had some earlier problems changing the dat/time when it did).

I just tested changing time/date using the applet and I did not have any resume problems anymore:-)

Here's the funny part though:-/

if I set the time correctly using the applet, than exit the GUI and run ntpdate, start the GUI,
suspend and resume: everything OK;

if I set the time off by f.i. 30 minutes; exit the GUI, run ntpdate ..... ;clock gets set back to time I set using the applet and input freezes up again.

It seems to me there is some reproducible error here dependant on the timedifference between time set by the applet and time set by 'date' and/or 'ntpdate'.

I'll do some more tests with NTPD running as well (I removed that because in the beginning I had problems with that as well).

4

Zaurus - pdaXrom / Kathrin RC8 Is Out..

« on: December 30, 2004, 06:37:55 am »

Hi,

I have a persistent problem with Rc8.
Whenever I change the date/time on my Z and do I suspend and subsequent wakeup from the GUI my keyboard and stylus input freezes.
After wakeup I see the clock being reset to the last systemtime *before* the date/time change.
System still runs afaict because if I wait long enough the clock gets updated.

I do not have NTPD running.
It happens if I change date/time with the 'date' command or the 'ntpdate' command.
It does not matter if I have my Wifi card inserted or not.
I have *all* updates installed which are available in the current feed.

Any ideas?