Laptop/ASUS

See also Wikipedia:Asus.

Advanced power management (Laptop Power Profile selection, battery charge limit and Panel Overdrive) and many other functions from recent laptops need the ASUS Linux stack installed and running.

Kernel 5.4 brought the ability to set the battery charge threshold for some Asus laptops, by modifying the charge_control_end_threshold variable exposed under /sys/class/power_supply/BAT0/[1] [2].

By default this value is set to 100 and reset on every power cycle[3].

The effect of its change can be demonstrated as follows:

$ cat /sys/class/power_supply/BAT0/status
Charging
$ cat /sys/class/power_supply/BAT0/capacity
74
# echo 60 > /sys/class/power_supply/BAT0/charge_control_end_threshold
$ cat /sys/class/power_supply/BAT0/status
Not charging

To work around cases of configuration failing to apply at boot because the required asus_wmi kernel module has not yet been loaded[5], configure early module loading for it.

TLP gained with version 1.4 the ability to set battery charge thresholds for laptops other than Thinkpads: see upstream documentation and config example.

Another (more simple) way to force the charging threshold is by using bat-asus-battery-bin ^AUR, which provides a bat-boot.service systemd service and an intuitive terminal interface to change the threshold by typing bat-asus-battery threshold value.

gnome-shell-extension-battery-health-charging-git ^AUR is a GNOME extension that "provides a graphical user interface for setting a laptop’s charging limit (charging threshold) within a Gnome environment". It supports ASUS laptops and many other brands. See its official website for details and screenshots.

The battery's charge_control_end_threshold power supply class attribute does not initially exist. It is added to the sysfs(5) directory by the asus-nb-wmi kernel module. Create a udev rule for asus-nb-wmi to set the battery's charge threshold:

/etc/udev/rules.d/asus-battery-charge-threshold.rules

ACTION=="add", KERNEL=="asus-nb-wmi", RUN+="/bin/bash -c 'echo value > /sys/class/power_supply/BAT?/charge_control_end_threshold'"

While this setting will persist after suspending to RAM, it will be reset when resuming from hibernation. In order to re-execute the service after hibernation, use one of the methods described in Power management/Suspend and hibernate#Sleep hooks.

If creating a script as described in Power management/Suspend and hibernate#Hooks in /usr/lib/systemd/system-sleep, use something similar to:

/usr/lib/systemd/system-sleep/battery-threshold.sh

#!/bin/sh
case 1ドル/2ドル in
 pre/*)
 echo "Going to 2ドル..."
  ;;
 post/*)
 echo "Waking up from 2ドル..."
 echo 60 > /sys/class/power_supply/BAT0/charge_control_end_threshold
  ;;
esac

Do not forget to make the script executable.

# rmmod i2c-hid-acpi

# modprobe i2c-hid-acpi

The Function keys default behavior is F1, F2, etc... and must be unset by using Fn+Esc to use alternative functions.

Add amd_iommu=off idle=nomwait amdgpu.gpu_recovery=1 to your kernel command line.

Some laptops with only an NVIDIA GPU and no integrated GPU may fail to resume properly from suspend, especially when the system only supports s2idle. To fix that enable S0ix support on NVIDIA Proprietary driver

You can check if S0ix is currently enabled for the NVIDIA GPU by running:

cat /proc/driver/nvidia/gpus/0000:01:00.0/power

Look for this section:

S0ix Power Management:

If it shows:

Status: Disabled

Then S0ix is not currently active.

To enable S0ix support, ensure you're using NVIDIA driver version 515 or newer. Then, configure the kernel module option:

Create a modprobe configuration file:

/etc/modprobe.d/nvidia-power.conf

options nvidia NVreg_EnableS0ixPowerManagement=1

Rebuild the initramfs:

sudo mkinitcpio -P

Then reboot:

sudo reboot

After rebooting, re-check:

cat /proc/driver/nvidia/gpus/0000:01:00.0/power

Confirm that the line now reads:

Status: Enabled

This indicates that S0ix is now active.

Additionally, enable NVIDIA suspend/resume services:

sudo systemctl enable nvidia-suspend.service nvidia-resume.service nvidia-hibernate.service

These services help properly transition the GPU into and out of low-power states during suspend/resume.

Boot with nouveau disabled: use nouveau.modset=0 on the kernel command line. Need to edit bumblebee service to boot : https://github.com/Bumblebee-Project/Bumblebee/issues/764#issuecomment-450749984.

Some fixes are needed: see https://bugzilla.redhat.com/show_bug.cgi?id=1543769.

• ASUS

• Pages or sections flagged with Template:Style
• Pages or sections flagged with Template:Accuracy