OS not sending ACPI commands properly?

[PunchFox]

OS: Gentoo
Hardware: Framework 16 (AMD Ryzen)
init system: OpenRC

Whenever I attempt to restart or shut down the computer, regardless of method, the OS will successfully shut down, but leaves my computer in an idle powered-on state, black screen with nothing happening. So restarting doesn't work, and shutting down keeps the power on, but doing nothing. To get the computer to shut down properly, I need to manually power-cycle the computer by holding the power button down.

I'm somewhat familiar with *nix systems, but would appreciate some direction on where to look for hints as to what may be going wrong. Eg, what logs might I look at, and what's the easiest way to parse/analyze/filter them for relevant info?

 

[Alexzee]

Hi! & Welcome to Linux.org.

You could try with root privileges running this command:

shutdown -h now

For the elogs you will have to run a script:-

Portage log - Gentoo wiki

wiki.gentoo.org

Portage also can have log files in /var/log/emerge.log, and /var/log/emerge-fetch.log.

After reading up on the Gentoo Forum it appears to be a kernel bug.

Gentoo Forums :: View topic - [SOLVED] no poweroff on reboot or shutdown

How long have you been running Gentoo?

 

[Alexzee]

FAQ's are pretty helpful too-

Gentoo Forums :: FAQ

Reading the documentation and getting the Handbook for Gentoo will most likely saved you lot's of headaches.

Documentation – Gentoo Linux

News and information from Gentoo Linux

www.gentoo.org

Handbook:Main Page - Gentoo wiki

wiki.gentoo.org

Let us know how things go PunchFox-

 

[f33dm3bits]

Try upgrading the firmware of your motherboard.

 

[PunchFox]

the "shutdown -h now" command has the same behavior. As far as the potential for this being a kernel bug goes, I'm using the latest stable version of the distribution kernel, 6.6.32. The user in the link you provided mentions upgrading to 6.8.7. If I upgraded, it would have to be to a version in the "testing" category. I'd be a bit surprised if the stable version had this bug, but I'll ask around in the Gentoo community maybe.

As far as looking through logs go, Portage is just Gentoo's package manager, its logs would only cover package management stuff. Is there not a generalized location for logs that would cover the reboot procedure? I'd imagine that's mostly distro-agnostic, no?

My BIOS is the latest version.

 

[Alexzee]

the "shutdown -h now" command has the same behavior. As far as the potential for this being a kernel bug goes, I'm using the latest stable version of the distribution kernel, 6.6.32. The user in the link you provided mentions upgrading to 6.8.7. If I upgraded, it would have to be to a version in the "testing" category. I'd be a bit surprised if the stable version had this bug, but I'll ask around in the Gentoo community maybe.

As far as looking through logs go, Portage is just Gentoo's package manager, its logs would only cover package management stuff. Is there not a generalized location for logs that would cover the reboot procedure? I'd imagine that's mostly distro-agnostic, no?

My BIOS is the latest version.

General location on logs in Linux is /var/log/.

On my Slackware system the path to my logs are /var/log/syslog and /var/log/lastlog and the like.

The system manager depends on what init system is in use. Like: systemd, sysvinit, openrc or runit.
From the reading I did on Gentoo systemd is disabled by default.

 

[Alexzee]

To have a look at the last shutdowns that are recent run:

last -x | grep shutdown

On a Debian system that's using systemd the shutdown script is in /etc/init.d/.

HTH