http://bugzilla.kernel.org/show_bug.cgi?id=11632





------- Comment #6 from [EMAIL PROTECTED]  2008-09-24 03:11 -------
(In reply to comment #4)
> Will you please not load the msi-laptop driver and see whether the problem
> still exists?
It seems that this indeed brought it back:
cat /proc/acpi/battery/BAT1/info
present:                 yes
design capacity:         4400 mAh
last full capacity:      2938 mAh
battery technology:      rechargeable
design voltage:          14800 mV
design capacity warning: 0 mAh
design capacity low:     0 mAh
capacity granularity 1:  1 mAh
capacity granularity 2:  1 mAh
model number:            MS-1058

serial number:

battery type:            LION

OEM info:                MSI Corp.

cat /proc/acpi/battery/BAT1/state
present:                 yes
capacity state:          ok
charging state:          charged
present rate:            0 mA
remaining capacity:      2938 mAh
present voltage:         16680 mV

Thank you.

So this is more a bug in the msi-laptop module, right?

(In reply to comment #5)
> So if you directly read the /proc/acpi/battery ... files, the info is correct.
> But acpi -sV will return error? This might be a bug of acpi tools.
No, both are wrong.
The acpi proc files state correctly, that the battery is present or not, but
all the values are wrong.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to