LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   [Arch] Alsa/Pulseaudio sound issue - Analogue sound card disabled (https://www.linuxquestions.org/questions/linux-software-2/%5Barch%5D-alsa-pulseaudio-sound-issue-analogue-sound-card-disabled-4175688716/)

Sudonix 01-16-2021 10:22 PM

[Arch] Alsa/Pulseaudio sound issue - Analogue sound card disabled
 
Hello. This is my first time completing an Arch installation, and I'm having a strange issue with my system's sound cards. By default, the system has set the output audio to my HDMI monitor (Nvidia HDA). I am trying to instead set the output to my motherboard's analogue audio which is 'Family 17h (Models 00h-0fh) HD Audio Controller' (AMD Ryzen chipset). Unfortunately, according to Pulsemixer, the only option for the card is "Off" or "Default / Off". There isn't much documentation about this issue online. Moving applications from the HDMI audio source to the Family 17h source does not yield any results. I've also tried installing various Alsa firmware to no avail. Alsamixer sees the sound card just fine, however.

I should also mention, when I was tweaking my motherboard's BIOS, enabling CSM support so I could dual boot an older operating system, the audio output changed from my main HDMI monitor to my secondary DisplayPort monitor, though still under the 'HDMI' label. I'm not sure why this happened.

Any ideas on what I could do? Thanks.

ferrari 01-16-2021 11:56 PM

I suggest that you start with some diagnostic information first. Run the alsa-info.sh diagnostic utility, let it upload the output to an online server, and post the URL here.

More info...
https://wiki.archlinux.org/index.php...Debugging_ALSA
https://www.alsa-project.org/wiki/AlsaInfo

That should show the state of the hardware etc.

ondoho 01-17-2021 01:20 AM

Pulseaudio is confusing.
Make sure to triple-check the settings in pavucontrol, all tabs, also advanced.

BTW, if Alsamixer shows any more than this it probably means that the ALSA-pulseaudio stack is misconfigured.

Sudonix 01-17-2021 11:20 AM

Alright, ran alsa-info. Here's the log.

As for Alsamixer, looks pretty much the same. Here's the Nvidia and motherboard audio, in case that helps. I have checked every audio jack on the motherboard. No output from any of the audio jack channels, even with volume on full.

ferrari 01-17-2021 03:28 PM

The alsa diagnostic output checks out ok at a quick glance (drivers loaded and output not muted).

Turning attention back to PulseAudio, you can choose a profile in pavucontrol in the 'Configuration' tab. So see if setting that as required helps.

A thread that may be of interest...
https://unix.stackexchange.com/quest...o-be-available

ferrari 01-17-2021 03:48 PM

I note that you have the ALC1220 chipset reported.....one possibility is that the internal pinout needs remapping so that sound can appear via the analog output. This can be resolved using the hdajackretask utility. For example, have a read of this Manjaro post...
https://archived.forum.manjaro.org/t...lc1220/89412/7

Another concerning a user with the ALC1220 chipset...
https://askubuntu.com/questions/9371...ones-work?rq=1

Sudonix 01-17-2021 04:31 PM

Quote:

Originally Posted by ferrari (Post 6208886)
Turning attention back to PulseAudio, you can choose a profile in pavucontrol in the 'Configuration' tab. So see if setting that as required helps.

I opened up Pavucontrol, but in the configuration tab it also only lists the options "Default (unavailable)" and "Off".

Installed and ran hdajackretask and tried setting the Green Line Out, Rear Side (rear IO headphone jack) to "Headphone". Unfortunately, it seems like the settings could not be applied due to some "not authorized/no session cookie" error.

ferrari 01-17-2021 07:08 PM

Quote:

Originally Posted by Sudonix (Post 6208900)
Installed and ran hdajackretask and tried setting the Green Line Out, Rear Side (rear IO headphone jack) to "Headphone". Unfortunately, it seems like the settings could not be applied due to some "not authorized/no session cookie" error.

A similar error reported in this Arch Linux thread. Not sure what else to advise here. You might want to cast your support net wider by posting to that forum as well.


All times are GMT -5. The time now is 05:09 PM.