At wits end... - Sleep power issue

I’m a college student, and I need my system retain it’s battery whenever I’m not using it. I can’t afford a dead laptop in the middle of class (speaking from experience) However, it cooks itself inside my backpack. I have tried for 2 days, combing through every solution on the internet.

In s2idle sleep mode, the laptop appears to go to sleep: the display turns off and the fans idle, however a concerning amount of heat emanates from the laptop, and over the course of 30 minutes my battery dropped 20 points.

I run an ASUS K6502VJ, on the latest release of EndeavorOS with KDE. NVIDIA proprietary drivers are installed as well. This has occurred on both power-profiles-daemon and TLP. I am currently using TLP.

Any help would be greatly appreciated.

Welcome to the community! :vulcan_salute: :enos_flag:

People who can help will need more info from you.
When logged in to your device, please follow this guide: https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/

I’m sure I’ve seen others with this issue on the forum. A search for “sleep” may already have a solution.
Sleep: https://forum.endeavouros.com/search?q=sleep%20order%3Alatest

Lastly, once your logs have been generated, please scroll to the bottom of the link to see how to post them.



PS: It’s great to know that students are using Linux somewhere. That being said, EndeavourOS is based on Arch Linux. I’m not sure how much you know about Linux, but it’s close to bleeding-edge, which means things may work today, and not tomorrow. As such, it may not be suitable, for a “production environment” — in your case, school. That is, unless you have the experience and expertise to fix things should something go wrong.

In other words, it may be more suitable to use an LTS release distro.

1 Like

A recent update stopped my system from going to sleep. I was working perfectly and then boom, it wasn’t working. I don’t know if your problem has been going on for a while but mine just started. Hopefully and future update will resolve as quickly as it broke it. :slight_smile:

I too have a nvidia card.

Good luck and welcome to the community, I hope you find a solution. I’m a newbie so I certainly don’t have anything to add.

Thank you, I was sucessfully able to get the log files.

inxi -Fxxc0z | eos-sendlog
https://0x0.st/XINs.txt
journalctl -k -b -0 | eos-sendlog
https://0x0.st/XINz.txt

In its current state, it enters s2idle, but got quite warm inside my bag. This does not happen on Windows.

1 Like

I just had a look at your journalctl, and reading the first Call Trace I see on there, it seems to be pointing at the nvidia driver.
unmap_mapping_range+0x116/0x140 Oct 15 23:08:14 Goober kernel: ? __pfx__main_loop+0x10/0x10 [nvidia 1400000003000000474e5500b6595e553982bbae]

Question #1: Are you running the most up-to-date nvidia driver?
Question #2: If you are, are you willing to try removal of the proprietary driver to see if this mitigates the issue?
Question #3: Alternatively if this issue is newer (after the last kernel update some 6 days ago), you might try running the older kernel version to see if the issue is mitigated.

I also had a similar issue after a recent update, but I just tried the solution at https://bbs.archlinux.org/viewtopic.php?id=296978 and updated my nvidia drivers again and after a restart it was fixed. So I’m not sure what fixed it.

I ran @Quower 's solution to no avail.
It still warms up in my bag. I am currently running the latest Nvidia drivers. I might try the open-source drivers, as long as blender can make use of the card.
I’m using kernel version 6.11.3-arch1-1.

What’s the output of:

pacman -Q | grep -A 0 -E "(headers|linux|nvidia)"

Try one of or a combination of these things:

  • Install and use the LTS kernel sudo pacman -S linux-lts linux-lts-headers
  • Try putting your device to sleep in an X11 session
  • Check your BIOS for any settings that may be specific to Sleep/Hibernation and Windows

The newest kernel can have the newest bugs.
If things work in X11, we know it’s a Wayland issue.
Sometimes BIOS settings and/or Windows causes problems they shouldn’t.

Lastly, as a sanity check, please share a screenshot(s) of your sleep settings in KDE.

pacman -Q | grep -A 0 -E "(headers|linux|nvidia) returns

archlinux-appstream-data 20240914-1
archlinux-keyring 20241015-1
--
linux 6.11.3.arch1-1
linux-api-headers 6.10-1
linux-firmware 20240909.552ed9b8-1
linux-firmware-marvell 20240909.552ed9b8-1
linux-firmware-whence 20240909.552ed9b8-1
linux-headers 6.11.3.arch1-1
--
nvidia-dkms 560.35.03-16
nvidia-hook 1.5.1-1
nvidia-inst 24.10.1-1
nvidia-settings 560.35.03-1
nvidia-utils 560.35.03-16
--
opencl-nvidia 560.35.03-16
--
util-linux 2.40.2-1
util-linux-libs 2.40.2-1
--
vulkan-headers 1:1.3.295-1

I’ve installed the LTS kernel, so I will try that.
I will also try X11 and report back. I also don’t have any BIOS options related to sleep, it’s unfortunately really basic.

The lid setting is the same across the 3 power settings.

1 Like

Have you already tried this? Hibernation and Sleep options not working, "Login Screen" shows instead - #2 by Dinomonster

Again, a search for “sleep” would be a good idea. “Hibernate” and “hibernation” too.

Sleep: https://forum.endeavouros.com/search?q=sleep%20order%3Alatest
Hibernate: https://forum.endeavouros.com/search?q=hibernate%20order%3Alatest
Hibernation: https://forum.endeavouros.com/search?q=hibernation%20order%3Alatest

Update: The LTS Kernel prevents the system from waking after sleep, so I will be reverting to the original
Update 2: It might be the nvidia drivers, im uninstalling them.

You should probably keep the LTS kernel installed alongside the current one. It often helps with hardware/firmware compatibility and booting issues.


Forgot to mention this, as I’m not sure if the base EndeavourOS hooks does it automatically.

It is possible that the reason it didn’t boot is that you needed to manually run two commands. Though, this may not be the case if you saw the LTS kernel in the bootloader options.

sudo mkinitcpio -P

Then for GRUB:

sudo grub-mkconfig -o /boot/grub/grub.cfg

or for Systemd-boot, I think it should be:

bootctl update

Thanks, however I ended up doing a complete reinstall of the system. I ran yay -S nvidia and yay -S cuda and everything works great! The system appears to sleep properly now.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.