kRiSiS112
January 19th, 2009, 04:04 AM
Hey all,
I'm having some trouble hooking my backend/frontend box up with wake-on-lan. I used the guide here (http://www.mythtv.org/wiki/ACPI_Wakeup) to set up ACPI on the motherboard to automatically wake up from the internal clock to record shows and shutdown again with mythwelcome on becoming idle. This uses "mythshutdown --shutdown" to set the clock's wake up time with /sys/class/rtc/rtc0/wakealarm and an ACPI enable setting on the BIOS.
The problem is getting the darn thing to boot back up on command! Having no wake-on-usb feature in the motherboard to use the remote, I figured my only option is wake-on-lan.
However, shutting down the PC through Linux somehow disables the hardware from accepting the "magic packet." If I turn on the computer and shut it right back down from POST, WOL works with no problem. It's once I get into Linux and shut down that it becomes unresponsive.
I've got ethtool-enabled wol support (I think) on each startup from /etc/rc.local with the command:
ethtool -s eth0 wol g
I don't know if it's relevant but when I use hibernate it has the same effect and when I use standby I can get my PC to wake up from suspension with the remote, but when waking up from either standby or hibernate, the system looks like it's waking but hangs on a black screen.
Much appreciation goes out to the helpful gurus out there who can help. :popcorn:
I'm having some trouble hooking my backend/frontend box up with wake-on-lan. I used the guide here (http://www.mythtv.org/wiki/ACPI_Wakeup) to set up ACPI on the motherboard to automatically wake up from the internal clock to record shows and shutdown again with mythwelcome on becoming idle. This uses "mythshutdown --shutdown" to set the clock's wake up time with /sys/class/rtc/rtc0/wakealarm and an ACPI enable setting on the BIOS.
The problem is getting the darn thing to boot back up on command! Having no wake-on-usb feature in the motherboard to use the remote, I figured my only option is wake-on-lan.
However, shutting down the PC through Linux somehow disables the hardware from accepting the "magic packet." If I turn on the computer and shut it right back down from POST, WOL works with no problem. It's once I get into Linux and shut down that it becomes unresponsive.
I've got ethtool-enabled wol support (I think) on each startup from /etc/rc.local with the command:
ethtool -s eth0 wol g
I don't know if it's relevant but when I use hibernate it has the same effect and when I use standby I can get my PC to wake up from suspension with the remote, but when waking up from either standby or hibernate, the system looks like it's waking but hangs on a black screen.
Much appreciation goes out to the helpful gurus out there who can help. :popcorn: