From: Joseph Parmelee <jparmele@wildbear.com>
To: linux-kernel@vger.kernel.org
Subject: Sound broken in 3.2.0 and 3.2.1
Date: Fri, 13 Jan 2012 13:44:03 -0600 (CST) [thread overview]
Message-ID: <alpine.LNX.2.00.1201131241090.1239@bruno> (raw)
Hello:
I have built standard kernels 3.2.0 and 3.2.1 and their respective modules.
Both exhibit no sound with the following sound modules installed:
snd_pcm_oss
snd_mixer_oss
snd_hda_codec_realtek
snd_hda_intel
snd_hda_codec
snd_pcm
snd_timer
snd
soundcore
snd_page_alloc
Kernels 3.1.8 works as expected with the same set of modules (for 3.1.8)
installed.
What appears to be happening is that the available controls are not being
properly elucidated in 3.2.x. For example both aumix and gamix show that
the PCM control is missing; it appears normally in 3.1.x using the same set
of driver modules. This is causing the immediate problem as this control is
set to zero on bootup and cannot be accessed thereafter. Sound appears to
play normally through the alsa driver in mplayer for example, and the
internal mplayer volume control appears to work normally, but there is no
sound.
The controls elucidated differ as follows (taken from gamix) for the same
hardware (intel hda with realtek alc662 codec):
3.1.x:
1 - PCM
2 - Headphone
3 - Rear Mic
4 - Front Mic
5 - Line
6 - Auto-mute Mode
7 - Capture
8 - Capture 1
9 - Input Source
10 - Input Source 1
11 - IEC958
12 - Master
3.2.x:
1 - Master
2 - Channel Mode
3 - Front
4 - Surround
5 - Center
6 - LFE
7 - Headphone
8 - Rear Mic
9 - Line
10 - Auto-mute Mode
11 - Capture
12 - Capture 1
13 - Input Source
14 - Input Source 1
15 - IEC958
Yours,
Joseph Parmelee
Wild Bear Systems
next reply other threads:[~2012-01-13 19:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 19:44 Joseph Parmelee [this message]
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
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=alpine.LNX.2.00.1201131241090.1239@bruno \
--to=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®