no WoL after installing Fedora Core 5

[DarkVolli]

hello,
I have installed Fedora Core 5 a few days ago on my server and everything works fine, but only wakeonlan is still not working. Also with Fedora 5 the link-led on my router is off. With Fedora Core 4 and Windows XP the link-led is on and I can wake up the Server with ether-wake. I have a Intel EtherExpress 1000 and with ethtool I get this:

Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: umbg
Wake-on: g
Current message level: 0x00000007 (7)
Link detected: yes

this seems ok. So what can i do? In my opinion this cant be a hardwareerror, because with Fedora 4 and XP I get the link-led on. Are there some changes of the default values from Fedora 4 to Fedora 5? How can I fix it? Please help....

cu
DarkVolli

[freddyfish]

Originally Posted by DarkVolli

hello,
I have installed Fedora Core 5 a few days ago on my server and everything works fine, but only wakeonlan is still not working. Also with Fedora 5 the link-led on my router is off. With Fedora Core 4 and Windows XP the link-led is on and I can wake up the Server with ether-wake. I have a Intel EtherExpress 1000 and with ethtool I get this:

Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: umbg
Wake-on: g
Current message level: 0x00000007 (7)
Link detected: yes

this seems ok. So what can i do? In my opinion this cant be a hardwareerror, because with Fedora 4 and XP I get the link-led on. Are there some changes of the default values from Fedora 4 to Fedora 5? How can I fix it? Please help....

cu
DarkVolli

I have a similar problem. I have Intel PRO/1000 GT adapter with similar ethtool values:
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: umbg
Wake-on: g
Current message level: 0x00000007 (7)
Link detected: yes

When powered down, the LEDs on both the NIC and connected switch port are off, and WOL magic packet has no effect. As a test I installed Win98SE on a separate drive, and WOL works perfectly using the exact same hardware (LEDs on both NIC and switch are on when powered down).

I am going to install FC4 on a separate disk to see whether I het the same results as you saw.

I noticed the following:
When booted with Windows and then shut down, the LEDs switch off momentarily as shutdown completes, then come back on.
When doing the same with FC5, they simply go off and stay off.
If the PC power is then turned off and back on, the LEDs come on, but WOL magic packet has no effect.

I really need to fix this -- and I am sure DarkVolli does too. Any help would be appreciated.

I'll post again after I have tried FC4.

[freddyfish]

I installed FC4 and found the same as DarkVolli -- WOL works with FC4 and Win 98 SE but does not work with FC5.

Can anybody help point us to how to fix this for FC5?

[Seve]

Hello:
Has anyone solved this yet ?
Seve

[jcliburn]

I'm using ether-wake from my downstairs FC5 x86_64 machine to wol a Dell Optiplex GX110 upstairs running FC5 i386. I'm not at home right now (on travel until next week), so I can't provide ethtool output, but wol *does* work, at least in my configuration.

[freddyfish]

I now have it working on FC5 -- just needed to update to the latest Intel NIC driver. Now it will WOL from shut down. Next step is to get WOL from suspend2 hibernated state. This is not working so far -- when hibernated, the NIC LED is on, but the WOL magic packet does not rouse the machine. Anybody any ideas how to fix this?

Cheers

[freddyfish]

At last -- Success with WOL from both suspend2 hibernated state and from powered off. I think my problem was the driver version again. Having installed from the Matthias Hensler kernel install rpm, I had of course reverted to the driver version provided by him, based on FC5 distribution. (I'm just learning this stuff!!) Having reinstalled, it now works fine as far as I can see so far.

[DarkVolli]

@freddyfish,
thanks a lot for your investigationes! I will try it out until I have reinstalled FC5.

cu
DarkVolli