Bug 39612

Created attachment 49652 [details]
cards

Created attachment 49653 [details]
aplay

Created attachment 49654 [details]
lspci

Created attachment 49655 [details]
lsmod

Created attachment 49656 [details]
unamer

Created attachment 49657 [details]
no connector in input/output tab

The Connector is not always shown. It depends on the Hardware present and whether or not the alsa driver presents itself in a sensible fashion (this is quite often not the case, and many alsa drivers use strange names in their kcontrols which we cannot handle).

Please attach the output from alsa-info.sh and "pacmd ls" and we can start to work out how to fix this (tho' I suspect the answer will be to update the alsa driver in some capacity (i.e. a kernel problem).

Created attachment 49705 [details]
alsa-info

Hi Sir,
I am enclosing the alsa-info for your reference.

Created attachment 49706 [details]
pcm ls

Hi Sir,
I am enclosing the info of "pcm ls" for your reference. Thanks.

If you look at the mixer controls for your card (search for the text, "Mixer controls for card 0 [PCH]" in the alsa-info output), you can see that the alsa driver does not expose controls for the various connectors/ports on your hardware.

This can happen for two reasons:
 1) The driver simply does not support this.
 2) The driver is not able to automatically work out the model of your soundcard.

If the latter is the problem you can potentially fix the issue by specifying the specific model via a setting in /etc/modprobe.d/ for the snd-hda-intel driver.

Your codec (ALC662) has several models listed here:
http://www.kernel.org/doc/Documentation/sound/alsa/HD-Audio-Models.txt

It is very much worth trying the different models manually, as the correct model may not be automatically detected correctly. If a model is found that gives you a fuller amixer -c0 output, then PA should hopefully be able to pick them up and use them.

You will have to make sure that the model= setting only applies to your sound card itself and not the HDMI sound output (which also uses the snd-hda-intel driver). I think there is some magic in the modprobe.d file that achieves this).


But either way, this is sadly not something we can fix in PulseAudio itself. It's something that needs to be addressed at a kernel level in alsa.

I suggest liaising with RHEL bugzilla and perhaps posting to alsa-devel mailing list directly if you are confident enough in taking the issue forward yourself. Otherwise your support contract with RHEL will likely allow them to pursue the issue on your behalf (tho' I won't pretend to know much about the technical details here!!).

All the best and if you need any further advise etc, please feel free to leave further comments.

Hi Sir,
Thanks for the quickly response.
For modifying the setting in /etc/modprobe.d/, there are several configuration files in it, they are anaconda.conf, blacklist-visor.conf, dist.conf, openfwwf.conf, blacklist.conf, dist-alsa.conf, dist-oss.conf.

I am not sure which I should use. 
I tried to add model in dist-alsa.conf, but it doesn't work.
Could you share with me which file I could try to modify the setting in it?

Thanks in advance.

(In reply to comment #11)
> Hi Sir,
> Thanks for the quickly response.
> For modifying the setting in /etc/modprobe.d/, there are several configuration
> files in it, they are anaconda.conf, blacklist-visor.conf, dist.conf,
> openfwwf.conf, blacklist.conf, dist-alsa.conf, dist-oss.conf.

Any file will do. You can even create a new one, provided it ends in .conf, e.g. my-broken-sound.conf :)

You can probably get some good advice on how to do it via searching the web for phrases such as "force hda model alsa" or similar terms.