[arch-general] Battery question about a Firmware Bug in logs.

Don Juan donjuansjiz at gmail.com
Wed Jan 4 19:07:52 EST 2012


On 01/04/2012 04:00 PM, Jason Melton wrote:
> On Thu, Jan 5, 2012 at 8:53 AM, Don Juan<donjuansjiz at gmail.com>  wrote:
>> do you know if changing the numbers in say VOLTAGE_NOW to match min on
>> mine would do anything? I know I can just try but is there something bad
>> that could happen? At least you have the same kernel message as me and
>> basically the same laptop as me. I wish I could get mine to charge that
>> close to full again while using Arch.
>>
>> Thanks for posting that though makes me feel better
>>
> I honestly don't know enough to say. I've never bothered with the battery
> life (I'm almost always plugged in), so this is an area I've never
> researched.
>
> I did experiment a little with unplugging and seeing what happens, all of
> these were run immediately after one another, immediately after unplugging
> the power:
>
> [✍]  /sys/class/power_supply/BAT1 $ cat uevent
>
>
> POWER_SUPPLY_NAME=BAT1
> POWER_SUPPLY_STATUS=Discharging
> POWER_SUPPLY_PRESENT=1
> POWER_SUPPLY_TECHNOLOGY=Li-ion
> POWER_SUPPLY_CYCLE_COUNT=0
> POWER_SUPPLY_VOLTAGE_MIN_DESIGN=12500000
> POWER_SUPPLY_VOLTAGE_NOW=12326000
> POWER_SUPPLY_CURRENT_NOW=2340000
> POWER_SUPPLY_CHARGE_FULL_DESIGN=8000000
> POWER_SUPPLY_CHARGE_FULL=7245000
> POWER_SUPPLY_CHARGE_NOW=7135000
> POWER_SUPPLY_MODEL_NAME=NS2P3SZNJ5WR
> POWER_SUPPLY_MANUFACTURER=SANYO
> POWER_SUPPLY_SERIAL_NUMBER=134
> [✍]  /sys/class/power_supply/BAT1 $ cat uevent
>
>
> POWER_SUPPLY_NAME=BAT1
> POWER_SUPPLY_STATUS=Discharging
> POWER_SUPPLY_PRESENT=1
> POWER_SUPPLY_TECHNOLOGY=Li-ion
> POWER_SUPPLY_CYCLE_COUNT=0
> POWER_SUPPLY_VOLTAGE_MIN_DESIGN=12500000
> POWER_SUPPLY_VOLTAGE_NOW=12319000
> POWER_SUPPLY_CURRENT_NOW=2317000
> POWER_SUPPLY_CHARGE_FULL_DESIGN=8000000
> POWER_SUPPLY_CHARGE_FULL=7245000
> POWER_SUPPLY_CHARGE_NOW=7131000
> POWER_SUPPLY_MODEL_NAME=NS2P3SZNJ5WR
> POWER_SUPPLY_MANUFACTURER=SANYO
> POWER_SUPPLY_SERIAL_NUMBER=134
> [✍]  /sys/class/power_supply/BAT1 $ cat uevent
>
>
> POWER_SUPPLY_NAME=BAT1
> POWER_SUPPLY_STATUS=Discharging
> POWER_SUPPLY_PRESENT=1
> POWER_SUPPLY_TECHNOLOGY=Li-ion
> POWER_SUPPLY_CYCLE_COUNT=0
> POWER_SUPPLY_VOLTAGE_MIN_DESIGN=12500000
> POWER_SUPPLY_VOLTAGE_NOW=12321000
> POWER_SUPPLY_CURRENT_NOW=2442000
> POWER_SUPPLY_CHARGE_FULL_DESIGN=8000000
> POWER_SUPPLY_CHARGE_FULL=7245000
> POWER_SUPPLY_CHARGE_NOW=7127000
> POWER_SUPPLY_MODEL_NAME=NS2P3SZNJ5WR
> POWER_SUPPLY_MANUFACTURER=SANYO
> POWER_SUPPLY_SERIAL_NUMBER=134
> [✍]  /sys/class/power_supply/BAT1 $ cat uevent
>
>
> POWER_SUPPLY_NAME=BAT1
> POWER_SUPPLY_STATUS=Discharging
> POWER_SUPPLY_PRESENT=1
> POWER_SUPPLY_TECHNOLOGY=Li-ion
> POWER_SUPPLY_CYCLE_COUNT=0
> POWER_SUPPLY_VOLTAGE_MIN_DESIGN=12500000
> POWER_SUPPLY_VOLTAGE_NOW=12315000
> POWER_SUPPLY_CURRENT_NOW=2374000
> POWER_SUPPLY_CHARGE_FULL_DESIGN=8000000
> POWER_SUPPLY_CHARGE_FULL=7245000
> POWER_SUPPLY_CHARGE_NOW=7119000
> POWER_SUPPLY_MODEL_NAME=NS2P3SZNJ5WR
> POWER_SUPPLY_MANUFACTURER=SANYO
> POWER_SUPPLY_SERIAL_NUMBER=134
Thank you that looks similar to how mine is responding, I just don't 
think its allowing it to fully charge on mine. I like you am mostly 
plugged in as well, but would be nice to know I can use the battery and 
rely on what results I am getting, though mostly my VOLTAGE_NOW is lower 
than MIN_DESIGN. Guess that just is me doing lots of testing, to figure 
the rest out.

Side note since you have a Qosmio as well have you ever tried messing 
with DSDT on yours?

Appreciate your time.


More information about the arch-general mailing list