On 6/4/05, Matthias Kilian <[EMAIL PROTECTED]> wrote: > However, the whole thing now gets even worse: I did a "hard" reset > as descriped in the install guide (hold down "b" and "d", remove > battery and power, wait a minute, insert battery, power-on, release > "b" and "d"). Worked fine (single user mode in Linux). Rebooted to > OpenBSD, also fine -- of course, fsck did have to check all > filessystems. I did some additional configurations not related to > the apm problems, with some reboots. Finally, I was just editing > /etc/fstab when the display suddenly switched off. It seemed to > suspend without any good reason. > > And now I can't get it back to life, even after removing and > reinserting the battery, regardless of the "b" & "d" trick or not. > > I've connected the power supply to recharge the battery, just in > case it's just exhausted. However, five minutes before the display > went black, apm(8) reported the battery status as 75% charged.
The battery is one of the most braindead I've ever seen. I'm trying to fix battery life prediction right now - not an easy thing as the battery really only gives us voltage, and that's nearly constant until right before the machine dies on you. Charge it up for a half hour, pop out the battery and wall plug for a minute, put everything back together and boot as normal works for me when I run my zaurus out of power... CK -- GDB has a 'break' feature; why doesn't it have 'fix' too?
