[HOWTO] wakeonlan

RayVad · n00b Joined: 10 Nov 2005 Posts: 67 Location: Netherlands

Dun,

What more should there be configured in /etc/conf.d/rc for the NIC except RC_DOWN_INTERFACE="yes" ?
There was no RC_DOWN_INTERFACE= in the rc file here, so i added it.

Will try WOL later.

anigel · Posted: Fri Jan 05, 2007 2:06 pm Post subject:

Yukimura · Posted: Sat Jan 06, 2007 1:53 pm Post subject:

I'm also using forcedeth but I can't even get my PC to wake up.
Maybe I'm doing something wrong but I can't see my mistake.

My ethtool eth0 gives me this:

anigel · Posted: Sat Jan 06, 2007 10:39 pm Post subject:

Wel... Maybe this post can help you ?

If not, I just don't have any idea, sorry.
_________________
Il y a 10 sortes d'individus en ce bas-monde : ceux qui causent binaire, et les autres.

Yukimura · Posted: Sun Jan 07, 2007 12:14 am Post subject:

It seems the problem was in wakeonlan utility. I installed etherwake on my linux router and now it works.

BTW really good how to (simple, and quick to do)

Kind regards.

alex.blackbit · Advocate Joined: 26 Jul 2005 Posts: 2288

i noticed that there is a little tripwire in the WOL thing.
even if the two machines are on the same subnet it can be mandatory to specify the -i option of wakeonlan.
i believe this is the case when the box which is sending the magic packet has multiple network connections, which is the case on my gentoo internet gateway.
in my case

Devport · Guru Joined: 15 Dec 2004 Posts: 361

Is there a way to detect if the system has been started threw wakeonlan ? I only want to start ssh on wakeonlan.

Yukimura · Posted: Mon Apr 16, 2007 5:52 am Post subject:

To check that out, I connect on my machine through ssh.

_________________
Linux registered user #413812

RayVad · n00b Joined: 10 Nov 2005 Posts: 67 Location: Netherlands

OK, got it solved!

I used another NIC again(with WOL cable), not the onboard one, to receive the wol packed (yes, got 2 NIC's because its a VPN server) and only APM, not ACPI!
Well, these are my configs:

Did NOT compile ACPI into kernel 2.6.20-r8, only enabled APM, nothing more!

[*] Power Management support │ │
│ │ [ ] Legacy Power Management API (DEPRECATED) │ │
│ │ [ ] Power Management Debug Support │ │
│ │ [ ] Driver model /sys/devices/.../power/state files (DEPRECATED│ │
│ │ [ ] Software Suspend │ │
│ │ ACPI (Advanced Configuration and Power Interface) Support --│ │
│ │ APM (Advanced Power Management) BIOS Support ---> │ │
│ │ CPU Frequency scaling ---> │ │
│ │

[ ] ACPI Support

<*> APM (Advanced Power Management) BIOS support │ │
│ │ [ ] Ignore USER SUSPEND │ │
│ │ [ ] Enable PM at boot time │ │
│ │ [ ] Make CPU Idle calls when idle │ │
│ │ [ ] Enable console blanking using APM │ │
│ │ [ ] RTC stores time in GMT │ │
│ │ [ ] Allow interrupts during APM BIOS calls │ │
│ │ [ ] Use real mode APM BIOS call to power off

Compiled the drivers of the NIC as module in the kernel.

/etc/conf.d/rc: RC_DOWN_INTERFACE="yes"
/etc/init.d/shutdown.sh: Just default!

Installed ethtool to set the WOL parameter on g

Added "ethtool -s eth0 wol g" to /etc/conf.d/local.start and, to be sure, to /etc/conf.d/local.stop

And Voila! it works!!!

Okay, some new issue.... to be fixed later... it starts spontanious now as it happens 3 times. Strange...but WOL works and will find out about this spontanious boot later and report here.