This is a brand new machine, have you made sure you’re on the latest bios?
“Firmware updates can be installed automatically… User reports not receiving UEFI and some other firmware updates this way when there were newer versions available for download.” arch wiki
Seriously…
It’s a single page, how about reading it.
“Alternatively, firmware updates can be installed manually by downloading them from the support page and placing the .exe file on a FAT32 drive or the EFI boot partition, then selecting the file in the “BIOS update” page after pressing F12 at boot time.”
My bad ^^ I was able to update the firmware and add the mem_sleep_default flag, but it doesn’t seem like deep sleep is working still. I find myself unable to follow the rest of the instructions in the reddit post since I can’t disable TPM when dual booting with windows 11. What else could I do to try and force at least a less power consuming option when suspending?
so if you updated your bios to the latest, does the reboot/shuting down still doesnt work?
and people didnt manage to work the deep sleep properly reading the reddit comments, the same goes for the yodell link…
your laptop supports only s2idle mode… and the reason why its not properly working is very likely the nvidia …
I also have an XPS 9720 and I had a lot of issues when I first installed Manjaro. I am also dual boot and everything seems to be working now, except the touchpad. I am up to date on all firmware and by switching to the 5.18 kernel I was able to get everything working.
kernel 5.18 is end of life, so if you are having nvidia, you will have problems with updates… and your inxi output is not complete… are you dual booting with windows too?
I’m glad you did.
Kernel 5.18 is EOL however and you should switch to an LTS kernel like 5.15 or (if it’s not working well with your hardware) try the latest stable kernels 5.19 (soon to be EOL) or 6.0.
See
Fortunately I don’t need the 3060 in Manjaro, I dual boot to win 11 for gaming.
I initially tried 5.15 and noticed similar issues as OP (specifically udev errors, failing to sleep). 5.19 mostly worked for me, but my Adler Lake audio was totally missing (Gnome settings just showed “Dummy Card”).
I see that a new version of 5.19 is available now and I’ll try that in a bit.
Just for OP, version 6 of the kernel did not work for me at all.
Did you get it to work after additional configuration? I also tried kernel 5.18 a while back but I got the same results. Shutdown issue is also still present
Linux brian-xps179720 5.19.16-2-MANJARO #1 SMP PREEMPT_DYNAMIC Sat Oct 15 13:37:00 UTC 2022 x86_64 GNU/Linux
And now everything appears to be working. I’m stumped as to why I keep getting different results when booting different versions of linux… (for example I booted into 5.19.16-2 yesterday and my audio card did not work and I had to manually force power off the laptop)
Here is the output of inxi -Faz: grep date:
v: 1.10.0 date: 08/09/2022
And these logs (I’m pretty sure) show OP the laptop fully suspending:
Oct 18 09:46:07 brian-xps179720 kernel: ACPI: button: The lid device is not compliant to SW_LID.
Oct 18 09:46:08 brian-xps179720 systemd[1]: Reached target Sleep.
Oct 18 09:46:08 brian-xps179720 systemd[1]: Starting System Suspend...
Oct 18 09:46:08 brian-xps179720 kernel: PM: suspend entry (s2idle)
Oct 18 09:46:08 brian-xps179720 systemd-sleep[8147]: Entering sleep state 'suspend'...
Oct 18 09:46:08 brian-xps179720 kernel: Filesystems sync: 0.009 seconds
Oct 18 09:48:07 brian-xps179720 kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.
Oct 18 09:48:07 brian-xps179720 kernel: OOM killer disabled.
Oct 18 09:48:07 brian-xps179720 kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Oct 18 09:48:07 brian-xps179720 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Oct 18 09:48:07 brian-xps179720 kernel: ACPI: EC: interrupt blocked
Oct 18 09:48:07 brian-xps179720 kernel: ACPI: EC: interrupt unblocked
Oct 18 09:48:07 brian-xps179720 kernel: nvme nvme0: Shutdown timeout set to 10 seconds
Oct 18 09:48:07 brian-xps179720 kernel: nvme nvme0: 20/0/0 default/read/poll queues
Oct 18 09:48:07 brian-xps179720 kernel: nvme nvme1: Shutdown timeout set to 10 seconds
Oct 18 09:48:07 brian-xps179720 kernel: nvme nvme1: 8/0/0 default/read/poll queues
Oct 18 09:48:07 brian-xps179720 kernel: nvme nvme1: Ignoring bogus Namespace Identifiers
Oct 18 09:48:07 brian-xps179720 kernel: i915 0000:00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin version 70.1
Oct 18 09:48:07 brian-xps179720 kernel: i915 0000:00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9
Oct 18 09:48:07 brian-xps179720 kernel: i915 0000:00:02.0: [drm] HuC authenticated
Oct 18 09:48:07 brian-xps179720 kernel: i915 0000:00:02.0: [drm] GuC submission enabled
Oct 18 09:48:07 brian-xps179720 kernel: i915 0000:00:02.0: [drm] GuC SLPC enabled
Oct 18 09:48:07 brian-xps179720 kernel: i915 0000:00:02.0: [drm] GuC RC: enabled
Oct 18 09:48:07 brian-xps179720 kernel: OOM killer enabled.
Oct 18 09:48:07 brian-xps179720 kernel: Restarting tasks ...
But I am still having issues with the touchpad
Oct 18 09:49:13 brian-xps179720 touchegg[654]: libinput error: event17 - VEN_06CB:00 06CB:CE7E Touchpad: kernel bug: Touch jump detected and discarded.
Oct 18 09:49:13 brian-xps179720 touchegg[654]: See https://wayland.freedesktop.org/libinput/doc/1.21.0/touchpad-jumping-cursors.html for details
Oct 18 09:49:13 brian-xps179720 gnome-shell[2104]: libinput error: event17 - VEN_06CB:00 06CB:CE7E Touchpad: kernel bug: Touch jump detected and discarded.
Oct 18 09:49:13 brian-xps179720 gnome-shell[2104]: See https://wayland.freedesktop.org/libinput/doc/1.21.0/touchpad-jumping-cursors.html for details
I’ll reboot into the bios/uefi settings later today and see what changes I did make. From memory I turned off AHCI, disabled secure boot and a setting to enable the nvidia card on the usb-c ports. I do not remember turning off fastboot nor disabling fast startup in windows.
yeah, but it uses S0 and not S3. Guess it is still a bit buggy and your device seems not to provide S3 (suspend-to-ram), but S0 (suspend-to-idle) what is the same as on smartphone for example. It doesn’t completely shutdown (except ram), but idle all the time, but on the other hand can wake up very quickly.
However… s2idle is just a generic approach which works on any system and is used where the suspend methods standby and suspend-to-ram are not available. It never shutdown, but set everything in powersaving mode (if possible) and idle.
@try2bgr8 Do you run wayland? touchegg only works on xorg.
@merlo I guess it gets hot on suspend, because one of the components still stays active and does not idle. Maybe nvidia.
Somehow DELL and Windows thinks that S3 is no longer needed… thanks, I will take this into account with my next purchase and make sure that the device is also S3 capable.
I missed this when buying as well, guess there isn’t a clear cut solution after all, my guess is also Nvidia. I will just try to power it off I guess. The main problem is that it’s also annoying, since it doesn’t actually turn off quickly due to the systemd-udevd and I still have no clue what to do there. @try2bgr8 does your system shut off fine? Did you change anything to make it do so?
Mine is mostly reliable (at least enough for me to get work done) now under Manajaro and kernel 5.19.16-2… BUT
I went into the BIOS and disabled the sound card. I always use bluetooth ear buds or bluetooth speakers so I don’t need the sound card. If you disable it, your laptop should work like expected (including systemd-udev will stop hanging which is what is stopping your laptop from shutting down).
I am just going to wait until the kernel/sof gets better support for the sound card in these types of laptops.
Also, I still do have intermittent issues with the touchpad (apparently a well know issue with the XPS laptops in general) and every now and then the i915 hangs but resets itself pretty quickly.
Sorry to revive this topic, but I’ve noticed this particular session I’m in seems to go to sleep fine and has working sound, while I usually didn’t have that. I haven’t changed anything in my setup. Is there a way to check through some log why this works to be able to recreate it? Currently I’m just not turning my PC off and have everything working fine, but it’ll probably go away on reboot