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 trying to wakeup a computer with the command etherwake <MAC>, but it doesn't work. The computer goes dow, maintains its ethernet card on (leds blinking), but when I send the wakeup packet, it does not wakeup. Instead, a few minutes later, it does wakeup by itself. It happens even if I do not send any magickpacket at all.
The motherboard I am using is the Aopen i855GMEm-LFS, with Gentoo intalled. See some information below:
Thank you for the reply. Actually, I had already read that thread.
The post 05-24-06, 05:17 PM from SlackTRAXX helped. I started there, installing the sk98lin driver, the version that came with the kernel did not support wol. Then I moved to skge. It supported, but kept not waking up and waking alone after a few minutes. After that, I downloaded the newer version from the marvell website. When I compiled the driver, I got some errors like USE_SYNC_TX_QUEUE not defined. To solve this, I used the patch in http :// linux . derkeiler . com / Mailing-Lists / Kernel / 2006-02 / msg04398 . html. With this new driver, I tried both sk98lin and skge, both supported wol, but none worked. The problem persists. The machine wakes up alone, and not with the magic packet.
Here are some update to my problem:
I solved it partially. I realized that I can wake up the machine with wol packets, but only if it was put in Suspend-to-Ram. In suspend-to-disk or shutdown, the ethernet card continues blinking, but wol doesn't work.
I disabled one of the ethernet interfaces in BIOS and this stoped with the problem of starting up the machine automatically after 4 minutes without the Wol packet. But then, I don know why, maybe I have missed some steps trying everything to solve the problem, I re-enabled the second interface and the automatic wake up disappeared.
Another thing I can't explain is that, amazingly, the power consumption in suspend-to-ram is 5W, while it is 9W in suspend to disk or normal shutdown. One observation that may help to explain is that in suspend to ram the ethernet interface leds stay lit, but not blinking, while it seems to show much more activity in the other sleep states, because it blinks a lot.
One question: Is it possible that, after disabling and re-enabling one interface, something changed, for example, IRQs assignments, and that changed everything?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.