On 12/09/14 06:33, Ian Smith:
Normally with 2 batteries catered for and only one fitted you'd expect to see
battery1: on acpi0
battery1: battery initialization start
battery1: battery initialization failed, giving up
Just for the completeness ...
... it is expected behavior for non-present
On 12/08/14 15:27, Adrian Chadd wrote:
> What's the output of acpiconf -i0 and acpiconf -i1?
acpiconf -i0 is exactly what you'd expect. acpiconf -i1 shows blank for
the model/serial/type/OEM info strings, and 0 mAh/mV for the rest except
State which is "not present".
> I wonder if changing 'stat
Colin Percival wrote:
> The hald code uses hw.acpi.battery.units to see how many batteries there are,
> then reads the _BIF data via ioctl; the "state"
> isn't even in _BIF.
ACPI specification 3.0a par. 10.2.1 :
-
... Unlike most other devices, when a battery is inserted or removed
On 12/08/14 21:33, Ian Smith wrote:
> And what does 'grep battery /var/run/dmesg.boot' have to say? Normally
> with 2 batteries catered for and only one fitted you'd expect to see eg:
>
> ./nicks_acpi/dmesg-bootwithacpi-2-part.txt:battery0: Battery> on acpi0
> ./nicks_acpi/dmesg-bootwithacpi-2-
