From: James Brents <James@nistix.com>
To: Mark Hahn <hahn@coffee.psychology.mcmaster.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: WOL failure after shutdown
Date: Sun, 11 Feb 2001 20:37:05 -0600 [thread overview]
Message-ID: <3A874C51.5030207@nistix.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10102111831050.30844-100000@coffee.psychology.mcmaster.ca>
Sorry, I wrote that in a hurry. Its a 3Com PCI 3c905C Tornado. I can
successfully use wakeonlan if I power off the machine immeadiatly after
turning it on. Using the shutdown command, which it will when I need it
to power back up, it will not work.
Im using a wakeonlan cable to my motherboard as well, not using wake
through PCI bus.
Kernel is 2.4.1
I appologize for not providing all required the specs in the original
message.
--
James
Mark Hahn wrote:
>> wakeonlan packets to my other servers to start them back up. Wakeonlan
>> works if i were to hit the power before Linux starts, so I know I have
>> it configured properly, and I also have wakeonlan turned on in the BIOS.
>> However, when I do shutdown -h, it will turn the power off, but
>> wakeonlan does not work. Ive tried enabling ACPI and tinkering with
>> options in the BIOS, but i cant power up with WOL after issuing shutdown -h.
>
>
> so when can you powerup with WOL? WOL requires that the driver leave the
> card in a particular state; obviously, you should mention which NIC.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~2001-02-12 2:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10102111831050.30844-100000@coffee.psychology.mcmaster.ca>
2001-02-12 2:37 ` James Brents [this message]
2001-02-12 8:06 ` WOL failure after shutdown Philipp Matthias Hahn
2001-02-12 8:16 ` Tobias Ringstrom
2001-02-12 8:26 ` Jeff Garzik
2001-02-12 9:54 ` Alan Cox
2001-02-11 23:28 James Brents
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=3A874C51.5030207@nistix.com \
--to=james@nistix.com \
--cc=hahn@coffee.psychology.mcmaster.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.