Bug 111691 - kernel 2.4.21-4.0.1.EL has no apm support (tested on dell d600 laptop)
Summary: kernel 2.4.21-4.0.1.EL has no apm support (tested on dell d600 laptop)
Keywords:
Status: CLOSED DUPLICATE of bug 111689
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel
Version: 3.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-12-08 20:37 UTC by Helmut G. Katzgraber
Modified: 2007-11-30 22:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:00:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Helmut G. Katzgraber 2003-12-08 20:37:36 UTC
Description of problem:

when running apm -s with the 2.4.21-4.0.1.EL kernel, apm returns

[root@localhost]# /usr/bin/apm -s
No APM support in kernel

more details:

[root@localhost]# uname -a
Linux localhost.localdomain 2.4.21-4.0.1.EL #1 Thu Oct 23 01:36:33 EDT 2003
i686 i686 i386 GNU/Linux

there exists no file called "/proc/apm".

Version-Release number of selected component (if applicable):

kernel: kernel-2.4.21-4.0.1.EL
apm: apmd-3.0.2-18

How reproducible:

Tested on one system. Not sure if reproducible but seems to be simple: apm is not 
compiled into the upgraded kernel.

Steps to Reproduce:
1. Install RHEL WS 3.0 on a laptop. run up2date-nox and upgrade the kernel to
 2.4.21-4.0.1.EL.
2. try to put the laptop to sleep with apm: /usr/bin/apm -s (nothing happens, 
program mentions that there is no support for APM in the kernel.
  
Actual results:

program exits with above mentioned error message: "No APM support in kernel"

Expected results:

laptop goes into suspend mode.

Additional info: output from dmesg after a boot attached later.

Comment 1 Bill Nottingham 2003-12-08 20:54:56 UTC

*** This bug has been marked as a duplicate of 111689 ***

Comment 2 Red Hat Bugzilla 2006-02-21 19:00:19 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


Note You need to log in before you can comment on or make changes to this bug.