Linux ACPI
 help / color / mirror / Atom feed
From: calvitohq@gmail.com
To: linux-acpi@vger.kernel.org
Cc: platform-driver-x86@vger.kernel.org
Subject: [BUG] ACPI battery: BAT1 status "Not charging" and capacity frozen at 99% while discharging (ASUS TUF A16 FA608UMI)
Date: Sat, 26 Sep 2026 13:25:00 +0200	[thread overview]
Message-ID: <6ab7abf7.09148f95.17f923.ff4b@mx.google.com> (raw)

Hi,

On an ASUS TUF Gaming A16 (FA608UMI), running on battery, the ACPI
battery reports status "Not charging" and the capacity stays frozen at
99% even though the battery is actively discharging (~11 W measured via
current_now). Expected status while on battery is "Discharging".

Hardware:
- DMI: ASUS TUF Gaming A16, product FA608UMI (1.0), board FA608UMI
- CPU: AMD Ryzen 7 260 w/ Radeon 780M Graphics

Software:
- Distro: Bazzite (Fedora 44 atomic)
- Kernel: 7.2.4-ogc3.1.fc44.x86_64

Symptom:
With AC offline (ACAD/online=0), repeated reads give a stable (not
oscillating) "Not charging":

  /sys/class/power_supply/BAT1/status       -> "Not charging" (stable)
  /sys/class/power_supply/BAT1/capacity     -> 99 (frozen; no change over ~40 min)
  /sys/class/power_supply/BAT1/current_now  -> 617000 (~0.62 A, ~11 W drain)
  /sys/class/power_supply/BAT1/charge_now   -> 4379000 (frozen)
  /sys/class/power_supply/BAT1/charge_full  -> 4424000

UPower consequently reports state "fully-charged", percentage 99% and a
bogus "time to empty", so the desktop shows no meaningful percentage
while actually discharging.

This looks related to the existing report for the ASUS Vivobook 18
M1807HA (Launchpad bug 2152185), where status oscillates between
"Discharging"/"Not charging" while on battery due to inconsistent ACPI
_BST values. Here it is stuck rather than oscillating.

dmesg shows:
  ACPI: battery: Slot [BAT1] (battery present)
  ACPI: battery: new hook: ASUS Battery Extension

I suspect this needs a DMI-matched quirk in drivers/acpi/battery.c to
force "Discharging" when no AC supply is online, as suggested in that
earlier report.

I have the DSDT/SSDT (acpidump) available if needed, and I'm happy to
test patches.

Thanks,
Marco


                 reply	other threads:[~2026-09-26 11:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6ab7abf7.09148f95.17f923.ff4b@mx.google.com \
    --to=calvitohq@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=soytucalvitofavorito@icloud.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox