Open darkwater opened 3 months ago
I had a similar issue; try this: https://github.com/mudkipme/awesome-minisforum-v3/issues/9
I have the same issue on Arch, regardless of whether I apply the fix from #9 or the one in the repo.
@Nixola @darkwater did you guys install alsa-firmware
?
I didn't have it, but installing it changed nothing; I'm still getting the same issues with both the fix in the repo and the one in issue #9 .
I think this is a bug upstream in pipewire/wireplumber, introduces somewhere around v1.2.0. It seems that the device is being muted in alsa and that state is not properly synced or something.
As a workaround, you can try the following (I'm not sure if all these steps are necessary, or that only the disabling of auto-mute is enough, but I've already spent way too long on getting this to work).
m
when you have master selected.auto mute mode
and press up
to make sure it's disabled
now the alsa settings should be saved properly and sound should work consistently after a reboot.
Furthermore, I am unable to get the microphone working with the wireplumber config from #9. However, when using the config from the repo and the following modprobe:
/etc/modprobe.d/audio.conf
# This enables the microphone
options snd-hda-intel model=alc256-asus-aio
the microphone does work for me.
This fixes the output for me, thanks!
I've installed Arch on my V3 and applied the soft mixing workaround, but the following does not work:
But this does work:
So, if my system boots with soft mixing enabled, the speakers will not work at all. Does anyone have an idea of what could cause this? My workaround for now will be to edit the configuration and restart pipewire automatically on boot.
*edit: found out the profile also needs to be changed
I see 5 audio devices on my Family 17h/19h HD Audio Controller:
Changing from whichever speaker profile is currently selected, to the other speaker profile, is the extra step mentioned.