[vortex] WOL on newer kernels

[Nenad Antonic]

On Tue, 3 Feb 2004, Donald Becker wrote:

> My driver does not implement the "enable_WOL" module parameter -- it
> always puts the NICs (chips with 'CapPwrMgmt') into WOL mode when the
> **module is removed**.

This answer allowed us to shorten the list of options.
I took ftp://scyld.com/pub/network/netdrivers-3.5.tgz
(Aug 25 23:55), and compiled with 2.4.23 kernel headers
the 3c59x driver (using gcc-3.3).

After loading it, the network works. 
pci-scan.c:v1.11 8/31/2002  Donald Becker <becker@scyld.com> http://www.scyld.com/linux/drivers.html
3c59x.c:v0.99Za 4/17/2003 Donald Becker, becker@scyld.com
  http://www.scyld.com/network/vortex.html
eth0: 3Com 3c905C Tornado at 0x2000,  00:e0:81:23:25:c3, IRQ 19
  8K buffer 5:3 Rx:Tx split, autoselect/Autonegotiate interface.
  MII transceiver found at address 24, status 782d.
  Using bus-master transmits and whole-frame receives.
        Interrupt: pin D routed to IRQ 19
        Region 0: Memory at f5000000 (32-bit, non-prefetchable) [size=4K]
Of course, lspci gives 
                Status: D0 PME-Enable- DSel=0 DScale=2 PME-

After performing rmmod 3c59x (and leaving pci-scan!)
                Status: D3 PME-Enable+ DSel=0 DScale=2 PME-

However, shutdown -h now halts the system, and sending the magic
packet 
		ether-wake 00:e0:81:23:25:c3
does nothing, but blinks the NICs led.

If I do not enable ACPI (which I usually do via append="acpi=force" 
in lilo), no success.

I have tried the same on another system, with a PCI card, repeating
all steps including the compilation. Both NICs show D3, but the
magic packet makes no magic.

What am I doing wrong? What else should I try?

Thanks
- Nenad Antonic.