Re: remote shutdown

On Thu, 14 Aug 2003 09:51:51 +0200
Erik Thiele <[email protected]> wrote:

This Email is Sent to 2 mailinglists:
- LTSP (www.ltsp.org) Linux Terminal Server Project
- Vortex (www.scyld.com) Vortex 3com linux drivers

> i wake up my terminal with WOL (wake on lan).
> but how do i put it to sleep again?
> (these terminals are public access, autologin with gdm, single fullscreen application)
> 
> i'd like to be able to call an "init 0" or whatever shuts those machines down,
> remotely by a cronjob on the server.
> 
> the machines must shutdown with apm!

ok. i now compiled a kernel with acpi or apm. both work fine.
i use runlevel 3 for terminal only operation.

the problem is:

in the bios i activate wake on pci feature. then i turn masterpower off.
after turning masterpower on, the nic gets active and the computer stays
powered down. i now use ether-wake to power it up. so this worked !

after powering it down by either the power button or poweroff -f,
either apm or acpi, always same result:

computer is off, but nic is active. but it won't react to WOL packages
until I mainpowerswitch it off and on again. so there is a difference
between powered off and powered off :)

i found the enable_wol=1 option for my 3c59x card in the kernel drivers.

i tried to figure out, how to pass it to the kernel.
i inspected linuxrc from your initrd and read about ${NICOPT}.
i tried to pass enable_wol=1 by adding NICOPT=enable_wol=1 to the kernel parameters list.
i tried to add the kernel parameters list by DHCP option 129, which did not work.
how can this be done? you could create an example with vga=ask and document it somewhere.
your documentation sais that additional kernel parameters can be passed, but not how.

the mknbi-linux docu also doesn't tell how the option-129 stuff really works.
it is hidden in cryptic vendor tags documentation that i don't understand :)
it sais that the option-129 only works if option-128 is correctly used,
but it is not documented anywhere how this is done!!! please forward this to
etherboot mknbi staff. . .

ok so then i patched your buildk initrd building toolkit and added NICOPT=enable_wol=1
to the $MKNBI call.

now it worked!!! it passed the option to the kernel.
it sais:
linuxrc: Installing 3c59x driver
modprobe 3c59x enable_wol=1
/sbin/insmod /lib/modu...../3c59x.o enable_wol=1
02:0b.0: 3Com PCI 3c905C Tornado

but all poweroff variants result in unability to ether-wake the machine.


PLEASE anyone enlighten me!

i have an ASUS P4B533 Mainboard
kernel version 2.4.21
i am using the 3c59x driver contained in that kernel.

cu
erik


-- 
Erik Thiele


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net