Bug 8376 - SOUNDCONFIG UTILITY HANGS MY SYSTEM
Summary: SOUNDCONFIG UTILITY HANGS MY SYSTEM
Status: CLOSED DUPLICATE of bug 5806
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: sndconfig (Show other bugs)
(Show other bugs)
Version: 6.1
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-01-11 16:02 UTC by rvsaldana
Modified: 2014-03-17 02:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-01-31 19:11:24 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description rvsaldana 2000-01-11 16:02:05 UTC 
The problem I have is is with the soundconfig utility it needs to function
properly. It all cases it recognizes my Soundblaster PCI 128 card in my
Gateway 300mghz but it fails it configuire itself it usually hangs my
RedHat Linux 6.1 system to the point I have no other choice but to pull
the plug and cut the electricity to my system. Why this happans I do not
know but I beleieve this is a serious error in the soundconfig utility. I
have also configuired my kernel to recognize sound on my system. But the
soundconfig utility still continues to hang. Right now I also get lib
module busy errors from this utility..? Right know I am in search of a
Soundcard that functions in Linux and is easily detected by Soundconfig.
Comment 1 Cristian Gafton 2000-01-27 08:22:59 UTC 
assigned to sndconfig
Comment 2 Bill Nottingham 2000-01-27 23:20:59 UTC 
It shouldn't hang the system completely. If you have one of
the newer PCI 128 cards, it will hang *sndconfig* when it
tries to play the audio file, but you should be able to
break out of it.

As for support for these PCI 128 cards, it should be fixed
in 2.2.15pre<whatever>.
Comment 3 Bill Nottingham 2000-01-31 19:11:59 UTC 
*** This bug has been marked as a duplicate of 5806 ***
Note You need to log in before you can comment on or make changes to this bug.