From: Takashi Iwai <tiwai@suse.de>
To: Joseph Parmelee <jparmele@wildbear.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Sound broken in 3.2.0 and 3.2.1
Date: Tue, 24 Jan 2012 09:44:49 +0100 [thread overview]
Message-ID: <s5hehup32wu.wl%tiwai@suse.de> (raw)
In-Reply-To: <alpine.LNX.2.00.1201230734100.5206@bruno>
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
next prev parent reply other threads:[~2012-01-24 8:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 19:44 Joseph Parmelee
2012-01-22 19:11 ` Maciej Rutecki
2012-01-23 9:44 ` Takashi Iwai
2012-01-23 20:27 ` Joseph Parmelee
2012-01-24 8:44 ` Takashi Iwai [this message]
2012-01-24 14:31 ` Joseph Parmelee
2012-01-24 14:37 ` Takashi Iwai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5hehup32wu.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=jparmele@wildbear.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®