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.
OK, so I'm doing, like, my four thousand three hundred and fiftieth attempt at a Mandy Kernel recompile. I have errors in make modules_install saying
depmod: unresolved symbols in /path/alsa/snd-cs4231.o.gz
pm_unregistered blah blah
Also, lots more depmod errors. What I don't understand though, is the fact that I went to hard Drake, found which sound card module the install had used and disabled *all* the other soundcards; didn't select <M>, but actually totally disabled them.
So why is it flagging loads of soundcard errors? I assume they're soundcard errors anyhow, all the trawling around on the web seems to indicate that's what all the path/alsa/snd-xxxxx entries are!
Either a solution or a donation for my looming entrance to the loony bin would be most welcome!
I vote you take your soundcard,
Dip it in crome,
Place it in the center of a roundabout and put candles around it, anounce to the world that it is the new messia,
convince people that all other forms of gods are evil,
write a bible based on the non-logical logic of ms programing,
Sacrifice 6 lizards, 6 mice, 6 fish beside each candle of your circle,
Create another circle of petrol around the outside,
Then
Surround the circle with fishing line about head height with poison hooks.
Put a sign up that says all yee who enter the circle of a the demon shall die..
After 3 deaths Re-aanounce that your messia has been changed to the anti-christ. Re-coat the sound card car in blood and re-display..
That way you won't have to worry about donations..
but if its onboard sound then I'd have no idea..motherboards alone will not get you there..
directory, there's a load of .o.gz files of the soundcards you can see in the menuconfig.
Also, in
/usr/src/linux-2.4.8
directory, there's an alsa-driver-0.5.11
directory, with a load of subdirectories which seems to have some c files in it...
Whether that's what's needed, I really don't know!
I thought I'd been really clever, got an unwanted SCSI card from my dad this afternoon, stuck that in and Mandy saw it and installed the drivers for it. However, there's *still* no f*****g /dev/sd* directories.
Problem with all this is I really don't know what I'm doing. I'm just blindly following HOW TOs without really knowing what's going on. I've just sussed out that the menuconfig program creates a .config file in the /usr/src/linux directory and you can see what you enabled and disabled in the menuconfig. What things like dep, bzImage, modules and modules_install actually do I don't understand - so I'm playing around in the dark really!
You sure its looking for the dir called path? or is it $path?
Its an odd place for it to be looking. What you've got is pretty much the same as what I had.
If its the first you may need to make it happy and install the alsa drivers again by use --prefix=/path on the ./configure part if you made it from source.. so it would look like
./configure --prefix=/path
Then when you do the kernel you have /path/alsa/etc etc..
If its the second then you could use export PATH=$PATH:[new pathname] to make it look where your drivers currently are..
But I'm sure you can just make it look in your existing dirs for the files when you try to recompile your kernel..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.