SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I upgraded to Slackware 12 this weekend and can't solve this (among several other problems):
I have a PCI Sound Blaster Live! sound card. It worked flawlessly in Slack 11. Now Slackware seems to think that I have 2 sound cards. The Sound Blaster Live! and some VIA 8237 thing.
I don't know what that second card is, maybe it is the onboard sound system, which I have disabled in the BIOS and never bothered me until I installed Slack 12. The problem is that one is /dev/mixer and the other one is /dev/mixer1, and I can never tell which one is going to be which in the next boot. It seems to be completely random, like a lottery.
When the OS boots up with the VIA 8237 thing as /dev/mixer, I don't have any sound in the loudspeakers, except loud feedback because the sound card lottery also creates a problem with the microphone. The microphone is connected to the SB Live! card, but it does pick up ambient sound although SB Live! won't give me any output in the loudspeakers. But there is "something" in the loudspeakers that the microphone picks up, so the system boots up with the loudspeakers screeching with feedback. The way to make them stop screeching is very annoying: I have to open kmix, select the SB Live! card in a drop-down (because the VIA card is selected), then click the Input tab, then click a button in the Mic slider then click a button in the Line slider. Or I can run rexima and tweak /dev/mixer1. That can be partially automated, but it's still annoying and I haven't found out how to get the normal output from the SB Live! card. I just end up rebooting a few times until I win "the lottery" again, then everything runs normally.
I've run alsaconf and "configured" the sound card. I see that it changed the /etc/modprobe.d/sound file, but it didn't fix the problem. I also uncommented "blacklist emu10k1" and added "blacklist via82xx" in /etc/modprobe.d/blacklist. But none of that has been enough. Can someone please help me get rid of this VIA 8237 card?
I could be wrong, but it seems to me that I can't remove snd_via82xx without killing the module that is using it, which would also kill snd_emu10k1, which the SBLive card requires.
iirc the stock slack12 kernel doesnt have forced module unloading... but thats ok. you can still kill all the sound modules then reload the ones you want. you could also add something to rc.alsa
Code:
if [ ! $DRIVER == "snd_via82xx" ]; then
modprobe $DRIVER
fi
that snippet may be incorrect syntax (?) I'm not the worlds greatest scripter..
alternatively since the rc.alsa script just loads everything it finds in /lib/modules/'uname'/kernel/drivers/sound you might try just renaming the vi82xx.ko file to something rc.alsa wont recognize as a kernel module.
of course, the most elegant solution remains to recompile without the via support.
gbonvehi, read my post again. I already added the unwelcome card to the blacklist file. It's not working.
bioe007, you do have a point. My Slackware 11 ran a custom kernel, I probably had removed support to extraneous sound cards. But recompiling a kernel is such a chore. I don't wanna go through all that again. Renaming the offending module file so rc.alsa won't find it is very tempting.
I am very optimistic about all these suggestions. I am going to try them now. But, incidentally, I just noticed that I have these two directories: /lib/modules/2.6.21.5 and /lib/modules/2.6.21.5-smp. I am running smp. Do I really need the other one? May I delete it to save space?
Back to the forum in a positive tone. The tips above worked - pretty much a combination of them all - no patience to isolate and check which one nailed it. The problem is gone. Better yet: music sounds a lot better than before. Maybe 12 comes with better drivers? I don't know, it just sounds great.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.