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.
Well originally upon the finalization of the install I had no sound. I did find the rc.modules file in my rc.d directory and found the correct driver for my sound card commented out. After uncommenting the command there to load the driver with a modprobe command, the sound does work when I finish booting into kde. The sound does not work during the inizialization of kde however. I believe this is due to the driver not being loaded directly by the kernel but being loaded when I enter kde. (I don't hear the default kde sound when I initially enter kde, but after a logout and logon I do) Well my question is this. After I made the change in the rc.modules script, I started getting errors on boot up, right before I get a prompt. It tries to load the wrong driver and I get errors. Saying it can't load the driver. Because it can't find the device or it is busy I think. I'm guessing if that is because a driver has already been loaded? I dunno, if that is the case then why don't I initially get sound when I freshly enter kde. And how do I stop an insmod command to be called during bootup? I could not find any insmod commands or references to the wrong driver in any scripts. Is this information hard-linked to the kernel? And I guess if that is the case then I would need to recompile my kernel, correct? I know what my correct driver is because I had Mandrake before and it had this driver loaded. Any info would greatly be appreciated, and I apologize for the long question. Thank you.
Try re-commenting out the modules in rc.modules. Then reboot and examine the output of lsmod. I believe most sound card drivers are automatically loaded by hotplug, and I suspect that may be what is happening here.
Also make sure you have run alsamixer, and saved the settings with 'alsactl store'. That may correct your lack of sound on bootup.
Well , a occasional empty line so now and then would improve the readability of your question greatly.
But some questions before a good answer could be supplied :
- what sound card are you using
- does it work as root or doesn't it work at all ?
Some possibilities:
- rights problem.
Normal users are not able to use sound by default . a search on this forum will provide an answer for that.
- alsamixer as mentioned above
The modprobe/insmod problem could be other modules already loaded before loading the oss ones in rc.modules , probably alsa modules invoked by hotplug (v 9.1) . Uninstalling the alsa drivers could be the easy solution if you are using 9.1 . Blacklisting those modules in hotplug is an option too. You can list the modules loaded using the command /sbin/lsmod .
if your haveing problems finding something in the slack boot scripts you can always use
> grep -R {what you are looking for module name/program put it in "" if 2 words} /etc/rc.d
if its 2 or more words they have to be exact ... ex. "red dog" wont find "redish dog" but would find "big red dog" it will output the line "red dog" was found on and the file it was found in. Dont know if this will help but good luck.
JonW I tried what you said, to no avail. I re-commented the driver module, and ran 'alsamixer' and made sure nothing was muted and everything was turned up. Then I ran 'alsactl store' No luck.
Rotvogel: I hear what you say, (like the spaces now?) I'm pretty sure permissions aren't the problem since I've tried initially booting into KDE as root and testing in regard to that. Same problem as a user. I've scoured over the rc.modules script looking for a command calling another sound driver, but nothing. No insmod commands period, all modprobe. I think it is an insmod command because the error I get upon bootup is saying the error and the command called to induce that error.
I am using my onboard sound on my FIC AD11 board. When I get the error I see that it is giving me an error dealing with loading a driver for a pci card. My correct driver is VIA82cxxx_audio. Now the error I receive is as follows:
insmod: /lib/modules/2.4.22/kernel/sound/pci/snd-via82xx.o.gz : insmod snd-via82xx failed
VIA82xx soundcard not found or device busy
init_module: no such device
I have tested the driver via82cxxx_audio but when loaded 'alsamixer' will not run. I have also scoured rc.hotplug but there was no relevent info. Is that the right place or is that script calling on others? I've done a search which yeilded no results for any insmod commands.
Ok here it goes.. I'm going to post 4 different lsmod outputs. I ran 4 different tests to see the results. Here it goes and I'm sorry for the length, I just wanted to be thorough.
(with rc.hotplug disabled and correct sound driver loaded)
Module Size Used by Not tainted
ide-scsi 9424 0
via82cxxx_audio 19704 1
ac97_codec 12296 0 [via82cxxx_audio]
soundcore 3332 2 [via82cxxx_audio]
agpgart 39576 0 (unused)
What I get from this is that rc.hotplug didn't have anything to do with it. Any ideas? Thank you by the way.
(via82xx is the wrong one.. via82cxxx_audio is the correct driver) Also alsamixer will not load with the correct sound module loaded. Here is the output for that.
alsamixer: function snd_ctl_open failed for default: No such device
Is there any reason you for wishing to use via82cxxx_audio and not snd-via82xx? Via82cxxx_audio is the OSS driver whereas snd-via82xx is equivalent ALSA driver (hence the reason for alsamixer not working without it). Generally, ALSA is being seen as the way of the future so unless there you have a particular reason for not using it, it may make more sense to try and get that working.
However if you really do need via82cxxx_audio, could you try removing the alsa-driver package? Then in /etc/hotplug/blacklist you will find a list of OSS modules - comment these out, make sure /etc/rc.d/rc.hotplug is executable, then reboot. Hopefully, hotplug will then load the required OSS drivers.
It might also be worth looking at /etc/modules.conf and (for the time being at least) removing any sound card references in there.
well the reason I was using via82cxxx_audio instead of snd-via82xx is because in mandrake it prompted me to use the snd module just like slackware, and just like slackware it would not work. via82cxxx_audio was listed as an alternate driver and just like in slackware it does work.
Also in slackware when I do have the via82cxxx_audio module loaded I get an error message during boot up as follows:
The thing I see is that it is looking in a pci folder for a driver when it is onboard sound?.... would onboard drivers be in that folder too? and if I use the default module what would I have to do to get that working? I've tried everything. Or at least it feels like that. If you think I can get the default module working, then I'll try it, I just don't know where to start.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
