Bug 188055

Summary: snd-sbawe module fails to load
Product: [Fedora] Fedora Reporter: David A. De Graaf <dad>
Component: system-config-soundcardAssignee: Martin Stransky <stransky>
Status: CLOSED CANTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5CC: jhhaynes
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-07-21 08:55:42 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:
Attachments:
Description Flags
log file of failed system-config-soundcard
none
Another failed attempt to run s-c-s
none
output of lshal
none
output of dmesg after reboot none

Description David A. De Graaf 2006-04-05 16:43:11 UTC
Description of problem:
Sound module fails to load


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


How reproducible:
Always


Steps to Reproduce:
1.  Fresh install FC5; run system-config-soundcard
2.
3.
  
Actual results:
The soundcard is detected correctly:  Vendor: Creative  Model: SB-AWE64
PnP-CTL0045  Module: snd-sbawe
but no sound is emitted, and /etc/modprobe.conf remains unsullied by sound
entries.  The log file, /root/scsound.log is attached.


Expected results:
Sound!


Additional info:
Next, I install this modprobe.conf from an FC4 backup and reboot:
$ cat /etc/modprobe.conf
alias eth0 8139too
alias snd-card-0 snd-sbawe
options snd-card-0 index=0
options snd-sbawe index=0
remove snd-sbawe { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; };
/sbin/modprobe -r --ignore-remove snd-sbawe

If I run   aplay /usr/share/sounds/generic.wav   I get a long string of ALSA
error messages, and no sound.  With lsmod I observe that the snd-sbawe and
related sound modules are NOT loaded.

However, if I manually run   modprobe -v snd-sbawe  I see about 11 modules being
installed, and sound then works perfectly.

Apparently, the automatic module loading dictated by modprobe.conf isn't working
 any more.  As a workaround, I've added a line to /etc/rc.d/rc.local,
    modprobe snd-sbawe
and this solves the problem for the moment.  I'd appreciate a proper fix, though.

Comment 1 David A. De Graaf 2006-04-05 16:43:11 UTC
Created attachment 127357 [details]
log file of failed system-config-soundcard

Comment 2 Martin Stransky 2006-04-08 15:34:43 UTC
Could you please add these old lines:

alias snd-card-0 snd-sbawe
options snd-card-0 index=0
options snd-sbawe index=0
remove snd-sbawe { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; };
/sbin/modprobe -r --ignore-remove snd-sbawe

to /etc/modprobe.conf, remove your workaround from /etc/rc.d/rc.local/, reboot
your box, run s-c-s and attach new /root/scsound.log?

Comment 3 David A. De Graaf 2006-04-08 19:24:59 UTC
Created attachment 127511 [details]
Another failed attempt to run s-c-s

Comment 4 David A. De Graaf 2006-04-08 19:26:12 UTC
Yes - it is attached.

I note that I had these exact lines in /etc/modprobe.conf already, but I did cut
& paste your lines, just in case I had a typo.

Upon rebooting, I verified with lsmod that the snd-sbawe module and all its
cousins were NOT loaded.  Then I ran s-c-s, which failed to produce any sound
and again failed to cause the required modules to be loaded.

After collecting the attached log file, I manually loaded the modules,  modprobe
snd-sbawe,  and was then able to produce sound with aplay.

Comment 5 Martin Stransky 2006-04-14 13:10:12 UTC
Could you please attach output of "$lshal"?

Comment 6 David A. De Graaf 2006-04-14 14:50:18 UTC
Created attachment 127751 [details]
output of lshal

Comment 7 David A. De Graaf 2006-04-14 14:51:00 UTC
Your request is somewhat cryptic.  What does $lshal mean?

# $lshal 

produces nothing.  Similarly,

# man lshal
No manual entry for lshal

In my rather primitive view, a command without a man page may as well not exist.
 However,

# lshal > /tmp/lshal.out

does produce a lengthy file, which is attached.  Hope it helps.

Comment 8 Martin Stransky 2006-04-18 20:35:12 UTC
Could you please attach output of dmesg?

Comment 9 David A. De Graaf 2006-04-19 00:19:08 UTC
Yes.  I first commented out from /etc/rc.d/rc.local the lines:
#  On datant, sound won't work until module is forcibly loaded.
# modprobe snd-sbawe
# aplay /home/dad/sounds/sparcle.wav

Then rebooted and captured the output  dmesg1.out.
Then I ran   modprobe -v snd-sbawe  and captured dmesg2.out.

These differ by only two lines:
$ diff dmesg1.out dmesg2.out
196a197,198
> pnp: Device 00:01.00 activated.
> pnp: Device 00:01.02 activated.

The complete dmesg1.out is attached.

Comment 10 David A. De Graaf 2006-04-19 00:20:33 UTC
Created attachment 127956 [details]
output of dmesg after reboot

Comment 11 Martin Stransky 2006-04-25 07:27:43 UTC
It's a bug in HAL, kudzu isn't used any more for loading modules and HAL doesn't
catch your card.

Comment 12 Jim Haynes 2006-05-23 19:01:17 UTC
I have exactly the same problem with a sound card that system-config-soundcard
identifies as SB AWE32 PnP CTL0031    This is an ISA card.  I used the above
workaround of putting the modprobe snd-sbawe into /etc/rc.d/rc.local and it
now works.

Comment 13 Jim Haynes 2006-05-26 16:18:58 UTC
Same problem (and same work-around works) on an ISA Sound Blaster that
the system-config-soundcard identifies as SB AWE64 PnP CTL0045

Comment 14 Martin Stransky 2006-06-15 15:06:34 UTC
support for ISA cards was removed in FC5 (I don't know why) so you have to add
line with modprobe to some init script (like /etc/rc.local)

Comment 15 David A. De Graaf 2006-06-15 20:15:17 UTC
No, no, no!   Support for this sound card exists - it works fine with the
snd-sbawe module, when loaded manually.

What's newly broken in FC5 is that proper lines in /etc/modprobe.conf are no
longer effective.  Something is causing /etc/modprobe.conf to be ignored.

That's what needs to be fixed.

Comment 16 Martin Stransky 2006-06-16 05:58:04 UTC
modprobe.conf isn't used for module loadig, it's a configuration file. Modules
are loaded by init scripts....

Comment 17 David A. De Graaf 2006-06-16 15:08:39 UTC
Whatever...

All I know is it used to work;  now it doesn't.

Where, exactly, is this init script for a sound device?  When was the need for
one introduced?  Where is that need documented?  For as long as I can remember,
system-config-soundcard, if it worked at all, resulted in whatever configuration
files that are needed to make the sound system work.  Now it doesn't.

That's broken.

Comment 18 Martin Stransky 2006-07-21 08:55:42 UTC
Unfortunately, support for ISA modules (loading during boot) was removed in FC5
and later kernels. If you want this feature back, report this bug against kernel.