Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 80450 - sndconfig fails to start on virgin install
sndconfig fails to start on virgin install
Product: Red Hat Public Beta
Classification: Retired
Component: sndconfig (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
David Lawrence
Depends On:
Blocks: 79578
  Show dependency treegraph
Reported: 2002-12-26 14:16 EST by charles nofsinger
Modified: 2014-03-16 22:33 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-12-31 22:06:46 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description charles nofsinger 2002-12-26 14:16:23 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 4.0; T312461)

Description of problem:
Having had Redhat 8.0 on an HP Kayak P3 533 with a gravis ultrasound
as the soundcard without problems, attempting to configure with sndconfig led 
to a message explaining that my module path was incorrect and soundcore.o could 
not be located.  

Manually configured the sound modules and everything worked fine

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Run sndconfig with gravis ultrasound on Phoebe

Expected Results:  Should have allowed configuration

Additional info:
Comment 1 Bill Nottingham 2002-12-30 01:28:57 EST
What was the config produced when running sndconfig?
Comment 2 westbrook 2002-12-31 14:15:22 EST
I have the same problem.  Here is the error:

ERROR: No Sound Modules Found

You don't seem to be running a kernel with modular sound
enabled.  (soundccore.o was not found in the module search path).
To use sndconfig, you must be running a kernel with modular
sound, such as the kernel shipped with Red Hat Linux or a 2.2
or greater kernel.


It then exits with no configuaration changes when you press enter.
Comment 3 Bill Nottingham 2002-12-31 22:00:28 EST
Oh, duh, I know what that is, it's not handling compressed modules right.
Comment 4 Bill Nottingham 2002-12-31 22:06:46 EST
Fixed in 0.70-1

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