Bug 7042

Summary: sndconfig command line parameters don't work
Product: [Retired] Red Hat Linux Reporter: dlee
Component: sndconfigAssignee: Bill Nottingham <notting>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-11-16 15:44:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description dlee 1999-11-16 13:06:48 UTC
I am having trouble configuring my sound, and tried to execute sndconfig
with the --noprobe option (sndconfig --noprobe).  I got a screen
recognizing the option, telling me that autoprobing was "DISABLED".
However, it autoprobed anyway, and I never got to pick from the list of
supported devices.  On the recommendation of one of your support people, I
tried "sndconfig --noprobe --noautoconfig", and got the same behavior.

sndconfig reports an unsupported Intel 8086:2425 device, whereas my Win98
device driver reports a Crystal Audio MPU-401 compatible device.  I would
like to try to force sndconfig to try that, but the --noprobe option is
failing.

Daryl Lee
770-579-6588
Product ID 5a21ae6699a89
dlee

Comment 1 Bill Nottingham 1999-11-16 15:44:59 UTC
--noprobe actually still did the PCI probe. This is fixed in the
sndconfig-0.39-6, which is in Raw Hide.