linux-kernel - Re: Wake On lan and ATL1 nic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <201102100859.39059.thomas@fjellstrom.ca>
Date:	Thu, 10 Feb 2011 08:59:38 -0700
From:	Thomas Fjellstrom <thomas@...llstrom.ca>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Linux-pm mailing list" <linux-pm@...ts.linux-foundation.org>
Subject: Re: Wake On lan and ATL1 nic

On December 23, 2010, Rafael J. Wysocki wrote:
> On Thursday, December 23, 2010, Thomas Fjellstrom wrote:
> > On December 22, 2010, Rafael J. Wysocki wrote:
> > > On Wednesday, December 15, 2010, Thomas Fjellstrom wrote:
> > > > I can't seem to get wol to work with my desktop, which has an
> > > > integrated ATL1 GbE nic. I can't be absolutely sure if it ever
> > > > worked, but I think it did at one point. I can use ethtool to look
> > > > at the wol status, that it supports magic-packet wol, and I can
> > > > enable it, which is done at boot using an init script. But No matter
> > > > how many times I try to send a wol packet to that machine it never
> > > > wakes up.
> > > > 
> > > > Looking around on the net seems to say it is supported, and should
> > > > work, but I'm not having any luck. Anyone have any hints?
> > > 
> > > It works for me with 2.6.37-rc7 and the appended patch applied (at
> > > least the machine is woken up from suspend to RAM).  Of course, the
> > > adapter needs to be configured for that with the help of ethtool.
> > 
> > Hi, thanks for making quick work of this. I have one slight problem, my
> > nic seems to use the atl1 driver, and not atl1c. I've tried using atl1c
> > and atl1e, both will load if I modprobe them, but neither actually bring
> > up the device. Even tried blacklisting atl1 first.
> 
> I see.
> 
> Please try the patch below, then.  It's analogous to the atl1c one, but
> it's untested (builds for me).
> 
> Thanks,
> Rafael
> 
> 

Hi, I just (finally) got around to testing this, and it all works now! thanks a 
lot. Though to be honest, it may not have had an impact. I noticed my BIOS 
settings for PCI device wakeup had been disabled (I could swear they were on, 
but after testing the patch, and wol STILL didn't work, I didn't have any 
other ideas...). And it seems WOL now works on both an unpatched 
2.6.36.1+autogroup, and a patched 2.6.37.

I haven't done any significant testing of this patch, other than the machine 
boots, the network comes up, and WOL works.

If you have any things you want me to try, to make sure the patch is correct, 
let me know.

Thanks again for working on the patches.

-- 
Thomas Fjellstrom
thomas@...llstrom.ca
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/