Bugzilla – Bug 117688
Yast quits when configuring soundcard, /etc/modprobe.d/sound not found
Last modified: 2006-05-23 10:42:52 UTC
When trying to configure my soundcard the Yast-module just quits. The soundcard is recognised correctly, a ESS18XX. When I have a look into the Yast log I see that ModulesConf.cc:282 Failed to stat /etc/modprobe.d/sound file not found
I can confirm such a behaviour here as well, on a clear new network installation of RC1. I have SB16. After detecting the card, YaST displays it in the list, saying that it is not configured, so I need to click "Edit" to configure the card. Clicking the "Edit" button causes the sound module to close immeadiately. I also tried earlier to add the card manually. The "normal" and "quick" setup failed with the message "The kernel module snd-sb16 could not be loaded ...". So, I get to advanced mode, reentered all the suggested settings for ports/IRQ, DMA, etc. These settings are reported from my WinXP intsallation the same machine, where it works. They match exactly. And still the same message. Attached are the log files.
Created attachment 50287 [details] The logs of unsucessfull SB16 config.
Oh, ISA cards are detected in different way and the detection doesn't provide some internal required information. It must be enhanced.
Just an addition: If I run hwinfo, among the lines when it tries to load the sound modules, there are messages stating that the modules are tainting the kernel. And, I do not know how relevant is this, but the detection process is somewhat broken. If I select all possible types of cards it locks up the machine on trying the second or third card. If I perform detecting card by card - i.e. leaving only one checkbox selected, trying to detect, after that go back, select another, try again - it does not lock. But if the selection includes more than 2 cards (any of them) it locks on second or third card. Cheers Sunny P.S. What are the chances this to be fixed for the official release? I.e. I'm considering a preorder, but this is a showstopper for me.
You should be able to use alsaconf for configuring the sound card if yast fails. Takashi, look at commment #4, it's strange that it doesn't lock in one-by-one case. How can I prevent the lock?
The ISA modules are no longer supported by us. That's the reason of tainting. It might be a bug in ISA PnP layer and ALSA drivers, or combination of kobject. Perhaps some of the drivers listed there have problems at unloading... Unfortuantely, it's hard to debug because I have no more ISA slots, and the drivers are no longer the target of support, as mentioned. (So I can't give my work time to fix such a bug.)
Following the advice in suse-linux-e mailing list (thread "SUSE 10.0 Yast sound bombs on compaq" from 10/27/2005), using alsaconf did solve the problem. My card is configured and working. So it looks like it is YaST problem (bug) in the sound testing and choosing the modules. alsaconf version: 1.0.9a Now ... the other problem with this approach is, that alsaconf makes the changes in /etc/modprobe.d/sound, but ... they never get used upon reboot, so - no sound. If I run alsaconf again, or better - modprobe snd_sb16 - the sound is back.
Have you tried updatemodules.dep?
(In reply to comment #8) > Have you tried updatemodules.dep? > Actually, I do not know who - the alsaconf, or the unsuccessful YaST try, have created hwinfo- file under /etc/sysconfig/hardware. I renamed this file to hwinfo-static-sb16, and now it was picked by the coldplug, and loads the modules.
This still happens with a SB 128 PCI.
Please, could you reproduce the problem in SUSE Linux 10.1? Does it still happens?
YaST does not quit anymore, so it seems to be fixed for 10.1. Will this be fixed in 10.0 too?
Thanks for testing! Sorry, for later releases only security fixes are provided. See comment #6 for more info.