From: Tony Vroon <tony@linx.net>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: alsa-devel@alsa-project.org, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.de>, "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] CONFIG_SND_HDA_INTEL regression on 2.6.37-rc3 - no audio
Date: Tue, 30 Nov 2010 21:39:57 +0000 [thread overview]
Message-ID: <1291153197.4814.11.camel@amalthea> (raw)
In-Reply-To: <AANLkTi=ywUP8QUDGqotutccf9E2a1b5U2bKNZDWa3PG3@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 826 bytes --]
On Tue, 2010-11-30 at 13:31 -0800, Luis R. Rodriguez wrote:
> snd_hda_codec_analog,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,thinkpad_acpi,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
Note that on some ThinkPads, there is an additional output mixer that is
not always exported to ALSA. Please make sure that your hardware volume
is unmuted and at a reasonable volume.
Could you use alsa-info.sh to gather your codec files, system DMI, etc
please?
(The only audio regression in 2.6.37 that I'm aware of was Realtek
ALC269-related and has already been fixed. It left me without volume
control until -rc3)
Regards,
--
Tony Vroon
UNIX systems administrator
London Internet Exchange Ltd, Trinity Court, Trinity Street,
Peterborough, PE1 1DA
Registered in England number 3137929
E-Mail: tony@linx.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-11-30 21:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 21:31 CONFIG_SND_HDA_INTEL regression on 2.6.37-rc3 - no audio Luis R. Rodriguez
2010-11-30 21:39 ` Tony Vroon [this message]
2010-11-30 21:45 ` [alsa-devel] " Daniel Chen
2010-12-01 6:50 ` Takashi Iwai
2010-12-17 1:04 ` [alsa-devel] " Adam Williamson
2010-12-17 8:05 ` Takashi Iwai
2011-01-02 9:11 ` Pavel Machek
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=1291153197.4814.11.camel@amalthea \
--to=tony@linx.net \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=perex@perex.cz \
--cc=rjw@sisk.pl \
--cc=tiwai@suse.de \
/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