I just complied a new 2.6.21.5 kernel and when I rebooted I dont have any modules loaded. When I made the new kernel I said

make
make modules
make modules_install (not sure if the last one is redundant)

Now when I run locate to try to find some of the modules I need to install manually I cant find any.

So, 'lsmod' produces not output at all ? (yes, 'make modules' is redundant with 'make', which is aka. 'make all')

lsmod doesnt list a thing and I cant modprobe any of the modules I need right now. I cant even find them.

I need more info on what you did. Can you describe what you did in more detail.

i really didnt do much more then that. I unpacked the source into /usr/src and pointed the sim link linux at it. I went into that directory and did make menuconfig and set up everything the way I wanted it. I exited out of there and said

make
make modules
make modules_install

I copied the bzImage over to /boot/vmlinuz. I went into lilo.config and added the only kernel image that i had renamed to vmlinuz.old. Then I ran lilo and it added my windows partition and the two linux kernels.

This is odd now, when i rebooted it went through lilo, it drew the dots across the screen as it was loading and then nothing. The screen was blank. The hard drive light was still flikering and i could hear it running so i didnt think it was stalled. I pressed ctrl alt del and the thing rebooted. The second time I waited till I knew it would be at the login prompt and logged in blind. Then I ran startx and the systems display came up and I was in KDE. I ran iwconfig to see if my wireless was up and there was nothing. I did a locate ipw2200 and only the source code came up in the kernel source directory. When I ran lsmod it said that nothing was loaded. Thats the most detailed explanation I can give you.

Thanks,

Ryan

i suggest that you do custom compiling kernel that suits your hardware, and then create your own /etc/rc.d/rc.modules-2.6.21.5
do chmod 755 rc.modules-2.6.21.5 and do as ln -sf rc.modules-2.6.21.5 rc.modules

http://www.kroah.com/lkn/ chapter 7 will show you what modules you need for your hardware(theres a script you need to run to determine what modules you need) and that way you accomplish editing rc.modules-2.6.21.5 and enter those in to load up.

the best to do is make mrproper, make menuconfig, make && make modules_install and then copy into boot vmlinuz, config and System.map you can then do your customized modules as described wich is preferable (at least for me) or you can then cat rc.modules-2.6.18 > rc.modules-2.6.21.5 chmod 755 rc.modules-2.6.21.5 and have rc.modules to be symlinked to rc.modules-2.6.21.5 edit lilo.conf or grub start lilo and it should be it!

I went in there just to have a look at it and see whats there and its not. That file does not even exist. What went wrong?

Just make your own, I suggest starting with one of the 2.6.x ones that Slackware provides.

so can I just copy the one for my old 2.6.17 kernel? Or create a simlink to it? Seems like compiling the new kernel should have created the new file. What was the point of compiling in all these modules if I still have to write a file to have the modules loaded. Seems rather redundant to me. Where did the old modules file come from?

First of all, go to /etc/lib/modules
there should be directory 2.6.21.5 and files in that dir. If thats the case modules are installed. and im sure theres such dir.

next thing to tell is that after kernel is compiled from source there modules wont get load at first, lsmod will show nothing. and rc.modules-2.6.21.5 wont get created automatically, you have to create yourself.

to illustrate that lsmod is actually working without a problem, ill assume that you configured 2.6.21.5 to have inside iptables,

by doing /usr/sbin/iptables -L will display your firewall default table, along with directives if you alredy configured it.

if you got an error then that means you didnt enable it in kernel,
but lets say you did

then you go lsmod
and ull see ip_tables
and x_tables listed for instance

thats just to illustrate that lsmod will actually list something before you load your modules

next you need to do is this :

ill assume that you wanted to upgrade kernel from 2.6.18 to 2.6.21.5

thats one way that will load modules on reboot, however if you want to have modules only for your hardware then check the link i gave you previously, chapter 7, and then you can instead cat rc.modules-2.6.18 > rc.modules-2.6.21.5

you just create rc.modules-2.6.21.5 empty file and enter modules in the file that script from generated, and that means that only modules from your hardware will load.