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
while sleep 1
do
BATSTATE="/proc/acpi/battery/BAT1/state"
read present state charging rate therest << EOState
$(cat $BATSTATE | cut -d":" -f2 | tr "\n" " " )
EOState
echo "time $(date +%H:%M.%S)\t$charging rate:     \t$rate"
done


** Attachment added: "Battery status log (each 1 second)"
   http://launchpadlibrarian.net/47398016/batinfo

-- 
Power manager mistakenly thinks my battery power is critically low, and 
hibernates -- MSI Wind U100
https://bugs.launchpad.net/bugs/558627
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Reply via email to