Bug 682
Summary: | "modprobe sound" done by RH 5.2 initscripts prevents eth0 init | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Andrew Pam <xanni> |
Component: | modutils | Assignee: | Cristian Gafton <gafton> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
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-06-17 16:33:43 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
Andrew Pam
1999-01-04 07:18:34 UTC
I have verified this to be true. I set up a test machine with a WD8013 BNC ISA and an Gravis Ultrasound MAx configured to the settings reported by the user. I did a fresh 'workstaion' install of 5.2. I ran sndconfig to configure the sound card with no problems. By this time the wd module was already running. I removed the wd and 8390 drivers from the running system. I ran modprobe wd and it did not insert the module. I removed all sound related modules from the running system and was then able to insert the wd module properly. One note is that I could use insmod instead of modprobe to insert the wd driver (inmodding 8390 first of course) after the sound modules were loaded. This leads me to believe the bug lies within modprobe. Is this still true with the current beta release ? Or the updated kernel form 5.2? Bug closed due to lack of feedback from the reporter. Please reopen if still valid. |