Jump to content

Lenovo LOQ 15ARP9

From ArchWiki

This article or section does not follow the Laptop page guidelines.

Reason: Too many issues to list. (Discuss in Talk:Lenovo LOQ 15ARP9)

Power management

Suspend

LOQ 15 laptops are known to have issues with suspend out of the box. Example scenarios include but are not limited to:

  • Suspending appears to work. On resume, fans begin spinning, but the screen backlight does not turn on. Userspace is unresponsive.
  • Suspending appears to work. On resume, fans begin spinning and a few seconds later the device reboots.
  • Suspending appears to work. Resume is impossible, as the device does not react to any input.
  • Suspending does not work. The screen may turn off for a second before coming back.

These issues might be intermittent, and the same device may experience different issues in an unpredictable manner. The following guide has been tested to work on 15ARP9 with a Lenovo LNVNB161216 motherboard, NVIDIA RTX 4070 Mobile GPU and AMD Ryzen 7 7435HS CPU on Linux 6.16.8-arch3-1 with nvidia-open 580.82.09-5, but it is likely to apply to other devices with similar specifications. You may use inxi to check if your device is similar.

Install dmidecode to check the BIOS version: 

dmidecode -t bios -q | grep -E '(Release|Version)'
        Version: PQCN24WW
        Release Date: 06/02/2025

Make sure the BIOS version is PQCN24WW released on June 2nd 2025 or newer. Note that the Release Date field returned by dmidecode is in an unusual MM/DD/YYYY format. If your BIOS is older and you are dual booting Windows, you may use Lenovo Vantage on Windows to update the BIOS. fwupd has not been tested (feel free to update this paragraph if you find that it works).

Regardless of whether you have attempted to solve this on your own before or not, ensure a clean slate before continuing:

  • Make sure nvidia-open is installed as the GPU driver.
  • Check /etc/modprobe.d for any configuration regarding the nvidia driver. Remove all of it, especially those related to dynamic power management and VRAM thresholds. If you have a file that blacklists nouveau, that is an exception and you can leave it in.
  • Remove any kernel parameters you may have added to try to remedy the issue before, in particular iommu=soft and power management related options.
  • Add the kernel parameter pcie_aspm=off to boot settings. This is not permanent, but it will be used as a checkpoint to ensure that suspend works without power management. PM will be reintroduced later, at which point you will be advised to remove this parameter. If you wish to get to the proper solution faster, skip this step and skip the ASPM-less suspend check later.
  • Rebuild initramfs with mkinitcpio -P. Note that due to early KMS this will likely be necessary even if all you have done is change files in /etc/modprobe.d.
  • Reboot.

During the reboot, enter BIOS configuration by repeatedly pressing the F2 key after the screen turns off and on until you see the main menu. Press More Settings to enter the actual configuration menu.

Navigate to the Exit menu and select the Load Default Settings option, then confirm the dialog that appears. Finally, press F10 and confirm to save and quit. This restores all BIOS settings to factory defaults and is a crucial step, even if you did not change the BIOS settings. It has been observed that the BIOS can find itself in a confused state which makes suspend behavior highly unpredictable, possibly as a result of BIOS updates, Windows updates or attempts to suspend with incorrect configuration in place. Restoring factory defaults appears to also restore this state to normal.

If you have some BIOS settings you want to keep, write them down before loading defaults and restore them on the next boot.

Once you exit from the BIOS, boot back into the Linux system. If you have added pcie_aspm=off to the kernel boot parameters, you can now test if suspend works without ASPM: 

systemctl suspend

Wait around 5 seconds after the power button starts flashing slowly, then press a couple of keys on the keyboard. If the screen does not immediately turn on, try using the touchpad to move the cursor.

At this point, resuming should work, but you are running without ASPM and may thus experience increased battery and power use. If a future BIOS update or something else ever breaks suspend/resume with the proper solution below, you can follow these steps up to this point to trade ASPM for working suspend.

To get working suspend/resume without losing ASPM, you have to enable S0ix support in the NVIDIA driver as described in the documentation. Add the following file to /etc/modprobe.d: 

/etc/modprobe.d/nvidia.conf
options nvidia NVreg_EnableS0ixPowerManagement=1

Afterwards remove the pcie_aspm=off kernel parameter. Rebuild the initramfs and reboot the machine.

Check the NVIDIA power settings by reading from this file in procfs: 

/proc/driver/nvidia/gpus/0000:01:00.0/power
Runtime D3 status:          Enabled (fine-grained)
Video Memory:               Active

GPU Hardware Support:
 Video Memory Self Refresh: Supported
 Video Memory Off:          Supported

S0ix Power Management:
 Platform Support:          Supported
 Status:                    Enabled

Notebook Dynamic Boost:     Supported

Status under S0ix Power Management should indicate Enabled.

Attempt suspending with systemctl suspend again. Once again, if the screen does not immediately turn back on when resumed, use the touchpad for a bit. If you are able to suspend and resume like this, you can now attempt to use the lid, which should work as expected. Note that after opening the lid you may still need to feed input to see the display.

This section is based on findings in the forum thread [1].

Hibernation

Hibernation does not work with early KMS. Remove NVIDIA modules from /etc/modprobe.d. Make sure you have read the page on hibernation and configured resume correctly.

There is a bug in both proprietary and open NVIDIA drivers where suspending fails if the system has previously been resumed from hibernation. Suspending in sequence and hibernating in sequence works, but if you attempt to execute a sequence of hibernate-resume-suspend-resume, the NVIDIA driver starts spamming errors and eventually triggers a page fault.

It has been reported on NVIDIA Forums[2] on October 2nd, 2025 with no response as of October 2nd, 2025.

Windows updates

Windows updates trigger the BIOS to enter a confused state. This may happen only after booting into Linux. In this confused state, suspending does not work correctly on Linux. The confused state will persist between reboots and attempts to sleep on Windows.

A way to tell if this has happened is if the power button flashes when the screen backlight is off. Normally, the power button should only flash if the laptop is suspended. If you observe flashing when the screen is completely black but the laptop is not suspended (for example when booting or logging into a graphical environment), you are affected by this issue.

Follow the instructions on how to reset the BIOS in #Suspend. If you have already configured power management in the NVIDIA driver, you do not have to do anything other than resetting the BIOS.