ASUS Zenbook UM3402YA
Audio
In the default kernel configuration, there is currently no sound output with the internal speakers, due to the Cirrus CS35L41 HD amplifier which cannot be set up properly on boot [1]. The ASUS Zenbook UM3402YA series seems to not be the only device where this problem occurs. This was first caused by a firmware bug, but according to a Cirrus developer, the no-sound-issue seems to be fixed in a BIOS update due to the missing of certain ACPI entries [2].
There are some unofficial patches available, but these patches got rejected by a kernel developer due to the possibility of harming your device. An updated patches is available for the 6.2 kernel. Also this ssdt patch can be applied by grub (also needs at least 6.2 kernel) possibility of harming your device.
Some further, related threads: [3], [4], [5], [6], [7], [8]
Suspend/resume: one speaker silent
On kernels 6.8+ where audio works at boot, one speaker (typically the right channel) may go silent after suspend/resume. The CS35L41 amplifier firmware fails to reinitialize due to missing ACPI GPIO reset pin, leaving the amp bound but without firmware (FW EN: 0 in kernel log).
Symptoms:
- One speaker goes silent after suspend, the other works fine
- ALSA mixer shows balanced levels (issue is at kernel driver level)
- Reboot temporarily fixes it
-
journalctl -b -k | grep cs35l41showsCannot Initialize Firmware. Error: -16on the affected amp
modprobe -r / modprobe while the issue is active — this kills both speakers and only a reboot recovers.The workaround is to unload the CS35L41 modules before suspend (while the I2C bus is still clean) and reload them after resume. Create the following system-sleep hook:
/usr/lib/systemd/system-sleep/cs35l41-fix.sh
#!/bin/sh
case $1 in
pre)
modprobe -r snd_hda_scodec_cs35l41_i2c snd_hda_scodec_cs35l41_spi 2>/dev/null
modprobe -r snd_hda_scodec_cs35l41 2>/dev/null
;;
post)
modprobe snd_hda_scodec_cs35l41_i2c 2>/dev/null
;;
esac
Make it executable
No PipeWire restart is needed — the CS35L41 modules have zero direct users even while audio is playing.
Bluetooth
If you have kept Windows in dual-boot and cannot get Bluetooth working: power-off your laptop, then hold power button for 60 seconds. That will reset UEFI settings, so disable Secure Boot again if needed. After that Bluetooth will be detected and work properly.
Fingerprint
See fprint, in particular fprint#Enrolling works but verifying does not for tips on how to use the sensor.
- You should move same finger several times through power button with speed of 1-2 seconds instead of holding or tapping on button.
- Tip (of the finger): If you still have problems with recognition, then try using your pinky finger. It will go from
"almost never working" to "almost always working". The core of the problem is the sensor being too small for fprint, so the solution is making the recognizable finger smaller.
Fan control
See ASUS Zenbook UM3402YAR#Fan control.