Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1031300AbWI1Ak4 (ORCPT ); Wed, 27 Sep 2006 20:40:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1031302AbWI1Ak4 (ORCPT ); Wed, 27 Sep 2006 20:40:56 -0400 Received: from mail.gmx.de ([213.165.64.20]:19098 "HELO mail.gmx.net") by vger.kernel.org with SMTP id S1031300AbWI1Ak4 (ORCPT ); Wed, 27 Sep 2006 20:40:56 -0400 X-Authenticated: #5039886 Date: Thu, 28 Sep 2006 02:40:53 +0200 From: =?iso-8859-1?Q?Bj=F6rn?= Steinbrink To: Andrew Morton , Martin Filip , linux-kernel@vger.kernel.org, Ayaz Abdulla Subject: Re: forcedeth - WOL [SOLVED] Message-ID: <20060928004053.GA3521@atjola.homenet> Mail-Followup-To: =?iso-8859-1?Q?Bj=F6rn?= Steinbrink , Andrew Morton , Martin Filip , linux-kernel@vger.kernel.org, Ayaz Abdulla References: <1159379441.9024.7.camel@archon.smoula-in.net> <20060927183857.GA2963@atjola.homenet> <1159389486.8902.4.camel@archon.smoula-in.net> <20060927165704.613bf0aa.akpm@osdl.org> <20060928000447.GB2963@atjola.homenet> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20060928000447.GB2963@atjola.homenet> User-Agent: Mutt/1.5.13 (2006-08-11) X-Y-GMX-Trusted: 0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2406 Lines: 67 On 2006.09.28 02:04:48 +0200, Bj?rn Steinbrink wrote: > > Hi Andrew, > > > On 2006.09.27 16:57:04 -0700, Andrew Morton wrote: > > On Wed, 27 Sep 2006 22:38:06 +0200 > > Martin Filip wrote: > > > > > Hi, > > > > > > Bj__rn Steinbrink p____e v St 27. 09. 2006 v 20:38 +0200: > > > > > > > Did you check that WOL was enabled? I need to re-activate it after each > > > > boot (I guess that's normal, not sure though). > > > > The output of "ethtool eth0" should show: > > > > > > > > Supports Wake-on: g > > > > Wake-on: g > > > > > > > Yes, of course :) > > > > > > > Also, I remember a bugzilla entry in which it was said that the MAC was > > > > somehow reversed by the driver. I that is still the case (I can't find > > > > the bugzilla entry right now), you might just reverse the MAC address in > > > > your WOL packet to workaround the bug. > > > > > > Hey! this is really crazy :) but it works! To bo honest - I really do > > > not know what crazy bug could cause problems like this. I thought it's > > > NIC thing to manage all the work about WOL. I thought OS only sets NIC > > > into "WOL mode". > > > > > > But seeing this - one packet for windows and one magic packet for linux > > > driver - I really do not get it. > > > > > > > Are you saying that byte-reversing the MAC address make WOL work correctly? > > > > What tool do you use to send the packet, and how is it being invoked? > > > > Do we know if this reversal *always* happens with this driver, or only > > sometimes? > > > > Thanks. > > searching bugzilla was more succesful this time (somehow bugzillas hate > me, so I need a bunch of tries every time), the bug I meant was #6604. > > The bugreport says that it should work with 0.57 though (which is in > 2.6.18 AFAICT), I'll go and see if it works for me... ... 5 reboots later ... It still breaks with 2.6.18. Not touching WOL from Linux at all, rebooting and turning the box off during POST, WOL works using the real MAC address. Booting 2.16.17.x or 2.6.18, turning on WOL and finally shutting down the box, I need to send the WOL packet with the MAC address reversed. Bj?rn - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/