From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755237Ab2AXIov (ORCPT ); Tue, 24 Jan 2012 03:44:51 -0500 Received: from cantor2.suse.de ([195.135.220.15]:33252 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753766Ab2AXIou (ORCPT ); Tue, 24 Jan 2012 03:44:50 -0500 Date: Tue, 24 Jan 2012 09:44:49 +0100 Message-ID: From: Takashi Iwai To: Joseph Parmelee Cc: linux-kernel@vger.kernel.org Subject: Re: Sound broken in 3.2.0 and 3.2.1 In-Reply-To: References: User-Agent: Wanderlust/2.15.6 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.7 Emacs/23.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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