Shutdown on boot when battery level is critically low

Support
,
1

Hello everyone,

Requirements:

I have Searched the forum for my issue and found nothing related or helpful
I have checked the Resources category (Resources Index)
I have reviewed the Wiki for relevant information
I have read the the Release Notes and Errata

OpenMandriva Lx version:
OpenMandriva ROME 25.06

Desktop environment (KDE, LXQT…):
KDE Plasma 6.3.4; KDE Frameworks Version 6.13.0

Description of the issue (screenshots if relevant):
At startup, in the early boot, it appears the following message

! Battery level critically low. Please connect your charger or the system will power off in 10 seconds.

and then it stopped the boot and power off the laptop.
At this point I need to unplug the pc and re-plug to have a normal boot.
It happens on every reboot or power-on.

I tried to change Settings → Power Management → Advanced Power Settings → Critical level to 0% but nothing changed.

Note: the laptop battery is dead and will remain always nearly 0%, I’m not using it.

I suppose it’s related to some systemd service (i.e. systemd-battery-check.service).

This behavior is not happening with any other system (Ubuntu, Windows, Almalinux).

I really don’t know what else to check to debug this issue. Can someone here help me please?

bootbattery
bootbattery1733×959 476 KB

Relevant informations (hardware involved, software version, logs or output…):
CPU: 8xIntel Core i7-6700HQ
RAM: 16GB
Graphics: NVIDIA GeForce GTX 960M; Intel HD Graphics 530
Battery:

BAT0-acpi-0
Adapter: ACPI interface
in0:          15.00 V  
power1:        0.00 W
2

You have not mentioned if your battery is fully charged or not. More information is needed.

Charging should be possible without the system booted, or there are other issues with the system that have nothing to do with OM.

Are you able to confirm that?

Unfortunately, that doesn’t mean anything. Ubuntu uses an older kernel and installs everything you could possibly need for every system ever made. Similar with AlmaLinux, I’m sure. Windows is a completely different system with the same driver coverage as Ubuntu (every system ever made).

This hardware is very old. It should work with minimal configuration changes. I have something older that does not have this issue, but it is using AMD and ATI hardware.

3

As you wrote, this hardware it’s old: by dead I mean the battery is installed but not working anymore. I use this laptop only powered with the ac power cord.

But it should not be necessary to disable this service.

My intent was to highlight that should not be hw related (the power cord i.e.). In fact, you’re confirming that there is other sw installed in the other distros I mentioned.

4

If it’s a safety check, it may be working as intended. If you were to accidentally or intentionally lose power then the system would need to shut itself down. It may be as simple as, the other OS’s you were using are not configured or do not have the newer version of this software.

This is how most critical battery power events are handled. UPS’s are designed in a similar way. To tell the system when to shutdown in a safe window of remaining battery so it doesn’t harm the system by a complete loss of power during a disk write, etc…

Try booting the PC without the battery and see if it has the same issue.

5

I physically disconnected the battery and now the system doesn’t see it, so there is no battery check and the OS can boot properly even after a reboot.

I thought it was possible to disable the critical level check when the battery is damaged without physically remove it.

In the list of other OS’s I forgot to mention OpenSuse Tumbleweed which is also a rolling release and I’m pretty sure the software is no more obsolete than OM.

Anyway, this workaround is fine with me. Thank you for your suggestions, much appreciated.

1 Like
6

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