-----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. 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. 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? - -- Randy Rathbun randy@randyrathbun.org http://astrodot.org - 100% Amateur Astronomy. No preservatives. http://randyrathbun.org http://quitequitefantastic.org "You're a brave man. Go and break through the lines. And remember, while you're out there risking you're life and limb through shot and shell, we'll be in be in here thinking what a sucker you are." - Groucho Marx -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjpWLh4ACgkQHtesIcBFkGQVKACgpUBFu/3zOaf1hlQXULnqfZMy KVIAn2RjMNuOC+IIYFyFKhZqDiBZ33ck =7/uw -----END PGP SIGNATURE-----
Randy Rathbun wrote:
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?
Put this at the top of yoour modules.conf file path=/lib/modules/2.4.0/kernel hope it helps -- Togan Muftuoglu toganm@turk.net 100% MS FREE Absolutely no component of Microsoft was used in the generation or posting of this e-mail. So it is virus free
On Friday 05 January 2001 14:27, 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.
Can't use .config from other kernel versions! I really mean it, read the README file that comes with the kernel, Linus did a splendid job writting it down -- it clarifies everything, including the modules part, which apparently you forgot to do 'make modules' and 'make modules_install' Hope it helps, Alvaro Novo SuSE 6.4 -=- Kernel 2.4.0-prerelease -=- KDE 2.1.0-Beta1-0 2:44pm up 12:18, 3 users, load average: 0.02, 0.02, 0.00
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
On Fri, 5 Jan 2001, Mark Hounschell wrote:
Randy Rathbun wrote:
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.
Ahhhh. So that is what oldconfig does... I will give that a shot....
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.
Oh yeah, I am sure they will too. But I am a rebel :)
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?
Did do make modules, make modules_install, etc. Did not do a depmod -a. Hmmm..... Gonna try that here in a few. -- Randy Rathbun randy@randyrathbun.org http://astrodot.org - 100% Amateur Astronomy. No preservatives. http://randyrathbun.org http://quitequitefantastic.org "I cannot say that I do not disagree with you. " ~ Groucho Marx
On Fri, Jan 05, 2001 at 02:27:06PM -0600, 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. You used the config file from 2.2.16 to build 2.4.0 ? Not wise. Order of events for buliding kernel: xconfig make dep make clean make bzImage make modules make modules_install cp /boot/vmlinuz /boot/vmlinuz.2.2.16 #or whatever cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz cp /usr/src/linux/System.map /boot/System.map
Fix lilo etc etc.
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.
You cannot use 2.2.16 modules with 2.4.0 Hide the 2.2.16 modules tree away somewhere. You can do a "depmod", although that will happen automatically when you boot (at least it does with Suse).
At this point I started creating symlinks all over in there trying to get it to a semi-2.2.16 structure.
No need for this. The modules_install will create the directory structure it needs.
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?
No it isn't the proper way to do it ! I played with 2.4 a bit a while back, I created a second root file system to boot it from to avoid the hassle with modules and other things. Cliff
participants (5)
-
Cliff Sarginson -
Mark Hounschell -
Randy Rathbun -
Togan Muftuoglu -
Álvaro A. Novo