![]() |
APMD-List: |
to APMD Home
|
Index:
[thread]
[date]
[subject]
[author]
From: Jont Allen <jba@research.att.com> To : <craigm@milkyway.gsfc.nasa.gov> Re: minor bug in apmd-3.0beta9Jont Allen wrote: > > Avery and Craig, > > I found a small bug. I have an IBM560X. F3 maps to standby and F4 to > suspend. When I hit F4, it calls > apmd_proxy standby system > rather than > apmd_proxy suspend system > > apm -s and apm -S call suspend and standby as user, which seems correct. > > Thus it looks like the system suspend (F4) is mapped wrong in the software > some how. > > Version 3.0 beta 8 worked fine. When I upgraded to 3.0 beta 9, the problem > appeared. > > Great job! > and thanks, > > Jont More info, that may help alot in understanding what is going on. If I have my NIC in, and up, then and only then do I get the above problem. Once I eject the nic, F4 works normally and results in the "apmd_proxy suspend system" call, as it should. (I just verified this once more) So it looks like the bios or apm driver is changing the suspend into a standby because the PCMCIA NIC (a waveland wireless card, FUI). I just tried it with a 3com 3c589D-TP, and got the same result (F4 = standby). Jont Index: [thread] [date] [subject] [author] |