Thanks tom, just one thing you didn't mention. use "make bzImage" instead
of "make bzlilo" to use the directions. ;) I'm going to have to go
investigate "make bzlilo" cause now i see your useing both, i was under
the impression make bzlilo compiled the bzImage
On Thu, 1 Jul 1999, Tom Berger wrote:
> On Thu, Jul 01, 1999 at 08:54:47AM -0700, Jay Summet for [EMAIL PROTECTED] wrote:
> > Ok, I have a dual CPU MB, so the first thing I want to do is recompile
> > with SMP support.
> > make clean
> > make xconfig
> > make dep
> > make bzImage
> > make modules
> > make modules_install
> > make bzlilo
> >
> > Unfortunatally, "make bzlilo" doesn't install the kernel correctly,
> > apparently because the lilo.conf file points to the kernel in the /boot
> > directory.
> >
> > No problem I think...edit lilo.conf to point to the new /vmlinuz kernel,
> > re-run lilo to install it, and the new kernel boots, and then promptly
> > hangs when "Finding Module Dependencies".
> >
> > After re-installing (I'm at a temp job working out of a motel, don't have
> > rescue boot disks, just install boot floppy from 5.3 and 6.0 CD...) I
> > tried just overwriting the old kernel image in the /boot directory (file
> > name called vmlinuz-2.2.9-19mdk or something like that) re-running lilo
> > and rebooting. Same error, hangs up after turning the HD for 15 seconds at
> > the "Finding Module Dependencies" part.
> >
> > I assume that there is something simple I'm doing wrong?
> >
> > Jay Summet
>
>
> Indeed :). Your system hangs because you either didn't update the System.map,
> forget to rerun /sbin/lilo or missed a link somewhere.
> If you don't mind doing it the long way round (I prefer this, because I don't
> trust installation scripts in general):
>
> Having built the kernel and its modules and installed those modules, do this
> being in /usr/src/linux:
>
> copy the kernel to /boot:
> cp arch/i386/boot/bzImage /boot/vmlinuz-[version number]
>
> copy the System.map to /boot:
> cp System.map /boot/System.map-[version number]
>
> link both to their default entries:
> ln -sf vmlinuz-[version number] vmlinuz
> ln -sf System.map-[version number] System.map
>
> open /etc/lilo.conf in your favourite editor:
>
> now *before* the first image entry add your new kernel:
>
> image=/boot/vmlinuz-[version number]
> label=linux
> root=/dev/hda1 #if /dev/hda1 is your root partition
> read-only
>
> Go to the now second entry for the old kernel and change the value for 'label'
> to 'old' (or what you like). This has the advantage that you will still be able
> to boot the old kernel by typing 'old' on the LiLo prompt.
>
> Run /sbin/lilo. You should see something like
>
> Adding linux*
> Adding old
>
> And now take a deep breath and reboot... :)
>
>
> HTH
>
> tom
>
> --
> "Everybody is someone else's newbie" (Marilyn Manson, edited)
> Thomas 'tom' Berger, [EMAIL PROTECTED] No spam, no UCE. 'Nuff said.
> Get Answers! Visit Mandrake Answers on http://aolmfaq.tsx.org!
>
You may or may not need to disregard these babbleing's it's aweful early
Axalon,
