Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Hello guy's. I just recompiled my kernel. Because I only needed some drivers to get build in to my kernel, I only did: "make mrproper", "make xconfig", "make dep", "make clean" and "make bzImage". So no "make modules" or "make modules install".
When I do "depmod -a" I get "depmod: *** Unresolved symbols in /lib/modules/2.4.20/kernel/drivers/net/dummy.o".
What can I do about this?
If all you did was change modules, then *I think* you could just get away with not creating a new kernel, but would still need make dep... make modules and make modules_install just not make bzImage.
However if you are adding things into the kernel, not just modules then I do think you need to whole process, as McLeodnine just said.
Okey, pleace don't mind my very stupid question. It was quite late at night. Pleace tell me it (asking things that you should of known) happens to every one .... right?
Distribution: Slackware, (Non-Linux: Solaris 7,8,9; OSX; BeOS)
Posts: 1,152
Rep:
Schatoor, did you move drivers that had been modules into the
kernel? If so, then you need to remove the old modules from
lib/modules/.... An easy way to do this (though it takes a while)
is:
Code:
cd /usr/src/linux
make modules && make modules_install
If you removed drivers from the kernel and made them modules
you HAVE to do it.
MasterC, you are correct, if you just want to build modules, you
can do a:
Code:
make (x|menu)config
make dep && make modules && make modules_install
Thanks for your reply moses. I needed to build some drivers in to the kernel. But I had'nt compiled them as modules as well. So the modules that I had in the first place are unchanged.It's just that I forgot to compile things in the first time round.
Any, to my susrprise, the problem is still there after I did "make modules" and "make modules install"
"make modules" went fine. But when I wanted to do "make modules install" it asked me if I wanted to make boot disks, which I didn't. Then it complained that there was no lilo on /dev/hda, which is correct. There is no lilo on the mbr, I know that. Any way, it went down with an error. So I tried again, this time making the boot disks. Which worked in some much that there was no error.
But after all this, depmod is still complaining.
I hope you guy's don't think i'm stupid now. God, i'm not a newbie any more so these crewups are really imberacing
BTW, make modules_install did the trick
I don't think you are stupid. Have you seen some of my questions lately? I think by now I should be able to write an Oreilly book, but I'm still on picture books
(Simpson's quote):
"It's all relative, I mean, is Moe that ugly, is Homer that bald, is Barney that fat stupid and drunk?" (Ok, so it's not completely accurate, I can't find a wav to help me out right now )
Anyway, it's all learning, we are all at LQ to learn, and luckily there are those here who also know ALOT and can help us to learn when we make these kinds of mistakes.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.