ASUS ProArt P16 H7606WV
| Hardware | PCI/USB ID | Working? |
|---|---|---|
| GPU (AMD) | 1002:150e |
Yes |
| GPU (NVIDIA) | 10de:28a0 |
Yes |
| Wi-Fi | 14c3:7925 |
Yes |
| Bluetooth | 0489:e11e |
Yes |
| Audio | 1022:15e3 |
Yes |
| Speakers | Yes | |
| Microphone | Yes | |
| Headphone jack | Yes | |
| Webcam | 3277:0059 |
Yes |
| Touchpad | I2C 2808:0234
|
Yes |
| ASUS DialPad | I2C 2808:0234
|
Partial |
| Touchscreen | I2C 2575:0926
|
Yes |
| Stylus | I2C 2575:0926
|
Untested |
| SD-card reader | 17a0:9767 |
Yes |
| NPU | 1022:17f0 |
Untested |
This article covers the installation and configuration of Arch Linux on the ASUS ProArt P16 H7606WV. Unless otherwise stated, hardware compatibility was tested using linux-zen and KDE Plasma on Wayland; these components are not model requirements.
Installation
To access the boot-device selection menu, repeatedly press Esc immediately after powering on the laptop, then select the Arch Linux installation medium.
The Arch Linux installation medium boots without requiring model-specific kernel parameters. Follow the standard Installation guide.
Graphics
Hybrid graphics
The laptop contains an integrated AMD Radeon 890M GPU and a discrete NVIDIA GeForce RTX 4060 Laptop GPU. A Wayland desktop session can run on the integrated AMD GPU while applications are selectively rendered on the NVIDIA GPU.
The AMD GPU is supported by the mesa package. The NVIDIA GPU works with nvidia-open-dkms and nvidia-utils. When using the DKMS package, install the headers corresponding to the selected kernel, such as linux-headers or linux-zen-headers.
NVIDIA DRM kernel mode setting is enabled without adding an explicit nvidia_drm.modeset kernel parameter.
To run an OpenGL application using the NVIDIA GPU:
$ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia application
For additional configuration and Vulkan offloading, see PRIME#PRIME render offload.
External displays
The internal display and the left-side USB4 Type-C display output are connected to the AMD GPU. The HDMI port is connected to the NVIDIA GPU.
Display output through the left-side USB4 Type-C port works using a USB-C to DisplayPort connection. Applications rendered on the NVIDIA GPU can be displayed through this port using PRIME render offload; the completed frames are transferred to the AMD GPU for display.
Because the HDMI port is connected directly to the NVIDIA GPU, a functioning NVIDIA driver is required to use it.
Audio
The internal speakers, built-in microphone and 3.5 mm combo audio jack work without model-specific configuration using PipeWire.
Audio output through a display connected to the left-side USB4 Type-C port also works. Select the HDMI/DisplayPort audio output associated with the AMD Radeon High Definition Audio controller.
Touchpad and touchscreen
The touchpad and touchscreen work without model-specific configuration using libinput.
The touchpad is exposed as an I2C device with ID 2808:0234 and supports pointer and multitouch gesture input. The touchscreen is exposed as an I2C device with ID 2575:0926.
A stylus interface is exposed through the same touchscreen device, but stylus operation has not been tested.
ASUS DialPad
Normal touchpad functionality works through the I2C device 2808:0234.
The DialPad illumination responds through the I2C interface, but specialized DialPad functionality requires additional userspace software and is not supported by the standard input stack.
Bluetooth
Bluetooth works without additional configuration. Pairing and A2DP audio playback were tested with an external speaker using PipeWire. Resume with an active Bluetooth audio connection has not been tested.
SD card reader
The internal Genesys Logic GL9767 card reader works with the sdhci-pci driver. Reading from and copying files from an SD card were tested successfully. The card remained mounted and accessible after suspend then hibernate.
Power management
Suspend
The firmware exposes only suspend-to-idle; S3 deep sleep is not available.
$ cat /sys/power/mem_sleep
[s2idle]
Suspend and resume work with the internal display and an external monitor connected through the left USB-C/DisplayPort output.
Hibernation
Hibernation works when configured according to Power management/Suspend and hibernate#Hibernation.
Testing used a dedicated persistent swap partition as the resume device alongside a higher-priority zram swap device. Zram remained active during hibernation; no custom service to disable it before hibernating was required.
The graphical session and external display restored successfully after repeated hibernation tests. An SD card in the internal card reader remained mounted and accessible.
Suspend then hibernate
Suspend then hibernate works, including the automatic transition from suspend-to-idle to ACPI S4.
The battery exposes a hardware alarm through /sys/class/power_supply/BAT1/alarm. Transition triggered by an actual low-battery condition has not yet been tested. See Power management/Suspend and hibernate#Suspend then hibernate.
Battery charge threshold
The battery exposes a configurable charge limit through /sys/class/power_supply/BAT1/charge_control_end_threshold.
Plasma can change the charge limit through Advanced Power Settings, but in the tested configuration the selected value is not retained across a reboot. The firmware resets the threshold to 100, which Plasma subsequently reflects.
Configure the desired threshold to be applied at boot as described in Laptop/ASUS#Battery charge threshold. With BIOS version 320, the configured threshold is retained across hibernation, so a periodic timer or post-resume hook is not required.
Function keys
The following results apply to the marked hotkey functions. “Visible” indicates that an input event is reported by libinput.
| Key | Visible? | Marked? | Effect |
|---|---|---|---|
F1 |
Yes | Yes | Toggles audio mute |
F2 |
Yes | Yes | Decreases audio volume |
F3 |
Yes | Yes | Increases audio volume |
F4 |
Yes | Yes | Toggles the keyboard backlight between off and its previous level |
F5 |
Yes | Yes | Decreases display brightness |
F6 |
Yes | Yes | Increases display brightness |
F7 |
Yes | Yes | Opens the display-layout selector |
F8 |
Yes | Yes | Emits KEY_EMOJI_PICKER; no default action
|
F9 |
Yes | Yes | Toggles microphone mute |
F10 |
Yes | Yes | Incorrectly decreases display brightness |
F11 |
Yes | Yes | Invokes the screen-capture tool; launches Spectacle under Plasma |
F12 |
Yes | Yes | Emits KEY_PROG1; no default action
|
| ProArt key | Yes | Yes | Emits KEY_PROG1; no default action
|
| Copilot key | Yes | Yes | Emits Meta+Shift+F23; no default action
|
F5 and F10 both produce scan code ff310010 and KEY_BRIGHTNESSDOWN through the ITE keyboard controller. They cannot be remapped independently using a standard input-device keymap.Keyboard backlight
The keyboard backlight is exposed as asus::kbd_backlight with brightness levels from 0 through 3. It can be controlled using brightnessctl as described in Keyboard backlight. The default Plasma binding for F4 toggles between off and the previously selected level; cycling through every level requires a custom shortcut or script.
Multiple-display brightness
Under Plasma, F5 and F6 adjust the internal panel and DDC/CI-capable external displays together. Relative brightness offsets are preserved, while each display is independently clamped when it reaches its minimum or maximum.
Known issues
Camera hotkey emits brightness-down event
The F10 camera-disable hotkey produces the same scan code and input event as the F5 brightness-down hotkey. Consequently, it decreases display brightness and cannot be remapped independently using a standard input-device keymap. See #Function keys.
ProArt and F12 keys are indistinguishable
The dedicated ProArt key and F12 both emit KEY_PROG1. They cannot be assigned independently using a standard input-device keymap. See #Function keys.
Special keys without default actions
The F8, F12, dedicated ProArt, and Copilot keys produce input events but have no default action in the tested environment. See #Function keys.
Hibernation resume sequence
With BIOS version 320, resuming from hibernation may require a two-stage power-button sequence. See #Hibernation.
Battery charge threshold resets after reboot
The firmware resets the configured charge threshold to 100 after reboot, and the tested desktop environment does not reapply the previous selection. See #Battery charge threshold.