You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2019-03-22 21:17:29
- fwillo
- Member
- Registered: 2019-03-22
- Posts: 5
Wakeup on LID not available (?)
Dear all,
I recently installed Arch on my notebook and I cannot complain at all. The notebook is working almost compleatly out of the box. However, a list of few things are not working as wanted. I'll address them separately in other threads though. Here, I have the following problem:
I'm using a Samsung 530U4E-S02. This notebook has two GPUs. A Radeon HD8750M and the integrated Intel GPU HD 4000 (from an i5-3337U). I installed budgie-desktop with gnome and I'm running GDM as Display Manager. Also I installed xf86-video-amdgpu as well as xf86-video-intel.
A feature I had on windows was wakeup from Standby when opening the lid of the notebook after I closed it before. This is not working on Arch though. I tried to figure out what the problem is. I read of people wanting to disable this feature, which is possible with "echo LID > /proc/acpi/wakeup". When examining the content of this "file", the output is:
$ cat /proc/acpi/wakeup
Device S-state Status Sysfs node
RP01 S4 *disabled pci:0000:00:1c.0
RP04 S4 *disabled pci:0000:00:1c.3
PEG0 S4 *disabled pci:0000:00:01.0
PEGP S4 *disabled pci:0000:01:00.0
PEGA S4 *disabled
PEG1 S4 *disabled
PEG2 S4 *disabled
PEG3 S4 *disabled
PWRB S5 *enabled platform:PNP0C0C:00It seems like the LID is not detected at all. Do I have to compile a custom kernel for this? My research one the Internet did not yield a useful information. Maybe somebody of you has an idea.
Looking forward to your answers!
Best wishes,
fwillo
Last edited by fwillo (2019-03-22 21:27:13)
Offline
#2 2019-03-22 22:36:49
- ewaller
- Administrator
- From: Pasadena, CA
- Registered: 2009-07-13
- Posts: 19,772
Re: Wakeup on LID not available (?)
You might try lying to ACPI about what OS is running. Here is an article on the topic:
https://wiki.archlinux.org/index.php/DSDT
see section 1.1
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
#3 2019-03-22 23:44:41
- fwillo
- Member
- Registered: 2019-03-22
- Posts: 5
Re: Wakeup on LID not available (?)
Hey,
thanks for the reply. I tried the OS names suggested in the article. Unfortunately, this did not work out. I copied the dmesg filtered with the ACPI keyword here. Interestingly, the LID0 "button" is recognized, but not listed as option in wakeup. Should I try the other points in the DSDT article?
[ 0.000000] Command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/sda2 rw radeon.si_support=0 amdgpu.si_support=1 radeon.cik_support=0 amdgpu.cik_support=1 acpi_os_name="Microsoft Windows XP" initrd=../initramfs-linux.img
[ 0.000000] BIOS-e820: [mem 0x00000000c9922000-0x00000000c9931fff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x00000000c9932000-0x00000000c9f67fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000ca851000-0x00000000ca893fff] ACPI NVS
[ 0.031327] ACPI: Early table checksum verification disabled
[ 0.034553] ACPI: RSDP 0x00000000000F0490 000024 (v02 SECCSD)
[ 0.034557] ACPI: XSDT 0x00000000C9925088 00008C (v01 SECCSD LH43STAR 01072009 AMI 00010013)
[ 0.034565] ACPI: FACP 0x00000000C992E540 00010C (v05 SECCSD LH43STAR 01072009 AMI 00010013)
[ 0.034573] ACPI: DSDT 0x00000000C99251A0 00939A (v02 SECCSD LH43STAR 00000024 INTL 20051117)
[ 0.034578] ACPI: FACS 0x00000000C9F65080 000040
[ 0.034582] ACPI: APIC 0x00000000C992E650 000072 (v03 SECCSD LH43STAR 01072009 AMI 00010013)
[ 0.034586] ACPI: FPDT 0x00000000C992E6C8 000044 (v01 SECCSD LH43STAR 01072009 AMI 00010013)
[ 0.034590] ACPI: MCFG 0x00000000C992E710 00003C (v01 SECCSD LH43STAR 01072009 MSFT 00000097)
[ 0.034594] ACPI: MSDM 0x00000000C992E750 000055 (v03 SECCSD LH43STAR 01072009 AMI 00010013)
[ 0.034599] ACPI: HPET 0x00000000C992E7A8 000038 (v01 SECCSD LH43STAR 01072009 AMI. 00000005)
[ 0.034603] ACPI: SSDT 0x00000000C992E7E0 000315 (v01 SataRe SataTabl 00001000 INTL 20091112)
[ 0.034608] ACPI: SSDT 0x00000000C992EAF8 0008FC (v01 PmRef Cpu0Ist 00003000 INTL 20051117)
[ 0.034612] ACPI: SSDT 0x00000000C992F3F8 000B0E (v01 PmRef CpuPm 00003000 INTL 20051117)
[ 0.034617] ACPI: DMAR 0x00000000C992FF08 0000B8 (v01 INTEL SNB 00000001 INTL 00000001)
[ 0.034621] ACPI: BGRT 0x00000000C992FFC0 000038 (v00 SECCSD LH43STAR 01072009 AMI 00010013)
[ 0.034627] ACPI: SSDT 0x00000000C992FFF8 0007E3 (v01 SgRef SgTabl 00001000 INTL 20051117)
[ 0.034631] ACPI: SSDT 0x00000000C99307E0 000E2B (v01 AmdRef AmdTabl 00001000 INTL 20051117)
[ 0.034646] ACPI: Local APIC address 0xfee00000
[ 0.115121] ACPI: PM-Timer IO Port: 0x408
[ 0.115124] ACPI: Local APIC address 0xfee00000
[ 0.115134] ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
[ 0.115150] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
[ 0.115152] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.115154] ACPI: IRQ0 used by override.
[ 0.115155] ACPI: IRQ9 used by override.
[ 0.115158] Using ACPI (MADT) for SMP configuration information
[ 0.115160] ACPI: HPET id: 0x8086a701 base: 0xfed00000
[ 0.304725] Kernel command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/sda2 rw radeon.si_support=0 amdgpu.si_support=1 radeon.cik_support=0 amdgpu.cik_support=1 acpi_os_name="Microsoft Windows XP" initrd=../initramfs-linux.img
[ 0.361587] ACPI: Core revision 20181213
[ 0.361716] ACPI: Overriding _OS definition to 'Microsoft Windows XP'
[ 0.569584] PM: Registering ACPI NVS region [mem 0xc9932000-0xc9f67fff] (6512640 bytes)
[ 0.569584] PM: Registering ACPI NVS region [mem 0xca851000-0xca893fff] (274432 bytes)
[ 0.569584] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[ 0.569584] ACPI: bus type PCI registered
[ 0.569584] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[ 0.572954] ACPI: Added _OSI(Module Device)
[ 0.572954] ACPI: Added _OSI(Processor Device)
[ 0.572954] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.572954] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.572954] ACPI: Added _OSI(Linux-Dell-Video)
[ 0.572954] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[ 0.572954] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
[ 0.586370] ACPI: 6 ACPI AML tables successfully acquired and loaded
[ 0.588899] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 0.590186] ACPI: Dynamic OEM Table Load:
[ 0.590195] ACPI: SSDT 0xFFFF93D9A5A3D000 000775 (v01 PmRef Cpu0Cst 00003001 INTL 20051117)
[ 0.590560] ACPI: Dynamic OEM Table Load:
[ 0.590560] ACPI: SSDT 0xFFFF93D9A5A86400 000303 (v01 PmRef ApIst 00003000 INTL 20051117)
[ 0.592064] ACPI: Dynamic OEM Table Load:
[ 0.592069] ACPI: SSDT 0xFFFF93D9A5423E00 000119 (v01 PmRef ApCst 00003000 INTL 20051117)
[ 0.593328] ACPI: EC: EC started
[ 0.593329] ACPI: EC: interrupt blocked
[ 1.032932] ACPI: \_SB_.PCI0.LPCB.H_EC: Used as first EC
[ 1.032935] ACPI: \_SB_.PCI0.LPCB.H_EC: GPE=0x17, EC_CMD/EC_SC=0x66, EC_DATA=0x62
[ 1.032937] ACPI: \_SB_.PCI0.LPCB.H_EC: Used as boot DSDT EC to handle transactions
[ 1.032938] ACPI: Interpreter enabled
[ 1.032984] ACPI: (supports S0 S3 S4 S5)
[ 1.032985] ACPI: Using IOAPIC for interrupt routing
[ 1.033035] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 1.033488] ACPI: Enabled 6 GPEs in block 00 to 3F
[ 1.044121] ACPI: Power Resource [FN00] (off)
[ 1.044270] ACPI: Power Resource [FN01] (off)
[ 1.045516] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
[ 1.045525] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[ 1.046047] acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug SHPCHotplug PME]
[ 1.046376] acpi PNP0A08:00: _OSC: OS now controls [AER PCIeCapability LTR]
[ 1.046378] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration
[ 1.054795] ACPI: PCI Interrupt Link [LNKA] (IRQs 5 7 10 *11)
[ 1.054905] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 7 10 11) *0, disabled.
[ 1.055013] ACPI: PCI Interrupt Link [LNKC] (IRQs 5 7 10 *11)
[ 1.055121] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 7 *10 11)
[ 1.055232] ACPI: PCI Interrupt Link [LNKE] (IRQs 5 7 10 11) *0, disabled.
[ 1.055340] ACPI: PCI Interrupt Link [LNKF] (IRQs 5 7 10 11) *0, disabled.
[ 1.055448] ACPI: PCI Interrupt Link [LNKG] (IRQs *5 7 10 11)
[ 1.055555] ACPI: PCI Interrupt Link [LNKH] (IRQs 5 *7 10 11)
[ 1.065213] ACPI: EC: interrupt unblocked
[ 1.065213] ACPI: EC: event unblocked
[ 1.065213] ACPI: \_SB_.PCI0.LPCB.H_EC: GPE=0x17, EC_CMD/EC_SC=0x66, EC_DATA=0x62
[ 1.065213] ACPI: \_SB_.PCI0.LPCB.H_EC: Used as boot DSDT EC to handle transactions and events
[ 1.065414] ACPI: bus type USB registered
[ 1.065633] PCI: Using ACPI for IRQ routing
[ 1.083669] pnp: PnP ACPI init
[ 1.083843] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
[ 1.084024] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 1.084107] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
[ 1.084194] system 00:03: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
[ 1.084289] pnp 00:04: Plug and Play ACPI device, IDs MSF0001 PNP0303 (active)
[ 1.084359] pnp 00:05: Plug and Play ACPI device, IDs ETD0b00 PNP0f13 (active)
[ 1.084446] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 1.084911] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 1.087076] system 00:08: Plug and Play ACPI device, IDs PNP0c01 (active)
[ 1.087133] pnp: PnP ACPI: found 9 devices
[ 1.093549] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[ 1.602941] ACPI: Lid Switch [LID0]
[ 1.605278] ACPI: Power Button [PWRB]
[ 1.608581] ACPI: Power Button [PWRF]
[ 1.610375] ACPI: Invalid active2 threshold
[ 1.630263] ACPI: Thermal Zone [TZ00] (41 C)
[ 1.660206] ACPI: Thermal Zone [TZ01] (41 C)
[ 2.874912] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[ 2.874924] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[ 2.874932] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[ 2.875017] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[ 2.875023] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[ 2.875031] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[ 2.877095] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[ 2.877106] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[ 2.877119] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[ 2.879316] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[ 2.879322] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[ 2.879327] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[ 3.716642] ACPI: AC Adapter [ADP1] (on-line)
[ 3.791990] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20181213/utaddress-213)
[ 3.791998] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 3.792003] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000055F (\_SB.PCI0.PEG0.PEGP.GPIO) (20181213/utaddress-213)
[ 3.792008] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20181213/utaddress-213)
[ 3.792013] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 3.792015] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000055F (\_SB.PCI0.PEG0.PEGP.GPIO) (20181213/utaddress-213)
[ 3.792019] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20181213/utaddress-213)
[ 3.792023] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 3.792025] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000055F (\_SB.PCI0.PEG0.PEGP.GPIO) (20181213/utaddress-213)
[ 3.792029] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20181213/utaddress-213)
[ 3.792033] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 3.863377] battery: ACPI: Battery Slot [BAT1] (battery present)
[ 4.642854] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS
[ 4.643792] ACPI: Video Device [PEGP] (multi-head: yes rom: no post: no)
[ 4.661269] acpi device:07: registered as cooling_device7
[ 4.663014] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
[ 4.698490] acpi device:15: registered as cooling_device8Offline
#4 2019-03-25 11:03:38
- fwillo
- Member
- Registered: 2019-03-22
- Posts: 5
Re: Wakeup on LID not available (?)
Hey,
I tried fixing the DSDT as suggested in the article. Recompiling led to the output of
$ iasl -tc dsdt.dsl
Intel ACPI Component Architecture
ASL+ Optimizing Compiler/Disassembler version 20190215
Copyright (c) 2000 - 2019 Intel Corporation
dsdt.dsl 2023: CreateDWordField (BUF0, \_SB.PCI0._Y0F._LEN, MSLN) // _LEN: Length
Warning 3128 - ResourceTag larger than Field ^ (Size mismatch, Tag: 64 bits, Field: 32 bits)
dsdt.dsl 3128: Method (_CRS, 0, NotSerialized) // _CRS: Current Resource Settings
Remark 2120 - ^ Control Method should be made Serialized (due to creation of named objects within)
dsdt.dsl 4763: Method (SPTS, 1, NotSerialized)
Remark 2146 - ^ Method Argument is never used (Arg0)
dsdt.dsl 4769: Method (SWAK, 1, NotSerialized)
Remark 2146 - ^ Method Argument is never used (Arg0)
dsdt.dsl 4839: Method (UXDV, 1, NotSerialized)
Remark 2120 - ^ Control Method should be made Serialized (due to creation of named objects within)
dsdt.dsl 4842: Name (_T_0, Zero) // _T_x: Emitted by ASL Compiler, x=0-9, A-Z
Remark 2011 - ^ Use of compiler reserved name (_T_0)
dsdt.dsl 4880: Method (RRIO, 4, NotSerialized)
Remark 2146 - ^ Method Argument is never used (Arg3)
dsdt.dsl 4880: Method (RRIO, 4, NotSerialized)
Remark 2120 - ^ Control Method should be made Serialized (due to creation of named objects within)
dsdt.dsl 4882: Name (_T_0, Zero) // _T_x: Emitted by ASL Compiler, x=0-9, A-Z
Remark 2011 - ^ Use of compiler reserved name (_T_0)
dsdt.dsl 5087: Method (RDMA, 3, NotSerialized)
Remark 2146 - ^ Method Argument is never used (Arg0)
dsdt.dsl 5087: Method (RDMA, 3, NotSerialized)
Remark 2146 - ^ Method Argument is never used (Arg1)
dsdt.dsl 5087: Method (RDMA, 3, NotSerialized)
Remark 2146 - ^ Method Argument is never used (Arg2)
dsdt.dsl 5100: Method (NPTS, 1, NotSerialized)
Remark 2146 - ^ Method Argument is never used (Arg0)
dsdt.dsl 5111: Method (NWAK, 1, NotSerialized)
Remark 2146 - ^ Method Argument is never used (Arg0)
dsdt.dsl 5189: Method (_DOD, 0, NotSerialized) // _DOD: Display Output Devices
Remark 2120 - ^ Control Method should be made Serialized (due to creation of named objects within)
dsdt.dsl 5611: Method (_BCM, 1, Serialized) // _BCM: Brightness Control Method
Warning 3115 - ^ Not all control paths return a value (_BCM)
dsdt.dsl 6579: Sleep (ASLP)
Remark 2159 - ^ Very long Sleep, greater than 1 second
dsdt.dsl 6589: Sleep (ASLP)
Remark 2159 - ^ Very long Sleep, greater than 1 second
dsdt.dsl 6658: Sleep (ASLP)
Remark 2159 - ^ Very long Sleep, greater than 1 second
dsdt.dsl 7520: If (CondRefOf (_OSI, Local0))
Warning 3144 - Method Local is set but never used ^ (Local0)
dsdt.dsl 8521: Name (_T_0, Zero) // _T_x: Emitted by ASL Compiler, x=0-9, A-Z
Remark 2011 - Use of compiler reserved name ^ (_T_0)
dsdt.dsl 8600: Name (_T_0, Zero) // _T_x: Emitted by ASL Compiler, x=0-9, A-Z
Remark 2011 - Use of compiler reserved name ^ (_T_0)
dsdt.dsl 8679: Name (_T_0, Zero) // _T_x: Emitted by ASL Compiler, x=0-9, A-Z
Remark 2011 - Use of compiler reserved name ^ (_T_0)
dsdt.dsl 8758: Name (_T_0, Zero) // _T_x: Emitted by ASL Compiler, x=0-9, A-Z
Remark 2011 - Use of compiler reserved name ^ (_T_0)
dsdt.dsl 9041: PLD_Revision = 0x2,
Error 6105 - Invalid object type for reserved name ^ (_PLD: found Buffer, Package required)
dsdt.dsl 9076: Name (_T_0, Zero) // _T_x: Emitted by ASL Compiler, x=0-9, A-Z
Remark 2011 - Use of compiler reserved name ^ (_T_0)
dsdt.dsl 9155: Name (_T_0, Zero) // _T_x: Emitted by ASL Compiler, x=0-9, A-Z
Remark 2011 - Use of compiler reserved name ^ (_T_0)
dsdt.dsl 9234: Name (_T_0, Zero) // _T_x: Emitted by ASL Compiler, x=0-9, A-Z
Remark 2011 - Use of compiler reserved name ^ (_T_0)
dsdt.dsl 9305: Method (POSC, 3, Serialized)
Remark 2146 - ^ Method Argument is never used (Arg0)
dsdt.dsl 10077: Method (_HID, 0, NotSerialized) // _HID: Hardware ID
Warning 3115 - ^ Not all control paths return a value (_HID)
dsdt.dsl 10077: Method (_HID, 0, NotSerialized) // _HID: Hardware ID
Warning 3107 - ^ Reserved method must return a value (Integer/String required for _HID)
dsdt.dsl 10135: Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method
Remark 2120 - ^ Control Method should be made Serialized (due to creation of named objects within)
dsdt.dsl 10139: Name (_T_0, Zero) // _T_x: Emitted by ASL Compiler, x=0-9, A-Z
Remark 2011 - ^ Use of compiler reserved name (_T_0)
dsdt.dsl 10293: Name (_T_1, Zero) // _T_x: Emitted by ASL Compiler, x=0-9, A-Z
Remark 2011 - ^ Use of compiler reserved name (_T_1)
dsdt.dsl 10393: Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method
Remark 2120 - ^ Control Method should be made Serialized (due to creation of named objects within)
dsdt.dsl 10397: Name (_T_0, Zero) // _T_x: Emitted by ASL Compiler, x=0-9, A-Z
Remark 2011 - ^ Use of compiler reserved name (_T_0)
dsdt.dsl 10500: Name (_T_1, Zero) // _T_x: Emitted by ASL Compiler, x=0-9, A-Z
Remark 2011 - ^ Use of compiler reserved name (_T_1)
dsdt.dsl 10577: Name (_HID, "pnp0c14") // _HID: Hardware ID
Error 6136 - ^ Non-hex letters must be upper case (pnp0c14)
dsdt.dsl 10587: Method (WQ00, 1, NotSerialized)
Remark 2146 - ^ Method Argument is never used (Arg0)
dsdt.dsl 10592: Method (WM00, 3, NotSerialized)
Remark 2146 - ^ Method Argument is never used (Arg0)
dsdt.dsl 10592: Method (WM00, 3, NotSerialized)
Remark 2146 - ^ Method Argument is never used (Arg1)
ASL Input: dsdt.dsl - 10715 lines, 342466 bytes, 4580 keywords
Hex Dump: dsdt.hex - 356939 bytes
Compilation complete. 2 Errors, 5 Warnings, 34 Remarks, 83 Optimizations... which was fixed with ... (thanks to http://forum.notebookreview.com/threads … /page-1187)
# Correction made per vim result in...
$ diff dsdt_mod.dsl dsdt.dsl
21c21
< DefinitionBlock ("", "DSDT", 2, "SECCSD", "LH43STAR", 0x00000025)
---
> DefinitionBlock ("", "DSDT", 2, "SECCSD", "LH43STAR", 0x00000024)
9040c9040
< Name (_PLD, Package() {ToPLD (
---
> Name (_PLD, ToPLD (
9067c9067
< PLD_HorizontalOffset = 0xBE)}
---
> PLD_HorizontalOffset = 0xBE)
10577c10577
< Name (_HID, "PNP0C14") // _HID: Hardware ID
---
> Name (_HID, "pnp0c14") // _HID: Hardware IDThis got loaded with syslinux correctly, as shown in the following excerpt:
$ dmesg | grep -i dsdt
[ 0.031947] ACPI: DSDT ACPI table found in initrd [kernel/firmware/acpi/dsdt.aml][0x948e]
[ 0.035264] ACPI: Table Upgrade: override [DSDT-SECCSD-LH43STAR]
[ 0.035267] ACPI: DSDT 0x00000000C99251A0 Physical table override, new table: 0x00000000CAFF6000
[ 0.035271] ACPI: DSDT 0x00000000CAFF6000 00948E (v02 SECCSD LH43STAR 00000025 INTL 20190215)However, this did not the trick. LID0 still is not listed as wakeup option in /proc/acpi/wakeup. Did I miss something in the output of recompilation? Suggestions are welcome!
Best,
fwillo
Last edited by fwillo (2019-03-25 11:04:40)
Offline
#5 2019-03-26 09:50:43
- fwillo
- Member
- Registered: 2019-03-22
- Posts: 5
Re: Wakeup on LID not available (?)
Hey,
I think for further discussion, some more information might be interesting:
$ dmesg | grep -i lid
[ 0.361966] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.
[ 1.603174] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
[ 1.603184] ACPI: Lid Switch [LID0]
[ 1.608977] ACPI: Invalid active2 threshold# tree /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/
├── driver -> ../../../../bus/acpi/drivers/button
├── hid
├── input
│ └── input0
│ ├── capabilities
│ │ ├── abs
│ │ ├── ev
│ │ ├── ff
│ │ ├── key
│ │ ├── led
│ │ ├── msc
│ │ ├── rel
│ │ ├── snd
│ │ └── sw
│ ├── device -> ../../../PNP0C0D:00
│ ├── event0
│ │ ├── dev
│ │ ├── device -> ../../input0
│ │ ├── power
│ │ │ ├── async
│ │ │ ├── autosuspend_delay_ms
│ │ │ ├── control
│ │ │ ├── runtime_active_kids
│ │ │ ├── runtime_active_time
│ │ │ ├── runtime_enabled
│ │ │ ├── runtime_status
│ │ │ ├── runtime_suspended_time
│ │ │ └── runtime_usage
│ │ ├── subsystem -> ../../../../../../../class/input
│ │ └── uevent
│ ├── id
│ │ ├── bustype
│ │ ├── product
│ │ ├── vendor
│ │ └── version
│ ├── modalias
│ ├── name
│ ├── phys
│ ├── power
│ │ ├── async
│ │ ├── autosuspend_delay_ms
│ │ ├── control
│ │ ├── runtime_active_kids
│ │ ├── runtime_active_time
│ │ ├── runtime_enabled
│ │ ├── runtime_status
│ │ ├── runtime_suspended_time
│ │ └── runtime_usage
│ ├── properties
│ ├── subsystem -> ../../../../../../class/input
│ ├── uevent
│ └── uniq
├── modalias
├── path
├── physical_node -> ../../../platform/PNP0C0D:00
├── power
│ ├── async
│ ├── autosuspend_delay_ms
│ ├── control
│ ├── runtime_active_kids
│ ├── runtime_active_time
│ ├── runtime_enabled
│ ├── runtime_status
│ ├── runtime_suspended_time
│ ├── runtime_usage
│ ├── wakeup
│ ├── wakeup_abort_count
│ ├── wakeup_active
│ ├── wakeup_active_count
│ ├── wakeup_count
│ ├── wakeup_expire_count
│ ├── wakeup_last_time_ms
│ ├── wakeup_max_time_ms
│ ├── wakeup_prevent_sleep_time_ms
│ └── wakeup_total_time_ms
├── subsystem -> ../../../../bus/acpi
└── uevent
15 directories, 62 files# cat /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/power/wakeup
enabled
# cat /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/power/wakeup_active
0The last block is interesting. wakeup seems enabled, wakeup_active is 0, though. I guess wakeup_active has another function?
I tried using the current linux-lts kernel, which also didn't bring up LID0 as wakeup option. I assumed a disability from the kernel. At the moment I'm asking myself: How does the /proc/acpi/wakeup get its content? How is proc deciding which devices are listed and which are not?
Best,
fwillo
Offline
Pages: 1