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.
Breezwell: i just noticed it wasnt a patch i installed....the auto install using slapt-get installed a fresh 2.4.23 kernel then removed the old kernel.
I am able to boot just fine... bare.i brings me to the same place as when I just cycle the power....its just loading the kernel modules thats an issue
Mmmhh...I think kernel bare.i (or every other) version 2.4.22 needs the modules for the same version. it search for modules during boot on your system but they were removed.
Quote:
argh, looks like the src was replaced with 2.4.23 too
So you can try to compile the modules for 2.4.23...
That's fine. You could go ahead and build a new kernel (and the modules) based on the 2.4.23 tree, but using the .config file from the bare.i kernel that slack provides (if you wish). Have you compiled a kernel from source before? There is a great guide post at the top of the Slackware forum... http://www.linuxquestions.org/questi...threadid=49035
I agree with BSlack on the modules issue. It sounds to me like the upgrade either:
1) installed a new kernel + sources + modules, but didn't have the same functionality as you wanted it to.
or...
2) installed a new kernel + sources but no modules at all.
I thought you may have had your /lib/modules/2.4.22* tree still lying around (hence the suggestion for the 2.4.22 bare.i kernel bootdisk), but that doesn't appear to be the case
Anyway, you wanted a 2.4.23 kernel anyway, right? You have everything you need since the sorces are installed!
i dunno what went wrong but lilo said the compiled kernel was too big or something....anyway i just backed up my important files and i'm going to reinstall slack 9.1...this time following the upgradepkg instructions from the mailing list. thanks for all the help all
Quick question before you go through the trouble to re-install: Did you 'make zImage' or 'make bzImage'? If zImage fails (kernel is too big) then you can try the bzImage approach and see if lilo likes it better...
Just a thought.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.