Hi everyone! I'm having trouble to set up my Linux box in order to wake it up via LAN.

I have an ASUS P4P800 motherboard with an onboard 3Com 3C940 nic. It does support WOL, given that when I shutdown my windows XP I can wake my machine up from another one inside the network. I can see that the LED of my nic stays on after Windows shutdown, but it does not in Linux (and it won't respond to Magic Packets to wake it up).

I'm using the sk98lin driver, version 6.23. The distribution: Slackware 10.2 running with a 2.6.15 kernel.

I tried ethtool to set the wol feature (ethtool -s eth0 wol g), but it gives me "Cannot get current wake-on-lan settings: Operation not supported. Not setting wol."

This is what ethtool eth0 shows me:

Besides this, the nic is working fine and ifconfig works like it should.

I've tried commenting out this lines in /etc/rc.d/rc.0:

and the nic had its LED on after I powered the machine down... however, it didn't wake up with any Magic Packet I sent.

I think the main problem here is that my sk98lin driver is the one who's not letting me add the "listen" flag in the nic (when I execute ethtool -s eth0 wol g) and that's what prevents the nic to accept the wake on lan signals to wake it up.

I've tried to find a newer version of that driver, but just couldn't... the guys at www.skd.de (former www.syskonnect.com) have completely erased it from their website, and I can't find it anywhere... I know they released a newer version, probably in 2005... but just couldn't find it.

Still, I'm not sure whether the sk98lin is really the problem, or there is something else.

What do you say, guys?

Sk98lin is OK on my Fedora 1 and 4.

The LED turns off because LINUX do so.

Is there any 3c940 driver on your Slackware, have you try it?
3c940 also works on Fedora 4.

There should be no problem with kernel 2.6.15 .
WOL should be triggered on machine that support +5v standby state.
The lamp on HUB supposed to be on with at least 2 machine to support WOL.

I dunno if the driver WOL capable.

Yes, but... that's the problem, I don't want it to turn itself off.

Hmmm, I think the only driver that works with this nic is the sk98lin (in any distribution). Are you using another one? Please let me know.

I don't quite understand this. Yes, my hardware can do it, because I do it in Windows. I don't know if the driver is WOL capable, as you do

Does anybody at least have a valid link to a newer version of the driver which supports wake on lan? I think that's the main problem.

3com 3C940 GIGAbit Marvell 10-100-1000 is the deafult driver in Fedora4.
I used SK98lin in fedora 1 ,also works on FEDORA 4.
My Kernel is 2.6-11.
I meant I do not know if the driver is WOL compatible.

[Is it possible to have 3c940 copied to the slackware?(it'll be alot of trick I think)]

I did WOL on windows years ago with PCI card on wich WOL cable plug into the motherboard.

Are you sending magic packet from MSwindow?What is you other machine&LANCARD?
Peer to Peer or HUB connection that you have there?

I suggest that you use FEDORA 4 or maybe 5 for you machine,since the driver is already there&suitable for your mainboard.

Hmmm, I do not know if there's a way to get that fedora driver (3C940 GIGAbit Marvell 10-100-1000)

The magic packet is sent OK, because I can wake my machine up when it halted from Windows.

I really want to keep my Slackware, I wouldn't change it for just this driver WOL thing

Does anybody have a link to a driver that actually can deal with both my 3c940 and WOL?

It would be a different parameter if you wake it up from LINUX/others than.

I woke it up from INTEL plug-in software.

Hmmm, I don't think that a Magic Packet changes from one OS to another. It has to follow the standard Magic Packet structure, or else the interface won't pick it up. The packet's structure is FF FF FF FF FF FF followed by sixteen repetitions of the target's MAC address.


Anyways, I wake it up from this website: http://www.depicus.com/wake-on-lan/woli.aspx (I port forwarded to a broadcast private IP, and, as I've said, it works when my computer's been powered off from Windows.


I've managed to find out that sk98lin v7 is out there (and it does support WOL). It seems like the guys at sysconnekt did release it, but it was available for public for a very shotr time, and I just can't find it!

I would try to wake LINUX from XP soon enough.

As I remember the WOL on window, server and client must've all the INTEL-soft installed.

I imagine that the software trigger the LANCARD before it goes to WOL state.
Does LINUX do that? (I don't really know)
____________________________________________
# Bring down the networking system:
if [ -x /etc/rc.d/rc.inet1 ]; then
. /etc/rc.d/rc.inet1 stop
fi
____________________________________________
Is that command bring the LANCARD to WOL state? (don't know either)
I think you have to got the software installed in LINUX also just to make sure.

There's a LANCARD software seems to come along with your motherboard on purchasing. There could be a 3comLOM linux driver inside.

So you're insist on looking/updating the sk98lin for your slackware, I hope you'll got it soon.

Wish this could be available soon

http://sourceforge.net/projects/pywol

BTW you can have Dual Boot OS slackware & fedora in your single Hardisk.

I managed 3 system (LINUX&window)in one HDD before I know this LQ page, it's splendid.

Thank you for your help Bobymc!

I'll tell you what I've been doing:

First, I've read this thread: http://www.linuxquestions.org/questi...d.php?t=199473

From there... I could assume that the latest sk98lin driver, 7.09, would allow me to use the ethtool correctly. So.. I started looking for that driver like crazy, finding links like these ones:

http://lists.centos.org/pipermail/ce...er/043886.html
http://oss.sgi.com/archives/netdev/2.../msg00958.html

That damn driver is impossible to find! Well... so looking around I found out that there is another driver that kind of replaces the sk98lin. It's called skge, and it comes with the 2.6 kernel... as an experimental driver. I activated the code maturity option to see experimental things from the make menuconfig, and... voila! There it was.

I installed skge as a module, removing sk98lin. I've done this by selecting it at the menuconfig and then doing a "make modules" and "make modules_install". Then I took out sk98lin with "modprobe -r sk98lin" and inserted skge with "modprobe /usr/src/linux-2.6.15.6/drivers/net/skge.ko" (I don't know how to do this in any other way, if anyone knows how to do it in a more... direct way, please tell me.

Now I'm browsing the Internet without any problem, so the driver works fine (as far as I know by now).

ethtool -s eth0 wol g worked fine, and... I still don't know if WOL will work, but I'll try as soon as I finish other things I have over here...

Now, if wol works... I will stay with skge for good, and the only thing that concerns me about that is that it's experimental... BUT, i've found this mail:

http://www.ussg.iu.edu/hypermail/lin...02.2/0544.html

I don't quite understand what do I have to do to 'upgrade' the skge driver that I have, in order to take it out of the experimental state (the author of the driver says there that it's no longer experimental after that patch, anyone knows how to do this?

What I know is something like;

make
make install
make load
insmod
modprobe

to compile your 'skge' module to your slackware.

I was just install Mandriva,FEORA,4,5 in a Hdrive, so I'm ready to experiment the LINUX on WOL.

OK I got the OS run on TRIPLE SYSTEM booting.

and dig som info;

Fedora 5

driver: skge
version: 1.3
firmware-version: N/A
bus-info: 0000:02:05.0
[root@localhost ~]#

MANDRIVA 2006

driver: sk98lin
version: 8.23.1.3 (01)
firmware-version: N/A
bus-info: 0000:02:05.0
[root@localhost ~]#

also my onboard LAN module;

02:05.0 Ethernet controller: 3Com Corporation 3c940 10/100/1000Base-T [Marvell]
(rev 12)
Subsystem: ASUSTeK Computer Inc. A7V600/P4P800/K8V motherboard
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 17
Memory at feaf8000 (32-bit, non-prefetchable) [size=16K]
I/O ports at d800 [size=256]
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data

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: g
Wake-on: g
Current message level: 0x00000037 (55)
Link detected: yes

with this kind of hardware , I don't think there's problem to bring the LAN
to WOL state.

What do ya have in mind?

Thanks Boby, but with the skge experimental driver I'm having the same performance than with sk98lin and WOL works just fine!!! I made it! :P

Hope this thread helps out many other people with the same problem. Bye!

BTW: I'v made another thread now, asking how to get my driver patched for it to be out of experimental state (http://www.linuxquestions.org/questi....php?p=2268569)