Control: tags -1 + moreinfo On Mon, 6 Feb 2017 15:45:20 +0100 "Milan P. Stanic" <m...@arvanta.net> wrote: > 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.
what's the output of evtest on those devices?
> 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
This looks quite a bit different here:
# evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: AT Translated Set 2 keyboard
/dev/input/event1: Lid Switch
/dev/input/event2: Sleep Button
/dev/input/event3: Power Button
...
Select the device event number [0-20]: 1
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x0 product 0x5 version 0x0
Input device name: "Lid Switch"
Supported events:
Event type 0 (EV_SYN)
Event type 5 (EV_SW)
Event code 0 (SW_LID) state 0
I wonder if logind does not detect the lid switch device as it
apparently also does all sort of other events.
Can you post the output of running
SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-logind
You need to stop the already running logind via
systemctl stop systemd-logind (make sure to run those commands from a
tty and not from within X)
--
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
