[BUG] UX582HS Asus No sound (ALC294) Subsystem 0x1043:1b52

[bulutthecat]

System Information:

• Computer: Asus Zenbook UX582HS
• CPU: Intel Tiger Lake H (i9-11900H)
• Audio Codec: Realtek ALC294
• Subsystem ID: 0x1043:1b52
• OS: Ubuntu 25.10
• Kernel: 6.17.0-8-generic

Internal speakers are detected in the UI (GNOME Settings) but produce no sound.
The system loads the SOF driver with a generic topology (sof-hda-generic-4ch.tplg).
Headphones work correctly.

ALSA information URL:
https://alsa-project.org/db/?f=f44dd09987e8af3e9eace09aa04c7e22f4ed1e19

Steps to Reproduce:

1. Boot system.
2. Open Settings -> Sound.
3. Select "Speaker" output.
4. Test audio (Result: Silence)

I have tried the following without success:

1. snd_intel_dspcfg.dsp_driver=1 Still no sound, device detected but silent.
2. snd_hda_intel.model=asus-zenbook No change.
3. Created firmware to force Pin 0x17 to 0x90170110 (Internal Speaker). UI correctly identifies "Speaker" instead of "Line Out", but audio remains silent.
4. Tried verb sequence:
   0x20 0x500 0x1b
0x20 0x477 0x4a4b
0x20 0x500 0xf
0x20 0x477 0x74
   This just caused the audio device to disappear/crash entirely until reboot.

I have had this issue since Ubuntu 22.04 when I first attempted to use Ubuntu on this laptop, ever since I have tested each major release with no change.
Any help would be appreciated in solving the issue.

[bulutthecat]

Just to note it down here, I am quite sure there is missing topology for this specific machine. I attempted all similar patches which were identical across ALC294 laptops and even newer variants of the same laptop but have had the same issue.

[kv2019i]

Checked the alsa-info details for SOF FW operation and this all looks good. sof-hda-generic-4ch.tplg is the correct DSP topology for this system (a generic HDA headset/speaker codec from Realteak, an 4 digital mics connected directly to the PCH handled by DSP). This looks like an issue with the HDA codec Linux driver. Let me move to kernel component.

[kv2019i]

@bulutthecat This looks like another case of #5504 ...
(UPDATE: I see you've tried multiple workarounds for ACL294 based ASUS machines already, so maybe the solutions for #5504 won't work, but something like this is needed to the codec driver to enable the speakers).

[bulutthecat]

@bulutthecat This looks like another case of #5504 ... (UPDATE: I see you've tried multiple workarounds for ACL294 based ASUS machines already, so maybe the solutions for #5504 won't work, but something like this is needed to the codec driver to enable the speakers).

I will look into getting a verb trace from a Windows VM in the meantime.