From: "Elaine C. Sharpe" <elaine@southernstarsolutions.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: ALSA - Still No Sound
Date: Sun, 6 Mar 2011 08:08:48 -0500 [thread overview]
Message-ID: <20110306130848.GA308@satcidananda> (raw)
In-Reply-To: <gtk0y-3vr-29@gated-at.bofh.it>
In linux.gentoo.user, you wrote:
> --nextPart2016980.EoLg6xAmlW
> Content-Type: Text/Plain;
> charset="us-ascii"
> Content-Transfer-Encoding: quoted-printable
>
> 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.
>> >=20
>> > Because alsaconf needs to probe one module at a time and set its
>> > parameters.
>>=20
>> 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.
>>=20
>> root@fireball / # cat /usr/src/linux/.config | grep REALTEK
>> CONFIG_SND_HDA_CODEC_REALTEK=3Dy
>> root@fireball / #
>>=20
>> Weird huh?
>
> Like you, I used to build the lot into the kernel for years and it worked=20
> fine. Suddenly it stopped. With no other discernible changes at the time =
> to=20
> blame for this I raised a bug. The devs recommended that I should build al=
> sa=20
> as modules and that fixed the problem. I haven't yet tried to go back to=20
> building it all in the kernel to see if it would still work.
>=2D-=20
> Regards,
> Mick
>
Same thing happened here, I used to build support for my sound card into
the kernel but it stopped working a few months ago. Rebuilding the
kernel without the built-in sound drivers and using the modules instead
works now. ISTR that years ago it was the opposite, which is why I got
in the habit of building kernels with alsa drivers built-in.
The odd thing is I didn't see any news about it, nor was the internet
packed with people suddenly having alsa problems, so I never knew what
exactly happened.
--
caveat utilitor
♫ ❤ ♫ ❤ ♫ ❤ ♫
next parent reply other threads:[~2011-03-06 13:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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
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
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=20110306130848.GA308@satcidananda \
--to=elaine@southernstarsolutions.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