Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Booting new Kernel Image

1 view
Skip to first unread message

Greg B.

unread,
Nov 5, 2001, 10:09:25 AM11/5/01
to
Hi all, I have used Linux off and on before, I am familiar with it it
many areas,
but one I am not is reconfiguring and recompiling the kernel. I have a
memorex 1622 CDRW
and wanted to use cdrecord. In my linux book it said I needed to
reconfigure the kernel to
support "scsi-emulation". I Did this, reconfigured the kernel, then
saved config using "xconfig".
I then ran "make mrproper", then "make dep" , then made a new image with
""make zImage"
but the "zImage" was too large so I made it as a commpressed image with
"make bzImage"
This all went ok, then I did make on the modules with "make modules",
and finally
installed the mofules wit "make modules_install".
All still fine. I went into the "lilo.conf" file and added a line for
the scsi emulation support
append="hdd=ide-scsi"
Then after reboot, did "dmesg | grep ^hd to look to see if it shows
-enabling SCSI emulation
on my Memorex CDRW, but it still looks the same as before "hdd: Memorex
CRW-1622, ATAPI drive"
I am thinking it is still booting off the old image, I looked at all the
images and they all seem to have
the new date of today, since I did this this morning.
How do I tell it to boot off the new image and which image is it?
in my folder /usr/src/linux/arch/i386/boot/ I have a "zImage" about 4k
in size, and a "bzImage" about 659 K
in size, also there is a folder here called compressed, it contains a
"vmlinux" that is 658K, and a "bvmlinux"
that is also 658K same as the "vmlinux" in this folder.
I know I need to set the Lilo.conf file to boot off the new image, but
which is it?
in lilo.conf, I have
image=/boot/vmlinux
should it now be image=/boot/bvmlinux
?
?

Andrew Marks

unread,
Nov 7, 2001, 12:32:36 AM11/7/01
to
First thing you need is a partition on your hard drive that is within the
first 1024 cylinders, This is usually mounted as /boot
Then you need to look in your linux source directory which is usually
/usr/src/linux and go into arch/i386/boot.
This is assuming that you are using an x86 processor. In that directory,
/usr/src/linux/arch/i386/boot. you should find a
file called bzImage. That is the kernel you compiled. copy or move it to
a place within the first 1024 cylinders of your hard drive,
usually /boot. After you find the image and put it where you want it you
need to edit /etc/lilo.conf and tell lilo where to find your new image.
I would recommend not overwriting your current kernel image and leaving
that information in /etc/lilo.conf. To be able to choose at
boot time what image you want to use. Put the word "prompt" somewhere
toward the beginning of the lilo.conf file. You may also want to
change the timeout if there is one. timeout=20 is plenty. you put that
toward the beginning of your lilo.conf file also.

Now, Look at the end of your lilo.conf for four lines that look like this:

image = /boot/vmlinuz
root = /dev/hda3
label = Linux
read-only

Once you find that, copy those for lines and edit the the image and label
values in your new copy accordingly:

image = /path-to-new-bzImage
root = /dev/hda3
label = newkernel
read-only


after doing this, run lilo and you should get
*Added Linux
Added newkernel


When you reboot, you should get some kind of prompt to select what image
you want to boot.
You may have to type it in. If there is no graphical selection utility you
can hit tab when lilo pauses to see your options
boot the new kernel which I called newkernel. Only after you are sure the
kernel works, you can get rid of the selection stuff
and even your old kernel if you really want, and make lilo boot the new
kernel by default.

Good Luck!

Greg B.

unread,
Nov 7, 2001, 3:09:15 PM11/7/01
to
Andrew Marks wrote:

Thanks for the help I cross posted to another group and see how it all works,.

My new kerel image was too large according to lilo, so I will have to try to
build another image smaller by disabling some things.
Thanks again
Greg


0 new messages