My current kernel is 2.6.27.21-0.1-pae and does not have usb gadget support built in.If i go to /usr/src/linux (which points to src for this kernel) and include the usb gadget support and recompile it, will the resulting kernel image overwrite the existing vmlinux-2.6.27.21-0.1-pae.gz in the **/boot *folder or will it create a new image with the corresponding *menu.lst entries?
thisisravi wrote:
> My current kernel is -2.6.27.21-0.1-pae- and does not have usb gadget
> support built in.If i go to -/usr/src/linux- (which points to src for
> this kernel) and include the usb gadget support and recompile it, will
> the resulting kernel image overwrite the existing
> -vmlinux-2.6.27.21-0.1-pae.gz- in the *-/boot- *folder or- will it
> create a new image with the corresponding -menu.lst entries?
If you “make install”, it might. Maybe you would like to
a) Set CONFIG_LOCALVERSION to something like “…-my-usb-patches” and
have/install that in parallel to the distribution kernel.
b) Above, plus build it as a rpm.
Boot menu entries will not be created. You’ll have to add it yourself.
Kind regards,
Andreas Stieger
You can have more than one kernel coexisting independently.
Before compiling you can edit /usr/src/linux/Makefile.
You should see EXTRAVERSION there. Add something, eg.
EXTRAVERSION=-test1
Then “make install” wont override.
I usually build an rpm package:
make clean && make binrpm-pkg
After installing, you still have to make the initrd file
and manually add entries to /boot/grub/menu.lst for
the new kernel. Also, you will have to install the nvidia
graphics driver manually. Yast wont do it for a custom
kernel.