From: "Michael Chan" <mchan@broadcom.com>
To: "Ben Hutchings" <ben@decadent.org.uk>
Cc: 690845@bugs.debian.org, "Teodor MICU" <mteodor@gmail.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: Bug#690845: ethtool: incorrect WoL detection on Broadcom NX II rev < 12
Date: Fri, 19 Oct 2012 12:38:50 -0700 [thread overview]
Message-ID: <1350675530.8764.131.camel@LTIRV-MCHAN1.corp.ad.broadcom.com> (raw)
In-Reply-To: <1350610209.22276.6.camel@deadeye.wl.decadent.org.uk>
On Fri, 2012-10-19 at 02:30 +0100, Ben Hutchings wrote:
> Teodor MICU reported that:
> > On Broadcom NX II rev < 12 network interfaces it's not possible to activate
> > WoL using 'ethtool' (it can only be done from the MBA Configuration Menu).
> >
> > However, even if "Pre-boot Wake On LAN" was enabled 'ethtool' doesn't
> > see this change:
> > Supports Wake-on: d
> > Wake-on: d
> >
> > I've just tested that WoL works for this system.
>
> He's been using Linux 2.6.32 and Linux 3.2, but there don't seem to have
> been any later changes to WoL support in bnx2.
>
Teodor MICU, please provide lspci -vvv and ethtool -i eth? on the
Broadcom bnx2 device. Thanks.
next prev parent reply other threads:[~2012-10-19 19:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121018134717.9579.22997.reportbug@palomino.museglobal.com>
[not found] ` <1350570748.26833.102.camel@deadeye.wl.decadent.org.uk>
[not found] ` <CAG2Wgfee=qsiUhAk5reYTypcOZL0kM5A58J+LjB1wuQ_k9FrfA@mail.gmail.com>
2012-10-19 1:30 ` Bug#690845: ethtool: incorrect WoL detection on Broadcom NX II rev < 12 Ben Hutchings
2012-10-19 19:38 ` Michael Chan [this message]
2012-10-22 7:52 ` Teodor MICU
2012-10-22 22:54 ` Michael Chan
2012-10-23 1:45 ` Ben Hutchings
2012-10-23 2:18 ` Michael Chan
2012-10-24 14:23 ` Ben Hutchings
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=1350675530.8764.131.camel@LTIRV-MCHAN1.corp.ad.broadcom.com \
--to=mchan@broadcom.com \
--cc=690845@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=mteodor@gmail.com \
--cc=netdev@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