Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 11 Aug 2009 12:17:54 -0400
From:      Matthew Hagerty <matthew@digitalstratum.com>
To:        freebsd-hackers@freebsd.org
Subject:   Re: Tracing Wake on Lan problem?
Message-ID:  <4A8199B2.30403@digitalstratum.com>
In-Reply-To: <58c737d70908110858l3548e91cnddb5fa1b85a29533@mail.gmail.com>
References:  <4A80EBA6.40908@digitalstratum.com>	 <06A3B5AF-D3DA-4446-84EF-93314B2EA636@gid.co.uk>	 <4A818B0E.7090609@digitalstratum.com> <4A819049.6030806@unsane.co.uk> <58c737d70908110858l3548e91cnddb5fa1b85a29533@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Chris Ruiz wrote:
> On Tue, Aug 11, 2009 at 10:37 AM, Vincent Hoffman<vince@unsane.co.uk> wrote:
>   
>> Matthew Hagerty wrote:
>>     
>>> Bob Bishop wrote:
>>>       
>>>> Hi,
>>>>
>>>> On 11 Aug 2009, at 04:55, Matthew Hagerty wrote:
>>>>
>>>>         
>>>>> I'm trying to get the Wake on Lan feature working on a 7.2-release
>>>>> box. [etc]
>>>>>           
>>>> You may need to turn WoL on in the BIOS, have a look in the same
>>>> place as the LAN boot settings.
>>>>
>>>> --
>>>> Bob Bishop
>>>> rb@gid.co.uk
>>>>         
>>> I guess I assumed that, since the WoL works with my Intel Pro/100 NIC,
>>> that the APCI and wake-up settings in the BIOS were set correctly.  It
>>> is only when I try the Pro/1000 that I'm having problems; and it seems
>>> to be a driver or config issue.
>>>
>>> Matthew
>>>       
>> I think  you are out of luck as yet. according to
>> http://wiki.freebsd.org/WakeOnLan
>> grep -l IFCAP_WOL /usr/src/sys/dev/*/*.c
>> should get a list of drivers that support WOL.
>>
>> 16:28:19 <~>)
>> [jhary@crab] 0 $ grep -l IFCAP_WOL /usr/src/sys/dev/*/*.c
>> /usr/src/sys/dev/ae/if_ae.c
>> /usr/src/sys/dev/age/if_age.c
>> /usr/src/sys/dev/alc/if_alc.c
>> /usr/src/sys/dev/ale/if_ale.c
>> /usr/src/sys/dev/fxp/if_fxp.c
>> /usr/src/sys/dev/jme/if_jme.c
>> /usr/src/sys/dev/nge/if_nge.c
>> /usr/src/sys/dev/re/if_re.c
>> /usr/src/sys/dev/stge/if_stge.c
>> /usr/src/sys/dev/txp/if_txp.c
>> /usr/src/sys/dev/vr/if_vr.c
>> (16:28:21 <~>)
>> [jhary@crab] 0 $ uname -r
>> 7.2-STABLE
>>
>> The Pro/1000 driver is if_em (or if_igb) So i think you are out of luck
>> on 7.x
>>     
>
> Vince is correct, the e1000 (if_em/igb) driver does not support WOL, yet.
>
> Chris
>   
Yes, but I'm trying to use Intel's driver at this point (since the stock 
7.2R em driver, as stated, does not support WoL yet):

http://downloadcenter.intel.com/filter_results.aspx?strTypes=all&ProductID=1938&OSFullName=FreeBSD*&lang=eng&strOSs=52&submit=Go!

And it does appear to offer support for WoL.  They (Intel) have 
functions in their if_em.c source file that sets up the WoL.  However, 
there is no IFCAP_WOL define in Intel's code, so maybe it does not 
interface with ifconfig correctly at this point?  I don't know.  I was 
hoping to get some pointers on where to look or how to tell.  Also, I'm 
not opposed to adding the WoL support - I'm not too bad in C - I've just 
never written a FreeBSD device driver and the excellent post by Stefan 
Sperling (referenced from the WoL wiki) seems to be too far out of date.

The wiki itself states: "Note that the obsolete ioctl-based 
configuration approach is discussed there, but ifcaps should be used 
instead."

So, not knowing anything about either ioctl-based or ifcaps config, I 
can't find any resources on how to get started in the right direction 
(hence my post to hackers).

Also, if Intel's driver code works, it seems to me that it makes more 
sense to use their code for em devices, no?  Is there a copyright 
problem with that?

Matthew




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A8199B2.30403>