linux-kernel - Re: Sound broken in 3.2.0 and 3.2.1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <s5hehup32wu.wl%tiwai@suse.de>
Date:	Tue, 24 Jan 2012 09:44:49 +0100
From:	Takashi Iwai <tiwai@...e.de>
To:	Joseph Parmelee <jparmele@...dbear.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Sound broken in 3.2.0 and 3.2.1

At Mon, 23 Jan 2012 14:27:01 -0600 (CST),
Joseph Parmelee wrote:
> 
> Hello again:
> 
> I have managed to find a work-around for this problem so that we are now
> running 3.2.1 on our production system.  For that reason I can't run
> also-info.sh on the 3.1.x system.  I do however have the results from
> /proc/asound/Intel/codec#2 for both systems taken earlier.  See below.

Hm, could you run alsa-info.sh now?  The proc codec file isn't
comprehensive and lacks of many info.  Also, if you get alsa-info.sh
outputs, please use attachments.  It's more handy to have them in
separate files than in embedded texts.

> To "fix" 3.2.1, I made the following changes to the system startup file:
> 
> I discovered that the PCM control, though absent in 3.2.1 on loading the
> sound modules with
> 
> modprobe snd_hda_intel
> modprobe snd_pcm_oss
> 
> appears after aplay is called on any sound file.  Also the main playback
> volume control has been shifted from "PCM" to "Front" which can be set with:
> 
> /usr/bin/amixer sset "Front",0 64,64

The main volume control is always "Master".  It wasn't changed.  "PCM"
is an additional control.  Now the driver supports multi-channel
playback, thus "PCM" control is split to each channel.

Usually alsactl should initialize such uninitialized volumes
appropriately at boot time, but this didn't seem to work in your
case.  Maybe it's a bug that was recently fixed in alsa-utils
package.

thanks,

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