You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The sound device is reported with lsusb as 0db0:543d Micro Star International USB Audio
With default configuration, all seems well until hearing 5.1/7.1 channel audio.
At this point it is realized that my 2.1 configuration is playing audio in surround mode and I'm missing virtually all of the most important sound.
After researching for a while, I've found the following to hacky-workaround? the issue:
This adds matching under ALC4080 for my 0db0:543d.
After this I have 2.1 as well as the ability to select 5.1 or 7.1.
I have patched the alsa-ucm-conf package locally with epoch to finalize the configuration.
However, I do not know that this is the appropriate solution. Whether my sound device is mis-identified by ALSA/UCM, misrepresented by MSI? Something else?
Please advise and perhaps this can be resolved in a way that benefits more than just myself.
The text was updated successfully, but these errors were encountered:
I have MSI TRX40 Pro 10G on Arch Linux.
alsa-ucm-conf 1.2.12-1
linux-zen 6.9.6.zen1-1
The sound device is reported with lsusb as
0db0:543d Micro Star International USB Audio
With default configuration, all seems well until hearing 5.1/7.1 channel audio.
At this point it is realized that my 2.1 configuration is playing audio in surround mode and I'm missing virtually all of the most important sound.
After researching for a while, I've found the following to hacky-workaround? the issue:
This adds matching under ALC4080 for my 0db0:543d.
After this I have 2.1 as well as the ability to select 5.1 or 7.1.
I have patched the alsa-ucm-conf package locally with epoch to finalize the configuration.
However, I do not know that this is the appropriate solution. Whether my sound device is mis-identified by ALSA/UCM, misrepresented by MSI? Something else?
Please advise and perhaps this can be resolved in a way that benefits more than just myself.
The text was updated successfully, but these errors were encountered: