True. But interestingly the release version does seem more stable than the snapshots: it is my very first time that i get zzz, lidsuspend and the power off button ALL working!
Still let me see if things are really stable during the weekend.
Last night I suspended my Z from within X using the lidsuspend option and when I resumed the device this morning the only problem was that the back light failed to turn back on. I saw a half second white flash on the screen, as if it was attempting to turn on, then a blank/black screen. I ssh'd into the Zaurus and issued
wsconsctl display.back light=100 and everything returned to normal. I also used lidsuspend outside of X and got similar results. (The back light failed to turn back on) However, if I used the power
on/off button in X or from the console the back light never failed to turn back on. So there is an issue with lidsuspend, but it dosn't result in complete catastrophic device lockup. Though out the day I've suspended and resumed the device via the
on/off button and lidsuspend multiple times and never once had the Z lock up or produce the error you describe below:
wdc0 channel 0: reset failed for drive 0
wd0a: device timeout reading fsbn 1595200 of 1595200-0 (wd0 bn 1595201; cn 1582 tn 8 sn 41), retrying
wdc0:0:0: not ready,st=0x88<BSY,DRQ>, err=0x00.
Finally, in regards to your battery status concerns:
From the apmd manual
-t seconds
apmd periodically polls the APM driver for the current power
state. If the battery charge level changes substantially or the
external power status changes, the new status is logged. The
polling rate defaults to once per 10 minutes, but may be speci-
fied using the -t command-line flag.
Therefore to get better battery status reports add the following to rc.conf.local
apmd_flags="-t 300"This changes the polling rate to once every 5 minutes instead of once every 10 minutes.
You might also want to check out:
http://ports.openbsd.nu/x11/asapm
