From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: ALSA - Still No Sound
Date: Sun, 6 Mar 2011 10:59:32 +0000 [thread overview]
Message-ID: <201103061059.44222.michaelkintzios@gmail.com> (raw)
In-Reply-To: <4D7353C7.7010002@gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1184 bytes --]
On Sunday 06 March 2011 09:28:39 Dale wrote:
> Mick wrote:
> > On Saturday 26 February 2011 21:53:52 walt wrote:
> >> 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.
> >
> > Because alsaconf needs to probe one module at a time and set its
> > parameters.
>
> Just to confuse things more, I have the same driver for my sound and I
> build everything into my kernel and always have. The sound worked as
> soon as I unmuted it.
>
> root@fireball / # cat /usr/src/linux/.config | grep REALTEK
> CONFIG_SND_HDA_CODEC_REALTEK=y
> root@fireball / #
>
> Weird huh?
Like you, I used to build the lot into the kernel for years and it worked
fine. Suddenly it stopped. With no other discernible changes at the time to
blame for this I raised a bug. The devs recommended that I should build alsa
as modules and that fixed the problem. I haven't yet tried to go back to
building it all in the kernel to see if it would still work.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-03-06 11:01 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
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 [this message]
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=201103061059.44222.michaelkintzios@gmail.com \
--to=michaelkintzios@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