Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am using an Asus P4P800 Motherboard, with an onboard 3c940 Gigabit LAN Chipset. Now I want it, to start up using WakeOnLan. It works fine, if I shutdown from Windoze, but doesnot when I do so from Mandrake 10.0c. When I commented out the lines from the init-script halting the network-devices the LEDs on the Plug kept alive (before they went black; from Windoze they also kept alive, so I guess this is minimum to get it working), but this was not enough to wake the PC up.
The Card seems to be running with the sk98lin-Module. In its sources I didn't find any line about wake on lan, and other module parameters like "enable_wol=1" didn't help.
So is there anyway to get it working? Maybe another module, or a new alpha version of sk98lin?
try "modinfo -p [sk98lin-module]" to get parameters the module is able to understand. also type "lspci -v" to see what powermodes are availible for that device.
for further information take a look at the source located in
/usr/src/[kernelsource]/drivers/net.. ,
also read the infos about powermanagement (under linux - it isn't quite ready yet and i also had lot of troubles setting up pm right).
"modinfo -p sk98lin" does not return anything at all (but it works, cause if I type something else instead of sk98lin, I get an error in return).
"lspci -v" returns the following related to the controller:
02:05.0 Ethernet controller: 3Com Corporation 3c940 1000Base? (rev 12)
Subsystem: Asustek Computer, Inc.: Unknown device 80eb
Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 22
Memory at feafc000 (32-bit, non-prefetchable) [size=16K]
I/O ports at d800 [size=256]
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
In the driver sources there is nothing about wake on lan, so probably the installed version does not support it. :-( Maybe there is another one, or I can use another driver? Or is it that difficult, to tell a card, to switch to standby on shutdown? It cannot be more than a simple flag to set, does it?
i don't think the driverversion is the prob. it sure will know wol IF the driver supports it. i always had troubles with things in the linux powermanagement. i think it's not quite finished.
it would be nice to know somebody got it working.
since i don't ever used it i'm not much of help here.
anyway. are u using acpi? and is your network-card-irq routed through it? (see dmesg | grep ACPI).
i have also heard something 'bout "magic packets" a network interface needs to wake up?
I am trying to route the Magic Packet from outside through my NAT-Router, but since I am not sure, this is working correctly, I also got a laptop sending the package locally. After shutdown from windows both methods work fine.
well, that looks quite fine -i can't see anything that's wrong.
i suggest searching the net for more information 'bout wol under linux.
i just don't know what would solve this prob. you may try to get debuging output from your kernel acpi funktion - maybe you'll need to recompile your kernel and i think this will be a good idea anyway. try with the sk98 as module and compiled in. you should also try some newer version of the kernel like 2.6.5 or even .6 or .7.
Did you find anything ?
I am trying to make work wol under linux and I can't.
When I shutdown the PC under windows I can awake it but when I shutdown under Linux i can't awake it
Still on it, but without any success. Currently I am running the 2.6.8rc2-Kernel, but there were no changes to the sk98lin-Module, wich fits to my onboard 3com NIC. The sk98lin module seems to be the standard driver for a lot of other controllers (e.g. found one from D-Link while googling), but when I looked in the sourcecode there where no comments about WOL, so I guess its simply not implemented yet. If it is, could anyone please tell me, what do I have to do different?
I don't think the previous sk98lin driver supported wol. At least, if you issued an "ethtool -s eth0 wol g" to enable it, you just got an error about the operation is not supported.
The good news is that for the sk98lin driver from Syskonnect, there is a new driver released (v7) that now supports the wol setting in ethertool.
Installation is pretty easy. You just need the kernel source for the version you are running installed in /usr/src. Most likely, you already have it installed as this happens with most distros. There is an install.sh script and, if you use the Basic option, it pretty much installs itself for you.
Now the command "ethtool -s eth0 wol g" works for me. You can issue an "ethtool eth0" and see the card settings.
My next problem is that the Magic Packet is still not waking up the 3C940 nic built into my Asus P4C800 Deluxe motherboard. I have the latest BIOS and have the BIOS options enabled for 1) Onboard NIC, 2) NIC's boot ROM, and 3) Wake on PCI Event in the Power Management section of the BIOS.
I boot to Linux, issue the "ethtool -s eth0 wol g" command, do a "shutdown -h now", and then try to issue the Wake on LAN Magic Packet from both a Linux box (using wol) and a Windows box using the AMD PCnet Magic Packet utility. Neither work for me.
Keep us updated on your progress. I am not sure if I am just the only one with this problem now.
I will check this out, if i find the time, maybe tonite. I don't think that sources should be a prob, since I am using gentoo now... I would really be glad, if this works.
Using windows, I just had to change a setting in the device-manager, something with "Device is allowed to wake up PC from stand-by." As I remember, it was set on, and I had to switch it of, to get it working. After this, I should it down using the regular windows way. The LEDs on the LAN-Plug kept on then (before this checkbox change they didn't), and it woke up fine. After shutting down from Linux before they went of after power-down; I could "force" them on with disabling the eth-down in the init-configs, but that didn't make him wake up on lan (but I neither expect this that way).
I cannot try windows again, because it ain't on my HD anymore... ;-)
That is fun, indeed. Module compiled and installed fine so far (BTW one of the best installers since long ago). Since it auto-modprobes the modules when done, the device (the link LEDs) came up immediatly. Ethtool tells me, that everything is ok, and it even was already configured to wake up on "g". After I shut down, the LEDs kept alive, so I guess it could have even wake up now.
But after adding the module to modules.autoload, the system now knows of the existence of this device at boot time, and, as you would expect from a clean system, it remembers to switch everything of after finishing - so the LEDs went off exaclty with "shutting down eth1" in the console.
Some tests confirmed, that ethtool does configure the card itself for WOL, but does not prevent the system from shutting it down. So I guess, I still have to take hand on the runlevel-scripts as I did before on mandrake to get this working; or find another tool, that takes care of this more cleanly.
The only problem, why I am not continuing here, is that I forgot my laptop at work, so I do not find any magic packet somewhere around here... ;-)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
