The kernel just finished uncompressed, then stopped. Then there were some occasional reads from the harddisk. If I disabled the power management, then the box would do the same, then did a reboot. What could be the problem? (I didn't copy the System.map, could this be the one? I dare not copy it, for fear that I couldn't use my old kernel)

I had the same problem. No matter what I tried it just wouldn't boot. I recompiled the 2.4.21-Stable kernel and it works great.
Unless you specifically need something offered only in the new test kernel I would stick with the Stable version.

Read the following it may shed some light on the problems you are having

http://www.codemonkey.org.uk/post-halloween-2.5.txt

Very nice. Thanks for the link. :-)

I recompiled the kernel with a trim-down config - no extra stuff. A very plain kernel. It finally boots. However, I can't load any modules. The message said, QM_MODULES function not implemented. What does it mean? How can I implement it? I have checked all options regarding loading modules in the .config.

Any input would be appreciated. Thanks.

i had the same QM_MODULES function not implemented. problem when trying to load modules off the 2.6.0-test2, i had it with all the 2.5.x's as well, i tried modprobe and insmod neither seemed ot know what was goin on, the modules some of them look like they have a .ko extention (i think) that i dont remember seeing in the /lib/modules of any of the 2.4.x's. i was thinking possibly you might need a "newer version" of the modprobe, insmod and what not to be able to use with the newer kernels with the new module form.

From what I heard, the .ko extension is just a cosmetic change, it doesn't really matter. modprobe will figure it out, but insmod (seemingly) can't.

PS. just wondering how many ppl have this problem.

You must install the new module-init-tools.

Thanks, max2003.

I did a google search and found this:
Additional note: in future kernels (newer 2.5 series and above), the module loader mechanism was changed. The new configuration file has to be named /etc /modprobe.conf instead of /etc/modules.conf but there is a translate-script available. For further details see [http://his.luky.org/ftp/mirrors/linu...rusty/modules/] module-init-tool.

http://www.duzijanca.co.yu/tepa/9448.htm


Do the new module-init-tools work with 2.4.21? I don't want to mess up my old kernel.

No they don't! But when installing the new mod utils, you can choose to move your current modultils. When you boot with the 2.4.21 kernel, the old modutils will be used, and if you boot with the 2.6-test kernel, the new one will be used. But you have to explicitly say you want to do that when installing the new version. Read the readme file for details.

thank you, the module-init-tools seemed to make it work correctly, i also reinstalled a 2.5 version of modutils for good measure before i used the module-init-tools.

Thank you all. I finally got 2.6 working. I guess my kernel not boot issue is solved by unchecking the Ram disk and initrd in .config.

Some advices after my experience:
The README comes with kernel source is helpful coz there may be some changes on kernel compilation method.
And the Documentation/Changes tells you what the softwares (and what versions) are required.

When updating the module-init-tool, remember to do
./configure --prefix=/
make moveold (if installing for the first time).
so the old version still works.

Enjoy your new kernel.