mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Martin Filip <bugtraq@smoula.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: forcedeth - WOL
Date: Wed, 27 Sep 2006 19:35:12 +0100	[thread overview]
Message-ID: <200609271935.12969.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <1159379441.9024.7.camel@archon.smoula-in.net>

On Wednesday 27 September 2006 18:50, Martin Filip wrote:
> Hi to LKML,
>
> I'm experiencing some troubles with WOL with my nForce NIC.
> The problem is simple - after setting WOL mode to magic packet my PC
> won't wake up. I've noticed there were some changes about this in new
> kernel, but no luck for me.
>
> I'm using 2.6.18 kernel, vanilla. I've tried this with Windows Vista RC1
> (build 5600) and WOL works correctly. My NIC is integrated on MSI K8N
> Neo4-FI

On my nForce4 CK804 it's disabled by default, I bet this is your problem:

[root] 19:33 [~] ethtool lan
Settings for lan:
        Supported ports: [ MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 100Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 1
        Transceiver: external
        Auto-negotiation: on
        Supports Wake-on: g
        Wake-on: d
        Link detected: yes

Read the manpage for ethtool. HTH.

-- 
Cheers,
Alistair.

Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.

  reply	other threads:[~2006-09-27 18:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-27 17:50 Martin Filip
2006-09-27 18:35 ` Alistair John Strachan [this message]
2006-09-27 20:26   ` Martin Filip
2006-09-27 20:48     ` Francois Romieu
2006-09-27 21:20       ` John W. Linville
2006-09-27 18:38 ` Björn Steinbrink
2006-09-27 20:38   ` forcedeth - WOL [SOLVED] Martin Filip
2006-09-27 23:57     ` Andrew Morton
2006-09-28  0:04       ` Björn Steinbrink
2006-09-28  0:40         ` Björn Steinbrink
2006-09-28  1:01           ` Björn Steinbrink
2006-09-28  1:36             ` Andrew Morton
2006-09-28  2:04               ` Björn Steinbrink
2006-09-28  2:24                 ` Björn Steinbrink
2006-09-28  3:39                   ` Andrew Morton
2006-09-28 11:37                     ` Martin Filip
2006-09-28 17:09                     ` Ayaz Abdulla
2006-09-28  1:03           ` Andrew Morton

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=200609271935.12969.s0348365@sms.ed.ac.uk \
    --to=s0348365@sms.ed.ac.uk \
    --cc=bugtraq@smoula.net \
    --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

all inboxes | Powered by JetHome®