LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - General (http://www.linuxquestions.org/questions/linux-general-1/)
-   -   compiling kernel/first time...issue (http://www.linuxquestions.org/questions/linux-general-1/compiling-kernel-first-time-issue-47664/)

wr3ck3d 02-28-2003 07:42 PM

compiling kernel/first time...issue
 
I am compiling the 2.4.20 kernel and following this page http://p-two.net/modules.php?op=modl...=article&sid=5
i am on the make install part and getting this (went up a few lines to show a better picture....

+ mv /boot/System.map /boot/System.old
+ cat bzImage
+ cp /usr/src/linux-2.4.20/System.map /boot/System.map
+ '[' -x /sbin/lilo ']'
+ /sbin/lilo
Warning: LBA32 addressing assumed
Added DOS *
Fatal: open /vmlinuz: No such file or directory
make[1]: *** [install] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.20/arch/i386/boot'
make: *** [install] Error 2
root@nixbox:/usr/src/linux-2.4.20#

I have followed that guide step by step....lilo, edit makefile, etc, etc.. -thnaks for any help


EDIT: nevermind....fixed for now

wr3ck3d 02-28-2003 08:13 PM

ok, finished compiling and rebooted and lilo had a checksum error...used boot disk to boot and ran liloconfig, it booted up into the new kernel and everything seems fine.....but why did it have the lilo checksum error?? was i supposed to have ran liloconfig after compiling?? also, what can/should i delete from the last kernel?? And lastly i used the old kernel config as kinda a guide to what i should choose...but was wondering since it was a fresh install and that kernel was really never compiled was the options checked in the 2.4.18 kernel source the ones being used in the actual kernel?? -thanks

kc8tbe 02-28-2003 08:46 PM

Wr3ck3d

Good thinking with that boot disk! Yes, you did need to run liloconfig after installing the new kernel. I actually run /sbin/lilo, but I think they do the same thing - that being making a map of the new kernel image (in your case, vmlinuz). Users of grub need run no such command after installing their new kernels.

If your new kernel is working flawlessly, it is probably safe to delete the old kernel's source. Kernel source takes up a lot of space, so it isn't always a good idea to have a lot of it sitting around. You may want to get a second opinion, though.

Even if you delete the old kernel's source, it is still a good idea to hang on to the old kernel itself (probably renamed to /boot/vmlinuz.old). Also, bear in mind that vmlinuz and vmlinuz.old are usually dynamic links - that is, the actually kernel image is someplace else. Make sure you know where the real kernel image resides before you go around deleting stuff!

And if you do keep the old kernel, be sure it is in lilo.conf (be sure it appears in your boot-up menu) or it isn't of much use to you. And, once again, if you modify lilo.conf follow up by running /sbin/lilo (or, in your case, liloconfig)!

Are the options specified in the old kernel's config the same as those in the old kernel? Since you've never compiled the old kernel, the answer is: probably not. I know this is the case for RedHat 8 and Mandrake 9. Regardless, you now have the current options situated in the current kernel's config, so I don't see how the old config would be of any use to you.

-kc8tbe

wr3ck3d 02-28-2003 09:27 PM

Ok, yea, i guess i did have to run just lilo, not liloconfig because i noticed that everything in lilo was reset, so just edited it and ran lilo....about the kernel options what i meant was i used the 2.4.18 menuconfig as sorta a guideline of what to fill in with the 2.4.20 kernel. So what I was asking was if the items/modules that were checked in the 2.4.18 menuconfig the actual options that were used on the system...i suppose since that actual source was not used to install slackware i would doubt if the items checked were actually the items made...but then again it could be, thats why asking. But i think sometime this weekend i am going to go thru the kernel config again slowly and learn what each item does, was kinda rushing thru it jsut to see if it was going to work. -thanks again


All times are GMT -5. The time now is 06:20 PM.