From: "Randy.Dunlap" <rddunlap@osdlab.org>
To: Alex Cruise <acruise@infowave.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: apm suspend broken in 2.4.10
Date: Thu, 27 Sep 2001 15:17:22 -0700 [thread overview]
Message-ID: <3BB3A572.BF263906@osdlab.org> (raw)
In-Reply-To: <6B90F0170040D41192B100508BD68CA1015A81AE@earth.infowave.com>
Alex Cruise wrote:
>
> From: Randy.Dunlap [mailto:rddunlap@osdlab.org]
>
> > Verified here.
> > APM doesn't install if apm=on or apm=off is used in 2.4.10.
> >
> > Here's a small patch for it. With this patch, apm thread,
> > /proc/apm, misc apm_bios device etc. are created.
>
> Thanks... apm=on works now, but APM functionality itself still suffers from
> the same failure as before (Resource temporarily unavailble.)
>
> I should mention that before your patch, /dev/misc/apm_bios, /dev/apm_bios
> and /proc/apm were already being created by the driver; it's going through
> the motions but not delivering the goods.
>
> -0xe1a
{little-endian n[iy]bbles ?}
Sounds like our 2.4.10's are different then. :)
Without this patch, mine didn't create /proc/apm, register as a
misc device, or create the kapmd-idle kernel thread.
Must be a distro thingy.
Return of EAGAIN from the SUSPEND ioctl means that
send_event() failed, which means that some device driver
didn't want suspend to happen...which means that some
device driver got changed. :(
What was the last working kernel AFAUK (for this APM stuff)?
~Randy
next prev parent reply other threads:[~2001-09-27 22:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-27 21:03 apm suspend broken in 2.4.10 Alex Cruise
2001-09-27 22:17 ` Randy.Dunlap [this message]
2001-09-28 9:12 ` jc
-- strict thread matches above, loose matches on Subject: below --
2001-09-28 22:30 Alex Cruise
2001-09-28 22:31 ` Randy.Dunlap
[not found] <6B90F0170040D41192B100508BD68CA1015A81B2@earth.infowave.co m>
2001-09-28 3:31 ` Lewin A.R.W. Edwards
2001-09-28 3:03 Alex Cruise
2001-09-28 1:50 Alex Cruise
2001-09-28 22:05 ` Randy.Dunlap
2001-09-27 23:56 Alex Cruise
2001-09-28 0:10 ` Randy.Dunlap
2001-09-28 0:52 ` Alan Cox
2001-09-28 9:09 ` jc
2001-09-28 10:05 ` Keith Owens
2001-09-27 21:07 Alex Cruise
2001-09-27 0:29 Alex Cruise
2001-09-27 20:36 ` Randy.Dunlap
2001-09-25 22:00 jc
2001-09-26 8:44 ` Matthias Andree
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3BB3A572.BF263906@osdlab.org \
--to=rddunlap@osdlab.org \
--cc=acruise@infowave.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox