On 03-07-2024 03:48PM, Carlos E. R. wrote:
On 2024-03-07 22:37, -pj via openSUSE Users wrote:
On 03-07-2024 03:30PM, Carlos E. R. wrote:
On 2024-03-07 06:25, Masaru Nomiya wrote:
What is going on here what are your thoughts about this?
I'll take this opportunity to say that I can't understand the point of using hibernation on a desktop pc.
It only increases hdd (or sdd) access and shortens their lifetime.
Barely.
It saves electricity. On mechanical disks it saves life. Ditto on fans.
I have been using hibernation on destop for "decades" :-)
Hello, thank you for your insight on this also. I would like to ask once again about a machine that does *hibernate* correctly but in the process of doing so turns back on after 2 seconds of shutting off.
I remember. No idea.
This could be a situation of ACPI speaking with the kernel and having some issue with the hardware of the machine perhaps?
Well, things like that make me not install Tumbleweed.
-Thanks :|
Oh, in my case restoring from hibernation is way faster than booting, login, start all the applications I need, open all the files I need. The caveat is that hibernation is not fully developed in Linux, and crashes eventually.
I wanted to put the following in here below if even for a bit of reference. I have found this:
cat /var/log/Xorg.0.log [ 47550.443] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon [ 47550.443] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X [ 47550.443] (II) NVIDIA(0): configuration option may not be set correctly. When the [ 47550.443] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will [ 47550.443] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For [ 47550.443] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and [ 47550.443] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X [ 47550.443] (II) NVIDIA(0): Config Options in the README. -
So i'm going to have to find more out about the "ConnectToAcpid" the "AcpidSocketPath" and the "ACPI event daemon" it looks like. Do you have any ideas on this by chance? -Thanks