[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ACPI battery state doesn't get updated



On Monday 03 January 2005 04:05 pm, Jan C. Nordholz wrote:
> Dear list,
>
> after installing Debian on an old IBM Thinkpad
> everything seems to be working fine, except that
> the battery state is constant, i.e. it is read
> once correctly at bootup and doesn't change
> afterwards. On the other hand, the ACPI system does
> recognise when I plug/unplug the AC (which sets
> /proc/acpi/ac_adapter/AC/state to off-line, but
> does not change /proc/acpi/battery/BAT1/state from
> charging to discharging).
> Is this a problem with the BIOS, or is there a
> possibility to set a polling interval for the
> battery, similar to the one found at
> /proc/acpi/thermal_zone/THRM/polling_frequency, that
> just has a ridiculously high default setting?
>
> Here is a copy of the ACPI lines of dmesg (if it
> is of help, I can attach the complete syslog/dmesg);
> all ACPI stuff is compiled into the kernel, so no
> module loading:
>
> ---
> jcn@muldvarp:~@ uname -a
> Linux muldvarp 2.6.9MULDVARP #10 Sun Jan 2 01:29:25 CET 2005 i686
> GNU/Linux ---
> jcn@muldvarp:~$ dmesg|grep ACPI
>  BIOS-e820: 0000000007ff0000 - 0000000007fffc00 (ACPI data)
>  BIOS-e820: 0000000007fffc00 - 0000000008000000 (ACPI NVS)
> ACPI: RSDP (v000 PTLTD                                 ) @ 0x000f71a0
> ACPI: RSDT (v001 PTLTD    RSDT   0x06040000  LTP 0x00000000) @
> 0x07ffaf8f ACPI: FADT (v001 IBM    430BX    0x06040000 PTL 
> 0x000f4240) @ 0x07fffb65 ACPI: BOOT (v001 PTLTD  $SBFTBL$ 0x06040000 
> LTP 0x00000001) @ 0x07fffbd9 ACPI: DSDT (v001    IBM      BT2
> 0x06040000 MSFT 0x01000007) @ 0x00000000 ACPI: IRQ9 SCI: Edge set to
> Level Trigger.
> ACPI: Subsystem revision 20040816
> ACPI: Interpreter enabled
> ACPI: Using PIC for interrupt routing
> ACPI: PCI Root Bridge [PCI0] (00:00)
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
> ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 14 15)
> ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 *5 6 7 9 10 11 14 15)
> ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 *11 14 15)
> ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11 14 15)
> ACPI: Embedded Controller [EC] (gpe 9)
> ACPI: Power Resource [PFNH] (off)
> ACPI: Power Resource [PFNM] (off)
> ACPI: Power Resource [PFNL] (off)
> PCI: Using ACPI for IRQ routing
> ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
> ACPI: PCI interrupt 0000:00:02.2[D] -> GSI 11 (level, low) -> IRQ 11
> ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
> ACPI: PCI interrupt 0000:00:03.0[A] -> GSI 11 (level, low) -> IRQ 11
> ACPI: PCI interrupt 0000:00:03.1[A] -> GSI 11 (level, low) -> IRQ 11
> ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
> ACPI: PCI interrupt 0000:00:06.0[A] -> GSI 11 (level, low) -> IRQ 11
> ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 5
> ACPI: PCI interrupt 0000:00:07.0[A] -> GSI 5 (level, low) -> IRQ 5
> ACPI: PCI interrupt 0000:01:00.0[A] -> GSI 11 (level, low) -> IRQ 11
> ACPI: AC Adapter [AC] (on-line)
> ACPI: Battery Slot [BAT1] (battery present)
> ACPI: Battery Slot [BAT2] (battery absent)
> ACPI: Power Button (FF) [PWRF]
> ACPI: Sleep Button (CM) [SLPB]
> ACPI: Lid Switch [LID]
> ACPI: Fan [FANH] (off)
> ACPI: Fan [FANM] (off)
> ACPI: Fan [FANL] (off)
> ACPI: Processor [CPU0] (supports C1, 8 throttling states)
> ACPI: Thermal Zone [THRM] (54 C)
> ACPI: PCI interrupt 0000:00:07.0[A] -> GSI 5 (level, low) -> IRQ 5
> ACPI: (supports S0 S1 S3 S4 S5)
> ACPI wakeup devices:
> ACPI: PCI interrupt 0000:00:03.0[A] -> GSI 11 (level, low) -> IRQ 11
> ACPI: PCI interrupt 0000:00:03.1[A] -> GSI 11 (level, low) -> IRQ 11
> ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 11 (level, low) -> IRQ 11
> ---
>
> I'd be very glad if someone can help me.
>
> Thanks in advance!
>
> Jan Nordholz

Hmm, I don't think  I can help much but I have been following the ACPI 
issue for a new laptop of mine, < 1year. I don't know how IBM supports 
ACPI in older laptops, maybe APM works better, less functions though.

My education so far is the ACPI in the latest 2.6 kernels works pretty 
well, it is the userland tools that can report all the data in a nice 
GUI interface is what I haven't found. I have had to resort to the 
command line to get/set parameters, but I don't use KDE or Gnome 
(WMaker) which may have more utilities in this area.

-- 
Greg C. Madden



Reply to: