Bug#290013: kernel-image-2.4.27-1 ACPI Fix
- To: VU NGOC San <firstname.lastname@example.org>
- Cc: Jan Nieuwenhuizen <email@example.com>, San Vu-Ngoc <firstname.lastname@example.org>, email@example.com, Arno <firstname.lastname@example.org>, email@example.com, Joerg Diederich <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org
- Subject: Bug#290013: kernel-image-2.4.27-1 ACPI Fix
- From: Horms <email@example.com>
- Date: Mon, 17 Jan 2005 09:57:54 +0900
- Message-id: <20050117005753.GB22308@verge.net.au>
- Reply-to: Horms <firstname.lastname@example.org>, email@example.com
- In-reply-to: <Pine.LNX.4.61.0501161734110.1676@mozart>
- References: <20041213205711.6F3C0AFAE8@oliebij.flower> <Pine.LNX.4.44.0501121418280.21361-100000@finity-new> <E1Cogfy-0000Th-RD@localhost.localdomain> <E1CnegPfirstname.lastname@example.org> <200501050957.j059vpWS075556@tibre2.ujf-grenoble.fr> <20050115071541.GB935@verge.net.au> <email@example.com> <Pine.LNX.4.61.0501161734110.1676@mozart>
On Sun, Jan 16, 2005 at 05:43:56PM +0100, VU NGOC San wrote:
> it also works for me, thanks ! (288712)
> (works means that, as before, ACPI does not work on the dell latitude
> d800, but at least I can manually turn off the laptop with the power
> button, and the "hardware call" to BIOS using the battery key works, so I
> can check battery status this way)
> actually no more message about ACPI shows up anymore on dmesg...
> in previous versions I had something like this:
> Dell Latitude with broken BIOS detected. Refusing to enable the local
> ACPI: RSDP (v000 DELL ) @ 0x000fdf00
> ACPI: RSDT (v001 DELL CPi R 0x27d4010c ASL 0x00000061) @ 0x1fff0000
> ACPI: FADT (v001 DELL CPi R 0x27d4010c ASL 0x00000061) @ 0x1fff0400
> ACPI: ASF! (v016 DELL CPi R 0x27d4010c ASL 0x00000061) @ 0x1fff0800
> ACPI: DSDT (v001 INT430 SYSFexxx 0x00001001 MSFT 0x0100000e) @ 0x00000000
Unfortunately I think that is about as good as it is going
to get on that hardware. As I understand it is known not
to work with local APIC, though I am not sure of the details why.
> it seems however that the i8k module (fan control) does not work anymore.
> Maybe I need some more testing
> (I used to launch it using
> modprobe i8k force=1)
Please let me know if you make any progress there.