public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kyle Rose <krose+linux-kernel@krose.org>
To: Adam Belay <ambx1@neo.rr.com>
Cc: Kyle Rose <krose+linux-kernel@krose.org>, linux-kernel@vger.kernel.org
Subject: Re: ACPI sleep states on Tyan Thunder K8W S2885
Date: Mon, 02 May 2005 10:16:10 -0400	[thread overview]
Message-ID: <4276362A.8090508@krose.org> (raw)
In-Reply-To: <20050501225335.GG3951@neo.rr.com>

> S5 wake devices can be a very fuzzy area.  In general, the ACPI spec
> recommends that wake capabilities are enabled before halting the system.
> Therefore, your network card driver may need to specifically handle this.

I'll check into that.

> For starters, we should probably look at "lspci -vv".  I'm assuming your
> network card is PCI.  This will allow us to see if it's capable of waking
> from D3-cold, the state it will most likely be in during S5.

I'll have to do this tonight.  I can't start the machine remotely. :)

> I would also check your BIOS configuration and see if it's possible to
> specifically enable wake-on-lan.  Let me know if this helps.

It only has an option for "wake on PME," which I've activated.  Again,
as I've said, shutting down from Win XP allows WOL, so the difference is
between how Linux and Windows handle the GigE device or handle shutdown.

> Finally, what kernel version are you using?

Sorry, I should have given more details.  It's Linux-2.6.11.7 with no
other patches.  I think the earliest I tested this was with 2.6.9, and
it didn't work there either.

Thanks,
Kyle

      reply	other threads:[~2005-05-02 14:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-29 16:36 ACPI sleep states on Tyan Thunder K8W S2885 Kyle Rose
2005-05-01 22:53 ` Adam Belay
2005-05-02 14:16   ` Kyle Rose [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=4276362A.8090508@krose.org \
    --to=krose+linux-kernel@krose.org \
    --cc=ambx1@neo.rr.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