No input after wakeup when acpi_osi=Linux kernel parameter set.

soocki · 2019-04-26 15:24:30

After wakeup the peripherials (mouse/integrated keyboard etc.) do not work (as in they are completly dead) when acpi_osi=Linux kernel paramater is set. It is needed for disabling the discreet graphics card. What do I do?

Last edited by soocki (2019-05-01 21:55:35)

Mortimer Houghton · 2019-05-01 17:10:40

Have you tried the tip at the bottom of the Hybrid graphics wiki page?

soocki · 2019-05-01 19:53:25

I have, just now. Not sure if running the

/usr/share/acpi_call/examples/turn_off_gpu.sh

yields any other results than disabling the USB peripherals.
Either way only one method succeedes (or works) and even if the card is disabled as a result (which I am unsure of, the remaining battery time indicator changed ever so slightly; fifteen minutes on the scale of seven hours) the peripherals are needed so no good.
For now the suspension remains disabled, shame I really enjoyed the swapfile-hibernate-on-lid-close mechanism.

Last edited by soocki (2019-05-01 20:18:30)

seth · 2019-05-01 20:32:07

I think he meant to follow a different approach to turn off the GPU.
Are you suggesting running turn_off_gpu.sh kills your usb input as well?
Does the input revive when you un/plug the devices?

soocki · 2019-05-01 20:40:42

seth wrote:

Are you suggesting running turn_off_gpu.sh kills your usb input as well?

I am pretty sure that is all it does.

seth wrote:

Does the input revive when you un/plug the devices?

They remain dead on re-plug, all the USB ports.

Ps. It's a Lenovo T440p by the way.

seth · 2019-05-01 20:48:07

I am pretty sure that is all it does.

Test or belief? W/ or w/o the acpi_osi parameter?
What's its actual output?

Also "lspci", it would seem GPU and USB hang on the same bus??

soocki · 2019-05-01 21:25:17

seth wrote:

W/ or w/o the acpi_osi parameter?

Withouth, the acpi_osi parmater was removed from the command line options.

seth wrote:

Test or belief?

Test it, as in:
- loaded the acpi_call module,
- run the [/usr/share/acpi_call/examples/turn_off_gpu.sh] script,
Like I said, only the one line of code returned works! result:

# modprobe acpi_call 
# /usr/share/acpi_call/examples/turn_off_gpu.sh
Trying \_SB.PCI0.P0P1.VGA._OFF: /usr/share/acpi_call/examples/turn_off_gpu.sh: line 39: warning: command substitution: ignored null byte in input
failed
(..)
Trying \_SB.PCI0.LPC.EC.PUBS._OFF: /usr/share/acpi_call/examples/turn_off_gpu.sh: line 39: warning: command substitution: ignored null byte in input
works!
(..)
Trying \_SB.PCI0.AGP.VGA.PX02: /usr/share/acpi_call/examples/turn_off_gpu.sh: line 39: warning: command substitution: ignored null byte in input
failed

As a result the peripherals are disabled, plugging out/in makes no change, whether the card is disabled remains questionable since it's effect on the remaining batery life was negligible:

soocki wrote:

fifteen minutes on the scale of seven hours

I don't know how to test it otherwise, this method was suggested in the mentioned article.

seth wrote:

(..) it would seem GPU and USB hang on the same bus??

That I don't know, here is the lspci:

# lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4)
00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d4)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation QM87 Express LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04)
02:00.0 VGA compatible controller: NVIDIA Corporation GK208M [GeForce GT 730M] (rev ff)
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01)
04:00.0 Network controller: Intel Corporation Wireless 7260 (rev 83)

Last edited by soocki (2019-05-01 21:52:19)

seth · 2019-05-02 07:11:46

Trying \_SB.PCI0.LPC.EC.PUBS._OFF: /usr/share/acpi_call/examples/turn_off_gpu.sh: line 39: warning: command substitution: ignored null byte in input works!

Would apparently shut down some embedded controller, could reasonably affect any device that's willing to respond (the nvidia chip and usb controllers are obviously not on the same bus)

You could try whether

echo "\_SB.PCI0.LPC.EC.PUBS._ON" | sudo tee /proc/acpi/call

re-activates the relevant controller (both after calling it off and after resuming from S3, in a systemd sleep hook you won't require the sudo tee dance)

Arch Linux

#1 2019-04-26 15:24:30

No input after wakeup when acpi_osi=Linux kernel parameter set.

#2 2019-05-01 17:10:40

Re: No input after wakeup when acpi_osi=Linux kernel parameter set.

#3 2019-05-01 19:53:25

Re: No input after wakeup when acpi_osi=Linux kernel parameter set.

#4 2019-05-01 20:32:07

Re: No input after wakeup when acpi_osi=Linux kernel parameter set.

#5 2019-05-01 20:40:42

Re: No input after wakeup when acpi_osi=Linux kernel parameter set.

#6 2019-05-01 20:48:07

Re: No input after wakeup when acpi_osi=Linux kernel parameter set.

#7 2019-05-01 21:25:17

Re: No input after wakeup when acpi_osi=Linux kernel parameter set.

#8 2019-05-02 07:11:46

Re: No input after wakeup when acpi_osi=Linux kernel parameter set.

Board footer