Randy Rathbun wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Maybe I have something goofed up, but 2.4.0 is giving me some troubles and I am unsure what to do as this is the first time I have ever done a kernel upgrade.
Here is what I did:
1. Went to 2.2.16.SuSE and ran xconfig and saved the config file to /usr/src. 2. Went to 2.4 and ran xconfig and read in the config file, then built it, installed it, booted it.
That probably won't work. Running your 2.2.16 kernel go to the 2.4 src dir and do make oldconfig. All of your original kernel stuff will be place in the new .config file + it will ask you a number questions about the new options in the 2.4 kernel which you will have to answer. When you are all done you will have a new .config for your 2.4 sources.
It boots fine. However now it can't find most of the modules. I went in and looked and the modules are in a different directory structure than 2.2.16. For example, most of the modules reside in /lib/modules/2.4.0/kernel.
I had this happen. I know it's probably not the right way but what I did to get all the modules in place was: 1. save that new .config file you made from above 2. ran xconfig and changed everything to module that could be made a module then did make modules and modules_install. 3. then restored my original .config from step 1. On the 6.4 cd there is a package with all the modules in it. Don't have one for 2.4. I'm sure SuSE will fiz all this up for us soon though.
At this point I started creating symlinks all over in there trying to get it to a semi-2.2.16 structure.
My question is this: is this the proper way to do this? Is there something else I should be doing instead of making all these blasted symlinks?
The make modules and modules_install should place all the modules in /lib/modules/2.4.0. Be sure that /usr/src/linux is a link to /usr/src/linux-2.4.0 before you start. Before you do a depmod -a I THINK that the System.map file from your complile needs to be in /boot. Did you do a depmod -a? -- Mark Hounschell markh@compro.net