Bug#288712: kernel-image-2.4.27-1 ACPI Fix
On Mon, Jan 17, 2005 at 10:54:41AM +0100, San Vu-Ngoc wrote:
> Actually I've just realized there is still a problem:
>
> At first I didn't use your patched package. instead I compiled the
> kernel using
> kernel-source 2.4.27-6 and your patch and the .config from
> kernel-headers 2.4.27-6.
> (I attach the file to this mail)
> That was when it worked !
>
> But today I tried your
> kernel-image-2.4.27-2-686_2.4.27-8_i386.deb
> you posted on
> http://debian.vergenet.net/testing/
> and it does not work !
> When I push the power button, now the LCD switches off, but not the
> laptop, and
> I still have to remove the battery.
That is very strange.
2.4.27-6
Includes 103-enter-acpi-early.diff
which I am pretty sure is the cause of your problem.
Unfortunately reversing it causes other issues,
so that isn't really an option.
It also includes 110-asus-boot-crash-fix.diff,
which is also an ACPI fix, but is probably not effecting you.
2.4.27-7
Includes 119-acpi_early-build.diff,
which is a build fix. If your kernel builds, this
probably isn't effecting you.
2.4.27-8 (proposed, from http://debian.vergenet.net/testing/ and SVN)
Includes 132_acpi_off.diff, which is a fix for
103-enter-acpi-early.diff. This should resolve your problem.
What I am curous is, what is the difference between the image
that you compiled, 2.4.27-6 + 132_acpi_off.diff. And the image
that I made, which is 2.4.27-8, which is basically
2.4.27-6 + 119-acpi_early-build.diff + 132_acpi_off.diff.
I checked your .config and the config for
kernel-image-2.4.27-2-686_2.4.27-8, and apart from some
unused, unrelated options, they are the same. So that
does not seem to be the cause of the difference.
Can you send the ACPI logs (and APIC just for good measure)
from the non-working 2.4.27-8 image, and the working 2.4.27-6
that you created? They should be the same by the reasoning above.
> Horms wrote:
> >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
> >>APIC.
> >>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.
--
Horms
Reply to: