Comment on Is the Intel N100 a better option than high-end ARM RK3588 boards at the moment?parentComments−Brybry2yWeirdly I've found with some (x86/x64) machines that their Wake-on-LAN doesn't work after a power loss.But could probably use a similar idea to signal the power button with a pi or esp32?−amelius2yBut could probably use a similar idea to signal the power button with a pi or esp32?I thought of that but it's not worth it, since these N100 systems cost around $150.Perhaps a better solution is with a 555 timer, that turns on the machine when the led goes off.−zh32yOn linux I find it's usually necessary to enable WoL on boot with 'ethtool -s eth0 wol g' (you can check the current state of all most wakeup stuff with 'cat /proc/acpi/wakeup').−doubled1122yI have a couple of Ryzen machines like that.They need a power button press to power on the NIC. As long as WoL is enabled everywhere, the NIC will stay on until they lose power again.−hattmall2yA switchbot might also be an option.−kijin2yYou don't even need to press a physical switch. Anything that can short a jumper on the motherboard would be enough.
Comments
Weirdly I've found with some (x86/x64) machines that their Wake-on-LAN doesn't work after a power loss.
But could probably use a similar idea to signal the power button with a pi or esp32?
I thought of that but it's not worth it, since these N100 systems cost around $150.
Perhaps a better solution is with a 555 timer, that turns on the machine when the led goes off.
On linux I find it's usually necessary to enable WoL on boot with 'ethtool -s eth0 wol g' (you can check the current state of all most wakeup stuff with 'cat /proc/acpi/wakeup').
I have a couple of Ryzen machines like that.
They need a power button press to power on the NIC. As long as WoL is enabled everywhere, the NIC will stay on until they lose power again.
A switchbot might also be an option.
You don't even need to press a physical switch. Anything that can short a jumper on the motherboard would be enough.