"Nothing to be done for bzImage..."

[Jeff Mutonho]

On 3/21/07, Brad Bonkoski <bbonkoski at mediaguide.com> wrote:
> Jeff Mutonho wrote:
> > On 3/21/07, Robert P. J. Day <rpjday at mindspring.com> wrote:
> >> On Wed, 21 Mar 2007, Jeff Mutonho wrote:
> >>
> >> > On 3/20/07, alan <alan at clueserver.org> wrote:
> >> > > On Tue, 20 Mar 2007, Phil Meyer wrote:
> >> > >
> >> > > > Jeff Mutonho wrote:
> >> > > >> I got the message "Nothing to be done for bzImage..."  during an
> >> > > >> attempt to do a kernel rebuild on an FC6 machine.This happened
> >> when I
> >> > > >> tried to do a "make bzImage"
> >> > > >>
> >> > > >> Thereafter "make install' failed with a message saying
> >> something about
> >> > > >> "vmlinuz" missing.
> >> > > >> What could be the problem?
> >> > > >>
> >> > > >>
> >> > > >>
> >> > > > There is a file called README in the top level of the kernel
> >> sources.
> >> > > >
> >> > > > % grep make README
> >> > > >
> >> > > > always shows the same sequence for building a kernel
> >> > > >
> >> > > > make mrproper or make oldconfig
> >> > > > make (choose configurator)
> >> > > > make
> >> > > > sudo make modules_install install
> >> > > >
> >> > > > Examination of the makefile should show that there is not a
> >> target called
> >> > > > bzImage.
> >> > >
> >> > > But there used to be.  Sounds like someone either has old
> >> instructions or
> >> > > has not upgraded their memories on kernel building.
> >>
> >> once again, the "bzImage" target is not a generic kernel-building
> >> target, it is i386-specific, which is why it can be found in
> >> arch/i386/boot/Makefile and not in the top-level Makefile.
> >>
> >> it most definitely *does* exist.  simply typing "make bzImage" should
> >> have established that.  "make help" would have demonstrated it as
> >> well.
> >>
> >> rday
> >> --
> >
> > Ok I read the README file and  i've done the 'make' , 'make
> > modules_install install' .A new kernel image was created as seen from
> > the last part of the log:
> > =========================================================
> > if [ -r System.map -a -x /sbin/depmod ]; then /sbin/depmod -ae -F
> > System.map  2.6.18-build-1; fi
> > mkdir -p /boot
> > ln -f -s vmlinuz-2.6.18-build-1 /boot/vmlinuz-2.6.18
> > rm -f /boot/vmlinuz-2.6.18-build-1
> > install -m0644 vmlinuz /boot/vmlinuz-2.6.18-build-1
> > install -m0644 vmlinux /boot/vmlinux-syms-2.6.18-build-1
> > install -m0664 .config /boot/config-2.6.18-build-1
> > install -m0664 System.map /boot/System.map-2.6.18-build-1
> > ln -f -s vmlinuz-2.6.18-build-1 /boot/vmlinuz-2.6
> > ====================================================================
> >
> > What extra step(s) do I need to do ?My grub.conf file still looks the
> > same as before (i.e does not show an entry for the new kernel).Isn't
> > it suppose to be updated automatically?
> I suspect there are way too many boot loaders for the kernel install
> process to make changes to this...
> Just copy & paste your current entry, rename it something different, and
> update the file names of the kernel image and initrd (if needed)
> -B

Hmmm.My current grub.conf looks as follows :
title Fedora Core (2.6.18-1.2798.fc6xen)
	root (hd1,0)
	kernel /xen.gz-2.6.18-1.2798.fc6
	module /vmlinuz-2.6.18-1.2798.fc6xen ro root=/dev/VolGroup00/LogVol00
rhgb quiet
	module /initrd-2.6.18-1.2798.fc6xen.img


Now to create an entry to for the new kernel , I would have to add the
following entry :

title Fedora Core (2.6.18-build-1)
	root (hd1,0)
	kernel /xen.gz-2.6.18-1.2798.fc6
	module /vmlinuz-2.6.18-build-1 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
	module /initrd-2.6.18-1.2798.fc6xen.img

but in there doesn't seem to be the corresponding files for the entries
kernel /xen.gz-2.6.18-1.2798.fc6    and
module /initrd-2.6.18-1.2798.fc6xen.img

in my /boot directory.




"Don't take the name of root in vain."

Jeff  Mutonho
Cape Town
South Africa

GoogleTalk : ejbengine
Skype        : ejbengine
Registered Linux user number 366042