Bug 31359 - Soundblaster 32 ISAPNP FAILS to WORK
Summary: Soundblaster 32 ISAPNP FAILS to WORK
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: sndconfig
Version: 6.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-03-10 18:03 UTC by Brian Z
Modified: 2014-03-17 02:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-04-19 15:36:27 UTC
Embargoed:


Attachments (Terms of Use)
2.4.2 isapnp (4.79 KB, text/plain)
2001-03-10 18:03 UTC, Brian Z
no flags Details

Description Brian Z 2001-03-10 18:03:19 UTC
Whenever I try to install the proper modules using setup (according 
to /proc/isapnp) I am unable to get the Soundblaster to run.  I receive an 
error 47 saying that the device is active.  This hasn't worked since 
version 6.2 of RedHat, but during the 7.0 beta cycle and afterwords, 
nobody would pay any attention to it.  I've also upgraded to the latest 
rawhide kernel 2.4.2 and setuptool.  Any help would be appreciated.  I am 
attaching my ISAPNP file to this bug (another bug has been filed for my 
failure to get the SYM53c416 working).  Thanks!

Comment 1 Brian Z 2001-03-10 18:03:44 UTC
Created attachment 12345 [details]
2.4.2 isapnp

Comment 2 Bill Nottingham 2001-03-11 03:52:58 UTC
Please try the sndconfig/kudzu RPMs available at
http://people.redhat.com/notting/sndconfig/

What error messages do you get?

Comment 3 Brian Z 2001-04-19 02:11:26 UTC
Hey, working in the official 7.1 :)  Good work.  Only thing was I had to 
manually run the sound configuration tool (through setup) to get the soundcard 
operational.  It would be nice if no additional steps pased kudzu were needed.  
Thanks!

Comment 4 Bill Nottingham 2001-04-19 15:36:24 UTC
Marking as resolved in the current release.


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