Hi guys,
I have a (heavily modified) pdaXrom 1.1.0beta3 running.
I never had a problem with resume / suspend, as long as I don't violate this rule:
Never use the On/Off button more than once within about 20 seconds.
Recently I have added the atd start / stop lines to the /etc/apm/scripts.d/hwclock script as suggested elsewhere here in the forum.
Since then, I have that occasional resume problem and have to reset the unit sometimes.
Now, removing these lines again, I have no problems at all anymore (also no clock drift etc.).
This is now my hwclock script now looks like (stripped all but the important suspend and resume parts):
suspend() {
# /etc/rc.d/init.d/atd stop 2>/dev/null >/dev/null
hwclock --systohc
return 0
}
resume() {
# /etc/rc.d/init.d/atd start 2>/dev/null >/dev/null
hwclock --hctosys
return 0
}
When leaving X, I see many of these error messages about non-accessable hw clock. This is probably caused by the hwclock calls in this script, which cannot access the hw clock because atd is running.
So my assumption is, that even the hwclock calls in this script are unnecessary (hence the entire hwclock script is unnecessary)
However, there remains the question why it is there...
Someone must have had an idea why he wrote it.
However, with the current state I have ZERO problems with clock or resume/suspend...
Any ideas?
daniel
