[vortex] 3c905B WOL troubleshooting

Martin d'Anjou point14 at magma.ca
Sun May 23 09:57:07 PDT 2004


Hello,

I have a 3c905B installed on the motherboard of my Optiplex, and I cannot get 
wake on lan (wol) to work. Assuming I have two machines, the server which I want 
to put to sleep, and the client which I use to wake up the server. I have the 
following lilo file on the server:

image=/boot/kernel-2.4.25-gentoo-r2.1
    label=Gentoo_ACPI
    read-only
    root=/dev/hda5
    append="acpi=off apm=off enable_wol=1"

Note that I tried various combinations of acpi and apm without success. Is 
enable_wol correctly set (I tried both 1 and 0)? I read the notes about it say 
enable_wol=N1,N2,N3,..., but what are actually these N's and what values should 
I put there?

Also the server is showing:

0000:00:11.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] 
(rev 24)
         Subsystem: Dell Computer Corporation 3C905B Fast Etherlink XL 10/100
         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- 
Stepping- SERR+ FastB2B-
         Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
         Latency: 64 (2500ns min, 2500ns max), cache line size 08
         Interrupt: pin A routed to IRQ 11
         Region 0: I/O ports at dc00 [size=128]
         Region 1: Memory at ff000000 (32-bit, non-prefetchable) [size=128]
         Expansion ROM at fb000000 [disabled] [size=128K]
         Capabilities: [dc] Power Management version 1
                 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-


The Status says D0. I read that it should be D3 for wol to function, so I use 
pci-config:

# ./pci-config -#17 -S
pci-config.c:v2.04a 8/14/2003 Donald Becker (becker at scyld.com)
  http://www.scyld.com/diag/index.html
#

But the status does not change to D3.

Lastly, I shutdown the server (shutdown -h -t 0 now). After it is off, I send a 
eth wake frame from the client on the same ethernet:
# ./ether-wake 00:b0:d0:43:ff:b5
# /sbin/arp -a
tux.homenetwork (192.168.0.16) at 00:B0:D0:43:FF:B5 [ether] on eth0

The server is sleeping and is there, but it won't wakeup. The lights flicker on 
the switch, but don't flicker on the ethernet card receiving the wake up frame 
(the green is on solid).

Can someone help?

Thanks in advance
Martin



More information about the vortex mailing list