Re: 3.19-rc1 regression bisected No sound on Dell Latitude d430

From: Hans de Bruin
Date: Mon Jan 12 2015 - 13:13:48 EST


On 01/12/2015 07:52 AM, Takashi Iwai wrote:
At Sun, 11 Jan 2015 22:44:37 +0100,
Hans de Bruin wrote:

On 01/11/2015 04:45 PM, Takashi Iwai wrote:
At Sun, 11 Jan 2015 13:21:34 +0100,
Hans de Bruin wrote:

This commit:

commit 3abb4f4d0e7aaad0d12004b5057f4486a688752b
Author: David Henningsson <david.henningsson@xxxxxxxxxxxxx>
Date: Thu Oct 16 15:33:46 2014 +0200

ALSA: hda - Use "Line Out" name instead of "PCM" when there are
other outputs

In case there are speakers or headphones as well, anything that only
covers the line out should not be labelled "PCM". Let's name it
"Line Out" instead for clarity.

Signed-off-by: David Henningsson <david.henningsson@xxxxxxxxxxxxx>
Signed-off-by: Takashi Iwai <tiwai@xxxxxxx>

breaks the sound on my dell laptop.

What sound? From the speaker, the headphone or the dock output?

The speaker. I have not checked the other exits

Are you using PulseAudio?

No

What if you adjust/unmute the volume
(likely "Line Out") manually?

running 3.18 alsamixer show these options:

Master
PCM
Mic Boost
Auto Mute mode

PCM affects the volume of the speaker.

running 3.19-rc1 alsamixer show these options:

Master
PCM
Line Out
Mic Boost
Auto Mute mode

Line out now controls the vole of the speaker (this 'new' channel had
volume 0 so did not hear anything). Changing PCM has no effect.

OK, then this is the expected change. It was a bug that we assigned
"PCM" only for the speaker and now it's corrected. Now "PCM" is still
present but this was created by alsa-lib softvol pcm, and has nothing
to do directly with the driver itself. This control is used only when
you play the stream with the dedicated setup, i.e. via "default" or
"sysdefault" device name, not via "hw", "plughw", etc.


Thanks for the explanation and the quick response. The issue can be closed.

--
Hans



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/