Closing Laptop Lid does not suspend in Gnome

shsina · 2016-10-25 19:59:23

Hi

I have searched a lot in google and forum and tried their solutions but the problem still exists.

and the systemd-logind doesn't report lid switch in the journal. I tried this command:

sudo journalctl -b -u systemd-logind

Last edited by shsina (2016-10-25 19:59:57)

seth · 2016-10-25 20:46:27

gnome on wayland? does it happen on gnome on xorg as well? (you can choose this on login, wayland is the default)

shsina · 2016-10-25 22:29:30

seth wrote:

gnome on wayland? does it happen on gnome on xorg as well? (you can choose this on login, wayland is the default)

It happens in both of them.

seth · 2016-10-26 06:39:41

Does it happen when not running gnome (eg. before logging in or running another desktop environment - try something simple like fluxbox or icewm etc) as well?
(ie. "gnome or udev issue")

shsina · 2016-10-26 08:43:08

seth wrote:

Does it happen when not running gnome (eg. before logging in or running another desktop environment - try something simple like fluxbox or icewm etc) as well?
(ie. "gnome or udev issue")

It happens in login screen too, so I think it is not cause of desktop env...

Last edited by shsina (2016-10-26 08:43:21)

seth · 2016-10-26 13:31:48

What does /etc/systemd/logind.conf look like?
Try adding/changing "HoldoffTimeoutSec=0s"
Is the lid switch monitored by "acpi_listen" running or "udevadm monitor" or mentioned in journalctl?

shsina · 2016-10-26 14:01:37

seth wrote:

What does /etc/systemd/logind.conf look like?

All commented. I have tested many solutions related to this file nothing work...

seth wrote:

Try adding/changing "HoldoffTimeoutSec=0s"

I have tried but nothing happend.

seth wrote:

Is the lid switch monitored by "acpi_listen" running or "udevadm monitor" or mentioned in journalctl?

I don't have "acpi_listen" installed.
"udevadm monitor": no.
"journalctl": no.

seth · 2016-10-26 14:28:17

Ensure /proc/acpi/button/lid/LID/state exists (the path may slightly differ depending on your hardware, but there should be some lid button in acpi or a dedicated hardware section like asus_whatever)
Run

sleep 20; cat /proc/acpi/button/lid/LID/state

Close the lid, get a cup of coffee, open the lid and check the output that should say "closed" when it was closed.
Run

cat /proc/acpi/button/lid/LID/state

and ensure it says open.

shsina · 2016-10-26 14:42:06

seth wrote:

Ensure /proc/acpi/button/lid/LID/state exists (the path may slightly differ depending on your hardware, but there should be some lid button in acpi or a dedicated hardware section like asus_whatever)
Run
sleep 20; cat /proc/acpi/button/lid/LID/state
Close the lid, get a cup of coffee, open the lid and check the output that should say "closed" when it was closed.
Run
cat /proc/acpi/button/lid/LID/state
and ensure it says open.

It always says "open".
I don't have "acpi" package installed, Shall I install it?

Last edited by shsina (2016-10-26 14:42:33)

seth · 2016-10-26 14:49:45

"acpi" is a client tool - nice to have, not mandatory.
Check "dmesg | grep -i acpi" for errors.

shsina · 2016-10-26 14:53:40

seth wrote:

Check "dmesg | grep -i acpi" for errors.

[    0.000000] BIOS-e820: [mem 0x000000007e047000-0x000000007e061fff] ACPI data
[    0.000000] BIOS-e820: [mem 0x000000007e062000-0x000000007e3c8fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x000000007ee82000-0x000000007f084fff] ACPI NVS
[    0.000000] ACPI: Early table checksum verification disabled
[    0.000000] ACPI: RSDP 0x00000000000F0490 000024 (v02 _ASUS_)
[    0.000000] ACPI: XSDT 0x000000007E04C080 000074 (v01 _ASUS_ Notebook 01072009 AMI  00010013)
[    0.000000] ACPI: FACP 0x000000007E05E980 00010C (v05 _ASUS_ Notebook 01072009 AMI  00010013)
[    0.000000] ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20160422/tbfadt-658)
[    0.000000] ACPI: DSDT 0x000000007E04C190 0127EC (v02 _ASUS_ Notebook 00000207 INTL 20051117)
[    0.000000] ACPI: FACS 0x000000007E3BE080 000040
[    0.000000] ACPI: APIC 0x000000007E05EA90 000072 (v03 _ASUS_ Notebook 01072009 AMI  00010013)
[    0.000000] ACPI: FPDT 0x000000007E05EB08 000044 (v01 _ASUS_ Notebook 01072009 AMI  00010013)
[    0.000000] ACPI: ECDT 0x000000007E05EB50 0000C1 (v01 _ASUS_ Notebook 01072009 AMI. 00000005)
[    0.000000] ACPI: MDSX 0x000000007E05EC18 000055 (v03 _ASUS_ Notebook 00000001 ASUS 00000001)
[    0.000000] ACPI: MCFG 0x000000007E05EC70 00003C (v01 _ASUS_ Notebook 01072009 MSFT 00010013)
[    0.000000] ACPI: HPET 0x000000007E05ECB0 000038 (v01 _ASUS_ Notebook 01072009 AMI  00000005)
[    0.000000] ACPI: SSDT 0x000000007E05ECE8 000A40 (v01 _ASUS_ Notebook 00000001 AMD  00000001)
[    0.000000] ACPI: SSDT 0x000000007E05F728 001F6E (v02 _ASUS_ Notebook 00000001 MSFT 04000000)
[    0.000000] ACPI: CRAT 0x000000007E061698 0002A8 (v01 _ASUS_ Notebook 00000001 AMD  00000001)
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] ACPI: PM-Timer IO Port: 0x808
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
[    0.000000] ACPI: IRQ0 used by override.
[    0.000000] ACPI: IRQ9 used by override.
[    0.000000] Using ACPI (MADT) for SMP configuration information
[    0.000000] ACPI: HPET id: 0x10228210 base: 0xfed00000
[    0.000032] ACPI: Core revision 20160422
[    0.009995] ACPI: 3 ACPI AML tables successfully acquired and loaded
[    0.386688] PM: Registering ACPI NVS region [mem 0x7e062000-0x7e3c8fff] (3567616 bytes)
[    0.386744] PM: Registering ACPI NVS region [mem 0x7ee82000-0x7f084fff] (2109440 bytes)
[    0.420187] ACPI: bus type PCI registered
[    0.420188] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[    0.436785] ACPI: Added _OSI(Module Device)
[    0.436785] ACPI: Added _OSI(Processor Device)
[    0.436785] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.436785] ACPI: Added _OSI(Processor Aggregator Device)
[    0.436785] ACPI : EC: EC description table is found, configuring boot EC
[    0.436785] ACPI : EC: EC started
[    0.437703] ACPI: Executed 1 blocks of module-level executable AML code
[    0.450636] ACPI : EC: EC stopped
[    0.450790] ACPI : EC: EC started
[    0.450885] ACPI: Interpreter enabled
[    0.450911] ACPI: (supports S0 S3 S4 S5)
[    0.450912] ACPI: Using IOAPIC for interrupt routing
[    0.451115] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
[    0.451131] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.475393] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[    0.475398] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[    0.475560] acpi PNP0A03:00: _OSC: platform does not support [PME]
[    0.475712] acpi PNP0A03:00: _OSC: OS now controls [PCIeHotplug AER PCIeCapability]
[    0.476905] pci 0000:00:10.0: System wakeup disabled by ACPI
[    0.477312] pci 0000:00:12.0: System wakeup disabled by ACPI
[    0.477556] pci 0000:00:12.2: System wakeup disabled by ACPI
[    0.477778] pci 0000:00:13.0: System wakeup disabled by ACPI
[    0.477955] pci 0000:00:13.2: System wakeup disabled by ACPI
[    0.478319] pci 0000:00:14.2: System wakeup disabled by ACPI
[    0.478679] pci 0000:00:14.4: System wakeup disabled by ACPI
[    0.479037] pci 0000:00:15.0: System wakeup disabled by ACPI
[    0.479221] pci 0000:00:15.1: System wakeup disabled by ACPI
[    0.479435] pci 0000:00:15.2: System wakeup disabled by ACPI
[    0.490701] pci 0000:04:00.0: System wakeup disabled by ACPI
[    0.500568] pci 0000:05:00.0: System wakeup disabled by ACPI
[    0.520397] ACPI: PCI Interrupt Link [LNKA] (IRQs 4 5 7 10 11 14 15) *0
[    0.520468] ACPI: PCI Interrupt Link [LNKB] (IRQs 4 5 7 10 11 14 15) *0
[    0.520538] ACPI: PCI Interrupt Link [LNKC] (IRQs 4 5 7 10 11 14 15) *0
[    0.520608] ACPI: PCI Interrupt Link [LNKD] (IRQs 4 5 7 10 11 14 15) *0
[    0.520664] ACPI: PCI Interrupt Link [LNKE] (IRQs 4 5 7 10 11 14 15) *0
[    0.520708] ACPI: PCI Interrupt Link [LNKF] (IRQs 4 5 7 10 11 14 15) *0
[    0.520751] ACPI: PCI Interrupt Link [LNKG] (IRQs 4 5 7 10 11 14 15) *0
[    0.520794] ACPI: PCI Interrupt Link [LNKH] (IRQs 4 5 7 10 11 14 15) *0
[    0.521158] ACPI: Enabled 1 GPEs in block 00 to 1F
[    0.521295] ACPI : EC: EC stopped
[    0.521377] ACPI : EC: GPE = 0xc, I/O: command/status = 0x66, data = 0x62
[    0.521377] ACPI : EC: EC started
[    0.521633] PCI: Using ACPI for IRQ routing
[    0.537657] pnp: PnP ACPI init
[    0.537828] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
[    0.537925] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.538281] system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.538317] pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
[    0.538363] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.538424] system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.538475] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.538540] pnp 00:07: Plug and Play ACPI device, IDs ETD0109 SYN1d00 SYN0002 PNP0f13 (active)
[    0.538581] pnp 00:08: Plug and Play ACPI device, IDs ATK3001 PNP0303 (active)
[    0.547140] pnp: PnP ACPI: found 9 devices
[    0.555125] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[    0.906316] ACPI: bus type USB registered
[    7.568005] acpi_cpufreq: overriding BIOS provided _PSD data
[    7.710226] ACPI: Video Device [VGA] (multi-head: yes  rom: no  post: no)
[    7.722696] ACPI Error: Method parse/execution failed [\_SB.PCI0.PCED.VGA.GCBL] (Node ffff880246c9de38), AE_AML_UNINITIALIZED_ELEMENT (20160422/psparse-542)
[    7.722703] ACPI Error: Method parse/execution failed [\_SB.PCI0.PCED.VGA.LCDD._BCM] (Node ffff880246c9df50), AE_AML_UNINITIALIZED_ELEMENT (20160422/psparse-542)
[    7.722708] ACPI Error: Evaluating _BCM failed (20160422/video-354)
[    7.761265] ACPI: Battery Slot [BAT0] (battery present)
[    7.761732] ACPI: Video Device [VGA1] (multi-head: yes  rom: no  post: no)
[    7.774732] ACPI Error: Method parse/execution failed [\_SB.PCI0.VGA.GCBL] (Node ffff880246ca1780), AE_AML_UNINITIALIZED_ELEMENT (20160422/psparse-542)
[    7.774748] ACPI Error: Method parse/execution failed [\_SB.PCI0.VGA.LCDD._BCM] (Node ffff880246ca1258), AE_AML_UNINITIALIZED_ELEMENT (20160422/psparse-542)
[    7.774757] ACPI Error: Evaluating _BCM failed (20160422/video-354)
[    7.885452] ACPI: AC Adapter [AC0] (on-line)
[    7.893582] ACPI: Lid Switch [LID]
[    7.893715] ACPI: Power Button [PWRB]
[    7.893860] ACPI: Sleep Button [SLPB]
[    7.894006] ACPI: Power Button [PWRF]
[    7.925613] ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B07 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B0F (\SMBX) (20160422/utaddress-255)
[    7.925626] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    7.997234] ACPI: Thermal Zone [THRM] (75 C)

seth · 2016-10-26 18:33:31

Unsuspicious to me. Kernel bug or hardware fault. Do we know the switch is good (ie. does it work on some random live linux or windows?)

shsina · 2016-10-26 18:59:24

seth wrote:

Unsuspicious to me. Kernel bug or hardware fault. Do we know the switch is good (ie. does it work on some random live linux or windows?)

I have tested it on Ubuntu Gnome 16.10, It doesn't work there too. I think it doesn't work in Ubuntu Gnome 16.04 which I had in past.

You asked about Windows, I have to say to you that every thing works well in windows, at the moment my laptop's bluetooth and lid doesn't work in Linux and I have a problem with Apache in Arch but with All of these problems I love Linux specially Arch

Thanks for your help

Last edited by shsina (2016-10-26 19:01:55)

seth · 2016-10-26 20:20:10

Bogus acpi? Googled hardware specs on the particular issue (along linux)?

shsina · 2016-10-26 20:28:09

seth wrote:

Bogus acpi?

Sry I can't understand what you mean...

seth wrote:

Googled hardware specs on the particular issue (along linux)?

Which issue you mean? this issue? I don't know my lid's model so I can't google it.
But if you mean bluetooth issue, there is a driver for it in AUR but it doesn't work on Linux kernel version >4.5.

seth · 2016-10-26 20:36:38

Vendors often don't really implement the ACPI specs but just TAE until it works with their windows version :-(
Which exact notebook is it? (Vendor seems asus, model would be?)

shsina · 2016-10-26 20:39:11

seth wrote:

Vendors often don't really implement the ACPI specs but just TAE until it works with their windows version :-(
Which exact notebook is it? (Vendor seems asus, model would be?)

ASUS X550DP

seth · 2016-10-26 21:07:52

in grub, add "acpi_osi=" to the kernel parameters (w/o quotes, really ends with the '=')
If not, you could try "acpi_force_32bit_fadt_addr" instead.

The relevant part is to get /proc/acpi/button/lid/LID/state alter its content.

shsina · 2016-10-26 21:15:00

seth wrote:

in grub, add "acpi_osi=" to the kernel parameters (w/o quotes, really ends with the '=')
If not, you could try "acpi_force_32bit_fadt_addr" instead.
The relevant part is to get /proc/acpi/button/lid/LID/state alter its content.

You mean /boot/grub/grub.cfg file?
I should add this variable without any value to end of the file?

seth · 2016-10-26 21:23:42

No, when booting, select the entry and press [e]dit, there append this to the line which has "quiet" on the end.
This way you do not mess around with the installed system - if anything goes wrong, simply rebooting (hard, in doubt) will clear the stage.

shsina · 2016-10-27 00:08:29

seth wrote:

No, when booting, select the entry and press [e]dit, there append this to the line which has "quiet" on the end.
This way you do not mess around with the installed system - if anything goes wrong, simply rebooting (hard, in doubt) will clear the stage.

Unfortunately same result...
/proc/acpi/button/lid/LID/state still say open.

Last edited by shsina (2016-10-27 00:11:41)

shsina · 2016-10-27 00:12:32

seth wrote:

The relevant part is to get /proc/acpi/button/lid/LID/state alter its content.

You mean manually changing it to close?

seth · 2016-10-27 14:03:30

Yes. Unless there's another lid somewhere else in /proc, this is (and should be) what all userspace tools build upon.
What's the output of "lsmod | grep asus"?
Just to be sure, suspending the device with "systemctl suspend" works as it should?

shsina · 2016-10-27 15:20:27

seth wrote:

What's the output of "lsmod | grep asus"?

asus_nb_wmi            24576  0
asus_wmi               24576  1 asus_nb_wmi
sparse_keymap          16384  2 asus_wmi,toshiba_wmi
rfkill                 20480  5 asus_wmi,cfg80211
asus_wireless          16384  0
wmi                    16384  2 asus_wmi,toshiba_wmi
video                  36864  1 asus_wmi
led_class              16384  5 asus_wmi,rt2x00lib,sdhci,input_leds,asus_wireless

seth wrote:

Just to be sure, suspending the device with "systemctl suspend" works as it should?

Yes. It works.

seth · 2016-10-27 15:21:57

Wild guess, "modprobe asus-laptop"
Then I'm out of ideas :-(

Arch Linux

#1 2016-10-25 19:59:23

Closing Laptop Lid does not suspend in Gnome

#2 2016-10-25 20:46:27

Re: Closing Laptop Lid does not suspend in Gnome

#3 2016-10-25 22:29:30

Re: Closing Laptop Lid does not suspend in Gnome

#4 2016-10-26 06:39:41

Re: Closing Laptop Lid does not suspend in Gnome

#5 2016-10-26 08:43:08

Re: Closing Laptop Lid does not suspend in Gnome

#6 2016-10-26 13:31:48

Re: Closing Laptop Lid does not suspend in Gnome

#7 2016-10-26 14:01:37

Re: Closing Laptop Lid does not suspend in Gnome

#8 2016-10-26 14:28:17

Re: Closing Laptop Lid does not suspend in Gnome

#9 2016-10-26 14:42:06

Re: Closing Laptop Lid does not suspend in Gnome

#10 2016-10-26 14:49:45

Re: Closing Laptop Lid does not suspend in Gnome

#11 2016-10-26 14:53:40

Re: Closing Laptop Lid does not suspend in Gnome

#12 2016-10-26 18:33:31

Re: Closing Laptop Lid does not suspend in Gnome

#13 2016-10-26 18:59:24

Re: Closing Laptop Lid does not suspend in Gnome

#14 2016-10-26 20:20:10

Re: Closing Laptop Lid does not suspend in Gnome

#15 2016-10-26 20:28:09

Re: Closing Laptop Lid does not suspend in Gnome

#16 2016-10-26 20:36:38

Re: Closing Laptop Lid does not suspend in Gnome

#17 2016-10-26 20:39:11

Re: Closing Laptop Lid does not suspend in Gnome

#18 2016-10-26 21:07:52

Re: Closing Laptop Lid does not suspend in Gnome

#19 2016-10-26 21:15:00

Re: Closing Laptop Lid does not suspend in Gnome

#20 2016-10-26 21:23:42

Re: Closing Laptop Lid does not suspend in Gnome

#21 2016-10-27 00:08:29

Re: Closing Laptop Lid does not suspend in Gnome

#22 2016-10-27 00:12:32

Re: Closing Laptop Lid does not suspend in Gnome

#23 2016-10-27 14:03:30

Re: Closing Laptop Lid does not suspend in Gnome

#24 2016-10-27 15:20:27

Re: Closing Laptop Lid does not suspend in Gnome

#25 2016-10-27 15:21:57

Re: Closing Laptop Lid does not suspend in Gnome

Board footer