Bug 2250
Summary: | sndconfig locks up while trying to detect sound card | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Joe Acosta <josepha48> |
Component: | sndconfig | Assignee: | David Lawrence <dkl> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 5.2 | ||
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-05-04 19:46:33 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
Joe Acosta
1999-04-18 14:49:14 UTC
if run with --noprobe, sndconfig won't look for isapnp cards, so it *can't* write an isapnp.conf file. Does running pnpdump from the command line lock up? ------- Email Received From Joe <josepha48> 04/20/99 09:17 ------- Considering that sndconfig just runs pnpdump, that's odd that one would lock up and the other wouldn't. In any case, what's probably the problem with the AWE synth you're having is that you need to edit your /etc/isapnp.conf. Find the line that says (IO 0 (BASE 0x620)) and change it to (IO 0 (BASE 0x620)) (IO 1 (BASE 0x0A20)) (IO 2 (BASE 0x0E20)) Then you can rerun 'isapnp /etc/isapnp.conf', and then 'modprobe awe_wave'. Does that work? ------- Email Received From Joe <josepha48> 04/21/99 20:06 ------- ------- Email Received From Joe <josepha48> 04/22/99 09:41 ------- the opl3 device can be loaded; it's the FM synth. If you're using the AWE synth, it isn't really necessary. |