Re: Modules not showing up after compile - why?
Hi,
how did you compile the kernel? Basically, it works the following:
make menuconfig (config or xconfig will also work)
make clean
make dep
make bzImage
make modules_install <-- have you done this?
If you are not sure if your new kernel will work, make a copy of the
modules: mv /lib/modules/2.2.17 /lib/modules/2.2.17.org
before executing make modules_install.
Greetings,
Sebastiaan
ps: you can still try running modules_install now and see if it works.
On Mon, 4 Dec 2000, Anthony Campbell wrote:
> Sorry for this basic query; I've always used monolithic kernels but
> decided to build a modules version to try it out and I don't understand
> what's happening..
>
> I selected various modules and built the kernel. I included the kernel
> module loader to enable automatic loading of modules. The kernel
> compiled OK and I booted with it without problems. All the functions
> seem to be implemented as I expected.
>
>
> However, lsmod and modprobe show nothing: there is no /proc/ksyms or
> /proc/modules.
>
> Questions: why don't these things show up, and how does the kernel work
> if the modules aren't there?
>
> Anthony
>
> --
> Anthony Campbell - running Linux Debian 2.2 (Windows-free zone)
> Over 100 book reviews: http://www.cix.co.uk/~acampbell/bookreviews/
> Skeptical essays: http://www.cix.co.uk/~acampbell/freethinker/
>
> "Palo y tente tieso." (Spanish proverb)
> Free translation: "Holdfast is your only dog."
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>
Reply to: