Having failed to get hibernation working (see recent posts about Secure Boot getting in the way), I tried to fall back to suspending the system overnight. That works of course.
What doesn't work is waking it up automatically. If the RTC can wake the system from hibernation, why can't it wake it from suspension? I don't want to have to be in front of the system to wake it up.
poc
On Sat, Aug 24, 2024, at 4:17 AM, Patrick O'Callaghan wrote:
Having failed to get hibernation working (see recent posts about Secure Boot getting in the way), I tried to fall back to suspending the system overnight. That works of course.
What doesn't work is waking it up automatically. If the RTC can wake the system from hibernation, why can't it wake it from suspension? I don't want to have to be in front of the system to wake it up.
I found that RTC wakeup did work to wake from suspend, but I also had a number of issues with it which I can't really remember right now. My solution was to utilize a "Magic Packet" ping from my Raspberry Pi. That seems to "just work" so far. This allows me to wake up the system at night once a month for "Smart" tests and "MD" checks. Obviously you need another system running to use this method, so it won't work for everybody. I added the Pi long ago as a way to keep a 24/7 system running that does not take much power.
On Sat, 2024-08-24 at 08:15 -0700, Doug Herr wrote:
On Sat, Aug 24, 2024, at 4:17 AM, Patrick O'Callaghan wrote:
Having failed to get hibernation working (see recent posts about Secure Boot getting in the way), I tried to fall back to suspending the system overnight. That works of course.
What doesn't work is waking it up automatically. If the RTC can wake the system from hibernation, why can't it wake it from suspension? I don't want to have to be in front of the system to wake it up.
I found that RTC wakeup did work to wake from suspend, but I also had a number of issues with it which I can't really remember right now. My solution was to utilize a "Magic Packet" ping from my Raspberry Pi. That seems to "just work" so far. This allows me to wake up the system at night once a month for "Smart" tests and "MD" checks. Obviously you need another system running to use this method, so it won't work for everybody. I added the Pi long ago as a way to keep a 24/7 system running that does not take much power.
I have an Android app that can supposedly do that, so I might try it. I think you have to enable the magic packet in UEFI if I'm not mistaken.
poc
On Sat, Aug 24, 2024, at 9:25 AM, Patrick O'Callaghan wrote:
On Sat, 2024-08-24 at 08:15 -0700, Doug Herr wrote:
I found that RTC wakeup did work to wake from suspend, but I also had a number of issues with it which I can't really remember right now. My solution was to utilize a "Magic Packet" ping from my Raspberry Pi. That seems to "just work" so far. This allows me to wake up the system at night once a month for "Smart" tests and "MD" checks. Obviously you need another system running to use this method, so it won't work for everybody. I added the Pi long ago as a way to keep a 24/7 system running that does not take much power.
I have an Android app that can supposedly do that, so I might try it. I think you have to enable the magic packet in UEFI if I'm not mistaken.
Since that is generally over WiFi I was curious. Yup, using "LanDroid" I was able to wake my system. As to the UEFI point, I am pretty sure I had to enable this via the bios. I have a UEFI system that is set to use "Legacy BIOS" mode.
I also enabled the "Magic" check box for the Network Manager config for my Ethernet port.
On 8/24/24 09:25, Patrick O'Callaghan wrote:
On Sat, 2024-08-24 at 08:15 -0700, Doug Herr wrote:
On Sat, Aug 24, 2024, at 4:17 AM, Patrick O'Callaghan wrote:
Having failed to get hibernation working (see recent posts about Secure Boot getting in the way), I tried to fall back to suspending the system overnight. That works of course.
What doesn't work is waking it up automatically. If the RTC can wake the system from hibernation, why can't it wake it from suspension? I don't want to have to be in front of the system to wake it up.
I found that RTC wakeup did work to wake from suspend, but I also had a number of issues with it which I can't really remember right now. My solution was to utilize a "Magic Packet" ping from my Raspberry Pi. That seems to "just work" so far. This allows me to wake up the system at night once a month for "Smart" tests and "MD" checks. Obviously you need another system running to use this method, so it won't work for everybody. I added the Pi long ago as a way to keep a 24/7 system running that does not take much power.
I have an Android app that can supposedly do that, so I might try it. I think you have to enable the magic packet in UEFI if I'm not mistaken.
I don't *think* bios or uefi control that.
ethtool wol [pumbag]
Check the man page. When I was testing it I used "g".
:m
On Sat, Aug 24, 2024 at 8:18 AM Patrick O'Callaghan pocallaghan@gmail.com wrote:
Having failed to get hibernation working (see recent posts about Secure Boot getting in the way), I tried to fall back to suspending the system overnight. That works of course.
What doesn't work is waking it up automatically. If the RTC can wake the system from hibernation, why can't it wake it from suspension? I don't want to have to be in front of the system to wake it up.
I have used WOL with Fedora Workstation by LAN when I didn't want to go outside to wake-up a suspended box in an outbuilding during sa storm.
Wireless WOL (WWOL) is a recent innovation, so may not be supported on older hardware. Some Fedora systems have issues with WiFI when waking from suspend by keyboard, so I wouldn't expect WWOL to work for those.
On Sat, 2024-08-24 at 12:00 -0700, Mike Wright wrote:
On 8/24/24 09:25, Patrick O'Callaghan wrote:
On Sat, 2024-08-24 at 08:15 -0700, Doug Herr wrote:
On Sat, Aug 24, 2024, at 4:17 AM, Patrick O'Callaghan wrote:
Having failed to get hibernation working (see recent posts about Secure Boot getting in the way), I tried to fall back to suspending the system overnight. That works of course.
What doesn't work is waking it up automatically. If the RTC can wake the system from hibernation, why can't it wake it from suspension? I don't want to have to be in front of the system to wake it up.
I found that RTC wakeup did work to wake from suspend, but I also had a number of issues with it which I can't really remember right now. My solution was to utilize a "Magic Packet" ping from my Raspberry Pi. That seems to "just work" so far. This allows me to wake up the system at night once a month for "Smart" tests and "MD" checks. Obviously you need another system running to use this method, so it won't work for everybody. I added the Pi long ago as a way to keep a 24/7 system running that does not take much power.
I have an Android app that can supposedly do that, so I might try it. I think you have to enable the magic packet in UEFI if I'm not mistaken.
I don't *think* bios or uefi control that.
ethtool wol [pumbag]
Check the man page. When I was testing it I used "g".
Thanks.
poc
On Sat, 2024-08-24 at 16:21 -0300, George N. White III wrote:
On Sat, Aug 24, 2024 at 8:18 AM Patrick O'Callaghan pocallaghan@gmail.com wrote:
Having failed to get hibernation working (see recent posts about Secure Boot getting in the way), I tried to fall back to suspending the system overnight. That works of course.
What doesn't work is waking it up automatically. If the RTC can wake the system from hibernation, why can't it wake it from suspension? I don't want to have to be in front of the system to wake it up.
I have used WOL with Fedora Workstation by LAN when I didn't want to go outside to wake-up a suspended box in an outbuilding during sa storm.
Wireless WOL (WWOL) is a recent innovation, so may not be supported on older hardware. Some Fedora systems have issues with WiFI when waking from suspend by keyboard, so I wouldn't expect WWOL to work for those.
My system has a wired connection, so that shouldn't be an issue.
poc
On Sat, 2024-08-24 at 10:49 -0700, Doug Herr wrote:
On Sat, Aug 24, 2024, at 9:25 AM, Patrick O'Callaghan wrote:
On Sat, 2024-08-24 at 08:15 -0700, Doug Herr wrote:
I found that RTC wakeup did work to wake from suspend, but I also had a number of issues with it which I can't really remember right now. My solution was to utilize a "Magic Packet" ping from my Raspberry Pi. That seems to "just work" so far. This allows me to wake up the system at night once a month for "Smart" tests and "MD" checks. Obviously you need another system running to use this method, so it won't work for everybody. I added the Pi long ago as a way to keep a 24/7 system running that does not take much power.
I have an Android app that can supposedly do that, so I might try it. I think you have to enable the magic packet in UEFI if I'm not mistaken.
Since that is generally over WiFi I was curious. Yup, using "LanDroid" I was able to wake my system. As to the UEFI point, I am pretty sure I had to enable this via the bios. I have a UEFI system that is set to use "Legacy BIOS" mode.
I use UEFI mode and don't want to change it. I'm pretty sure the UEFI settings have toggles for WOL but I'll need to check. The Android app I have is called WolOn and includes a scheduler, but I'll take a look at LanDroid to compare.
I also enabled the "Magic" check box for the Network Manager config for my Ethernet port.
Not sure what that is. I don't see any such box.
poc
Doug Herr:
I also enabled the "Magic" check box for the Network Manager config for my Ethernet port.
Patrick O'Callaghan:
Not sure what that is. I don't see any such box.
In the Network Manager open up the editing window for a connection, go into the ethernet tab, the wake-on LAN section has a bunch of tickboxes which become active if you untick "ignore." Mine has:
Default Phy Unicast Multicast Ignore Broadcast Arp Magic
Ticking magic un-ghosts the wake on LAN password gadget below it.
On Sat, Aug 24, 2024, at 2:23 PM, Patrick O'Callaghan wrote:
I use UEFI mode and don't want to change it. I'm pretty sure the UEFI settings have toggles for WOL but I'll need to check. The Android app I have is called WolOn and includes a scheduler, but I'll take a look at LanDroid to compare.
Sounds like you have a good option. LanDroid is more of a general toolkit. But it is worth checking out
On 24 Aug 2024, at 12:18, Patrick O'Callaghan pocallaghan@gmail.com wrote:
If the RTC can wake the system from hibernation, why can't it wake it from suspension?
The RTC wake powers on the system. But a suspended system is already powered up and kernel is in charge.
You need to use a systemd timer to schedule the wake up.
Barry
On Sat, 2024-08-24 at 20:22 -0700, Doug Herr wrote:
On Sat, Aug 24, 2024, at 2:23 PM, Patrick O'Callaghan wrote:
I use UEFI mode and don't want to change it. I'm pretty sure the UEFI settings have toggles for WOL but I'll need to check. The Android app I have is called WolOn and includes a scheduler, but I'll take a look at LanDroid to compare.
Sounds like you have a good option. LanDroid is more of a general toolkit. But it is worth checking out
I've been using Fing as a general tool for some time (there are free and paid versions). It has some network security monitoring features which I don't actually use, but for general mapping and discovery it's pretty good.
And I've just noticed it also has a WOL tool :-)
poc
On Sun, 2024-08-25 at 08:51 +0100, Barry wrote:
On 24 Aug 2024, at 12:18, Patrick O'Callaghan pocallaghan@gmail.com wrote:
If the RTC can wake the system from hibernation, why can't it wake it from suspension?
The RTC wake powers on the system. But a suspended system is already powered up and kernel is in charge.
You need to use a systemd timer to schedule the wake up.
I've actually managed to get the RTC to work now (it needed another UEFI setting). I agree a systemd timer would be preferable in general, but I'm currently using suspend as a temporary substitute for hibernation until I get the latter to work (I have a separate thread on this).
poc
On Sat, 2024-08-24 at 12:17 +0100, Patrick O'Callaghan wrote:
Having failed to get hibernation working (see recent posts about Secure Boot getting in the way), I tried to fall back to suspending the system overnight. That works of course.
What doesn't work is waking it up automatically. If the RTC can wake the system from hibernation, why can't it wake it from suspension? I don't want to have to be in front of the system to wake it up.
Sigh. Turns out the UEFI had *another* setting aside from enabling wakeup. You have to tell it that the RTC alarm is controlled by the OS and not the BIOS.
It's working now.
poc
On Sun, 2024-08-25 at 11:13 +0930, Tim via users wrote:
Doug Herr:
I also enabled the "Magic" check box for the Network Manager config for my Ethernet port.
Patrick O'Callaghan:
Not sure what that is. I don't see any such box.
In the Network Manager open up the editing window for a connection, go into the ethernet tab, the wake-on LAN section has a bunch of tickboxes which become active if you untick "ignore." Mine has:
Default Phy Unicast Multicast Ignore Broadcast Arp Magic
Ticking magic un-ghosts the wake on LAN password gadget below it.
This is now academic as I've managed to get the RTC wakeup working, but just as a matter of interest I'm using KDE. Maybe this is a limitation of the NM widget, but I see no Ethernet tab, much less a WOL section.
poc
On 8/25/24 12:51 AM, Barry wrote:
On 24 Aug 2024, at 12:18, Patrick O'Callaghan pocallaghan@gmail.com wrote:
If the RTC can wake the system from hibernation, why can't it wake it from suspension?
The RTC wake powers on the system. But a suspended system is already powered up and kernel is in charge.
Sort of. It's no longer running and the BIOS/UEFI is in charge of wakeup.
You need to use a systemd timer to schedule the wake up.
Again, sort of. If the wakeup option is set, it will set the HW RTC to trigger a wakeup so it can run.
On Sun, 2024-08-25 at 08:51 +0100, Barry wrote:
The RTC wake powers on the system. But a suspended system is already powered up and kernel is in charge.
I wouldn't say so. It's barely powered up, and you're relying on firmware to control waking it up.
On Sun, 2024-08-25 at 20:09 -0700, Samuel Sieb wrote:
On 8/25/24 12:51 AM, Barry wrote:
On 24 Aug 2024, at 12:18, Patrick O'Callaghan pocallaghan@gmail.com wrote:
If the RTC can wake the system from hibernation, why can't it wake it from suspension?
The RTC wake powers on the system. But a suspended system is already powered up and kernel is in charge.
Sort of. It's no longer running and the BIOS/UEFI is in charge of wakeup.
You need to use a systemd timer to schedule the wake up.
Again, sort of. If the wakeup option is set, it will set the HW RTC to trigger a wakeup so it can run.
Currently I do this by writing directly to /sys/class/rtc/rtc0/wakealarm. Are you saying there's a way to get systemd to do that for me?
poc
-
Barry -
Doug Herr -
George N. White III -
Mike Wright -
Patrick O'Callaghan -
Samuel Sieb -
Tim