Hi, I am attempting to operate openSUSE Tumbleweed on this machine (fully updated). I and have discovered acpi errors in journalctl output. These errors are shown as follows:
Thinkcentre-M57p:/etc/udev/rules.d # journalctl -p3 -b Mar 06 18:06:06 paul-Thinkcentre-M57p kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0._OSC.CAPB], AE_ALREADY_EXISTS (20230628/dsf> Mar 06 18:06:06 paul-Thinkcentre-M57p kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20230628/dswload2-477) Mar 06 18:06:06 paul-Thinkcentre-M57p kernel: ACPI Error: Aborting method \_SB.PCI0._OSC due to previous error (AE_ALREADY_EXISTS) (20230628/psparse-529) Mar 06 18:06:06 paul-Thinkcentre-M57p kernel: platform INT0800:00: failed to claim resource 0: [mem 0xff800000-0xffffffff] Mar 06 18:06:06 paul-Thinkcentre-M57p kernel: acpi INT0800:00: platform device creation failed: -16 Mar 06 18:06:23 paul-Thinkcentre-M57p kernel:
I do hope the journalctl output above is displayed correctly. I chose to 'paste as quotation' the journalctl output using Thunderbird mail client here. I have also attempted adding the 'acpi=off' parameter to /etc/default/grub then updated grub/bootloader resulting in *no graphical target* is reached after powercycling the machine. What is displayed is TTY login - which I can login and then remove the "acpi=off" parameter. My brief searching of this on the web has not yielded results explaining anything related to failing to load into SDDM or KDE. Do you think these acpi warnings could have something to do with: Hibernating the machine results in a proper hibernation *but* does not shut completely down (2 seconds then instantly powers up again) - goes through boot - grub - login again... What is going on here what are your thoughts about this?
Hello, In the Message; Subject : acpi journalctl errors: Message-ID : <3b5b2e53-6e19-491c-9272-f373e2064b0a@gmx.com> Date & Time: Wed, 6 Mar 2024 21:47:26 -0600 -pj via openSUSE Users <users@lists.opensuse.org> has written:
Hi, I am attempting to operate openSUSE Tumbleweed on this machine (fully updated). I and have discovered acpi errors in journalctl output. These errors are shown as follows: [...] I have also attempted adding the 'acpi=off' parameter to /etc/default/grub then updated grub/bootloader resulting in *no graphical target* is reached after powercycling the machine. What is displayed is TTY login - which I can login and then remove the "acpi=off" parameter.
How about 'nomodeset' parameter?
My brief searching of this on the web has not yielded results explaining anything related to failing to load into SDDM or KDE.
Do you think these acpi warnings could have something to do with: Hibernating the machine results in a proper hibernation *but* does not shut completely down (2 seconds then instantly powers up again) - goes through boot - grub - login again...
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. I understand that hibernation is used in laptops in order to use them for as long as possible with limited battery life, but it is only a necessary evil. My WM, enlightenment, is set to disable hibernation on my desktop pc, which is reasonable. I think it is reasonable to use sleep mode on a desktop pc. Best Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Distinguish between what is meaningful to me and what is meaningless, and forget what is meaningless to me. This is where individuality comes into play. This is a function that computer cannot perform." -- Shigehiko Toyama (in Japanes) --
On 03-06-2024 11:25PM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : acpi journalctl errors: Message-ID : <3b5b2e53-6e19-491c-9272-f373e2064b0a@gmx.com> Date & Time: Wed, 6 Mar 2024 21:47:26 -0600
-pj via openSUSE Users <users@lists.opensuse.org> has written:
Hi, I am attempting to operate openSUSE Tumbleweed on this machine (fully updated). I and have discovered acpi errors in journalctl output. These errors are shown as follows: [...] I have also attempted adding the 'acpi=off' parameter to /etc/default/grub then updated grub/bootloader resulting in *no graphical target* is reached after powercycling the machine. What is displayed is TTY login - which I can login and then remove the "acpi=off" parameter.
How about 'nomodeset' parameter?
Hey, I have a Nvidia Quadro K600 installed on this machine with G05 drivers. If I choose "nomodeset" it will cause Nvidia drivers failure to load correctly when booting machine I thought?
# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.7.7-1-default root=/dev/mapper/system-root resume=/dev/system/swap nvidia_drm.modeset=1 splash=0 plymouth.enable=0 mitigations=auto nosimplefb=1 security=apparmor
My brief searching of this on the web has not yielded results explaining anything related to failing to load into SDDM or KDE.
Do you think these acpi warnings could have something to do with: Hibernating the machine results in a proper hibernation *but* does not shut completely down (2 seconds then instantly powers up again) - goes through boot - grub - login again...
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.
You can explain this more if you wish also.
I understand that hibernation is used in laptops in order to use them for as long as possible with limited battery life, but it is only a necessary evil.
Yes, hibernation does work on the compaq nc-6400 here without modifications. It seems like it hardly takes less time to power up than a fresh boot though really.
My WM, enlightenment, is set to disable hibernation on my desktop pc, which is reasonable.
So you are using a window manager called "enlightenment' I have not heard of this before? You are not using KDE?
I think it is reasonable to use sleep mode on a desktop pc.
Sleep mode does work on Lenovo m57p desktop machine here.
-Greatest Wishes
Hello, In the Message; Subject : Re: acpi journalctl errors: Message-ID : <a7d6f170-7d7e-4ae4-b887-7b1cea0343c8@gmx.com> Date & Time: Thu, 7 Mar 2024 00:46:36 -0600 -pj via openSUSE Users <users@lists.opensuse.org> has written:
On 03-06-2024 11:25PM, Masaru Nomiya wrote:
[...]
How about 'nomodeset' parameter?
Hey, I have a Nvidia Quadro K600 installed on this machine with G05 drivers. If I choose "nomodeset" it will cause Nvidia drivers failure to load correctly when booting machine I thought?
What the hell kind of driver are you using? I'm using NVIDIA GeForce RTX 2060 with driver 550.54.14, with setting NOMODESET!
# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.7.7-1-default root=/dev/mapper/system-root resume=/dev/system/swap nvidia_drm.modeset=1 splash=0 plymouth.enable=0 mitigations=auto nosimplefb=1 security=apparmor
/boot/vmlinuz-6.7.7-1-default root=UUID=e6e9f642-b848-4a6c-8720-7c4971e3e5d0 ${extra_cmdline} splash=silent nomodeset quiet security=apparmor acpi=on apm=off nosimplefd=1 preempt=full threadirqs mitigations=auto [...]
It only increases hdd (or sdd) access and shortens their lifetime.
You can explain this more if you wish also.
Do you even know how hibernation works? [...]
My WM, enlightenment, is set to disable hibernation on my desktop pc, which is reasonable.
So you are using a window manager called "enlightenment' I have not heard of this before? You are not using KDE?
No.
I think it is reasonable to use sleep mode on a desktop pc.
Sleep mode does work on Lenovo m57p desktop machine here.
Can you hibernate on a PC where sleep mode doesn't work? Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "As Google fights for positioning in a new AI boom and an era where some consumers are turning to TikTok or ChatGPT instead of Google Search, some employees now worry product development could become dangerously hasty. The restructuring of RESIN has increased those concerns, the sources say." -- Google Splits Up a Key AI Ethics Watchdog --
On 03-07-2024 02:34AM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: acpi journalctl errors: Message-ID : <a7d6f170-7d7e-4ae4-b887-7b1cea0343c8@gmx.com> Date & Time: Thu, 7 Mar 2024 00:46:36 -0600
-pj via openSUSE Users <users@lists.opensuse.org> has written:
On 03-06-2024 11:25PM, Masaru Nomiya wrote:
[...]
How about 'nomodeset' parameter?
Hey, I have a Nvidia Quadro K600 installed on this machine with G05 drivers. If I choose "nomodeset" it will cause Nvidia drivers failure to load correctly when booting machine I thought?
What the hell kind of driver are you using?
I'm using this driver (nvidia-smi): NVIDIA-SMI 470.239.06 Driver Version: 470.239.06 CUDA Version: 11.4
I'm using NVIDIA GeForce RTX 2060 with driver 550.54.14, with setting NOMODESET!
Please see "nvidia_drm.modeset=1" below, is this incorrect?
# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.7.7-1-default root=/dev/mapper/system-root resume=/dev/system/swap nvidia_drm.modeset=1 splash=0 plymouth.enable=0 mitigations=auto nosimplefb=1 security=apparmor
/boot/vmlinuz-6.7.7-1-default root=UUID=e6e9f642-b848-4a6c-8720-7c4971e3e5d0 ${extra_cmdline} splash=silent nomodeset quiet security=apparmor acpi=on apm=off nosimplefd=1 preempt=full threadirqs mitigations=auto
[...]
It only increases hdd (or sdd) access and shortens their lifetime.
You can explain this more if you wish also.
Do you even know how hibernation works?
Hibernate attempts to save the current state of the machine to disk and not to memory like system sleep does. Sometimes modifications are necessary because there are not standards with ACPI power features.
[...]
My WM, enlightenment, is set to disable hibernation on my desktop pc, which is reasonable.
So you are using a window manager called "enlightenment' I have not heard of this before? You are not using KDE?
No.
I think it is reasonable to use sleep mode on a desktop pc.
Sleep mode does work on Lenovo m57p desktop machine here.
Can you hibernate on a PC where sleep mode doesn't work?
I believe 'yes' you can hibernate on a pc if sleep mode does not work. The issue is though in order to get hibernate feature to work you must have the swap partition or swapfile appropriate as well as other (sometimes hidden or difficult to locate) power features/settings set correctly. Note: I have been seeing some arch wiki stuff that seems to correlate some with openSUSE also.
Regards.
--- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "As Google fights for positioning in a new AI boom and an era where some consumers are turning to TikTok or ChatGPT instead of Google Search, some employees now worry product development could become dangerously hasty. The restructuring of RESIN has increased those concerns, the sources say."
-- Google Splits Up a Key AI Ethics Watchdog --
Hello, In the Message; Subject : Re: acpi journalctl errors: Message-ID : <2317912e-2f97-469e-bf30-2ac9cc6c89de@gmx.com> Date & Time: Thu, 7 Mar 2024 02:47:33 -0600 -pj via openSUSE Users <users@lists.opensuse.org> has written:
On 03-07-2024 02:34AM, Masaru Nomiya wrote: [...]
What the hell kind of driver are you using?
I'm using this driver (nvidia-smi): NVIDIA-SMI 470.239.06 Driver Version: 470.239.06 CUDA Version: 11.4
My CUDA version is 12.4.0.
I'm using NVIDIA GeForce RTX 2060 with driver 550.54.14, with setting NOMODESET!
Please see "nvidia_drm.modeset=1" below, is this incorrect?
Is nvidia_drm.modeset=1 necessary if it is required for some of the PRIME-related interoperability features, in addition to allowing low-level DRM interfaces and talking clients to work? The parameter 'nomodeset' is to disable kernel mode.
I think it is reasonable to use sleep mode on a desktop pc.
Sleep mode does work on Lenovo m57p desktop machine here.
Can you hibernate on a PC where sleep mode doesn't work?
I believe 'yes' you can hibernate on a pc if sleep mode does not work. The issue is though in order to get hibernate feature to work you must have the swap partition or swapfile appropriate as well as other (sometimes hidden or difficult to locate) power features/settings set correctly.
What is the results of; # systemctl list-unit-files | grep sleep Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Distinguish between what is meaningful to me and what is meaningless, and forget what is meaningless to me. This is where individuality comes into play. This is a function that computer cannot perform." -- Shigehiko Toyama (in Japanes) --
On 03-07-2024 03:13AM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: acpi journalctl errors: Message-ID : <2317912e-2f97-469e-bf30-2ac9cc6c89de@gmx.com> Date & Time: Thu, 7 Mar 2024 02:47:33 -0600
-pj via openSUSE Users <users@lists.opensuse.org> has written:
On 03-07-2024 02:34AM, Masaru Nomiya wrote: [...]
What the hell kind of driver are you using?
I'm using this driver (nvidia-smi): NVIDIA-SMI 470.239.06 Driver Version: 470.239.06 CUDA Version: 11.4
My CUDA version is 12.4.0.
I'm using NVIDIA GeForce RTX 2060 with driver 550.54.14, with setting NOMODESET!
Ok you have newer hardware I believe and are possibly using G06 Nvidia drivers?
The CUDA toolkit here: https://developer.nvidia.com/cuda-downloads?target_os=Linux&target_arch=x86_64&Distribution=OpenSUSE&target_version=15&target_type=rpm_local Cuda toolkit assists with designing applications that use CUDA to render graphics? Can I ask about your what your current output of 'cat/proc/cmdline' is on that machine there?
Please see "nvidia_drm.modeset=1" below, is this incorrect?
Is nvidia_drm.modeset=1 necessary if it is required for some of the PRIME-related interoperability features, in addition to allowing low-level DRM interfaces and talking clients to work?
The parameter 'nomodeset' is to disable kernel mode.
Ok but *only* "nomodeset" is used if *NO* graphical target is reached i.e. (BLANK SCREEN) I think. Maybe I should have said the following (with the situation here)! If I add "acpi=off" to /etc/default/grub then 'update bootloader' -> powercycle -> SDDM target is not reached? As am dumped to a TTY prompt which still is legible and displayed. Should I try again maybe by toggling "acpi=off" and then passing 'startx' in order to gain access to the SDDM login window?
Ok I do think I *want* to keep this in /etc/default/grub -> nvidia_drm.modeset=1
I think it is reasonable to use sleep mode on a desktop pc.
Sleep mode does work on Lenovo m57p desktop machine here.
Can you hibernate on a PC where sleep mode doesn't work?
I believe 'yes' you can hibernate on a pc if sleep mode does not work. The issue is though in order to get hibernate feature to work you must have the swap partition or swapfile appropriate as well as other (sometimes hidden or difficult to locate) power features/settings set correctly.
What is the results of;
# systemctl list-unit-files | grep sleep
Thinkcentre-M57p:~ # systemctl list-unit-files | grep sleep systemd-hybrid-sleep.service static - hybrid-sleep.target static - sleep.target static - Thinkcentre-M57p:~ # I see these are currently set as static service and targets above. Hey, I was told recently to not attempt to disable ACPI as it is there for a reason. In the case of the machine here it's obviously helping achieve reaching the graphical target which here is SDDM and KDE Plasma I think. I felt to add that to get your deeper thoughts on it if possible. The journalctl errors reported by 'journalctl -p3 -b' (on this machine). Are kernel messages being displayed, caused by hardware communication to kernel related errors and bugs being reported by the kernel? Can you discuss on this some if possible?
Regards.
--- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Distinguish between what is meaningful to me and what is meaningless, and forget what is meaningless to me. This is where individuality comes into play. This is a function that computer cannot perform."
-- Shigehiko Toyama (in Japanes) --
-Great Wishes
Hello, In the Message; Subject : Re: acpi journalctl errors: Message-ID : <63f9e62f-7261-4278-9117-d09af68959bc@gmx.com> Date & Time: Thu, 7 Mar 2024 13:45:23 -0600 -pj via openSUSE Users <users@lists.opensuse.org> has written:
On 03-07-2024 03:13AM, Masaru Nomiya wrote: [...]
I'm using NVIDIA GeForce RTX 2060 with driver 550.54.14, with setting NOMODESET!
Ok you have newer hardware I believe and are possibly using G06 Nvidia drivers?
No, I'm using open-gpu-kernel-modules-550.54.14.
The CUDA toolkit here: https://developer.nvidia.com/cuda-downloads?target_os=Linux&target_arch=x86_64&Distribution=OpenSUSE&target_version=15&target_type=rpm_local
Cuda toolkit assists with designing applications that use CUDA to render graphics?
It depends on the design of the application. However, there is nothing in the application provided by openSUSE that indicates a dependency on cuda. I have looked at the source code and compiled the appplications that can incorporate cuda. ffmpeg, vlc, opencv, vtk, etc.
Can I ask about your what your current output of 'cat/proc/cmdline' is on that machine there?
BOOT_IMAGE=/boot/vmlinuz-6.7.7-1-default root=UUID=e6e9f642-b848-4a6c-8720-7c4971e3e5d0 splash=silent nomodeset quiet security=apparmor acpi=on apm=off nosimplefd=1 preempt=full threadirqs mitigations=auto [...]
Should I try again maybe by toggling "acpi=off" and then passing 'startx' in order to gain access to the SDDM login window?
I guessed that yours is running in kernel mode, so I suggested that you add a nomodeset. [...]
What is the results of;
# systemctl list-unit-files | grep sleep
Thinkcentre-M57p:~ # systemctl list-unit-files | grep sleep systemd-hybrid-sleep.service static - hybrid-sleep.target static - sleep.target static - Thinkcentre-M57p:~ #
I see these are currently set as static service and targets above.
OK. Try; # systemctl start systemd-suspend.service What results did you get?
Hey, I was told recently to not attempt to disable ACPI as it is there for a reason.
Normally, acpi=on, and as mentioned above, that's how I set mine. However, the phenomenon you reported can only be attributed to acpi, so I suggested trying it with acpi=off. Because, your PC is quite old. Kind Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Companies have come to view generative AI as a kind of monster that must be fed at all costs―even if it isn’t always clear what exactly that data is needed for or what those future AI systems might end up doing." -- Generative AI Is Making Companies Even More Thirsty for Your Data --
On 03-07-2024 08:04PM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: acpi journalctl errors: Message-ID : <63f9e62f-7261-4278-9117-d09af68959bc@gmx.com> Date & Time: Thu, 7 Mar 2024 13:45:23 -0600
-pj via openSUSE Users <users@lists.opensuse.org> has written:
On 03-07-2024 03:13AM, Masaru Nomiya wrote: [...]
I'm using NVIDIA GeForce RTX 2060 with driver 550.54.14, with setting NOMODESET!
Ok you have newer hardware I believe and are possibly using G06 Nvidia drivers?
No, I'm using open-gpu-kernel-modules-550.54.14.
Ok, I filed the open-gpu-kernel-modules under open-GPU and will check into more about what that is.
The CUDA toolkit here: https://developer.nvidia.com/cuda-downloads?target_os=Linux&target_arch=x86_64&Distribution=OpenSUSE&target_version=15&target_type=rpm_local
Cuda toolkit assists with designing applications that use CUDA to render graphics?
It depends on the design of the application.
However, there is nothing in the application provided by openSUSE that indicates a dependency on cuda.
Ok, Nvidia is not opensource software either.
I have looked at the source code and compiled the appplications that can incorporate cuda. ffmpeg, vlc, opencv, vtk, etc.
Very good indeed. When you compile ffmpeg, vlc, opencv, vtk and so on... Do you get better performance and options that you more really want?
Can I ask about your what your current output of 'cat/proc/cmdline' is on that machine there?
BOOT_IMAGE=/boot/vmlinuz-6.7.7-1-default root=UUID=e6e9f642-b848-4a6c-8720-7c4971e3e5d0 splash=silent nomodeset quiet security=apparmor acpi=on apm=off nosimplefd=1 preempt=full threadirqs mitigations=auto
Ok, I have noted this above. One thing I do notice is yours has specifically acpi=on . Do you recommend I do the same at this time? The machine here appears to default to acpi=on .
[...]
Should I try again maybe by toggling "acpi=off" and then passing 'startx' in order to gain access to the SDDM login window?
I guessed that yours is running in kernel mode, so I suggested that you add a nomodeset.
Ok
[...]
What is the results of;
# systemctl list-unit-files | grep sleep
Thinkcentre-M57p:~ # systemctl list-unit-files | grep sleep systemd-hybrid-sleep.service static - hybrid-sleep.target static - sleep.target static - Thinkcentre-M57p:~ #
I see these are currently set as static service and targets above.
OK.
Try;
# systemctl start systemd-suspend.service
What results did you get?
The machine immediately goes into a suspended state. I initially thought the system powered completely down. It happened very quickly. Pressing a key on the keyboard wakes the system up and allows password to be entered at the SDDM menu. I believe after installing acpid (see below). That pressing a single key on keyboard wakes machine from suspend. Prior had to press power button to wake from suspend. Same as adding usbcore.autosuspend=-1 to /etc/default/grub it seems.
Hey, I was told recently to not attempt to disable ACPI as it is there for a reason.
Normally, acpi=on, and as mentioned above, that's how I set mine. However, the phenomenon you reported can only be attributed to acpi, so I suggested trying it with acpi=off. Because, your PC is quite old.
Yes. I would like to give you an update if possible. 1. 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. - 2. Have installed the acpid package on the machine. - 3. Referenced here for doing so: -> https://wiki.archlinux.org/title/acpid - 4. Enabled the acpid service to: acpid.service enabled enabled - 5. Powercycled the machine. - 6. I do not see anymore ACPI related errors when reviewing Xorg.0.log The current Xorg.0.log is here: https://paste.opensuse.org/pastes/2dacbed41fe9 - 6.1. Pressing power button while journalctl -f is open in Konsole results in: Thinkcentre-M57p systemd-logind[1271]: Power key pressed short. Mar 07 21:00:29 Thinkcentre-M57p dbus-daemon[1911]: [session uid=1000 pid=1911] Activating service name='org.kde.LogoutPrompt' requested by ':1.23' (uid=1000 pid=2093 comm="/usr/bin/ksmserver") Mar 07 21:00:30 Thinkcentre-M57p dbus-daemon[1911]: [session uid=1000 pid=1911] Successfully activated service 'org.kde.LogoutPrompt' - 6.2. Do you think perhaps the reason hibernate doesn't stick is the machine "Power key pressed short." should be altered? - 7. journatlctl does still have ACPI related bug/errors at the top. journalctl -p3 -b output is here: https://paste.opensuse.org/pastes/20d9a6680e72 - 8. I changed permissions of /usr/lib/systemd/systemd.login.d To as follows: ---------- 1 root root 271K Feb 23 10:51 systemd-logind - Please Note as per #3. above the following: Note: Events such as button/power, button/lid, button/suspend and button/hibernate are handled by systemd-logind.service(8) by default, see Power management#Power management. If handling these events with acpid, the handling of these events by logind should either be disabled first, or inhibited. 9. How can I read systemd-logind.service(8) ? Now after writing this I will save notes to usb and powercycle. What do you think about trying to follow the link in #3. above? Since it relates to ArchWiki many files are different. Example: /etc/acpi *and* /etc/acpi/events is empty in openSUSE Tumbleweed. 10. How to proceed? 11. Will you be able to review the journalctl log and Xorg.0.log perhaps? If I hibernate and time my manually pressing of the power button during the 2 second off period. I am able to essentially kill the machine with hibernation intact. Goal here as you know is to hibernate the machine with out pressing a key. -Best Hopes
Hello, In the Message; Subject : Re: acpi journalctl errors: Message-ID : <b6b23b76-56c8-40e6-b92f-9135a45e87a2@gmx.com> Date & Time: Thu, 7 Mar 2024 21:29:00 -0600 -pj via openSUSE Users <users@lists.opensuse.org> has written: [...]
Try;
# systemctl start systemd-suspend.service
What results did you get?
The machine immediately goes into a suspended state. I initially thought the system powered completely down. It happened very quickly. Pressing a key on the keyboard wakes the system up and allows password to be entered at the SDDM menu.
I believe after installing acpid (see below). That pressing a single key on keyboard wakes machine from suspend. Prior had to press power button to wake from suspend. Same as adding usbcore.autosuspend=-1 to /etc/default/grub it seems.
It's a hybrid sleep mode. yes, SLEEP MODE. [...]
If I hibernate and time my manually pressing of the power button during the 2 second off period. I am able to essentially kill the machine with hibernation intact. Goal here as you know is to hibernate the machine with out pressing a key.
Sorry, but I'm not interested in hibernation on a desktop PC, so I'll leave it to other members. Kind Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Distinguish between what is meaningful to me and what is meaningless, and forget what is meaningless to me. This is where individuality comes into play. This is a function that computer cannot perform." -- Shigehiko Toyama (in Japanes) --
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" :-) -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
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. This could be a situation of ACPI speaking with the kernel and having some issue with the hardware of the machine perhaps? -Thanks :|
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. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [03-07-24 16:59]:
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.
amazing false observation. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
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
participants (4)
-
-pj -
Carlos E. R. -
Masaru Nomiya -
Patrick Shanahan