From: Sven Ladegast <sven@linux4geeks.de>
To: linux-kernel@vger.kernel.org
Subject: Re: VIA Rhine WOL
Date: Thu, 18 Nov 2004 22:46:59 +0100 [thread overview]
Message-ID: <200411182246.59461.sven@linux4geeks.de> (raw)
In-Reply-To: <20041118181045.GC28972@k3.hellgate.ch>
On Thursday 18 November 2004 19:10, Roger Luethi wrote:
> The via-rhine code has changed in the 2.6.9/2.6.10 time frame: Legacy
> WOL is turned off (mostly), so it will not work unless you explicitly
> tell the driver to enable WOL. You can do this using ethtool(8).
>
> If WOL used to work with your Rhine hardware and now all of a sudden
> doesn't, check first if you enabled WOL using ethtool.
>
> Roger
That was the information I needed... :o)
I just wondered why my machine did not want to wake up.
Sven
--
Sven Ladegast, Friedrich-Fröbel-Straße 11, 93310 Arnstadt / Germany
Phone: +49-175-5334308, PGP-key: 0x5856A5ED
prev parent reply other threads:[~2004-11-18 21:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 18:10 VIA Rhine WOL Roger Luethi
2004-11-18 21:46 ` Sven Ladegast [this message]
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=200411182246.59461.sven@linux4geeks.de \
--to=sven@linux4geeks.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;
as well as URLs for NNTP newsgroup(s).