no Laptop Shutdown with Power Button

[Member kernelpanic]

Acer Extensa (Laptop), antix22 full 64bit, HD install, booted by Legacy Grub on MBR:

Working with antX17 (32bit) on this machine so far, so it was time to upgrade to antiX22 (64bit).
Everything works fine, wifi was a little bit of a hassle (broadcom module and connman are not in
love with each other), but finally working.
64bit system needs a little bit more RAM (machine has 1 GB), but all running surprisingly well.

There was only one problem I couldn´t solve:
the power off button of the laptop does not do what it`s expected to do: shutdown the system
(pressing the button just does not do anything).
in antiX17 the button worked the same way as if using the “exit session / shutdown” via the menu,
in antiX22 it does NOT.

systemwide keyboard setup is the same as in antix17, tried some other keyboard setups, no result.
any ideas/hints would be appreciated 🙂

• This topic was modified 3 months, 1 week ago by kernelpanic.
• This topic was modified 3 months, 1 week ago by kernelpanic.

[Member sybok]

Helpful

Up

0

::

Hi, could you please post output of ‘inxi -Fxz’ to provide more inforrmation on the HW.

BTW, some Acer Extensa models have more RAM. Is this a lower-end variant?
What kernel did you use with antiX-17? It could be something related to drivers.
Also, why did you decide to switch from 32-bit to 64-bit?

[Moderator Brian Masinick]

Helpful

Up

0

::

Press and hold the power button for AT LEAST 5-10 seconds. That’s worked for me on everything I have used.

If that doesn’t work I have no idea.

--
Brian Masinick

[Member kernelpanic]

Helpful

Up

0

::

hello sybok, yes this is a low budget variant of the acer extensa.
I bought it about 15 years ago for “low level” tasks like office, email, surfing …
it came with windows vista installed, which I erased pretty quick and multibooted some
linux variants. finally settled with antiX (of course, what else for low budget hardware?).

because of the limited RAM I used 32bit kernels so far (series 3 and 4 kernels with antiX17).
Since the prozessor is 64bit capable, I wanted to give 64bit a try, just out of couriosity
(working surprisingly well).

I think the problem has to do with the 64bit system, because the alternative 64bit 4.9.0-kernel
(came with the default install of antiX22) behaves the same way.

here is my …

$ inxi -Fxz
System:
  Kernel: 5.10.142-antix.2-amd64-smp arch: x86_64 bits: 64 compiler: gcc
    v: 10.2.1 Desktop: IceWM v: 3.3.0
    Distro: antiX-22-runit_x64-full Grup Yorum 18 October 2022
    base: Debian GNU/Linux 11 (bullseye)
Machine:
  Type: Laptop System: Acer product: Extensa 5220 v: 0100
    serial: <superuser required>
  Mobo: Acer model: Columbia v: Rev serial: <superuser required>
    BIOS: Phoenix v: 1.16 date: 08/07/2007
Battery:
  ID-1: BAT0 charge: 5.6 Wh (100.0%) condition: 5.6/53.3 Wh (10.6%)
    volts: 12.4 min: 11.1 model: SAN PP GRAPE32 status: full
CPU:
  Info: single core model: Intel Celeron 530 bits: 64 arch: Core2 Merom
    rev: 1 cache: L1: 64 KiB L2: 1024 KiB
  Speed (MHz): 1729 min/max: N/A core: 1: 1729 bogomips: 3457
  Flags: lm nx pae sse sse2 sse3 ssse3
Graphics:
  Device-1: Intel Mobile GM965/GL960 Integrated Graphics
    vendor: Acer Incorporated ALI driver: i915 v: kernel arch: Gen4
    bus-ID: 00:02.0
  Display: server: X.Org v: 1.20.11 driver: X: loaded: intel gpu: i915
    resolution: 1280x800~60Hz
  OpenGL: renderer: Mesa DRI Intel 965GM (CL) v: 2.1 Mesa 20.3.5
    direct render: Yes
Audio:
  Device-1: Intel 82801H HD Audio
    vendor: Acer Incorporated ALI Realtek ALC268 codec driver: snd_hda_intel
    v: kernel bus-ID: 00:1b.0
  Sound Server-1: ALSA v: k5.10.142-antix.2-amd64-smp running: yes
Network:
  Device-1: Broadcom NetLink BCM5787M Gigabit Ethernet PCI Express
    vendor: Acer Incorporated ALI driver: tg3 v: kernel port: N/A
    bus-ID: 02:00.0
  IF: eth0 state: down mac: <filter>
  Device-2: Broadcom BCM4311 802.11b/g WLAN vendor: AMBIT Microsystem
    driver: b43-pci-bridge v: N/A bus-ID: 04:00.0
  IF-ID-1: wlan0 state: up mac: <filter>
Drives:
  Local Storage: total: 74.53 GiB used: 5.22 GiB (7.0%)
  ID-1: /dev/sda vendor: Hitachi model: HTS541680J9SA00 size: 74.53 GiB
Partition:
  ID-1: / size: 15.64 GiB used: 5.22 GiB (33.4%) fs: ext3 dev: /dev/sda3
Swap:
  ID-1: swap-1 type: partition size: 1.38 GiB used: 0 KiB (0.0%)
    dev: /dev/sda7
Sensors:
  System Temperatures: cpu: 57.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 125 Uptime: 5m Memory: 968.9 MiB used: 418.4 MiB (43.2%)
  Init: runit runlevel: 2 Compilers: gcc: 10.2.1 Packages: 1578 Shell: Bash
  v: 5.1.4 inxi: 3.3.19

[Member kernelpanic]

Helpful

Up

0

::

hello brian,
your suggestion works, however this way the shutdown is more like “just pulling the plug”, not the usual
way of controlled shutting the system down.
since I can properly shutdown the system via the menu, it´s not a really important matter. I just wanted
to know if there was a simple solution to that.
thanks anyway!

[Moderator Brian Masinick]

Helpful

Up

0

::

Brian Masinick wrote:

Press and hold the power button for AT LEAST 5-10 seconds. That’s worked for me on everything I have used.

If that doesn’t work I have no idea.

I think I had a system once that would shutdown the operating system but did not turn the physical power off.
In that scenario I ran the usual shutdown sequence (for me, I usually use either “sudo halt” or “sudo poweroff”).
Once the operating system does down, then I hold the power button to complete the physical power off;
not many systems have done that, but I’ve seen it once or twice and that is my solution for those situations; do the normal shutdown first, then
physically power off.

--
Brian Masinick

[Forum Admin rokytnji]

Helpful

Up

0

::

Is acpi-support installed?

Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.

Linux Registered User # 475019
How to Search for AntiX solutions to your problems

[Moderator Brian Masinick]

Helpful

Up

0

::

rokytnji wrote:

Is acpi-support installed?

Nice catch; that may affect the system actions.

--
Brian Masinick

[Member kernelpanic]

Helpful

Up

0

::

hello roky,
yes, acpi-support is installed and up to date.
and you are right, behavior of power button is handled by acpi,
the script /etc/acpi/powerbtn-acpi-support.sh is supposed to handle it.

I found a nice description in debian wiki here:
https://wiki.debian.org/ConfigurePowerButton

so I just try to understand this script and fiddling around with it,
I guess for some reason the script is exited too early, so it doesn´t get to the point of

else
	# Normal handling.
	/sbin/shutdown -h -P now "Power button pressed"
fi

when you have enough spare time to play around with it, linux is fun! 😉

• This reply was modified 3 months, 1 week ago by kernelpanic.

[Moderator Brian Masinick]

Helpful

Up

0

::

Notice the message near the beginning of the script.
IF the /etc/acpi/events/powerbtn or its backup is missing,
THEN the script says
” logger Acpi-support not handling power button, acpid handler exists at /etc/acpi/events/powerbtn or /etc/acpi/events/powerbtn.dpkg-bak.
exit 0″

IT also checks for the existence of another script and runs
. /usr/share/acpi-support/policy-funcs
as long as these files exist, the scripts work; if these are missing, or not invoked, then clearly the intended functions are not
performed.

As far as the physical halting of the operating system, the shutdown, halt, and poweroff scripts will turn off the operating system.
The acpi tools and events handle the physical power from what I can tell.

Hope this helps.

--
Brian Masinick

[Member kernelpanic]

Helpful

Up

0

::

ok, I will play around with these scripts and try to find out where exactly the problem is.
maybe the init system (runit vs sysvinit) may also be a player here.
as I said, no real problem, because I can shutdown the system conveniently via the menu.
thank you anyway, brian, your hints are always appreciated!

[Moderator Brian Masinick]

Helpful

Up

0

::

If I’m reading the display properly it also looks like your system is running pretty warm, if not hot (57C). Unless it was rebooted and had previously been running for quite a while, a temperature of any component over 50 degrees C seems pretty warm; not sure if that is adversely impacting anything or not, but it’s something to watch. If the internal components could be cleaned of dust and grime that would probably help the overall operation and performance, but it may not be directly impacting the specific issues you’re facing, just a general item for overall system well being.

--
Brian Masinick

[Author]

Posts