[ASUS] Battery charge limit does not persist after reboot on universal Bazzite image

[denmelon]

Describe the bug

Summary

After rebasing from the ASUS-specific Bazzite image to the current universal Bazzite image,
battery charge limiting on ASUS laptops no longer persists across reboots.

This is a regression compared to the ASUS image, where battery charge limiting worked
reliably via ROG Control.

---

Environment

• OS: Bazzite (43)
• Previous image: Bazzite ASUS image
• Hardware: ROG Strix G512LW_G512LW
• Kernel: 6.17.7-ba22.fc43.x86_64 (64-bit)
• Rebase method:

  rpm-ostree reset
  rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-nvidia-open:stable
  

Additional Notes

Other ASUS WMI features (keyboard backlight, hotkeys) work correctly.

Only battery charge limit persistence is affected.

What did you expect to happen?

Actual Behavior

Battery charge limit set via built-in / standard mechanisms:

resets after reboot

system starts charging battery to 100%

UI feedback exists, but the limit is not enforced after reboot.

Expected Behavior

Battery charge limit (e.g. 80%) should:

persist across reboots

be enforced early enough to prevent charging above the limit

Behavior should be equivalent to what was provided by the ASUS-specific Bazzite image.

Regression

On the ASUS Bazzite image, battery charge limiting worked reliably via ROG Control:

settings persisted across reboots

charging was correctly capped

On the current universal image, this functionality is missing or incomplete.

asusctl / ASUS-specific tooling is not available or not integrated by default.

Session Logs

# on ASUS image
cat /sys/class/power_supply/BAT0/charge_control_end_threshold
# => 80 (persisted after reboot)

# on universal image
cat /sys/class/power_supply/BAT0/charge_control_end_threshold
# => resets to 100 after reboot



@bazzite:~$ lsmod | grep -E 'asus|wmi'

asus_nb_wmi            32768  0
asus_armoury           73728  0
wmi_bmof               12288  0
firmware_attributes_class    12288  1 asus_armoury
asus_wireless          16384  0
hid_asus               45056  0
led_class_multicolor    16384  1 hid_asus
asus_wmi              118784  3 asus_armoury,asus_nb_wmi,hid_asus
sparse_keymap          12288  1 asus_wmi
platform_profile       20480  1 asus_wmi
rfkill                 45056  9 iwlmvm,asus_wmi,bluetooth,cfg80211
mxm_wmi                12288  0
video                  81920  5 asus_wmi,amdgpu,asus_nb_wmi,i915,nvidia_modeset
wmi                    32768  5 video,asus_armoury,asus_wmi,wmi_bmof,mxm_wmi

Hardware

• OS: Bazzite (43)
• Previous image: Bazzite ASUS image
• Hardware: ROG Strix G512LW_G512LW
• Kernel: 6.17.7-ba22.fc43.x86_64 (64-bit)

Extra information or context

Why this matters

Battery charge limiting is critical for battery health, especially on gaming laptops.

ASUS laptops are very common among Bazzite users.

This becomes a blocking issue when migrating users from the ASUS image to the promoted
universal image.

From a user perspective, this is a clear feature regression.

Priority: High
Affected users: ASUS laptop owners

Questions / Suggestions

Is there a planned replacement for ROG Control on the universal image?

Should asusctl or equivalent tooling be:

automatically included on ASUS hardware?

offered as an officially supported optional component?

Is this behavior expected or an unintended regression?