Your message dated Fri, 7 Sep 2018 19:11:51 +0200
with message-id <[email protected]>
and subject line Re: systemd: lid switch not detected on acer chromebook
has caused the Debian Bug report #854388,
regarding systemd: lid switch not detected on acer chromebook
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
854388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854388
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 232-15
Severity: normal
Dear Maintainer,
* What led up to the situation?
Installed Debian on the acer chromebook R13 (mediatek MT8173 SOC,
board called elm (oak)) armv8 with the kernel source from chromeos
site and built myself for that device.
* What exactly did you do (or not do) that was effective (or
ineffective)?
By closing screen logind does not detect lid switch
* What was the outcome of this action?
Device does not suspend
* What outcome did you expect instead?
Suspend
During boot kernel recognizes that the device have lid switch, here is
the log from journalctl:
Feb 05 17:20:01 zarya kernel: of_get_named_gpiod_flags: parsed 'gpios' property
of node '/gpio-keys/lid[0]' - status (0)
Feb 05 17:20:01 zarya kernel: of_get_named_gpiod_flags: parsed 'gpios' property
of node '/gpio-keys/power[0]' - status (0)
Feb 05 17:20:01 zarya kernel: of_get_named_gpiod_flags: parsed 'gpios' property
of node '/gpio-keys/tablet_mode[0]' - status (0)
Feb 05 17:20:01 zarya kernel: of_get_named_gpiod_flags: parsed 'gpios' property
of node '/gpio-keys/volume_down[0]' - status (0)
Feb 05 17:20:01 zarya kernel: of_get_named_gpiod_flags: parsed 'gpios' property
of node '/gpio-keys/volume_up[0]' - status (0)
Feb 05 17:20:01 zarya kernel: input: gpio-keys as
/devices/gpio-keys/input/input5
but systemd-logind does not report that it is watching any of these
keys, as it does on another armv7 or amd64 where I tested lid switch.
evtest detect all these when I run it to test does kernel works, here it
is output of invoking it:
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: cros_ec
/dev/input/event1: Elan Touchscreen
/dev/input/event2: Elan Touchpad
/dev/input/event3: mtk-rt5650 Headset Jack
/dev/input/event4: mtk-rt5650 HDMI Jack
/dev/input/event5: gpio-keys
Select the device event number [0-5]: 5
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100
Input device name: "gpio-keys"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 114 (KEY_VOLUMEDOWN)
Event code 115 (KEY_VOLUMEUP)
Event code 116 (KEY_POWER)
Event type 5 (EV_SW)
Event code 0 (SW_LID) state 0
Event code 1 (SW_TABLET_MODE) state 0
Properties:
Testing ... (interrupt to exit)
Event: time 1486391966.918428, type 5 (EV_SW), code 0 (SW_LID), value 1
Event: time 1486391966.918428, -------------- SYN_REPORT ------------
Event: time 1486391968.734410, type 5 (EV_SW), code 0 (SW_LID), value 0
Event: time 1486391968.734410, -------------- SYN_REPORT ------------
-- Package-specific info:
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (600, 'testing'), (400, 'unstable')
Architecture: arm64 (aarch64)
Kernel: Linux 3.18.0-5-oak (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii adduser 3.115
ii libacl1 2.2.52-3
ii libapparmor1 2.11.0-2
ii libaudit1 1:2.6.7-1
ii libblkid1 2.29.1-1
ii libc6 2.24-9
ii libcap2 1:2.25-1
ii libcryptsetup4 2:1.7.3-3
ii libgcrypt20 1.7.6-1
ii libgpg-error0 1.26-2
ii libidn11 1.33-1
ii libip4tc0 1.6.0+snapshot20161117-5
ii libkmod2 23-2
ii liblz4-1 0.0~r131-2
ii liblzma5 5.2.2-1.2
ii libmount1 2.29.1-1
ii libpam0g 1.1.8-3.5
ii libseccomp2 2.3.1-2.1
ii libselinux1 2.6-3
ii libsystemd0 232-15
ii mount 2.29.1-1
ii util-linux 2.29.1-1
Versions of packages systemd recommends:
ii dbus 1.10.14-1
ii libpam-systemd 232-15
Versions of packages systemd suggests:
ii policykit-1 0.105-17
pn systemd-container <none>
pn systemd-ui <none>
Versions of packages systemd is related to:
pn dracut <none>
pn initramfs-tools <none>
ii udev 232-15
-- Configuration Files:
/etc/systemd/logind.conf changed:
[Login]
HandlePowerKey=suspend
HandleSuspendKey=suspend
HandleLidSwitch=suspend
SuspendKeyIgnoreInhibited=no
HibernateKeyIgnoreInhibited=no
LidSwitchIgnoreInhibited=yes
IdleAction=suspend
IdleActionSec=3min
-- no debconf information
--- End Message ---
--- Begin Message ---
Am 07.09.18 um 11:54 schrieb Milan P. Stanic:
> Dear Michael,
>
> I gave that acer chromebook to another person before more than one and a
> half year, so I can't check how it works now regarding that systemd
> problem. I have another chromebook (samsung one plus) but it works under
> Alpine Linux and openrc so I cannot test Debian systemd on it.
Apologies that we didn't get back to you in a more timely manner.
Given that you can no longer test if the system is still affected or
test a possible fix, I'd say it's best to close this bug at this point.
Should you ever run Debian again on this chromebook and you can still
reproduce the problem, please either file a new bug report or let use
know and we can reopen this one.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
