Site Map - skip to main content

Hacker Public Radio

Your ideas, projects, opinions - podcasted.

New episodes Monday through Friday.

hpr3536 :: Laptop power problems

This is a story of a laptop with two power problems.

<< First, < Previous, , Latest >>

Thumbnail of Andrew Conway
Hosted by Andrew Conway on 2022-02-21 is flagged as Clean and is released under a CC-BY-SA license.
laptop,linux,power. 1.

Listen in ogg, spx, or mp3 format. Play now:

Duration: 00:23:18


This is a story of a laptop with two power problems.

The first and less severe is that sometimes the charging of the battery will get stuck at a certain percentage. This is not simply due to the effect commonly found with aging batteries but a fault with the laptop's charging hardware. A full reset of the charging system can fix it, which for this ASUS Zenbook UX550vd laptop requires a long press — meaning 40 seconds — from its shutdown state.

The second and more serious issue is that the laptop thinks that it is plugged into AC power even when it is running only on battery. I ruled out an operating system or software issue because the issue remains whether running GNU/linux or Windows. The problem is serious because the power management software, in my case in KDE, will not respond to critically low battery levels by suspending or gracefully shutting down. It may be that a sudden loss of power damaged the previous SSD in this laptop, which was the subject of HPR 3428.

My first attempt to fool KDE into seeing accurate battery information under /sys/class/power_supply/BAT0 using an overlay filesystem failed presumably because KDE's power system is listening out for some kind of event rather than simply monitoring those files. My second and successful attempt involved writing my own bash scripts run by cron to monitor battery levels and initiate actions when they got too low. There were errors with comedic consequences along the way. In fact, while writing these shownotes after I finished recording the audio, the laptop suspended itself because of a bug in my script - I used le (less than or equal to) rather than lt (less than) in my test for a change in the battery charge leading to unintended and fun consequences when the battery was fully charged.


Subscribe to the comments RSS feed.

Comment #1 posted on 2022-02-22 19:30:38 by Zen_floater2

I have the Google GO pro chromebook, had the same problems

I assume it was a Russian attack at first. It all happened after one of Google's updates. I then just unplugged the chrome book and powered it off. Then I started the chrome book up again and plugged it into a power source and the entire thing was resolved. I also notice that Slackware 15 had locked up twice on me after my 1st boot on a different laptop and the same kind of thing had to be done over there too.

Leave Comment

Note to Verbose Commenters
If you can't fit everything you want to say in the comment below then you really should record a response show instead.

Note to Spammers
All comments are moderated. All links are checked by humans. We strip out all html. Feel free to record a show about yourself, or your industry, or any other topic we may find interesting. We also check shows for spam :).

Provide feedback
Your Name/Handle:
Anti Spam Question: What does the P in HPR stand for ?