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.
I compiled/installed a linux kernel from source for the first time and i copied and pasted the output to
/boot
for System.map and vmlinuz etc.
I configured lilo and i am able to boot from "linux_2.6.0" on lilo upon restart, except when the kernel boots up and i'm brought to the prompt it says "Kernel 2.4.22" still...
I'm sure i probably just didn't replace something properly or i linked a file badly or something. Does anyone have any suggestions/ideas of what a kernel newb like me might have messed up on??
Hey, thank you for responding. Sorry i should have left more details, i wrote a log of everything i did but i didn't have it on me at the time of posting. But now that it's in front of me i'll post it here for you to analyse.
Unpacked source to home directory /root
"bunzip2 linux-2.6.0.tar.bz2"
"tar -tvf linux-2.6.0.tar"
changed directories too /src/linux directory
"cd /usr/src/linux"
"make mrproper"
"xconfig" saved .config file to the directory
compiled
"make dep clean bzImage"
"make modules"
"make modules_install"
"image=/boot/vmlinux-2.6.0
label=linux_2.6.0
root=/dev/hda5 <-- (same partition as current linux fs)
didn't set as default or anything, saved the file
ran
"/sbin/lilo"
rebooted, chose "linux_2.6.0" from lilo boot selecter screen.
it boots up and then i get the "kernel 2.4.22" message.
oh and afterwords i replaced System.map with the System.map-2.6.0 file and still get the same result.
oh, and i checked the threads on compiling here and elsewhere and havne't been able to find anything that was dramatically different from what i did that would lead me to any answers.
that is awsome, you kept a log, and checked threads!...
Unpacked source to home directory /root
"bunzip2 linux-2.6.0.tar.bz2"
"tar -tvf linux-2.6.0.tar"
it may be preference, but just so you know, this can be done with the line
tar -jxvf linux-2.6.0.tar.bz2
the -j option filters thru bzip, and the -x option untars.
-----------
stupid questions follow:
is kernel vmlinux-x.x.x in the /boot directory ?
does the lilo config file contain the correct kernel name and directory?
i know this is a dumb question, but are you sure it's 2.6 kernel src? have to ask.. i'm sure it is..
did you untar the 2.6 kernel, make compile, ect, and then copy /usr/src/linux/arch/i386/boot/bzImage, which was linked to your 2.4 kernel (linux -> linux-2.4.x) ?
end stupid questions
it's worth the few seconds to check those, i've done a few..
check on spoto's suggestion.. for one iof the above questions..
Check the Makefile in /usr/src/<kernel version>, or whereever your kernel source is. The version info is kept in the first few lines of that file.
also please send output of uname -a
this will give host and date info, which is useless to us, but it will also give, kernel version and *build number*..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.