Mon, Apr 17, 2023 at 09:14:30PM +0300, Marko Mäkelä wrote:
The "rtcwake -m show" straight after the reboot indicated that the
alarm is off. I read all journal entries between the two rtcwake
commands, which were helpfully logged. The only thing I found was a
kernel boot message that said that
Mon, Apr 17, 2023 at 04:38:11PM +0300, Marko Mäkelä wrote:
Mon, Apr 17, 2023 at 10:17:03AM +0200, g.bruno wrote:
here a longer thread at problems with rtcwake (in German):
https://forum.ubuntuusers.de/topic/rtcwake-geht-nicht-mehr/#post-9369451
Thank you. I am not going to use rtcwake on
Mon, Apr 17, 2023 at 10:17:03AM +0200, g.bruno wrote:
here a longer thread at problems with rtcwake (in German):
https://forum.ubuntuusers.de/topic/rtcwake-geht-nicht-mehr/#post-9369451
Thank you. I am not going to use rtcwake on those 2 problematic laptops
for anything real, but out of
Hallo,
here a longer thread at problems with rtcwake (in German):
https://forum.ubuntuusers.de/topic/rtcwake-geht-nicht-mehr/#post-9369451
Perhaps it might be useful for someone,
GBruno
Am 16.04.23 um 19:54 schrieb Marko Mäkelä:
Today, I tested rtcwake on several x86 or x86-64 based
Reminds me of the nvram-wakeup lotto back in the day.
Am 16. April 2023 19:54:03 MESZ schrieb "Marko Mäkelä" :
>Today, I tested rtcwake on several x86 or x86-64 based computers.
>
>The outcome:
>
>(1) Suspend to RAM (say, "rtcwake -m mem -s 10"):
>* Success: Every system.
>(2) Wake-on-timer
Today, I tested rtcwake on several x86 or x86-64 based computers.
The outcome:
(1) Suspend to RAM (say, "rtcwake -m mem -s 10"):
* Success: Every system.
(2) Wake-on-timer ("rtcwake -m no -s 120 && shutdown -h now" or "rtcwake
-m off -s 120"):
* Success: Lenovo Thinkpad X220 (2012?), and a
