No modules built or installed at kernel compile [solved!]

Message

Andru · Post by **Andru** » Wed Mar 31, 2004 4:51 pm

The (minimal) livecd detected all my hardware perfectly and loaded all the right modules, but my compiled kernal (compiled with "make dep && make bzImage modules modules_install") doesn't seem to compile the modules I've selected (with Y, not modularised) in the kernal config menu.

It doesn't load them by default - when I lsmod it shows a blank table - and they don't reside anywhere in /lib/modules/3.4.25-gentoo/kernel, as far as I can tell. Using modprobe for the driver names fails saying it can't find the specified module, and no matter how many times I recompile the kernel (trying the make module commands seperately from the make dep, too), it just won't seem to compile them. I've checked the sources directory for the drivers and they all seem to be there, so I can't understand why it's not compiling them.

Any ideas?

nrl · Post by **nrl** » Wed Mar 31, 2004 6:01 pm

Andru wrote:The (minimal) livecd detected all my hardware perfectly and loaded all the right modules, but my compiled kernal (compiled with "make dep && make bzImage modules modules_install") doesn't seem to compile the modules I've selected (with Y, not modularised) in the kernal config menu.

It doesn't load them by default - when I lsmod it shows a blank table - and they don't reside anywhere in /lib/modules/3.4.25-gentoo/kernel, as far as I can tell. Using modprobe for the driver names fails saying it can't find the specified module, and no matter how many times I recompile the kernel (trying the make module commands seperately from the make dep, too), it just won't seem to compile them. I've checked the sources directory for the drivers and they all seem to be there, so I can't understand why it's not compiling them.

Any ideas?

If you select an option with Y then it is compiled into the kernel not as a module so the driver will work but obviously won't be listed with lsmod as it isn't a module. If you want it as a module select M then put the module name in the /etc/modules.autoload file if you want it loaded at boot, rather than manually loading it later.

Andru · Post by **Andru** » Wed Mar 31, 2004 6:10 pm

Well it doesn't appear to be doing that correctly, as my network card isn't detected.

And by specifying modules and modules_install in the make option, aren't I asking it to compile it to modules as well? I'm not sure, but I assumed thats what it meant.

I'm new to linux so I'm still learning how everything works, but all I know at the moment is that my network card fails to initialise at boot, despite me selecting t compile the necessary drivers into the kernal.

Needless to say, I'm feeling a little confused

YopWongSapn · Post by **YopWongSapn** » Wed Mar 31, 2004 6:24 pm

Andru wrote:And by specifying modules and modules_install in the make option, aren't I asking it to compile it to modules as well?

Actually, the modules/modules_install options will only compile modules if you specify in the kernel config to compile them as modules (<M> instead of <*>). Anything you put directly into the kernel will not be compiked as a module.

As for your network card...did you select the correct driver in your kernel config? What kind of card is it? And which card's driver did you build into the kernel?

nrl · Post by **nrl** » Wed Mar 31, 2004 6:26 pm

Andru wrote:Well it doesn't appear to be doing that correctly, as my network card isn't detected.

And by specifying modules and modules_install in the make option, aren't I asking it to compile it to modules as well? I'm not sure, but I assumed thats what it meant.

I'm new to linux so I'm still learning how everything works, but all I know at the moment is that my network card fails to initialise at boot, despite me selecting t compile the necessary drivers into the kernal.

Needless to say, I'm feeling a little confused

OK don't worry

.

Well no you aren't, by specifying modules and modules_install it tells it to make the modules you asked for (by choosing M) and to install them, just like bzImage tells it to compile the kernel with all the things you asked to be compiled in (by choosing Y).
So if you compiled it in with Y it should work without needing to load any modules but if you compiled it as a module with M then it needs to be loaded either with the file I mentioned earlier or manually with the modprobe program.

Once you have done one of these (which it seems you already have tried compiling it into the kernel) then perhaps you should start another thread about the problem with your network card now that you (hopefully) see how modules work

. Or just post the details of the network card problem here - it's up to you.

Andru · Post by **Andru** » Wed Mar 31, 2004 6:59 pm

heh, well funnily enough I made the post here because I posted a thread in the networking section stating my problem, and I got the impression that it was more of a topic for this forum (though re-reading the thread with my new understanding of how the modules work, I think I got the wrong impression

).

Anyway, I chose all the 3com card available when I first compiled - but that didn't work, so I recompiled. Though my exact card wan't listed, I chose what looked the closest - the "3com 3c590/3c900 series (592,595,597) "Vortex/Boomerang" support" - as my card is the "3c905 [boomerang]".

Obviously this didn't work either, but how else do I get the drivers for my card if they're not listed?

YopWongSapn · Post by **YopWongSapn** » Wed Mar 31, 2004 7:12 pm

Well, that should be the correct driver. Try running

Code: Select all

# ifconfig -a

Does eth0 show up anywhere?

If not, try installing the 3c59x as a module (<M>) instead of compiling it into the kernel. This would be where you add the modules/modules_install option to make. Reboot, then try

Code: Select all

# modprobe 3c59x

If that works, you can add the module to your modules.autoload to load eth0 on boot.

Andru · Post by **Andru** » Wed Mar 31, 2004 7:56 pm

That works perfectly, and I think I've just realised why I was having problems (and am testing it at the moment).....

It seems I've been forgetting to mount /boot before copying over my newly compiled kernel, so it's actually remained the same without my knowledge. Ack.

Well I'm recompiling again (well, at least I know all the commands off by heart now

) with the network driver built in to see if that was my problem.

YopWongSapn · Post by **YopWongSapn** » Wed Mar 31, 2004 7:59 pm

Ah yes, I've don that a few times hehe. No worries, just make sure you run lilo/grub after you recompile the kernel. Funky problems can result if you don't.

Good luck.

Andru · Post by **Andru** » Wed Mar 31, 2004 8:03 pm

Heh, well it worked!

Thanks for everyone's help!

nrl · Post by **nrl** » Wed Mar 31, 2004 8:14 pm

YopWongSapn wrote:Ah yes, I've don that a few times hehe. No worries, just make sure you run lilo/grub after you recompile the kernel. Funky problems can result if you don't.

Good luck.

It is only LILO you need to run after compiling a new kernel there is no need to do that with Grub.

YopWongSapn · Post by **YopWongSapn** » Wed Mar 31, 2004 8:23 pm

Good call, nrl. It's been so ling since I've used grub, I forgot about that.

No modules built or installed at kernel compile [solved!]

No modules built or installed at kernel compile [solved!]

Re: No modules built or installed at kernel compile