MandrivaThis Forum is for the discussion of Mandriva (Mandrake) Linux.
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.
Originally posted by ejupin How can I get the newest kernel for MDK 9.1 without doing a full kernel rebuild..? Could I get it through update, etc? Thanks
Updating (overwriting) the kernel is a bad idea.
New kernels should be installed along side the original, not by overwriting the original kernel.
I'm not so sure that running urpmi kernel will do that. (install along side of, instead of overwriting)
Do you get a choice of what kernel version number to boot during the boot process?
If the new kernel is bad, or corrupt, how would you fix it after it overwrote the working one?
Please open a terminal, use this command rpm -qa | grep kernel and post the results here.
I'm curious as to what that command output shows after a update by urpmi, because you are the first person that has done it this way that I know of.
The rest of us always download the new kernel rpm and install the new kernel along side of the original working kernel. This way we have a escape route if the new kernel is somehow bad, corrupt, or broken.
Originally posted by ejupin How can I get the newest kernel for MDK 9.1 without doing a full kernel rebuild..? Could I get it through update, etc?
Thanks
Just DL the RPM and install....it takes a whole minute.
urpmi is smart enough to not upgrade the kernel by relacing it as ejupin's output shows. There is a file /etc/urpmi/inst.list that lists the things that should not be replaced by a new version (so instead, it installs the new version alongside the old one) and kernel is one of those things.
If you use rpm instead of urpmi, it's a different story. You MUST use
rpm -ivh kernel-blah
and NOT
rpm -Uvh kernel-blah (this will replace the old kernel with potential hazards)
Don't worry. you did it all right. As you can see from the output that you provided above, you still have the old kernel around. BTW, there already is an update for 2.4.22mdk available. It contains a few bug fixes and if you have a CD drive made by LG, you should get it before you break your CD drive.
I am using the new kernel then? Tell me how you see this. I would like to know how to verify a kernel change when I make one.
Thanks for all your help!
you can see which kernel you are using by the command
uname -a
or uname -r (for just the kernel version).
basically, the entries in lilo.conf determine which kernel you will be using.
image=/boot/vmlinuz-2.4.22-10mdk
would use the kernel version 2.4.22-10mdk. The stanza's initrd has to match up with this:
initrd=/boot/initrd-2.4.22-10mdk.img
note that the number 2.4.22-10mdk is the same for vmlinuz and initrd.
The default entries in lilo.conf make use of symlinks but I find it easier to get rid of them and give the full path/name of the kernels and initrds (the make install messes up the symlinks).
So you can boot using different kernels - which is useful if you're not a sure a new kernel is going to work.
Originally posted by quatsch urpmi is smart enough to not upgrade the kernel by relacing it as ejupin's output shows. There is a file /etc/urpmi/inst.list that lists the things that should not be replaced by a new version (so instead, it installs the new version alongside the old one) and kernel is one of those things.
Thanks quatsch, I learned something new today.
And I can see from ejupin's output that it works like its suppose to.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.