You are not logged in.
Hello. This is a week old install using Archinstall script (KDE Wayland). In October 2024 I installed Arch manually, and decided to reinstall last week partially because of this same issue and also to debloat. I have been busy so this is the first opportunity I had to report this, but it has been an issue for 3 or 4 months. I didn't notice anything that might have changed then, to start this off as everything was normal from October 24 until around May 2025.
I was on linux kernel until September, changed to linux-lts and it seemed to stop for a couple of recharges, but soon came back. I mainly keep the laptop plugged in, but maybe once a week it gets unplugged. I have UEFI setting to only charge from 40% to 80%, in reality in the OS it goes from 38% to 79%.
Here is the journal from the minutes leading up until I need to restart...
Nov 23 11:37:28 archlee rtkit-daemon[1537]: Supervising 8 threads of 4 processes of 1 users.
Nov 23 11:37:28 archlee rtkit-daemon[1537]: Supervising 8 threads of 4 processes of 1 users.
Nov 23 11:37:30 archlee systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Nov 23 11:38:34 archlee rtkit-daemon[1537]: Supervising 8 threads of 4 processes of 1 users.
Nov 23 11:38:34 archlee rtkit-daemon[1537]: Supervising 8 threads of 4 processes of 1 users.
Nov 23 11:39:00 archlee rtkit-daemon[1537]: Supervising 8 threads of 4 processes of 1 users.
Nov 23 11:39:00 archlee rtkit-daemon[1537]: Supervising 8 threads of 4 processes of 1 users.
Nov 23 11:39:07 archlee rtkit-daemon[1537]: Supervising 8 threads of 4 processes of 1 users.
Nov 23 11:39:07 archlee rtkit-daemon[1537]: Supervising 8 threads of 4 processes of 1 users.
Nov 23 11:41:08 archlee rtkit-daemon[1537]: Supervising 8 threads of 4 processes of 1 users.
Nov 23 11:41:08 archlee rtkit-daemon[1537]: Supervising 8 threads of 4 processes of 1 users.
-- Boot 3529fd513b5f4ac5b07f6e5881d78de6 --
Nov 23 11:42:30 archlee kernel: Linux version 6.12.58-1-lts (linux-lts@archlinux) (gcc (GCC) 15.2.1 20251112, GNU ld (GNU Binutils) 2.45.1) #1 SMP PREEMPT_DYNAMIC Fri, 14 Nov 2025 05:38:58 +0000
Nov 23 11:42:30 archlee kernel: Command line: initrd=\initramfs-linux-lts.img cryptdevice=PARTUUID=b7b9457b-f702-4abf-9a1b-e47ed01f2c45:root root=/dev/mapper/root zswap.enabled=0 rw quiet splash rootfstype=ext4I videoed it this time, and shared it from Filen..
https://app.filen.io/#/d/adba10b8-8b79- … 6474326874
Hopefully someone can help. Thanks.
Last edited by leedaz (2025-12-22 12:01:39)
Offline
This doesn't look like it's related to the OS, your PC simply crashes.
Do you have a parrallel windows install or what makes you suspect linux?
Last edited by jl2 (2025-11-26 10:07:49)
Why I run Arch? To "BTW I run Arch" the guy one grade younger.
And to let my siblings and cousins laugh at Arsch Linux...
Offline
Hi jl2. I only use Linux on this laptop. It has worked fine with Arch over 3 different installs since I bought it in 2022. It might be that the hardware is failing at some point, but impossible to say. I hoped someone else was having similar issues, but it seems not. It isn't a big problem though. Cheers.
Offline
Boot some live distro, test the behavior there, maybe even first just enter the UEFI and plug the charger there.
Hard reboots are down to
* overheated
* underpowered
* bad RAM
* bad CPU
The question is: does the charger trigger some ACPI event that causes any of those conditions or does it all happen on the hardware level directly.
Offline
Thanks seth, I have been thinking about doing that, I have MX Linux on a usb stick, I will boot that and run down the battery and try plugging back in. Also will try booting into UEFI and unplug - plug. Will report back. Cheers.
Offline
Just coming back to confirm a few things... Plugging power in UEFI interface does nothing.
I removed power-profiles-daemon disabled UEFI battery control and installed tlp. After much toil I have discovered this laptop (PC Specialist Lafité Pro Series) which has Tuxedo drivers installed for keyboard backlight etc, does not support charge thresholds other than from within UEFI. (Also not available in KDE advanced power settings).
It appears that Tuxedo drivers includes a module 'tuxedo_nb04_power_profiles', but modprobing that gives an error message, and I was well in over my head by that point !
I reversed everything and am now back to square one, but after 4 times this last week, running down the battery to 38% and plugging in, twice it just started charging back up as normal, and twice the power cut out !! So it seems to be a random problem, I'm no nearer to solving it, but it isn't the end of the world.
In future, I'll power down at 38%, plug back in and boot up. a little inconvenient but no biggie really.
I will boot into a live usb at some point and try there when I get time.
Cheers all, have a good weekend.
Offline
I have MX Linux on a usb stick, I will boot that and run down the battery and try plugging back in.
Did you and have any results on that as well?
running down the battery to 38% and plugging in
For clarification: it's *only* around 38%? You can drain the system to 20% and then plug the charger and by fine?
And I assume
I have UEFI setting to only charge from 40% to 80%, in reality in the OS it goes from 38% to 79%.
there's also no problem w/o those constraints (particularly the lower one)?
Offline
Hi seth, I will try a distro on USB stick when I get a minute. Regarding letting the battery run down below 38%, no I have not tried it. I will give that a go today or tomorrow and report back. Thanks for the tips.
Offline
Just an update, still not resolved.. I let battery run down to 20% and when plugging back in, the laptop turned off, so same problem.. I tried booting MX Linux on a USB stick (toram) and plugging back in around 37% also cause a shutdown, so all I can gather is that it isn't distro specific.
For clarity. Arch KDE running Linux 6.12.61-1-lts (but the issue has been happening since early Summer)
MX Linux 6.12.48+deb13-amd64 (OS: MX 25 Infinity x86_64) XFCE.
Same thing happening on both, so I guess it's either hardware specific or maybe something introduced in 6.12 Kernel. I bought this laptop in October 2022 and have happily run Arch, Endevour OS and back to Arch in October 2024 without a problem. Big issue is that nothing at all appears in the journal when the loss of power happens, so no error messages to search for. I also have not found anyone else complaining about this problem through several search engines.
When I get time, I will disable battery control in UEFI for a few days and manually charge down and back up to see if problem goes away.
Also, is it possible (recommended or not) to install Kernel 6.11 or older on arch without issue ? Thanks.
EDIT.. Just installed Linux 6.17.9-arch1-1. Will try with this kernel today.
Last edited by leedaz (2025-12-15 10:30:10)
Offline
Also, is it possible (recommended or not) to install Kernel 6.11 or older on arch without issue ? Thanks.
Absolutely no problem in that. downgrade is a nice little package to automatically download and install older packages.
I'd go for the linux 6.6 or 6.1 LTS, if you want to have that kernel for longer period of time.
Why I run Arch? To "BTW I run Arch" the guy one grade younger.
And to let my siblings and cousins laugh at Arsch Linux...
Offline
I guess it's either hardware specific
as you're getting hard shutdowns/reboots.
Minor caveat
Absolutely no problem in that.
While the kernel is mostly self contained and unlike other packages typically safe to downgrade in isolation there're limitations to that and the kernel might fail to boot if it was compiled w/ a too old toolchain or you can run into troubles if it doesn't support the compression you're currently using for the initramfs
Offline
Thanks guys. I installed Linux 6.17.9-arch1-1 and ran battery down, re-plugged power and no shutdown.... Will try again tomorrow or Wednesday. Not getting too excited yet, as this has been somewhat intermittent (which is also weird) but 80% plus times the power cuts but like this, today, there are times when it doesn't. It's not often though, adding to the frustrating nature of this problem.
Offline
kernel might fail to boot if it was compiled w/ a too old toolchain or you can run into troubles if it doesn't support the compression you're currently using for the initramfs
I wouldn't expect that to happen with kernels >6.x.x.
As I said, I wouldn't use them for anything mid/long term, LTS exists for that.
Why I run Arch? To "BTW I run Arch" the guy one grade younger.
And to let my siblings and cousins laugh at Arsch Linux...
Offline
zstd is supported since 5.19, idr when the last breaking glibc change was - it was just meant as a general warning that you cannot downgrade/stall the kernel indefinitely (for future readers who otherwise might take the wrong message out of it)
Offline
(for future readers who otherwise might take the wrong message out of it)
Gotcha, I learned something new too ![]()
Why I run Arch? To "BTW I run Arch" the guy one grade younger.
And to let my siblings and cousins laugh at Arsch Linux...
Offline
I discovered the shutdowns when plugging in the charger were intermittent and not distro-specific. After testing, installing Linux 6.17.9-arch1-1 seems to stop the problem for now. I suspect it’s either a kernel issue or hardware-specific quirk with my laptop’s ACPI handling, so I’ll continue monitoring before taking further action.
Offline
Thanks Banjo536. My findings too, intermittent but more like 80% of the time a shutdown occurred. Monday on same Kernel as you the issue didn't occur and this morning on Linux 6.18.1-arch1-2 also it didn't occur so I'm tentatively hoping it was an issue introduced in 6.12. I'll continue testing for a week or so before marking this as solved.
Offline
I am coming back to mark as solved after running battery down below 40% 4 more times since my last post without the issue occurring... Running Linux 6.18.2-arch2-1 at the moment, so it looks like something introduced in 6.12 has been resolved in 6.17.9 or thereabouts. Thanks for the help.
Offline