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.
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)
Distribution: Fedora, Debian, OpenSuSE and Android
Posts: 1,820
Rep:
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.
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.
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.
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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.