Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Having trouble getting linux to use my new audigy sound card.When I start X KDE gives me a error staing that the sound server cant initialize a driver for /dev/dsp because no such device is found. Ive already installed the latest beta drivers and still no go. Anyone have any theories as to what is wrong?
you installed the latest drivers? but did you get the audigy drivers and not the normal emu10k1 drivers (they are branched off). also did you get any errors when you inserted the modules.
do
modprobe emu10k1
does it give you any errors
also, since you changed your sound card, make sure you have permissions to /dev/dsp
a good check is starting kde as root and seeing if it has sound then, if it does its a permission prob
/lib/modules/2.4.7-10smp/kernel/drivers/sound/emu10k1/emu10k1.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
/lib/modules/2.4.7-10smp/kernel/drivers/sound/emu10k1/emu10k1.o: insmod /lib/modules/2.4.7-10smp/kernel/drivers/sound/emu10k1/emu10k1.o failed
/lib/modules/2.4.7-10smp/kernel/drivers/sound/emu10k1/emu10k1.o: insmod emu10k1
failed
And yes when I start KDE there is no sound. I havent had any sound since I put in the card. The card was in during a fresh install.Ive been checking to make sure the card is in the whole way.
try doing insmod emu10k1, and see if it says something about unresolved symbols. mine did that at first, and it wus because there is another module besides emu10k1 that wusnt autoloaded, and when using modprobe it wus
from what u posted tho it looks like it made the modules and attempted to load them correctly, but it doesnt see the card for some reason. ive heard stuff about some mb's or bios having a prob with which slot u put a sound card in, so try moving it and trying again
while searching the web for some answers regarding this topic I found this post and guess what:
I can't get it to run either !
I tried to install the drivers at sourcefourge but no luck, eventhough the kernel-source is installed in my system he can't find a file called version.h (called by the script get_version of the driver), I did all the right things but no luck.
My install is a default Redhat 7.2 install
If someone of you resulted in setting it up, please provide some detailed description of how they did it.
I'm no novice user and have problems with it so......it's to bad that I have no sound....I hate it ;-)
Anyhow, I know that the kernel of RH7.2 has a file called linux_version in the sources but no version.h.....even after a rebuild of the kernel, a make and make dep.....the driver will not install.
cheers,
David
ps: we are not alone, I know a lot of ppl who switched back to fucking XP cause of the NO SOUND problem ;(
i got it to work on debian testing with a vanilla 2.4.18
just have sound suport, but no driver modules
make and make install like the files say
then i ran into probs but i discovered that it wus because i wus using insmod and not modprobe and insmod wusnt loading the second module it creates
if you need any more info let me know
I tried modprobe and insmod of emu10k1 but both resulting in errors ;(
Here is what I did:
- Installed kernel sources for RH 7.2 in /usr/src/linux-2.4
- Run a make in my install dir of the emu soft.
This resulted in errors telling me a lot of crappy things.
After running the script in emu10k1/scripts called get_version I saw the error telling me that a header-file called version.h is not on my system.
After verifying the kernel sources I can tell that it is not on the system.
I will try to hack the code so that it doesn't look for the version.h anymore and see if that will help or not.
(kinda force the install a bit).
Even with the pay-version of the drivers I ran out of luck.
I have very recent hardware and the latest RH version.....
Well I tried recompiling the kernel with only sound support and no drivers but still same problem. Here's the latest after trying insmod.
[root@localhost emu10k1-audigy]# insmod emu10k1.o
emu10k1.o: unresolved symbol ac97_probe_codec_Rsmp_1c61c357
emu10k1.o: unresolved symbol ac97_read_proc_Rsmp_bae4da72
Im going to possibly give a fresh install one more try but Im wondering after reading your following posts if it could be a RH issue. The system Im trying to get this going on is running RH7.2. I also have a P233mmx system with RH7.2 that I tried it on and it gave me the same problem.Of course there is stilI the possibility of me having a bad card. Is there any way to tell if the card even works? The only life Ive seen is if I plug the speaker into where the microphone plug should be . I get that scratch noise like voltage actually exist. Is this at least a good sign the card is okay.
well, that red hat problem i cant solve, i think that might have to do with the red hat modified kerenl.
but kage:
ac97_codec is a second required module that is built. if you just try to insmod emu10k1 it does not auto load the ac97_codec which is required, and thats why you get unresolved symbols. you must either use modconf or modprobe, which will automatically install needed modules for you, or do an insmod ac97_codec first.
Last edited by AzrielMacKay; 03-11-2002 at 08:38 AM.
Thanx Azriel I tried insmodding the ac97codec then the emu10k1 and I got no errors. I now have sound and I tried restarting X and when KDE came up there was sound and the error was gone.Woohoo!!
BTW :Are all unresolved symbol errors the result of some module that doesnt get loaded or is there other reasons you might get unresolved symbols?
im not sure ALL of them are, but a majority of the time ive seen them thats what it wus. thats why modprobe or modconf can many times be the better choice over insmod.
well, im glad it works, and glad i could be of help
Thanx for the help once again but it looks like my woes arent completly gone. After loading the module I could go into and out of X with no problem . The issue came when I tried to reboot. For some reason the sound drivers wont load automatically so I always have to open a console and insmod them in after every boot. Ive already went into modules.conf and added the line "alias sound emu10k1" like it said in the install instructions but that had no effect. So what file do I need to modify now?
That alias only works if the kernel module auto-loader is enabled. An easier way is to find wherever your modules are loaded in your boot scripts and add the lines to insmod those two drivers.
In a reference to your earlier comment, the reason that you get unresolved symbols is quite simple, the module you are trying to load is trying to call a function located elsewhere(in the other module). When it can't find it loaded it bombs out.
I recommend always using modprobe. Modprobe will seek out and auto-load any dependencies if they exist on the system, otherwise it'll bomb out with an error that you should be able to trace to the missing module.
Hi, I just posted about an error that I'm getting when I try to install the Audigy drivers. Everything goes great until I get to the "Make Install" command. Then it does its thing, and comes back with "ac97_codec.0: Device or resource busy.
I can't get it to do anything beyond that, even with insmod or modprobe.
Thanks for any help,
Jed
That "busy" error generally means it's not detecting something right and you need to pass command line options. Might try a clean CVS build to see if anything is patched up that might not have been right on your system, otherwise you've got some IO and IRQ settings to play with.
One other thought, make sure that no other soundcard drivers are loaded before you run Make install. It might be trying to install a newer ac97 driver, and the hardware is occupied by the older driver.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.