* FSC Amilo M-3438G
@ 2006-01-12 9:21 Magnus Sandberg
[not found] ` <20060112092118.84F211C812-FBVcP3zgNXfBmJu9jE4dRbNAH6kLmebB@public.gmane.org>
2006-01-19 10:27 ` Matthew Garrett
0 siblings, 2 replies; 4+ messages in thread
From: Magnus Sandberg @ 2006-01-12 9:21 UTC (permalink / raw)
To: linux-acpi-u79uwXL29TY76Z2rM5mHXA; +Cc: mem-P9zfqOBuU5vLoDKTGw+V6w
Hi,
I'm new to this list and I have just got a Fujitsu-Siemens Amilo M-3438G
which I'm installing Debian on.
I have some problems with ACPI on the machine. The problems I have found so
far is that;
- I don't get any events when the battery is discharged or running low
- The lid button only reports close events so the lid-state is always
"closed"
- I don't know if "Fn"-keys should be reported via ACPI or not?
I only get the "sleep mode" Fn-key event, no other Fn-keys.
- I don't get events for "special hot keys" like "silent mode", etc
(The Amilo M3438 has 4 hot keys above the Fn-keys)
Things that do work;
- Power button generate event
- I get events for AC, CPU and BAT when I add or remove AC-adator
- As mentioned above Fn-key for sleep button works
- I can read battery state and battery info. Remaining capacity and voltage
seams to be okay. Remaining capacity is like 2 mAh just before the
machine dies. Warning and low levels seams to be calculated from
"last full capacity", I don't know if that is the way it should be done?
- Thermal Zone seams to work, get values in the range 31 C - 53 C
My questions are if I have to compile a new DSDT or if I should do
something else to correct the problems. And what things should or can ACPI
support (like Fn-keys or hot keys, etc)?
I changed the scripts in /etc/acpi to send all unknown events via logger to
/var/log/messages
If I remove the AC, I get the following;
ac_adapter AC0 00000080 00000000
battery BAT0 00000080 00000001
processor CPU1 00000080 00000006
If I connect the AC, I get;
ac_adapter AC0 00000080 00000001
battery BAT0 00000080 00000001
processor CPU1 00000080 00000005
On my system I can find all ACPI related things in /var/log/kern.log.
I did a 'grep -i acpi kern.log | cut -d: -f4-12' and got the following
output (removed dates, etc for readability);
000000003ffd0000 - 000000003ffde000 (ACPI data)
000000003ffde000 - 0000000040000000 (ACPI NVS)
RSDP (v000 ACPIAM ) @ 0x000f8110
RSDT (v001 A M I OEMRSDT 0x10000505 MSFT 0x00000097) @ 0x3ffd0000
FADT (v002 A M I OEMFACP 0x10000505 MSFT 0x00000097) @ 0x3ffd0200
MADT (v001 A M I OEMAPIC 0x10000505 MSFT 0x00000097) @ 0x3ffd0390
MCFG (v001 A M I OEMMCFG 0x10000505 MSFT 0x00000097) @ 0x3ffd03f0
OEMB (v001 A M I AMI_OEM 0x10000505 MSFT 0x00000097) @ 0x3ffde040
MCFG (v001 A M I OEMMCFG 0x10000505 MSFT 0x00000097) @ 0x3ffd4e80
SSDT (v001 AMI CPU1PM 0x00000001 INTL 0x02002026) @ 0x3ffd4ec0
DSDT (v001 UW____ F18_____ 0x00000001 INTL 0x02002026) @ 0x00000000
PM-Timer IO Port: 0x808
Local APIC address 0xfee00000
LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
IRQ0 used by override.
IRQ2 used by override.
IRQ9 used by override.
2 duplicate MCFG table ignored.
Subsystem revision 20050309
Interpreter enabled
Using IOAPIC for interrupt routing
PCI Root Bridge [PCI0] (0000:00)
PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
Embedded Controller [EC0] (gpe 24)
PCI Interrupt Routing Table [\_SB_.PCI0.P0P3._PRT]
PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 11 12 14 15)
PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12 14 15)
PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 7 10 11 12 14 15)
PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 *11 12 14 15)
PnP ACPI init
PnP ACPI: found 12 devices
Disabled by ACPI PNP
Using ACPI for IRQ routing
PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 169
PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 169
(supports S0 S3 S4 S5)
PCI Interrupt 0000:01:07.0[A] -> GSI 16 (level, low) -> IRQ 169
PCI Interrupt 0000:01:04.0[A] -> GSI 18 (level, low) -> IRQ 201
PCI Interrupt 0000:01:05.0[A] -> GSI 19 (level, low) -> IRQ 209
PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 201
PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 169
PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level, low) -> IRQ 217
PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 209
PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 201
PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 169
PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level, low) -> IRQ 217
Battery Slot [BAT0] (battery present)
AC Adapter [AC0] (off-line)
CPU0 (power states: C1[C1] C2[C2])
Processor [CPU1] (supports 8 throttling states)
Power Button (FF) [PWRF]
Lid Switch [LID]
Sleep Button (CM) [SLPB]
Thermal Zone [THRM] (52 C)
At some points I have got the following;
(grep Error kern.log | cut -d: -f4-12)
ACPI-0405: *** Error: Handler for [EmbeddedControl] returned AE_TIME
ACPI-1138: *** Error: Method execution failed [\_SB_.PCI0.BAT0._BIF]
(Node dfdc04a0), AE_TIME
ACPI-0405: *** Error: Handler for [EmbeddedControl] returned AE_TIME
ACPI-1138: *** Error: Method execution failed [\_SB_.PCI0.BAT0._BIF]
(Node dfdc04a0), AE_TIME
ACPI-0405: *** Error: Handler for [EmbeddedControl] returned AE_TIME
ACPI-1138: *** Error: Method execution failed [\_SB_.PCI0.BAT0._BST]
(Node dfdc0460), AE_TIME
ACPI-0405: *** Error: Handler for [EmbeddedControl] returned AE_TIME
ACPI-1138: *** Error: Method execution failed [\_SB_.PCI0.BAT0._BIF]
(Node dfdc04a0), AE_TIME
ACPI-0405: *** Error: Handler for [EmbeddedControl] returned AE_TIME
ACPI-1138: *** Error: Method execution failed
[\_SB_.PCI0.SBRG.EC0_._Q39] (Node dfdc05e0), AE_TIME
ACPI-0405: *** Error: Handler for [EmbeddedControl] returned AE_TIME
ACPI-1138: *** Error: Method execution failed [\_SB_.PCI0.BAT0._BST]
(Node dfdc0460), AE_TIME
# find /proc/acpi/
/proc/acpi/
/proc/acpi/thermal_zone
/proc/acpi/thermal_zone/THRM
/proc/acpi/thermal_zone/THRM/polling_frequency
/proc/acpi/thermal_zone/THRM/cooling_mode
/proc/acpi/thermal_zone/THRM/trip_points
/proc/acpi/thermal_zone/THRM/temperature
/proc/acpi/thermal_zone/THRM/state
/proc/acpi/fan
/proc/acpi/button
/proc/acpi/button/sleep
/proc/acpi/button/sleep/SLPB
/proc/acpi/button/sleep/SLPB/info
/proc/acpi/button/lid
/proc/acpi/button/lid/LID
/proc/acpi/button/lid/LID/state
/proc/acpi/button/lid/LID/info
/proc/acpi/button/power
/proc/acpi/button/power/PWRF
/proc/acpi/button/power/PWRF/info
/proc/acpi/processor
/proc/acpi/processor/CPU1
/proc/acpi/processor/CPU1/power
/proc/acpi/processor/CPU1/limit
/proc/acpi/processor/CPU1/throttling
/proc/acpi/processor/CPU1/info
/proc/acpi/ac_adapter
/proc/acpi/ac_adapter/AC0
/proc/acpi/ac_adapter/AC0/state
/proc/acpi/battery
/proc/acpi/battery/BAT0
/proc/acpi/battery/BAT0/alarm
/proc/acpi/battery/BAT0/state
/proc/acpi/battery/BAT0/info
/proc/acpi/wakeup
/proc/acpi/alarm
/proc/acpi/sleep
/proc/acpi/event
/proc/acpi/fadt
/proc/acpi/dsdt
/proc/acpi/info
/proc/acpi/power_resource
/proc/acpi/embedded_controller
/proc/acpi/embedded_controller/EC0
/proc/acpi/embedded_controller/EC0/info
# find /sys/firmware/acpi/
/sys/firmware/acpi/
/sys/firmware/acpi/namespace
/sys/firmware/acpi/namespace/ACPI
/sys/firmware/acpi/namespace/ACPI/_TZ
/sys/firmware/acpi/namespace/ACPI/_TZ/THRM
/sys/firmware/acpi/namespace/ACPI/_SB
/sys/firmware/acpi/namespace/ACPI/_SB/LNKH
/sys/firmware/acpi/namespace/ACPI/_SB/LNKG
/sys/firmware/acpi/namespace/ACPI/_SB/LNKF
/sys/firmware/acpi/namespace/ACPI/_SB/LNKE
/sys/firmware/acpi/namespace/ACPI/_SB/LNKD
/sys/firmware/acpi/namespace/ACPI/_SB/LNKC
/sys/firmware/acpi/namespace/ACPI/_SB/LNKB
/sys/firmware/acpi/namespace/ACPI/_SB/LNKA
/sys/firmware/acpi/namespace/ACPI/_SB/PWRB
/sys/firmware/acpi/namespace/ACPI/_SB/SLPB
/sys/firmware/acpi/namespace/ACPI/_SB/LID
/sys/firmware/acpi/namespace/ACPI/_SB/RMEM
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/P0P2
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/P0P2/NEWC
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/P0P3
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/P0P3/PEG
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/P0P3/PEG/AMW0
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/P0P3/PEG/DVIA
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/P0P3/PEG/DVI
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/P0P3/PEG/LCD
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/P0P3/PEG/TV
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/P0P3/PEG/CRT
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/IDE1
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/P0P7
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/P0P6
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/P0P5
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/AZC
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/MC97
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/EUSB
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB4
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB3
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB2
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB1
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/IDE0
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/IDE0/CHN1
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/IDE0/CHN1/DRV1
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/IDE0/CHN1/DRV0
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/IDE0/CHN0
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/IDE0/CHN0/DRV1
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/IDE0/CHN0/DRV0
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/AC0
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/BAT0
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/PCIE
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/SBRG
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/SBRG/EC0
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/SBRG/OMSC
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/SBRG/RMSC
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/SBRG/COPR
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/SBRG/SPKR
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/SBRG/PS2M
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/SBRG/PS2K
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/SBRG/RTC0
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/SBRG/TMR
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/SBRG/DMAD
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/SBRG/PIC
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/P0P1
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/P0P1/IE3A
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/P0P1/LAN
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/P0P1/RAID
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/P0P1/MPC1
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/MCH
/sys/firmware/acpi/namespace/ACPI/CPU1
/sys/firmware/acpi/namespace/ACPI/PWRF
Regards,
_\\|//_
(-0-0-)
/---------ooO-(_)-Ooo--------\
| Magnus Sandberg |
| Email: mem-P9zfqOBuU5vLoDKTGw+V6w@public.gmane.org |
| GSM: +46-70-205 81 84 |
\----------------------------/
|| ||
ooO Ooo
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: FSC Amilo M-3438G
[not found] ` <20060112092118.84F211C812-FBVcP3zgNXfBmJu9jE4dRbNAH6kLmebB@public.gmane.org>
@ 2006-01-12 21:51 ` Magnus Sandberg
2006-01-19 9:58 ` Magnus Sandberg
0 siblings, 1 reply; 4+ messages in thread
From: Magnus Sandberg @ 2006-01-12 21:51 UTC (permalink / raw)
To: linux-acpi-u79uwXL29TY76Z2rM5mHXA; +Cc: mem-P9zfqOBuU5vLoDKTGw+V6w
Hi again,
I should clarify that I'm running Debian Etch (testing) with Linux
kernel 2.6.12-1-686.
I have now tried to recompile the dsdt and got the following output.
How should I correct the warnings? Could this warnings have anything to do
with my battery problems? Why is the new compiled DSDT.aml much smaller
than the dumped one? I small difference in size is okay, I guess. But 13%
smaller, is that okay?
# acpidump -b -t DSDT -o dsdt.aml
# iasl -d dsdt.aml
Intel ACPI Component Architecture
AML Disassembler version 20051117 [Nov 27 2005]
Copyright (C) 2000 - 2005 Intel Corporation
Supports ACPI Specification Revision 3.0
Loading Acpi table from file dsdt.aml
Acpi table [DSDT] successfully installed and loaded
Pass 1 parse of [DSDT]
Pass 2 parse of [DSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)
............................................................................
............................................................................
............................................................................
............................................................................
......
Parsing completed
Disassembly completed, written to "dsdt.dsl"
# iasl -tc dsdt.dsl
Intel ACPI Component Architecture
ASL Optimizing Compiler version 20051117 [Nov 27 2005]
Copyright (C) 2000 - 2005 Intel Corporation
Supports ACPI Specification Revision 3.0
dsdt.dsl 2017: Store (0x1F, DBG8)
Warning 2097 - Statement is unreachable ^
dsdt.dsl 2022: Store (0x0F, DBG8)
Warning 2097 - Statement is unreachable ^
dsdt.dsl 3357: Name (_WDG, Buffer (0x50)
Warning 2096 - Unknown reserved name ^ (_WDG)
ASL Input: dsdt.dsl - 4389 lines, 145148 bytes, 1799 keywords
AML Output: DSDT.aml - 16556 bytes 565 named objects 1234 executable opcodes
Compilation complete. 0 Errors, 3 Warnings, 0 Remarks, 614 Optimizations
# ls -lrt
total 344
-rw-r--r-- 1 root root 19011 2006-01-12 22:06 dsdt.aml
-rw-r--r-- 1 root root 145148 2006-01-12 22:07 dsdt.dsl
-rw-r--r-- 1 root root 155519 2006-01-12 22:21 dsdt.hex
-rw-r--r-- 1 root root 16556 2006-01-12 22:21 DSDT.aml
Regards,
_\\|//_
(-0-0-)
/-----------ooO-(_)-Ooo----------\
| Magnus Sandberg |
| Email: mem (a) datakon <.> se |
| GSM: +46-70-205 81 84 |
\--------------------------------/
|| ||
ooO Ooo
----- On 12th of January 2006 Magnus Sandberg wrote; -----
Subject: FSC Amilo M-3438G
From: Magnus Sandberg
Date: Thu, 12 Jan 2006 10:21:18 +0100
To: linux-acpi
Hi,
I'm new to this list and I have just got a Fujitsu-Siemens Amilo M-3438G
which I'm installing Debian on.
I have some problems with ACPI on the machine. The problems I have found so
far is that;
- I don't get any events when the battery is discharged or running low
- The lid button only reports close events so the lid-state is always
"closed"
- I don't know if "Fn"-keys should be reported via ACPI or not?
I only get the "sleep mode" Fn-key event, no other Fn-keys.
- I don't get events for "special hot keys" like "silent mode", etc
(The Amilo M3438 has 4 hot keys above the Fn-keys)
Things that do work;
- Power button generate event
- I get events for AC, CPU and BAT when I add or remove AC-adator
- As mentioned above Fn-key for sleep button works
- I can read battery state and battery info. Remaining capacity and voltage
seams to be okay. Remaining capacity is like 2 mAh just before the
machine dies. Warning and low levels seams to be calculated from
"last full capacity", I don't know if that is the way it should be done?
- Thermal Zone seams to work, get values in the range 31 C - 53 C
My questions are if I have to compile a new DSDT or if I should do
something else to correct the problems. And what things should or can ACPI
support (like Fn-keys or hot keys, etc)?
I changed the scripts in /etc/acpi to send all unknown events via logger to
/var/log/messages
If I remove the AC, I get the following;
ac_adapter AC0 00000080 00000000
battery BAT0 00000080 00000001
processor CPU1 00000080 00000006
If I connect the AC, I get;
ac_adapter AC0 00000080 00000001
battery BAT0 00000080 00000001
processor CPU1 00000080 00000005
<<< The rest of the email is removed >>>
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: FSC Amilo M-3438G
2006-01-12 21:51 ` Magnus Sandberg
@ 2006-01-19 9:58 ` Magnus Sandberg
0 siblings, 0 replies; 4+ messages in thread
From: Magnus Sandberg @ 2006-01-19 9:58 UTC (permalink / raw)
To: linux-acpi; +Cc: mem
Hi,
Could someone give me a hint, like
"you need a never kernel" or
"you need to give us more info" or
"read more on that site" or
"your problem can't be solved" or something like that.
Regards,
_\\|//_
(-0-0-)
/-----------ooO-(_)-Ooo----------\
| Magnus Sandberg |
| Email: mem (a) datakon <.> se |
| GSM: +46-70-205 81 84 |
\--------------------------------/
|| ||
ooO Ooo
----- On 12th of January 2006 Magnus Sandberg wrote; -----
Subject: Re: FSC Amilo M-3438G
From: Magnus Sandberg
Date: Thu, 12 Jan 2006 22:51:02 +0100
To: linux-acpi
Hi again,
I should clarify that I'm running Debian Etch (testing) with Linux
kernel 2.6.12-1-686.
I have now tried to recompile the dsdt and got the following output.
How should I correct the warnings? Could this warnings have anything to do
with my battery problems? Why is the new compiled DSDT.aml much smaller
than the dumped one? I small difference in size is okay, I guess. But 13%
smaller, is that okay?
# acpidump -b -t DSDT -o dsdt.aml
# iasl -d dsdt.aml
Intel ACPI Component Architecture
AML Disassembler version 20051117 [Nov 27 2005]
Copyright (C) 2000 - 2005 Intel Corporation
Supports ACPI Specification Revision 3.0
Loading Acpi table from file dsdt.aml
Acpi table [DSDT] successfully installed and loaded
Pass 1 parse of [DSDT]
Pass 2 parse of [DSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)
............................................................................
............................................................................
............................................................................
............................................................................
......
Parsing completed
Disassembly completed, written to "dsdt.dsl"
# iasl -tc dsdt.dsl
Intel ACPI Component Architecture
ASL Optimizing Compiler version 20051117 [Nov 27 2005]
Copyright (C) 2000 - 2005 Intel Corporation
Supports ACPI Specification Revision 3.0
dsdt.dsl 2017: Store (0x1F, DBG8)
Warning 2097 - Statement is unreachable ^
dsdt.dsl 2022: Store (0x0F, DBG8)
Warning 2097 - Statement is unreachable ^
dsdt.dsl 3357: Name (_WDG, Buffer (0x50)
Warning 2096 - Unknown reserved name ^ (_WDG)
ASL Input: dsdt.dsl - 4389 lines, 145148 bytes, 1799 keywords
AML Output: DSDT.aml - 16556 bytes 565 named objects 1234 executable opcodes
Compilation complete. 0 Errors, 3 Warnings, 0 Remarks, 614 Optimizations
# ls -lrt
total 344
-rw-r--r-- 1 root root 19011 2006-01-12 22:06 dsdt.aml
-rw-r--r-- 1 root root 145148 2006-01-12 22:07 dsdt.dsl
-rw-r--r-- 1 root root 155519 2006-01-12 22:21 dsdt.hex
-rw-r--r-- 1 root root 16556 2006-01-12 22:21 DSDT.aml
Regards,
----- On 12th of January 2006 Magnus Sandberg wrote; -----
Subject: FSC Amilo M-3438G
From: Magnus Sandberg
Date: Thu, 12 Jan 2006 10:21:18 +0100
To: linux-acpi
Hi,
I'm new to this list and I have just got a Fujitsu-Siemens Amilo M-3438G
which I'm installing Debian on.
I have some problems with ACPI on the machine. The problems I have found so
far is that;
- I don't get any events when the battery is discharged or running low
- The lid button only reports close events so the lid-state is always
"closed"
- I don't know if "Fn"-keys should be reported via ACPI or not?
I only get the "sleep mode" Fn-key event, no other Fn-keys.
- I don't get events for "special hot keys" like "silent mode", etc
(The Amilo M3438 has 4 hot keys above the Fn-keys)
Things that do work;
- Power button generate event
- I get events for AC, CPU and BAT when I add or remove AC-adator
- As mentioned above Fn-key for sleep button works
- I can read battery state and battery info. Remaining capacity and voltage
seams to be okay. Remaining capacity is like 2 mAh just before the
machine dies. Warning and low levels seams to be calculated from
"last full capacity", I don't know if that is the way it should be done?
- Thermal Zone seams to work, get values in the range 31 C - 53 C
My questions are if I have to compile a new DSDT or if I should do
something else to correct the problems. And what things should or can ACPI
support (like Fn-keys or hot keys, etc)?
I changed the scripts in /etc/acpi to send all unknown events via logger to
/var/log/messages
If I remove the AC, I get the following;
ac_adapter AC0 00000080 00000000
battery BAT0 00000080 00000001
processor CPU1 00000080 00000006
If I connect the AC, I get;
ac_adapter AC0 00000080 00000001
battery BAT0 00000080 00000001
processor CPU1 00000080 00000005
<<< The rest of the email is removed >>>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: FSC Amilo M-3438G
2006-01-12 9:21 FSC Amilo M-3438G Magnus Sandberg
[not found] ` <20060112092118.84F211C812-FBVcP3zgNXfBmJu9jE4dRbNAH6kLmebB@public.gmane.org>
@ 2006-01-19 10:27 ` Matthew Garrett
1 sibling, 0 replies; 4+ messages in thread
From: Matthew Garrett @ 2006-01-19 10:27 UTC (permalink / raw)
To: Magnus Sandberg; +Cc: linux-acpi
On Thu, Jan 12, 2006 at 10:21:18AM +0100, Magnus Sandberg wrote:
> - I don't get any events when the battery is discharged or running low
The spec requires that an event be generated, but it's possible that
your hardware just doesn't.
> - The lid button only reports close events so the lid-state is always
> "closed"
I've seen this before. I think it's a crap hardware thing rather than
anything else.
> - I don't know if "Fn"-keys should be reported via ACPI or not?
That's highly hardware dependent. Some Fujitsus seem to expose their
keys via ACPI, but you'd still need another driver for them to work.
--
Matthew Garrett | mjg59@srcf.ucam.org
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2006-01-19 10:28 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-01-12 9:21 FSC Amilo M-3438G Magnus Sandberg
[not found] ` <20060112092118.84F211C812-FBVcP3zgNXfBmJu9jE4dRbNAH6kLmebB@public.gmane.org>
2006-01-12 21:51 ` Magnus Sandberg
2006-01-19 9:58 ` Magnus Sandberg
2006-01-19 10:27 ` Matthew Garrett
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox