WOL with sk98lin driver
 

Hi!

Does anybody get onboard Marvell 8053 (sk98lin driver ver.8.28.1.3) working with Wake-On-Lan feature after system shuts down (halt).
After system halt onboard Gigabit also shuts down completely while with ethtool wol function is enabled per default, also in BIOS everything that corresponds to WOL is enabled.
P.S. With WinXP there is no problem.

Any suggestions?

Thank you.

Maybe some sort of power management problem,
For example, if you use ACPI, try using APM or if you use APM,
try to use ACPI

There is an updated version of the syskonnect gigabit ethernet driver for linux built into the kernel now, called skge. It is supposed to support WOL, whereas I dont think the sk98lin driver does.

config SKGE
tristate "New SysKonnect GigaEthernet support (EXPERIMENTAL)"
depends on PCI && EXPERIMENTAL
select CRC32
---help---
This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
and related Gigabit Ethernet adapters. It is a new smaller driver
driver with better performance and more complete ethtool support.

It does not support the link failover and network management
features that "portable" vendor supplied sk98lin driver does.

it says its experimental, so you may need to enable experimental driver options, (right at the beginning of the kernel configure questions if I remember correctly), but it works fine for me, I changed over from the sk98lin last time i recompiled with 2.6.13.1.

Maybe worth looking into anyway.

tobyl

edit I have not tried the wake on lan feature, but have read that it is included

I am using Ubuntu 5.10 on a server, trying to get wol to work.
ethtool tells me wake on magic packet is on (Wake-up: g), but linux switches the nic off on 'halt'
Has anyone a solution for this problem?

I altered /etc/init.d/halt last line and removed the -I option, as it turns off the nic, but it didn't affect my problem at all....
Thanks for reply

Ps: bootloader is grub, kernel is a 2.6.12-9, i use the default kernel

are you connected directly to the box or via a switch/hub ?

The 'server' ;-) is connected to a wlinx router (smd barricade). this may not be the problem, as wake on lan works under win xp.