Battery killed?
Joachim Ott
jo.omsl at googlemail.com
Wed Nov 12 14:00:21 CET 2008
2008/11/12 Alastair Johnson <alastair at truebox.co.uk>
> It should be possible to charge the 'dead' battery. Boot with the
> working one, attach the mains charger or USB so you have external power
> to keep it going, then pull the working battery and insert the 'dead'
> one. It should be detected and start charging, and you should be able to
> monitor its progress using the usual /sys entries:
I tried this once more. I wouldn't charge. I started this around 12:45, went
off to another room around 13:10, when I came back at 13:30 the FR was dead,
no flashing LED this time, and no messages on the screen. This is what I had
on 2 shells:
ott at hv:~ $ ssh root at neo
root at om-gta02:~# cat /proc/apm
1.13 1.2 0x02 0x01 0x03 0x03 0% 65535 min
root at om-gta02:~# date
Wed Nov 12 12:45:04 CET 2008
root at om-gta02:~# cat /proc/apm
1.13 1.2 0x02 0x01 0x03 0x03 0% 65535 min
root at om-gta02:~# cat /proc/apm
1.13 1.2 0x02 0x01 0x03 0x03 0% 65535 min
root at om-gta02:~# cat /proc/apm
1.13 1.2 0x02 0x01 0x03 0x03 0% 65535 min
root at om-gta02:~# w
12:49:58 up 37 min, 2 users, load average: 0.00, 0.05, 0.07
USER TTY LOGIN@ IDLE JCPU PCPU WHAT
root pts/1 12:42 5:46 0.09s 0.02s tail -f /var/log/messages
root pts/2 12:44 0.00s 0.17s 0.08s w
root at om-gta02:~# cat /proc/apm
1.13 1.2 0x02 0x01 0x03 0x03 0% 65535 min
root at om-gta02:~# cat /proc/apm
1.13 1.2 0x02 0x01 0x03 0x03 0% 65535 min
root at om-gta02:~# cat /proc/apm
1.13 1.2 0x02 0x01 0x03 0x03 0% 2014 min
root at om-gta02:~# cat /proc/apm
1.13 1.2 0x02 0x01 0x03 0x03 0% 65535 min
root at om-gta02:~# w
13:00:26 up 48 min, 2 users, load average: 0.03, 0.09, 0.08
USER TTY LOGIN@ IDLE JCPU PCPU WHAT
root pts/1 12:42 16:14 0.09s 0.02s tail -f /var/log/messages
root pts/2 12:44 0.00s 0.18s 0.08s w
root at om-gta02:~# Read from remote host neo: Connection timed out
and the last messages were:
Nov 12 12:42:51 om-gta02 authpriv.warn dropbear[1509]: lastlog_openseek:
/var/log/lastlog is not a file or directory!
Nov 12 12:43:26 om-gta02 user.err kernel: power_supply bat: driver failed to
report `voltage_now' property
Nov 12 12:43:26 om-gta02 user.debug kernel: modem wakeup interrupt
Nov 12 12:43:27 om-gta02 user.err kernel: power_supply bat: driver failed to
report `voltage_now' property
Nov 12 12:44:45 om-gta02 authpriv.info dropbear[1518]: Child connection from
::ffff:192.168.0.200:39497
Nov 12 12:44:46 om-gta02 authpriv.notice dropbear[1518]: pubkey auth
succeeded for 'root' with key md5
a6:51:5b:85:6f:86:0c:5d:8a:c4:f3:3c:91:c9:8d:da from ::ffff:
192.168.0.200:39497
Nov 12 12:44:46 om-gta02 authpriv.warn dropbear[1519]:
lastlog_perform_login: Couldn't stat /var/log/lastlog: No such file or
directory
Nov 12 12:44:46 om-gta02 authpriv.warn dropbear[1519]: lastlog_openseek:
/var/log/lastlog is not a file or directory!
Nov 12 12:48:49 om-gta02 local0.info /usr/sbin/gsm0710muxd[1400]:
gsm0710muxd.c:609:pseudo_device_read(): Logical channel 1 for (null) closed
Read from remote host neo: Connection timed out
Connection to neo closed.
Again, the "power_supply bat: driver failed to report `voltage_now" are from
the time when I switched batteries.
Anyone who wants to check it with this battery? Preferrably someone from
Berlin too but I can send it anywhere.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openmoko.org/pipermail/support/attachments/20081112/9663aace/attachment.htm
More information about the support
mailing list