public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: walt <w41ter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: ALSA - Still No Sound
Date: Sat, 26 Feb 2011 13:53:52 -0800	[thread overview]
Message-ID: <ikbsph$8qn$1@dough.gmane.org> (raw)
In-Reply-To: <4D5A58ED.4090602@optonline.net>

On 02/15/2011 02:43 AM, dhk wrote:
> On 02/14/2011 12:29 PM, walt wrote:
>> On 02/14/2011 03:43 AM, dhk wrote:
>>
>>> What are the "Intel HD Audio" codecs?  I don't
>>> remember doing anything explicitly for them.  How do I check them?
>>> Thanks.
>>
>> Under the HD-Intel sound card driver menu there are several codecs for
>> specific sound chips.  e.g. I use the one for realtek, but yours may be
>> a different one.  Doesn't hurt to build them all as modules and see which
>> one(s) your kernel actually uses.
>>
>>
>>
>
> It looks like all the codec's are built in.  I'm not sure what the last
> one in the list does.
>
> # grep -i realtek /etc/kernels/kernel-config-x86_64-2.6.36-gentoo-r5
> CONFIG_REALTEK_PHY=m
> CONFIG_SND_HDA_CODEC_REALTEK=y
> # grep -i codec /etc/kernels/kernel-config-x86_64-2.6.36-gentoo-r5
> CONFIG_SND_AC97_CODEC=m
> CONFIG_SND_HDA_CODEC_REALTEK=y
> CONFIG_SND_HDA_CODEC_ANALOG=y
> CONFIG_SND_HDA_CODEC_SIGMATEL=y
> CONFIG_SND_HDA_CODEC_VIA=y
> CONFIG_SND_HDA_CODEC_ATIHDMI=y
> CONFIG_SND_HDA_CODEC_NVHDMI=y
> CONFIG_SND_HDA_CODEC_INTELHDMI=y
> CONFIG_SND_HDA_CODEC_CIRRUS=y
> CONFIG_SND_HDA_CODEC_CONEXANT=y
> CONFIG_SND_HDA_CODEC_CA0110=y
> CONFIG_SND_HDA_CODEC_CMEDIA=y
> CONFIG_SND_HDA_CODEC_SI3054=y
> # CONFIG_SND_SOC_ALL_CODECS is not set
>
> This is the genkernel so pretty much everything is built in.

There is a very recent post from someone (Walter?) that says he got audio
only after compiling all the kernel sound features as modules, but he has
no idea why (nor do I) but, as no one yet has a better idea, I'd try it as
an experiment.





  reply	other threads:[~2011-02-26 22:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-13 23:19 [gentoo-user] ALSA - Still No Sound dhk
2011-02-14  2:01 ` Bill Kenworthy
2011-02-14 11:43   ` dhk
2011-02-14 17:29     ` [gentoo-user] " walt
2011-02-15 10:43       ` dhk
2011-02-26 21:53         ` walt [this message]
2011-03-06  0:29           ` dhk
2011-03-06  9:01             ` Mick
2011-03-06  8:56           ` Mick
2011-03-06  9:28             ` Dale
2011-03-06 10:59               ` Mick
2011-03-06 11:33                 ` Dale
2011-03-06 16:25               ` dhk
2011-02-15 11:10       ` laconism
2011-02-15 11:35         ` dhk
2011-02-25 12:03           ` dhk
2011-03-06 18:50             ` Mark Knecht
2011-03-06 20:38               ` James Wall
2011-03-06 21:31                 ` Mark Knecht
2011-03-07 12:41                   ` dhk
2011-03-07 16:15                     ` Mick
2011-03-15 12:42                       ` dhk
2011-03-30  9:37                         ` dhk
2011-03-30 13:50                           ` Mark Knecht
2011-03-30 14:00                             ` dhkuhl
2011-02-14  2:21 ` Nikos Chantziaras
2011-02-14 11:44   ` dhk
     [not found] <glTy9-4Uo-3@gated-at.bofh.it>
     [not found] ` <gti8p-ia-5@gated-at.bofh.it>
     [not found]   ` <gtiBs-ZD-5@gated-at.bofh.it>
     [not found]     ` <gtk0y-3vr-29@gated-at.bofh.it>
2011-03-06 13:08       ` Elaine C. Sharpe

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='ikbsph$8qn$1@dough.gmane.org' \
    --to=w41ter@gmail.com \
    --cc=gentoo-user@lists.gentoo.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