Re: apm(8) on Zaurus
On Sat, Jun 04, 2005 at 03:20:54PM -0600, Chris Kuethe wrote: > 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. Doesn't sound funny. > 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... That helped. Suspend also works, too. Thank you all for your help. Ciao, Kili
Re: apm(8) on Zaurus
On Sun, Jun 05, 2005 at 05:40:51AM +0900, Hiroshi Maruyama wrote: > One different thing I did when installing is the following. > I went into shell before installing OpenBSD/zaurus to pass options '-h > 16 -s 63 -c 7936' with OpenBSD's fdisk, which might not be descrived > in the install guide. So far, I'd no problems with the disk layout, but I'll surely watch for potential problems in in the future. Ciao, Kili
Re: apm(8) on Zaurus
On Sat, 4 Jun 2005, Matthias Kilian wrote: > 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. that's probably dead. they also apparently won't run off wall power when the battery is too drained. -- we used to hate people now we just make fun of them it's more effective that way
Re: apm(8) on Zaurus
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?
Re: apm(8) on Zaurus
In message "Re: apm(8) on Zaurus" of <[EMAIL PROTECTED]> On Sat, 4 Jun 2005 21:50:55 +0200, Matthias Kilian <[EMAIL PROTECTED]> wrote: > 9. Shrunk the MSDOS partition as described in the install guide, >created the A6 partition etc, including creating a new MSDOS >filesystem on the shrunk partition. > 10. Limited the disklabel boundaries to the A6 partition, just to be > safe. One different thing I did when installing is the following. I went into shell before installing OpenBSD/zaurus to pass options '-h 16 -s 63 -c 7936' with OpenBSD's fdisk, which might not be descrived in the install guide. -- Hiroshi Maruyama [EMAIL PROTECTED] +81-90-2084-9962
Re: apm(8) on Zaurus
On Sun, Jun 05, 2005 at 03:39:05AM +0900, Hiroshi Maruyama wrote: > > For now, I'll just remove the battery, reboot and have a closer > > look at what happened. > > How about adding apmd="-q" in /etc/rc.conf.local? That's disabling announcements of standby and suspend on the speaker. I don't see how this may help. After all, there was no audible announcement at all, probably because I didn't yet fiddle with audio/mixer settings? 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. Below is a list of things I've done since I received the zaurus. The only two possibly silly things were an initial junky disklabel and an el-cheapo USB-Ethernet adapter (Typhoon Speednet). That adapter was connected to the zaurus when the above happend. It's an aue(4), here's a dmesg from it connected to another computer: aue0 at uhub3 port 1 aue0: USBs USB 10/100 Fast Ethernet, rev 1.10/1.01, addr 2 aue0: address 00:e0:98:9b:df:16 acphy0 at aue0 phy 1: AC_UNKNOWN 10/100 PHY, rev. 0 I still hope it's a PEBCAC and not some hardware failure. Ciao, Kili History of (maybe silly) things I did: 1. First boot to Linux, connected to power supply. 2. Asked Wim and google for how to make it display less japanese. 3. Found http://www.users.on.net/~hluc/myZaurus/custom.html 4. Installed qkonsole, changed Language and Timzone /home/zaurus/Settings/locale.conf as described in 3 (with *my* timezone, of course). 5. Downloaded the base install sets, kernels, and openbsd37_arm.ipk. 6. Installed the latter and run it. 7. Rebooted into Linux. 8. Started the OpenBSD installer. 9. Shrunk the MSDOS partition as described in the install guide, created the A6 partition etc, including creating a new MSDOS filesystem on the shrunk partition. 10. Limited the disklabel boundaries to the A6 partition, just to be safe. 11. (Very silly one): created a 64m slice for swap (b) followed by one large slice (a) for the remaining space. Hey, I just wanted to run an initial "play- and throw-away" install. 12. Installed the some sets (bsd, bsd.rd, base37.tgz, comp37.tgz). Forgot etc37.tgz, so everything bailed out when it came to touchscreen calibration. 13. Reboot (disconnect power supply, remove battery, ...) 14. Repeat everything, with etc37.tgz included. 15. Won't boot, due to my braindead disklabeling. 16. Repeat everything, this time with a reasonable layout (100 MB for /, 64 MB swap, 400 MB for /usr, 100 MB for /var, the remaining space for /home. 17. Enable ssh, ntpd, set allowaperture for later use of X. Do some basic setup, configure network for the above mentioned aue(4) device, using DHCP and rtsol. Enable apmd in /etc/rc.conf.local. First tests with ssh, both from and to the Zaurus were fine (i.e. no network problems). 18. Run zzz(8). See my first mail. 19. Remove battery, ... reboot. 20. Sudden hang/suspend/whatever (see above). 21. Despair.
Re: apm(8) on Zaurus
In message "Re: apm(8) on Zaurus" of <[EMAIL PROTECTED]> On Sat, 4 Jun 2005 20:06:20 +0200, Matthias Kilian <[EMAIL PROTECTED]> wrote: > On Sat, Jun 04, 2005 at 11:33:24AM -0600, Chris Kuethe wrote: > > Tap the power button on the front. > > Well, of course this was the first thing I tried, with no effect > at all. > > For now, I'll just remove the battery, reboot and have a closer > look at what happened. How about adding apmd="-q" in /etc/rc.conf.local? -- Hiroshi Maruyama [EMAIL PROTECTED] +81-90-2084-9962
Re: apm(8) on Zaurus
On Sat, Jun 04, 2005 at 11:33:24AM -0600, Chris Kuethe wrote: > Tap the power button on the front. Well, of course this was the first thing I tried, with no effect at all. For now, I'll just remove the battery, reboot and have a closer look at what happened. Ciao, Kili
Re: apm(8) on Zaurus
Tap the power button on the front. see the zkbd manpage for more cool APM tricks http://www.openbsd.org/cgi-bin/man.cgi?query=zkbd&apropos=0&sektion=0&manpath=OpenBSD+Current&arch=zaurus&format=html On 6/4/05, Matthias Kilian <[EMAIL PROTECTED]> wrote: > Hi, > > now that I've OpenBSD (snapshot from may, 18th) up and running on > my new toy, I wanted to try out suspend. So I just ran zzz(8) -- > hmm may be that was a mistake, since I've just no idea how to get > the zaurus to live again (without removing batteries etc.) > > I didn't find anything about this in the FAQ, zaurus.html nor in > the manpages. > > Any help appreciated. TIA. > > Ciao, > Kili > > ps: no dmesg yet, since my zaurus is currently suspended ;-) > > -- GDB has a 'break' feature; why doesn't it have 'fix' too?
apm(8) on Zaurus
Hi, now that I've OpenBSD (snapshot from may, 18th) up and running on my new toy, I wanted to try out suspend. So I just ran zzz(8) -- hmm may be that was a mistake, since I've just no idea how to get the zaurus to live again (without removing batteries etc.) I didn't find anything about this in the FAQ, zaurus.html nor in the manpages. Any help appreciated. TIA. Ciao, Kili ps: no dmesg yet, since my zaurus is currently suspended ;-)
