On 08/30/12 10:41, Stefan Sperling wrote:
On Wed, Aug 29, 2012 at 07:53:54AM -0700, russell wrote:
finally even though it did not work out for me. ( my nics were
nfe(4) which has no WOL bits in OBSD, I blame nvidia, those
secretive assholes.)
Yes, but they cannot hide their secrets forever ;)
The nfe driver already knows the which register to poke, and in fact
it currently attempts to enable WOL by default. However, it always
shuts down the receive engine when the interface goes down which
prevents wol from working.
The diff below disables wol by default and makes it configurable.
Works for me with:
nfe0 at pci0 dev 5 function 0 "NVIDIA nForce3 LAN" rev 0xa2: apic 1 int 9,
address 00:11:d8:90:b3:56
rlphy0 at nfe0 phy 1: IP101 10/100 PHY, rev. 4
Can you please test if this works for you, too?
<snip diff>
Very cool, like Christmas came early this year.
Sorry for the wait, caught me with my metaphorical trousers down
much to my shame I did not have a build environment set up.
I can now confirm the patch does work.(I tested with -current)
before:
nfe0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
hwfeatures=37<CSUM_IPv4,CSUM_TCPv4,CSUM_UDPv4,VLAN_MTU,VLAN_HWTAGGING>
lladdr 00:e0:81:77:e8:78
priority: 0
groups: netboot egress
media: Ethernet autoselect (1000baseT full-duplex)
status: active
inet 192.168.16.11 netmask 0xffffff00 broadcast 192.168.16.255
after:
nfe0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
hwfeatures=8037<CSUM_IPv4,CSUM_TCPv4,CSUM_UDPv4,VLAN_MTU,VLAN_HWTAGGING,WOL>
lladdr 00:e0:81:77:e8:78
priority: 0
groups: netboot egress
media: Ethernet autoselect (1000baseT full-duplex)
status: active
inet 192.168.16.11 netmask 0xffffff00 broadcast 192.168.16.255
I can set and disable the WOL flag with wol and -wol
When set, i can turn off machine and turn it back on with arp -W
This is great,
Thank you very much.
