public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: ALSA - Still No Sound
Date: Sun, 6 Mar 2011 10:50:50 -0800	[thread overview]
Message-ID: <AANLkTinKeNuRGMr9XLN-6UjeiL1RmsmUQ3a7C-ikbdEk@mail.gmail.com> (raw)
In-Reply-To: <4D679A90.5030606@optonline.net>

On Fri, Feb 25, 2011 at 4:03 AM, dhk <dhkuhl@optonline.net> wrote:
<SNIP>
> I think I have made some progress.  After getting a new sound card
> (Sound Blaster X-Fi) and building X-Fi in the kernel I have some sound,
> but it sounds terrible.  It's mostly a static noise with a hint of the
> actual audio underneath.  Also the volume is almost all the way up, but
> the volume still sounds low.
>
> The ALSA Soundcard Matrix for this card says:
> Sound Blaster X-Fi emu20k1 Details [PCI] Partially supported on 1.0.21;
> EAX and Advanced sound options like crystalizer not available
>
<SNIP>

I've got one of these X-Fi devices although mine is not a Creative
Labs device.. The device looks like a PCI-Express 1x devices but on my
motherboard it turned out it only works in one specific slot. Check
your MB specs for any similar limitations.

As for the in-kernel/module question, I've done Linux audio for years.
I can almost promise you that the Alsa devs never build the drivers
into the kernel. For that reason alone I never do. I've had a few
problems over the years when they were built in, later fixed by the
devs so that it worked built in, but in my experience it's always
better to start with it as a module, get it working, and then if it's
important to you build it in. I have about 2 dozen sound cards here. I
build all of them as drivers for every machine so that I can move
cards around for special needs and not need to rebuild the kernel.

Good luck,
Mark



  reply	other threads:[~2011-03-06 18:52 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
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 [this message]
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=AANLkTinKeNuRGMr9XLN-6UjeiL1RmsmUQ3a7C-ikbdEk@mail.gmail.com \
    --to=markknecht@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