Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 187 - Sndconfig cant configurate Ensoniq card.
Summary: Sndconfig cant configurate Ensoniq card.
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: sndconfig
Version: 5.2
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1998-11-24 16:34 UTC by arcadepreserv
Modified: 2014-03-17 02:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1998-12-29 16:26:46 UTC

Attachments (Terms of Use)

Description arcadepreserv 1998-11-24 16:34:06 UTC
I have a Soundscape Ensoniq vivo 90 Soundcard PnP (ISA), and
I cant get it to work with Redhat Linux 5.2 (Or earlier).

5.2 is the first redhat version that can find the correct
card when autoprobing, but when it is up to play the test
sound, it claims that some resource is busy. I get a click
in the speakers, like the card is resetted so there is a
little life in it.

I have also tested to set the parametsers manually, and have
also tested using the soundblaster xxx instead.

Comment 1 Bill Nottingham 1998-11-24 16:54:59 UTC
I'm not that surprised; we don't have any sorts of soundscapes
to test with, much less PnP ones. If you could e-mail

- the /etc/isapnp.conf sndconfig wrote
- the /etc/conf.modules sndconfig wrote
- the output of the command '/sbin/pnpdump'
- the settings required to make it work, if you can get it
to work by futzing the settings manually

to, I'll take a look at it and try
and make sure that it's at least doing something somewhat

Comment 2 Bill Nottingham 1998-12-29 16:26:59 UTC
This should hopefully be fixed (to some extent) in
sndconfig-0.29-1, available from
If this still fails, reopen the bug and we'll try again.

Note You need to log in before you can comment on or make changes to this bug.