Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Dan Lasley <Dan_Lasley@hilton.com>
To: linux-sound@vger.kernel.org
Subject: Ensoniq AudioPCI problem solved
Date: Mon, 17 Jul 2000 14:32:22 +0000	[thread overview]
Message-ID: <marc-linux-sound-96384437322596@msgid-missing> (raw)

In a recent posting, I asked if anyone knew why Red Hat 6.0 couldn't
see and configure my Ensoniq AudioPCI sound card.  A number of
respondents suggested I load the ALSA sound drivers
(http://www.alsa-project.org/).

I thanked everyone who responded (except jay@toltec.metran.cx, who I
could not reach via e-mail).

The ALSA code worked, but eLinux.com, the vendor who sold the AudioPCI
card, had a better solution:

   "It is supported automatically under redhat 6.2 but under 6.0 you're
   probably going to have to recompile your kernel and enable its support
   as a module under sound support. Redhat 5.2 and 6.0 didn't have the
   sound autodetected too well although 6.2 is just fine for the most part."

The RH 6.0 information in the first sentence is incorrect; I'd already
tried that.

I guessed that a newer kernel (rather than a Red Hat 6.2 component
such as "sndconfig") would fix the problem, so I loaded the 2.2.16
kernel and configured sound as:

   <M> Sound card support
   <M> Creative Ensoniq AudioPCI 97 (ES1371)

Now the Ensoniq AudioPCI works with standard Linux components,
including the X Windows mixer.

Dan

             reply	other threads:[~2000-07-17 14:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-17 14:32 Dan Lasley [this message]
2000-07-18 11:38 ` Ensoniq AudioPCI problem solved 

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=marc-linux-sound-96384437322596@msgid-missing \
    --to=dan_lasley@hilton.com \
    --cc=linux-sound@vger.kernel.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