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.
Okay, I have a problem here. All the kernel-compiling threads say that you have to install module-init-tools to compile kernel 2.6.3.
The problem is, I want to have access to my old kernel 2.4.22 because I know that kernel 2.6.3 will fail to load my modules correctly and I still want to have sound and have access to the Internet and my printer after I upgrade.
The last time I installed module-init-tools, it screwed up my modprobe. When I boot into my old kernel, everytime it tries to load a module, I get the error message: "Kernel requires old modprobe"
Anyway to keep modutils and module-init-tools on the same computer so that I can run 2.6 without sacrificing my 2.4?
well the way i look at it, why do you want to install the 2.6.x kernel if you still wanna use your 2.4 ? cause how i am looking at this, why don't you just keep the 2.4 kernel for "backup" purposes (even if some things don't load) for just in case you blow up the 2.6 compile process ... and you'll have something to fall back on just in case you don't succeed.... and then try again ...
and then troubleshoot your problems with 2.6 and get it up and running to where you want it ?
Quote:
I want to have access to my old kernel 2.4.22 because I know that kernel 2.6.3 will fail to load my modules correctly
and then i know you are saying this above, but if you think about it, do you think that your 2.4 kernel is going to support something that the newer 2.6 doesn't support ? or for that matter even if it was the case, don't you think you'd be able to download "the driver" to get whatever it is to work ??
i am just not grasping what your trying to do, cause it just appears to me by the way your talking that your going to compile the 2.6 kernel and not even use it ...
I'm hoping to get my kernel 2.6 to work eventually but I know that it won't work the first time. So I want to be able to get help through the Internet after my 2.6 kernel fails without having to boot into Windows (whose filesystem is on the verge of collapsing any second, I don't want to risk it).
I am not talking about 2.6 not supporting certain modules, just that the 2.6 modules don't work. I am getting unresolved symbols errors and QM_MODULES errors everywhere. It's going to take at least a week to fix my problems, if they get fixed at all, and I don't want to live so long without internet, access to my printer, and sound. I'm in school, you know?
I want to use the 2.6 kernel eventually but I want to have access to 2.4 until it does fully work.
Am I the only person in the whole world who has compiled 2.6 a dozen times but has never gotten it to work? Everybody here seems to compile 2.6 and happily ditch 2.4. Yes, I have read all the compiling threads here and nobody has my problem.
when you upgraded to the module-init-tools did you do the "make moveold" before you did "make and make install" . The reason for doing this is so you can still boot older kernels and module loading for them will still work
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.