Bug 102543
Summary: | non PnP SB16 soundcard init fails after SOFT reboot. | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <fruitless> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i586 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-30 15:41:26 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
Need Real Name
2003-08-17 05:27:11 UTC
What I meant by the soundcard init failing was that the sb module failed to load, it crashes before a green OK comes up after a soft reboot. What I've recently found is that if I set: options sound dmabuf=0 instead of options sound dmabuf=1 in the /etc/modules.conf file, then the card appears to work OK without crashing on boot, although any message of a soundcard module being loaded now does not come up on boot. I'm not sure what dmabuf does, or if setting it to 0 reduces performance at all, but when it was =1 everything froze, so maybe the option isn't compatible with the SB16 NonPNP. What I've now noticed so far is: 1) To avoid the sound module crashing the whole computer on boot (the bit where it says "No ISAPnP devices found, trying standard ones..."), you have to put the dmabuff=0 in the modules.conf file in the blurb generated by sndconfig (at whatever cost that does to it) 2) Even if you do that, with the soundcard working acceptably as far as its own functionality goes from then on, it causes very frequent lock ups booting into Gnome, with litterally EVERYTHING freezing up when it switches to the light blue screen just after logging in, an instant before the splash screen appears. 3) The latter is less likely to happen, though not immune from happening, if one logs in as root instead of pleb user. Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/ |