From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0; DigExt)
Installed RedHat 7.1 (florence) on Dell PowerEdge (newt) 300. The apmd
script did not start the daemon /etc/rc3.d/S26apmd. also
calling "/usr/sbin/apmd start" resulted in error message "no apmd support
in kernel. Checked ntsysv, it showed apmd service set to start on boot.
Steps to Reproduce:
1. call "/usr/bin/apmd start"
Is this an SMP system?
It's either an SMP system or the kernel was recompiled without APM support.
apmd is working perfectly on all my UP systems.
SMP and APM don't work together, this is a limitation of the apm protocol, not
I didn't know that apmd is not supported with the SMP kernel. I verified that
apmd does start and work correctly with the UP kernel on this system, and that
it does not work with the SMP kernel.
This gentleman has a Presarrio 1900 163XL.
The installer put a kernel that has no apmd support.
He is Cc'd on this Bug report and will post comments.
I had him type:
He got the error message "no apmd support in kernel."
So I am assuming there is a porblem either with ampd or the intaller.
Mr. Holcomb is the one who has this issue. He will post the results of uname
[root@localhost /root]# uname -r
This is the kernel I am running.
The apm daemon is not supposed to start on kernels without APM support (such
as all SMP systems - APM is not SMP-safe).
I am reopening this because I do not believe that 2.4.2-2 is an SMP kernel.
2.4.2-2smp is, right?
Please explain why you are saying that 2.4.2-2 is an SMP kernel?
Also, this system is a laptop with one processor., just so ya know.
Finally, I want to recommend to Mr. Holcomb that he upgrade to the latest Kernel
erratta by either updating RHN first:
Then running up2date. Or by upgrading the kernel by hand:
My guess is it's a recompiled 2.4.2-2 with modified settings.
The 2.4.2-2 we shipped has apm support and works on all machines here.
Thanks for the feedback Bero.
So Mr. Holcomb, did you make your own kernel? I thought I asked you this before
filling this report, but I want to get a response on the record.
Also, I remember seeing something funny in your lilo.conf. What was that entry
caused by again?
Finally, please let me know if the kernel update fixes this issue ASAP so we can
close this bug.
Thanks a million.
I reinstalled Redhat fresh using the default Laptop configuration. I notice in
the output when booting the line: apm: Bios not found.
Then apmd is doing the right thing - if you don't have an APM BIOS (or if your APM
BIOS is broken), apmd shouldn't start.
Assigning to kernel because it might actually be a problem with the kernel not
detecting the APM BIOS, but it's much more likely a BIOS bug.
This is probably a system with only ACPI, which is not yet supported.
Unfortunately, I don't think this is a bug, just a not-yet-ready and
thus missing feature.