[BUG] ASUS ProArt PX13 HN7306EA - No sound (AMD ACP70 no playback device)

[zakissimo]

Pre-flight checklist

• I have searched existing issues and this is not a duplicate.
• I have read the Contributing Guidelines.
• I have verified the issue is reproducible with the latest available CachyOS kernel.

Upstream / vanilla kernel check

I was unable to test with a vanilla/upstream kernel

Kernel variant

linux-cachyos (EEVDF, Clang)

System information (cachyos-bugreport.sh)

https://paste.cachyos.org/p/3ccdbcb.log

Manual system information (if cachyos-bugreport.sh is unavailable)

Bug description

Hardware: ASUS ProArt PX13 HN7306EA (AMD Ryzen AI MAX+ 395)
OS: CachyOS 6.19.3-2-cachyos
Kernel: 6.19.3-2-cachyos

Issue Summary

Fresh CachyOS install could not boot. After adding iommu=pt kernel parameter, system boots but has no sound.

Boot Issue (Workaround Found)

• Error on fresh boot: AMD-Vi: Event: logged IO_PAGE_FAULT
• Fix: Add iommu=pt to kernel parameters

Audio Issue

• Internal speakers do not work
• No playback device created for AMD ACP70 audio

Verification

$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
  (no playback on card 1)

$ cat /proc/asound/cards
 0 [Generic        ]: HDA-Intel - HD-Audio Generic
                      HD-Audio Generic at 0xa0440000 irq 161
 1 [acppdmmach     ]: acp-pdm-mach - acp-pdm-mach
                      ASUSTeK COMPUTERINC.-ProArtPX13HN7306EA-1.0-HN7306EA

Card 1 (AMD ACP70) has no playback device, only DMIC capture exists.

Steps to reproduce

1. Install CachyOS on ASUS ProArt PX13 HN7306EA laptop
2. Attempt to boot (fresh install)
3. System fails to boot with error: AMD-Vi: Event: logged IO_PAGE_FAULT
4. Add iommu=pt kernel parameter to boot (workaround for boot issue)
5. System boots successfully but has no sound

Expected behavior

Internal speakers should work like other AMD Strix Halo laptops.

Actual behavior

No sound output from internal speakers

Logs / stack traces

Additional system information

No response

[1Naim]

Feb 27 12:46:21 consider wireplumber[1342]: wp-state: failed to create directory /.local/state/wireplumber: Permission denied
Feb 27 12:46:21 consider wireplumber[1342]: wp-state: failed to create directory /.local/state/wireplumber: Permission denied
Feb 27 12:46:21 consider wireplumber[1342]: wp-state: failed to create directory /.local/state/wireplumber: Permission denied
Feb 27 12:46:21 consider wireplumber[1342]: wp-state: failed to create directory /.local/state/wireplumber: Permission denied
Feb 27 12:46:21 consider wireplumber[1342]: wp-state: failed to create directory /.local/state/wireplumber: Permission denied
Feb 27 12:46:21 consider wireplumber[1342]: wp-state: failed to create directory /.local/state/wireplumber: Permission denied
Feb 27 12:46:21 consider wireplumber[1342]: s-monitors: Failed to create 'api.alsa.acp.device' device

Weird, can you try to create that directory manually and then restart wireplumber?

mkdir -p ~/.local/state/wireplumber
systemctl --user restart pipewire pipewire-pulse.socket wireplumber

[zakissimo]

I did and generated a new bug report:

Feb 27 14:39:48 consider wireplumber[2632]: pw.core: 0x55b1e328a7c0: leaked proxy 0x55b1e32d53f0 id:3
Feb 27 14:39:48 consider wireplumber[2632]: pw.core: 0x55b1e328a7c0: leaked proxy 0x55b1e33af420 id:5
Feb 27 14:39:48 consider wireplumber[2632]: pw.core: 0x55b1e328a7c0: leaked proxy 0x55b1e338b540 id:6
Feb 27 14:39:48 consider wireplumber[2632]: pw.core: 0x55b1e328a7c0: leaked proxy 0x55b1e33b4190 id:7
Feb 27 14:39:48 consider wireplumber[2632]: pw.core: 0x55b1e328a7c0: leaked proxy 0x55b1e3387c90 id:8
Feb 27 14:39:48 consider wireplumber[2632]: pw.core: 0x55b1e328a7c0: leaked proxy 0x55b1e33813a0 id:9
Feb 27 14:39:48 consider /usr/lib/xdg-desktop-portal[1843]: Caught PipeWire error: connection error
Feb 27 14:39:48 consider wireplumber[2949]: s-monitors: Failed to create 'api.alsa.acp.device' device

Full report

[1Naim]

It looks like you have the LTS kernel installed, can you try with that? You don't need the iommu argument with that kernel.

[zakissimo]

Report after rebooting with LTS without that kernel param
Same message again, weird because the directory exists. But it's looking into /.local and not ~/.local.
I tried booting from the usb/iso and there too I don't have any sound. I can try running a report from there?
Also just in case it might be relevant, when shutting down / rebooting I see the following message:
Calling import-environment without a list of variable names is deprecated

[1Naim]

Also just in case it might be relevant, when shutting down / rebooting I see the following message:
Calling import-environment without a list of variable names is deprecated

Is this niri?

[zakissimo]

Is this niri?

yes, I just tried rebooting from kde and I don't see the message.

[1Naim]

That's fine then, you can ignore it.

[zakissimo]

I created /.local/state/wireplumber and I see this:

Feb 27 15:17:27 consider wireplumber[1357]: s-monitors: Failed to create 'api.alsa.acp.device' device
Feb 27 15:17:27 consider wireplumber[1357]: default: Failed to get percentage from UPower: org.freedesktop.DBus.Error.NameHasNoOwner
Feb 27 15:17:28 consider wireplumber[1357]: wp-state: <WpState:0x563b43a8a3c0> could not save stream-properties: Failed to create file “/.local/state/wireplumber/stream-properties.K6MJL3”: Permission denied

[1Naim]

Do you get no sound and the same log from KDE too?

[zakissimo]

Log from kde
I deleted the directory before rebooting. Same log and no sound :(

[1Naim]

I'm out of ideas. Are you sure $HOME is not just an empty string?