SUSE / openSUSEThis Forum is for the discussion of Suse 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.
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
Not sure if this is a procedure you are telling us or need some question answered. In the 2.6 kernel things have been changed.
run ' make xconfig ' or others to configure kernel options
run ' make ' it now does both make bzImage and make modules
run ' make modules_install ' to install modules
then run ' make install ' to do the rest of of the following and add the boot line to your grub. cp arch/i386/boot/bzImage /boot/bzImage-2.6.13-15.7, cp System.map /boot/System.map-2.6.13-15.7, cp vmlinux /boot/vmlinux-2.6.13-15.7, mkinitrd -k vmlinux-2.6.13-15.7 -i initrd-2.6.13-15.7
So for a complete install from start to finish and ready to boot.
make xconfig
make
make modules_install
make install
Reboot
And if you are using rpms then running the command ' make rpm ' will make an rpm file of the kernel.
"This command will also replace old symlinks pointing to the default kernel with the new ones. However Failsafe GRUB option menu should point to the old and ~&trusty kernel. You can eaither correct this with the steps from ad 17, or you can modify GRUB menu.lst file. This is entirely up to you"
no this is not correct way.
If you want to have several versions of kernel 2.6.13.15, you will simply overwrite kernels if you do not modify .config file.
However this is pretty easy to do.
When done with kernel configuration: make xconfig (or such)
edit .config file and modify this line:
CONFIG_LOCALVERSION=""
eg
CONFIG_LOCALVERSION="-spanking_new_kernel"
pay attention to the hyphen at the beginning
now your kernel will be named: vmlinuz-2.6.13.15-spanking_new_kernel
and what's important, you will create (instead of overwriting old one) new entry in
/lib/modules
in this case
/lib/modules/2.6.13.15-spanking_new_kernel
these are symlinks, I have explained why you should remove them or what to do if you dont want to remove them assuming that yo are using "make install" command
However if you don ton use "make install" command then old symlinks are not replaced and are still pointing to the old working kernel. I assume that you know what symlinks are?
Otherwise, it is up to you
Personally, I dont care about symlinks because GRUB points to the real kernel so changing symlinks will not affect failsafe (to boot old working kernel).
However this is pretty easy to do.
When done with kernel configuration: make xconfig (or such)
edit .config file and modify this line:
CONFIG_LOCALVERSION=""
eg
CONFIG_LOCALVERSION="-spanking_new_kernel"
pay attention to the hyphen at the beginning
why in your tutorial you said
"Now very important: edit Makefile and add/change the line:
EXTRAVERSION = -unique_name (pay attention to "-" sybmol in front of the name)"
I explained this in my tutorial.
Let's say that you have SuSE WORKING default kernel. Now you want to customize it. So you install sources, configure it and install. If you do not change the internal kernel name and you will run make modules_nstall, this will overwrite default modules in
/lib/modules
So if you messed up something (and let's say file system module will not start), you are "done". Because you did in fact overwrite modules it really does not matter if you will try to boot default or customized kernel your modules are fck up because kernel (whatever name you added after compaling) will still refer to the internal name to look for modules.
The fact that later you change the name of vmlinuz does not matter: this is too late and only takes care of vmlinuz, not modules.
If you want to experiment and have several custom kernels built from the same source, only the last one's modules are on the disk.
when i need to build a module like when we install ati or nvidia driver... there a surely a way to said build it for the new and old kernel....
any idea?
unfortunately, nvidia must be recompiled each time you change kernel..
nvidia allow to be installed on working kernel or any other installed kernel, but only one.
I don't have experience with vmware, but it is possible that you will have the same problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.