On Mon, Jun 27, 2011 at 11:21:26PM +0100, Ben Hutchings wrote: > On Mon, Jun 27, 2011 at 11:28:34PM +0200, Hans Ekbrand wrote: > > Package: linux-source-2.6.39 > > Version: 2.6.39-2 > > Severity: normal > > > > Summary: I recompiled with make menuconfig, loaded the default > > config for linux-image-2.6.39-486-2 into menuconfig, disabled ACPI, > > enabled APM (but not the sub-items of APM in menuconfig). Then > > booted this image with "apm=on" and now: > > > > # apm -S > > No APM support in kernel > > So apm lies... > > > selected output from dmesg: > > > > $ dmesg | grep -i apm > > [ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.39 root=/dev/mapper/amin-root ro apm=on quiet > > [ 12.378224] apm: BIOS not found. > [...] > > Well, are you sure that this machine does have APM BIOS support? > Because the kernel cannot use APM that is not there... Yes I am sure, because apm -S has worked perfectly on this particular machine with older kernels. Could it be a battery thing? Otherwise I know APM is supported by that BIOS. This is an old compaq laptop, "Armada 1540D", so I don't expect the BIOS to be perfectly compliant with the standards. But it did work with older official debian kernels, however, this is the first time I have tried a custom kernel on it. That I did not enable the sub-itmes of APM in menuconfig, might that be a problem? They were described as "(NEW)", so I thought that they cannot be necessary, but later on I saw that they have been "(NEW)" for the last ten years or so :-)
Attachment:
signature.asc
Description: Digital signature