mapping hardware buttons?

'User made' tutorials related to Porteus Kiosk edition.
Official kiosk documentation can be find here: http://porteus-kiosk.org/documentation.html
Forum rules
Porteus Kiosk section of the forum is unmaintained now. Its kept in a 'read only' mode for archival purposes.
Please use the kiosk contact page for directing your queries: https://porteus-kiosk.org/contact.html
brutus
Black ninja
Black ninja
Posts: 42
Joined: 20 May 2022, 06:10
Distribution: openSUSE

mapping hardware buttons?

Post#1 by brutus » 13 Jul 2022, 09:34

Hi,

currently I am trying to optimize the energy consumption on the tablet PC which is very poor. The device has 4 buttons.
One is for the barcode scanner, the second for the shutdown menu and then there are the + (plus) and - (minus) buttons.

Now when I have freeze_idle enabled, I can wake up the device with the power button. But then the menu appears, which I click away with the cancel button. With the second freeze I can't wake up the device at all.

Is there a way to set the system so that I can wake up the device with the plus or minus button?
This might also solve the problem with the 2nd freeze?!

### Edit - added right after
It looks like the second freeze I can get the device to wake up, but the screen stays dark. Because I can then log in via ssh.

BR,
Michael

User avatar
fanthom
Moderator Team
Moderator Team
Posts: 5666
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

mapping hardware buttons?

Post#2 by fanthom » 13 Jul 2022, 10:09

Michael,

Must be a hardware -> drivers related problem.

Please recreate the issue then post the output of following command (run it over SSH):

Code: Select all

dmesg | tail -n 20

Also - please check if 'suspend_idle=' works better (if gives a biggest power savings).

Thanks
Please add [Solved] to your thread title if the solution was found.

brutus
Black ninja
Black ninja
Posts: 42
Joined: 20 May 2022, 06:10
Distribution: openSUSE

mapping hardware buttons?

Post#3 by brutus » 13 Jul 2022, 12:53

I changed to suspend_idle - same behavior.

This is the output I got:

Code: Select all

Right after boot:
[   45.081439] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[   45.081477] intel_sst_acpi 808622A8:00: fw returned err -16
[   45.081513] sst-mfld-platform sst-mfld-platform: ASoC: POST_PMU: pcm1_in event failed: -16
[   46.105438] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[   46.105478] intel_sst_acpi 808622A8:00: fw returned err -16
[   46.105512] sst-mfld-platform sst-mfld-platform: ASoC: POST_PMU: media2_in event failed: -16
[   47.257428] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x2 fw_state 0x3
[   47.257445] intel_sst_acpi 808622A8:00: fw returned err -16
[   48.281465] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x2 fw_state 0x3
[   48.281481] intel_sst_acpi 808622A8:00: fw returned err -16
[   49.306178] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x2 fw_state 0x3
[   49.306194] intel_sst_acpi 808622A8:00: fw returned err -16
[   50.329452] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x2 fw_state 0x3
[   50.329474] intel_sst_acpi 808622A8:00: fw returned err -16
[   51.739819] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[   51.739837] intel_sst_acpi 808622A8:00: fw returned err -16
[   51.739859] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: sprot_loop_out mix 0 event failed: -16
[   52.761158] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[   52.761176] intel_sst_acpi 808622A8:00: fw returned err -16
[   52.761191] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: sprot_loop_out event failed: -16

After first wakeup:
[  138.369421] intel_sst_acpi 808622A8:00: fw returned err -16
[  138.369456] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: pcm0_out event failed: -16
[  139.393296] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[  139.393334] intel_sst_acpi 808622A8:00: fw returned err -16
[  139.393368] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: media_loop1_out event failed: -16
[  140.417365] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[  140.417405] intel_sst_acpi 808622A8:00: fw returned err -16
[  140.417441] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: media_loop2_out event failed: -16
[  141.441428] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[  141.441467] intel_sst_acpi 808622A8:00: fw returned err -16
[  141.441501] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: sprot_loop_out event failed: -16
[  142.465282] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[  142.465322] intel_sst_acpi 808622A8:00: fw returned err -16
[  142.465360] sst-mfld-platform sst-mfld-platform: ASoC: POST_PMU: media2_in event failed: -16
[  143.489264] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[  143.489302] intel_sst_acpi 808622A8:00: fw returned err -16
[  143.489336] sst-mfld-platform sst-mfld-platform: ASoC: POST_PMU: pcm0_in event failed: -16
[  144.513277] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[  144.513316] intel_sst_acpi 808622A8:00: fw returned err -16
[  144.513351] sst-mfld-platform sst-mfld-platform: ASoC: POST_PMU: pcm1_in event failed: -16

After second wakeup (darkness!):
[  261.041115] sst-mfld-platform sst-mfld-platform: SET_SWM cmd max inputs reached
[  262.065227] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[  262.065265] intel_sst_acpi 808622A8:00: fw returned err -16
[  262.065302] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: media_loop1_out mix 0 event failed: -16
[  262.065331] sst-mfld-platform sst-mfld-platform: SET_SWM cmd max inputs reached
[  263.089227] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[  263.089267] intel_sst_acpi 808622A8:00: fw returned err -16
[  263.089301] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: media_loop2_out mix 0 event failed: -16
[  263.089329] sst-mfld-platform sst-mfld-platform: SET_SWM cmd max inputs reached
[  264.113239] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[  264.113278] intel_sst_acpi 808622A8:00: fw returned err -16
[  264.113317] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: sprot_loop_out mix 0 event failed: -16
[  264.113350] sst-mfld-platform sst-mfld-platform: SET_SWM cmd max inputs reached
[  265.137237] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[  265.137276] intel_sst_acpi 808622A8:00: fw returned err -16
[  265.137313] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: codec_out0 mix 0 event failed: -16
[  265.137341] sst-mfld-platform sst-mfld-platform: SET_SWM cmd max inputs reached
[  266.161280] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[  266.161319] intel_sst_acpi 808622A8:00: fw returned err -16
[  266.161353] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: codec_out1 mix 0 event failed: -16

brutus
Black ninja
Black ninja
Posts: 42
Joined: 20 May 2022, 06:10
Distribution: openSUSE

mapping hardware buttons?

Post#4 by brutus » 13 Jul 2022, 13:20

A 'whole cycle' is perhaps more interesting - starting from the point I push the button:

Code: Select all

[Wed Jul 13 13:26:54 2022] intel_sst_acpi 808622A8:00: fw returned err -16
[Wed Jul 13 13:26:54 2022] sst-mfld-platform sst-mfld-platform: ASoC: POST_PMD: media0_out mix 0 event failed: -16
[Wed Jul 13 13:26:54 2022] wlan0: deauthenticating from 00:1a:8c:c9:51:90 by local choice (Reason: 3=DEAUTH_LEAVING)
[Wed Jul 13 13:26:56 2022] serial 00:01: disabled
[Wed Jul 13 13:39:42 2022] iwlwifi 0000:01:00.0: Applying debug destination EXTERNAL_DRAM
[Wed Jul 13 13:39:42 2022] iwlwifi 0000:01:00.0: Applying debug destination EXTERNAL_DRAM
[Wed Jul 13 13:39:42 2022] iwlwifi 0000:01:00.0: FW already configured (0) - re-configuring
[Wed Jul 13 13:39:43 2022] usb 1-4.2: reset full-speed USB device number 6 using xhci_hcd
[Wed Jul 13 13:39:43 2022] Goodix-TS i2c-GDIX1002:00: Error reading config version: -121, resetting controller
[Wed Jul 13 13:39:43 2022] usb 1-4.3.1: reset full-speed USB device number 10 using xhci_hcd
[Wed Jul 13 13:39:43 2022] OOM killer enabled.
[Wed Jul 13 13:39:43 2022] Restarting tasks ... done.
[Wed Jul 13 13:39:44 2022] video LNXVIDEO:00: Restoring backlight state
[Wed Jul 13 13:39:44 2022] PM: suspend exit
[Wed Jul 13 13:39:45 2022] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x2 fw_state 0x3
[Wed Jul 13 13:39:45 2022] intel_sst_acpi 808622A8:00: fw returned err -16
[Wed Jul 13 13:39:45 2022] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: codec_out0 event failed: -16
[Wed Jul 13 13:39:46 2022] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x2 fw_state 0x3
[Wed Jul 13 13:39:46 2022] intel_sst_acpi 808622A8:00: fw returned err -16
[Wed Jul 13 13:39:46 2022] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: codec_out1 event failed: -16
[Wed Jul 13 13:39:47 2022] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x2 fw_state 0x3
[Wed Jul 13 13:39:47 2022] intel_sst_acpi 808622A8:00: fw returned err -16
[Wed Jul 13 13:39:47 2022] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: codec_in0 event failed: -16
[Wed Jul 13 13:39:47 2022] wlan0: authenticate with 00:1a:8c:c9:51:98
[Wed Jul 13 13:39:47 2022] wlan0: send auth to 00:1a:8c:c9:51:98 (try 1/3)
[Wed Jul 13 13:39:47 2022] wlan0: authenticated
[Wed Jul 13 13:39:47 2022] wlan0: associate with 00:1a:8c:c9:51:98 (try 1/3)
[Wed Jul 13 13:39:47 2022] wlan0: RX AssocResp from 00:1a:8c:c9:51:98 (capab=0x11 status=0 aid=1)
[Wed Jul 13 13:39:47 2022] wlan0: associated
[Wed Jul 13 13:39:48 2022] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x2 fw_state 0x3
[Wed Jul 13 13:39:48 2022] intel_sst_acpi 808622A8:00: fw returned err -16
[Wed Jul 13 13:39:48 2022] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: codec_in1 event failed: -16
[Wed Jul 13 13:39:49 2022] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[Wed Jul 13 13:39:49 2022] intel_sst_acpi 808622A8:00: fw returned err -16
[Wed Jul 13 13:39:49 2022] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: media0_out mix 0 event failed: -16
[Wed Jul 13 13:39:50 2022] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[Wed Jul 13 13:39:50 2022] intel_sst_acpi 808622A8:00: fw returned err -16
[Wed Jul 13 13:39:50 2022] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: media1_out mix 0 event failed: -16
[Wed Jul 13 13:39:50 2022] sst-mfld-platform sst-mfld-platform: SET_SWM cmd max inputs reached
[Wed Jul 13 13:39:51 2022] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[Wed Jul 13 13:39:51 2022] intel_sst_acpi 808622A8:00: fw returned err -16
[Wed Jul 13 13:39:51 2022] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: pcm0_out mix 0 event failed: -16
[Wed Jul 13 13:39:51 2022] sst-mfld-platform sst-mfld-platform: SET_SWM cmd max inputs reached
[Wed Jul 13 13:39:52 2022] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[Wed Jul 13 13:39:52 2022] intel_sst_acpi 808622A8:00: fw returned err -16
[Wed Jul 13 13:39:52 2022] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: media_loop1_out mix 0 event failed: -16
[Wed Jul 13 13:39:52 2022] sst-mfld-platform sst-mfld-platform: SET_SWM cmd max inputs reached
[Wed Jul 13 13:39:53 2022] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[Wed Jul 13 13:39:53 2022] intel_sst_acpi 808622A8:00: fw returned err -16
[Wed Jul 13 13:39:53 2022] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: media_loop2_out mix 0 event failed: -16
[Wed Jul 13 13:39:53 2022] sst-mfld-platform sst-mfld-platform: SET_SWM cmd max inputs reached
[Wed Jul 13 13:39:54 2022] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[Wed Jul 13 13:39:54 2022] intel_sst_acpi 808622A8:00: fw returned err -16
[Wed Jul 13 13:39:54 2022] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: sprot_loop_out mix 0 event failed: -16
[Wed Jul 13 13:39:54 2022] sst-mfld-platform sst-mfld-platform: SET_SWM cmd max inputs reached
[Wed Jul 13 13:39:55 2022] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[Wed Jul 13 13:39:55 2022] intel_sst_acpi 808622A8:00: fw returned err -16
[Wed Jul 13 13:39:55 2022] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: codec_out0 mix 0 event failed: -16
[Wed Jul 13 13:39:55 2022] sst-mfld-platform sst-mfld-platform: SET_SWM cmd max inputs reached
[Wed Jul 13 13:39:56 2022] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[Wed Jul 13 13:39:56 2022] intel_sst_acpi 808622A8:00: fw returned err -16
[Wed Jul 13 13:39:56 2022] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: codec_out1 mix 0 event failed: -16
[Wed Jul 13 13:39:57 2022] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[Wed Jul 13 13:39:57 2022] intel_sst_acpi 808622A8:00: fw returned err -16
[Wed Jul 13 13:39:57 2022] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: media0_out event failed: -16
[Wed Jul 13 13:39:58 2022] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[Wed Jul 13 13:39:58 2022] intel_sst_acpi 808622A8:00: fw returned err -16
[Wed Jul 13 13:39:58 2022] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: media1_out event failed: -16
[Wed Jul 13 13:39:59 2022] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[Wed Jul 13 13:39:59 2022] intel_sst_acpi 808622A8:00: fw returned err -16
[Wed Jul 13 13:39:59 2022] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: pcm0_out event failed: -16
[Wed Jul 13 13:40:00 2022] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[Wed Jul 13 13:40:00 2022] intel_sst_acpi 808622A8:00: fw returned err -16
[Wed Jul 13 13:40:00 2022] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: media_loop1_out event failed: -16
[Wed Jul 13 13:40:01 2022] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[Wed Jul 13 13:40:01 2022] intel_sst_acpi 808622A8:00: fw returned err -16
[Wed Jul 13 13:40:01 2022] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: media_loop2_out event failed: -16
[Wed Jul 13 13:40:02 2022] intel_sst_acpi 808622A8:00: Wait timed-out condition:0x0, msg_id:0x1 fw_state 0x3
[Wed Jul 13 13:40:02 2022] intel_sst_acpi 808622A8:00: fw returned err -16
[Wed Jul 13 13:40:02 2022] sst-mfld-platform sst-mfld-platform: ASoC: PRE_PMU: sprot_loop_out event failed: -16

User avatar
fanthom
Moderator Team
Moderator Team
Posts: 5666
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

mapping hardware buttons?

Post#5 by fanthom » 13 Jul 2022, 13:47

Try to set the backlight manually over SSH:

Code: Select all

for x in `ls -1 /sys/class/backlight`; do echo $((`cat /sys/class/backlight/$x/max_brightness`*100/100)) > /sys/class/backlight/$x/brightness; done
Thanks
Please add [Solved] to your thread title if the solution was found.

brutus
Black ninja
Black ninja
Posts: 42
Joined: 20 May 2022, 06:10
Distribution: openSUSE

mapping hardware buttons?

Post#6 by brutus » 13 Jul 2022, 13:53

Nothing happened.

User avatar
fanthom
Moderator Team
Moderator Team
Posts: 5666
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

mapping hardware buttons?

Post#7 by fanthom » 13 Jul 2022, 16:47

Please run this command to restart the Xorg session:

Code: Select all

openbox --exit
If it wont help then please check if MX Linux suffers for the same problem.

Thanks
Please add [Solved] to your thread title if the solution was found.

brutus
Black ninja
Black ninja
Posts: 42
Joined: 20 May 2022, 06:10
Distribution: openSUSE

mapping hardware buttons?

Post#8 by brutus » 14 Jul 2022, 06:08

openbox restart didn't work and having same behavior on MX Linux: set to 'standby' -> first time wakening works -> 'standby' a second time -> screen stays dark

User avatar
fanthom
Moderator Team
Moderator Team
Posts: 5666
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

mapping hardware buttons?

Post#9 by fanthom » 14 Jul 2022, 06:56

Must be a driver problem.

Does MX Linux give you an opportunity to upgrade the kernel from their repos?
If yes then please test latest kernel version.

If it wont help then we cannot do anything about it I'm afraid (hardware change is needed).

Thanks
Please add [Solved] to your thread title if the solution was found.

brutus
Black ninja
Black ninja
Posts: 42
Joined: 20 May 2022, 06:10
Distribution: openSUSE

mapping hardware buttons?

Post#10 by brutus » 14 Jul 2022, 11:23

MX Linux: Bad luck. Standby doesn't work properly with its latest kernel (5.16.14).

I guess there's no other energy option in Porteus I could try, right? For sure all the same.

### Edit
dpms_idle works

User avatar
fanthom
Moderator Team
Moderator Team
Posts: 5666
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

mapping hardware buttons?

Post#11 by fanthom » 14 Jul 2022, 13:54

Kiosk boots fast so you may consider using 'halt_idle=' function for maximum power savings.

Thanks
Please add [Solved] to your thread title if the solution was found.

brutus
Black ninja
Black ninja
Posts: 42
Joined: 20 May 2022, 06:10
Distribution: openSUSE

mapping hardware buttons?

Post#12 by brutus » 18 Jul 2022, 07:31

Just fyi it works with Endeavour OS (Arch, 5.18.12 Kernel).
So time might come.

Locked