From: Santiago Garcia Mantinan <manty@manty.net>
To: linux-kernel@vger.kernel.org
Cc: acpi@phobos.fachschaften.tu-muenchen.de
Subject: Wake On Lan broken since kernel version 2.4.14
Date: Sat, 2 Feb 2002 11:14:03 +0100 [thread overview]
Message-ID: <20020202101403.GA6122@man.beta.es> (raw)
Hi!
On kernel 2.4.13 with acpi compiled one could have at least the cards which
use the driver 3c59x, when option enable_wol=1 was set, to wake his computer
when a WOL packet had been sent to the net.
However, since version 2.4.14 and up to 2.4.18pre7 inclusive, WOL is not
working, and it is again because of ACPI code, if you don't compile ACPI in
and you compile for example APM, then it will work, but if you compile ACPI
then it won't.
I'd like to provide more info on this, but I don't know what else to say
exept that this was tested on a PIII via chipset based machine and on a PIV
intel based one with the same results, I'm using Donald Becker's ether-wake.
If you want more info I'll try to gatter it.
Regards...
--
Manty/BestiaTester -> http://manty.net
reply other threads:[~2002-02-02 10:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020202101403.GA6122@man.beta.es \
--to=manty@manty.net \
--cc=acpi@phobos.fachschaften.tu-muenchen.de \
--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