it will output some windows version, and now add it to grub: /etc/default/grub
and in this line: GRUB_CMDLINE_LINUX_DEFAULT inside the quotes add these parameters:
acpi_osi=! acpi_osi='Windows 2015'
where Windows 2015 will be replaced with the output from the sudo strings commandā¦
dont remove any parameters, add them to existing ones;
save the file and update grub: sudo update-grub
reboot and test
if the sudo strings version doesnt work, try with different one:
I tried a couple strings that I found in the dsdt file, the ones that represent the systems this laptop comes with, and nothing changed with the suspend issue.
check in bios:
if fast boot is disabled, you may not have this option;
and if you are using windows, check if fast startup is disabled;
also in bios check if you have enabled this setting:
Advanced Options > Built-in device options > Wake unit from sleep when lid is opened
also do you have tlp installed? check with: pacman -Qs tlp
if yes, remove it: sudo pacman -Rcns tlp
reboot and testā¦
if it still happens, boot into manjaro live usb, and test suspending there
Iām using manjaro, I tired to suspend with fast boot disabled in the bios and nothing changed (keyboard still doesnāt work)
The only option I have in BIOS regarding the lid is Turn on when lid is opened, my laptop wakes up normally when opening the lid while in s2idle sleep so I guess its on by default and unchangable.
(s2idle also has issues as when using it sometimes the computer will not wake up at all, the fans are running but screen is black)
Also when waking up from deep sleep I do it by pressing the powerbutton so I donāt think lid is related to the issue.
Yes I have it, turned it off rebooted and nothing changed
I tested many live usb distros and all of them face the same issues (ubuntu, manjaro, endeavour)
Before fiddling hereā¦ could you test if suspend-to-ram (S3) (linux: deep) works on Windows? Since this laptop has only support for Windows it would be a better idea to test first there. If only suspend-to-idle (S0) (linux: s2idle) works, then there is actually no chance to use S3. Some Vendors already removed S3 completely from the firmware, not only hiding it. And the errors could be a sign of it.
Beside thatā¦
There seems to be a newer firmware available: 01.07.00 Rev.A
Could I do that with a bootable usb? Or do I need to uninstall my whole system?
The problem for me is that neither of the suspends work correctly, Iāll be fine using either one and just hibernating my laptop for the long periods but the s2idle likes to randomly break and just not wake back up and the deep one wakes up every time but without the keyboard.
Thats a wierd one, I tried to update my laptop bios after 1.07 released and I thought I had it downloaded but it seems that something went wrong.
Iāll try to get this new version and will report back.
Edit:
Updated my BIOS, thanks for noticing, the deep sleep issue hasnāt changed but I will try to test s2idle to chceck if it still randomly breaks.
I canāt test the suspend on windows as I will need to get a bigger USB so Iāll test it tommorow.
Reading your deep logs it looks generally the same (except for all the erros ā¦), but I noticed that i8042 fails for some reason in my logs and as far as Iām aware toghether with i915 it is responsible for keyboard and touchpad control.
i915 seems to be working fine while i8042 gives me a error of -19
I feel like this is the part that causes the keyboard to not work. Iām just not able to find anything about error -19 on the internet so I donāt even know what could casue it.
It seems not be able to find the device, which were known before. But that is firmware related and probably a bug. You could try to disable ASPM, since touchpads and keyboards are connected via PCIE on notebooks.
This kernel parameter disables it completely: pcie_aspm=off
And in the notes section the only thing that is mentioned is this:
Notes
WWAN device is not supported on this machine
Which makes it look like the suspend thereticly should work on ubuntu? But I tested it on the live env ubuntu and it didnāt work
I donāt know how trustable the ubuntu certification is
Well, it is not really off-topic. There is the HWE kernel, which comes with LTS releases and OEM Kernels, which were patched for very specific hardware, especially for new hardware, which has no support in the mainline kernel yet. So I guess they patched it in their kernel. You can install the OEM kernel in Ubuntu.
Added this in the grub editor while booting the pc (coz I feared adding it in permanently would cause hard to fix problems without additional keyboard) and the error didnāt change.
Is it aviable only in ubuntu and I cannot try it in manjaro?
If so could I just test it in the bootable env?
I looked at the OEM kernel changes and saw some s2idle related fixes for HP laptops and none for deep sleep so its seems that if the OEM kernel devs are not doing anything about it the s2idle is the only option accessible. (or Iām bad at searching for things which is also likely)
I made a live usb with ubuntu with OEM kernel installed using Cubic (btw uname -r showed me the oem kernel in the laptop so I assume that it worked) and I tried out deep sleep with it and it still had the same issues, specifically the keyboard not working and the whole system in general seemed to be more crash prone after deep sleep.
Do you perhaps know if the changes made in this kernel go into the mainline and if so how long it takes?
I had some other kernel related issues that I saw were fixed on the OEM and later I got the fixes in the main kernel that I have on my laptop so I assume that the main kernel takes some bits from them?
Also I was unable to test s2idle correctly in the live env as I still donāt know what causes it to fail, it can sit for 40 minutes untouched one time and not break and other times it will break with the same apps open.
do you have actually the deep sleep available? check if deep is listed: cat /sys/power/mem_sleep
if yes, you can try also these parameters: i8042.nomux=1 i8042.reset=1 atkbd.reset=1
also you can try modprobe the module during suspend;
create this script: sudo nano /usr/lib/systemd/system-sleep/fix_i8042.sh
and put there this:
#!/bin/sh
case $1/$2 in
pre/*)
echo "Removing 'i8042' for $2..."
modprobe -r i8042
;;
post/* )
echo "Waking up from $2 , adding 'i8042' ..."
modprobe i8042
;;
esac
save it with ctrl+x, press āyā, then enter;
then navigate to the folder and open terminal in the system-sleep folder and run: chmod a+x fix_i8042.sh ./fix_i8042.sh
reboot and check
No, sorry. It takes how long it takes. Canonical is not one of the top contributor of the kernel. Maybe some patches, they made to the OEM kernel, can be decline.
(I knotw currently s2 is enabled but every time Iām testing I change it temporarly)
Are they diffrent in anyway from the ones before?
Update: Tried it, keyboard issue still present
Did that, the issue with the keyboard wasnāt fix but the errors changed:
lip 13 18:00:22 siema systemd-sleep[2904]: Waking up from suspend , adding 'i8042' ...
lip 13 18:00:22 siema systemd-sleep[2906]: Error: TLP power save is disabled. Set TLP_ENABLE=1 in /etc/tlp.conf.
lip 13 18:00:22 siema (sd-executor)[2903]: /usr/lib/systemd/system-sleep/tlp failed with exit status 1.
lip 13 18:00:25 siema kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
lip 13 18:00:25 siema kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
lip 13 18:00:25 siema kernel: i8042: Can't read CTR while initializing i8042
lip 13 18:00:25 siema kernel: i8042: probe of i8042 failed with error -5
