I tried this again with gdm stopped, so changes can happen with no suspending or hibernate.
As you can see here in my battery watch file this time my BIOS took 15 seconds to start giving reasonable values.
My netbook charges at about 35-40 Watts, discharges at 13 Watts. 700 to 750 Watts is more power then my microwave oven uses and should be ignored by any program reading the acpi battery status. When the status file shows stupid values like this one, it should be completely ignored a re-read until is looks sane.
The log file was made with this very simple shell script:
I tried this again with gdm stopped, so changes can happen with no suspending or hibernate.
As you can see here in my battery watch file this time my BIOS took 15 seconds to start giving reasonable values.
My netbook charges at about 35-40 Watts, discharges at 13 Watts. 700 to 750 Watts is more power then my microwave oven uses and should be ignored by any program reading the acpi battery status. When the status file shows stupid values like this one, it should be completely ignored a re-read until is looks sane.
The log file was made with this very simple shell script:
#!/bin/bash "/proc/ acpi/battery/ BAT1/state" %S)\t$charging rate: \t$rate"
while sleep 1
do
BATSTATE=
read present state charging rate therest << EOState
$(cat $BATSTATE | cut -d":" -f2 | tr "\n" " " )
EOState
echo "time $(date +%H:%M.
done