Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Hi!
I was using Fedora Core 2 some weeks ago, and played around with various kernel
versions and -configurations.
After some time then, I finally broke my system so that it didn't boot up with
any of the custom compiled kernels.
I then felt that it was time to change to Mandrake 10, mostly because of the
working ATI graphics drivers.
Mandrake 10 came with an rather old kernel, 2.6.3, in fact, so I soon compiled
my own 2.6.7 kernel with the enwset 2.6.7 patch by Con Kolivas. It's working
well now, but what should I do if the new 2.6.8 kernel is finalized and I want
to install it? How do I keep all those kernel versions and the corresponding
modules isolated from each other? What do you recommend?
After you compile a new kernel, you have to copy arch/... to /boot/vmlinuz...
The new /boot/vmlinuz... is just a name, different for each kernel you compile.
It could be /boot/vmlinuz-2.4.26 or /boot/vmlinuz-2.6.7 or /boot/vmlinuz-new, /boot/vmlinuz-new1, it doesn' t matter, it is just a name.
Just make another entry in LILO, with the new name you gave for each kernel.
image=/boot/vmlinuz
root=/dev/hda1
label=slackware1
read-only
This one of my entries. The next one is:
Give aswell a timeout, and a default entry to be booted
.
When modifying LILO, don' t forget rerun lilo /sbin/lilo to update LILO at the next boot.
Same way for GRUB, even I am not really familiar yet.
Hi,
managing the already compiled kernels was not my problem, but managing the sources and keeping them isolated from each other. I have some modules that didn't came with the kernel, but needed the kernel sources to compile cleanly. So, when I compile an new kernel, how can I make sure that the version of the module corresponding to the old kernel is not loaded, but the new version?
Aargh, 10 minutes ago a typical problem happened again, and I have no plan how to fix it!
I compiled the 2.6.8-rc2 kernel, no problems. It is present in /usr/src/linux-2.6.8-rc2, but there's no symlink /usr/src/linux refering to it; there is my 2.6.7-ck5 kernel.
So, everytime the kernel tries to boot, I get a kernel panic: VFS: Unable to mount root fs on unknown-block(3,9)
I gave the kernel the command line option root=/dev/hda9, but it didn't help!
Can someone help me? The 2.6.7 kernel worked correctly, and I don't think that it's a bug in the kernel
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.