All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan_Lasley@hilton.com
To: linux-sound@vger.kernel.org
Subject: Ensonic AudioPCI sound card problems
Date: Tue, 11 Jul 2000 14:37:19 +0000	[thread overview]
Message-ID: <marc-linux-sound-96332630904955@msgid-missing> (raw)



I have an old, scrounged Aztec ISA sound card that works just fine in a
Gateway P5-133.  I bought an Ensoniq AudioPCI and I can't make it
work!

I'm using Red Hat Linux 6.0 and I'm trying to install the sound card
with "sndconfig".  sndconfig worked like a charm for the old sound
card, but I've tried the following configurations with the new card
and neither will work:

     Ensoniq AudioPCI 1370 (SoundBlaster 64/128 PCI)

     Creative/Ensoniq AudioPCI 1371

I get this error for the first:

     The following error occurred running the modprobe program:
     /lib/modules/2.2.5-15/misc/es1370.o:
     init_module: Device or resource busy

And this error for the second:

     The following error occurred running the modprobe program:
     /lib/modules/2.2.5-15/misc/es1371.o:
     init_module: Device or resource busy

I don't find any other information in /var/log/messages.

I am using the kernel which comes with Red Hat 6.0, so it should have
support for all known sound cards.  Again, I had *no* problems in
configuring and running another sound card in this system.

I've checked /usr/src/linux/Documentation/sound/* and I found no
help on this particular sound card.

Can anyone furnish a clue?

Thanks.

Dan

             reply	other threads:[~2000-07-11 14:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-11 14:37 Dan_Lasley [this message]
2000-07-11 15:28 ` Ensonic AudioPCI sound card problems Jay Ts
2000-07-11 15:50 ` Dave Phillips
2000-07-11 19:01 ` D. Marcus Johnson
2000-07-11 19:10 ` 
2000-07-12 10:09 ` Thomas Sailer

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-96332630904955@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.