Bug 5382 - sndconfig can cause permanent system crash
sndconfig can cause permanent system crash
Status: CLOSED DUPLICATE of bug 5429
Product: Red Hat Linux
Classification: Retired
Component: sndconfig (Show other bugs)
i386 Linux
high Severity high
: ---
: ---
Assigned To: Bill Nottingham
Depends On:
  Show dependency treegraph
Reported: 1999-09-26 18:44 EDT by Stephen John Smoogen
Modified: 2014-03-16 22:10 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-09-29 12:24:17 EDT
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 Stephen John Smoogen 1999-09-26 18:44:19 EDT
If your system contains certain sound cards (Dell Inspiron
3500 ) you can end up with a locked system that can only be
edited from a rescue mode.

The problem is that sndconfig edits /etc/conf.modules before
it tests if your system has a working sound card. On
installing module it can crash the system. If you reboot you
cannot get around the modules being loaded even if you do
a linux single because of /etc/conf.modules syntax.

Suggested Fix:
a)  have sndconfig test modules via explicit insmod commands
and at end of run write /etc/conf.modules
b) have initscripts not load sound modules in single user
Comment 1 Bill Nottingham 1999-09-26 18:57:59 EDT
FWIW, sndconfig does tell you it's writing a new
conf.modules. :)

Boot with "linux nomodules"; alternatively "linux init=/bin/bash".
Comment 2 Bill Nottingham 1999-09-29 12:24:59 EDT
*** This bug has been marked as a duplicate of 5429 ***

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