On Mon, 27 Sep 1999, Paul Clyne wrote:
> Good listers,
>
> I'm having a problem with compiling my own Kernel (I have done so several
> times sucessfully in the past on RH5.2) but on RH6.0....
>
> I do all the 'propper' things, in the propper order and get zImage which I
> then move to /boot, update lilo.conf and lilo.. all seems in order..
It would have been beter if you had given the exacht commands used,
pls, do that next time.
> However when I re-boot (their must be a way of 'running' a new kernel
> without rebooting) the start-up gets as far as 'FINDING MODULE
> DEPENDANCIES' the HD flashes for a while then all is silent (even leaving
> the system wait for 10+ minutes it didn't carry on).
What it _sounds_ like is a problem of the kernel not being able to
find the modules, but you seem to have found that out, i think the
only thing i can do is explain how it should be done in the hope it
will get rid of your problem.
cd /usr/src/linux
edit Makefile
add -1 (or you choose) to EXTRAVERSION = so it looks like
EXTRAVERSION = 1
do not forget the white space between the = and the number.
(if you are satisfied you have configured the kernel properly) do;
make oldconfig This will automaticly use the old configuration, you
can check it first if you wish, its called /usr/src/linux/.config
then,
make dep clean zImage (yes all on one line).
make modules modules_install
cp System.map /boot/System.map-2.2.5-1 (or what ever version number
it is).
cp arch/i386/boot.zImage /boot/vmlinuz-2.2.5-1
edit /etc/lilo.conf
add the nessacary lines somewhere after the first iamge, remember the
first image is the default.
image=/boot/vmlinuz-2.2.5-15
label=linux
root=/dev/hda1
read-only
image=/boot/vmlinuz-2.2.5-1
label=2.2.5-1
root=/dev/hda1
read-only
Note the example has /dev/hda1 make sure you use _your_ correct
partition.
Rerun lilo this will not even touch your old kernel and will always
allow you to use it if the new kernel gives problems.
Another way is to use make install instead of make zImage which will
do al of the above (execpt edit lilo.conf and the linux Makefile)
That would then be.
cd /usr/src/linux
edit Makefile
make oldconfig dep clean install
edit lilo.conf
rerun lilo
reboot
What it sounds like to me is that you over wrote the old kernel and
modules, as to why it froze at modules i would imagen they were
either not installed or disfigured in one or another way.
The secret is edit the Kernel Makefile before every attempt to make a
kernel then you get modules in 2.2.5-1 in the above case. the rest
will be done by the kernel/linux bit of magic concerning kernel
modules.
The next time you make a kernel edit the Makefile and change the 1 to
2 etc etc.
>
> No problem I thought, I'll just re-boot with my old working kernel and see
> what I did wrong... Unfortunately the old (used to work) kernel suffers
> the same fate (ie : FINDING MODULE DEPENDANCIES and hanging).
>
> So what gives ?. I'm a newbie and I'm stumped ?.
>
> What did I do that broke BOTH kernels. I re-installed from the CD and the
> old Kernel image works again (remember this is the exact same backup image
> that refused to work in the steps above).
>
> Possibly I've broken one of the modules ? (ie : make modules or make
> modules_install) but I really wan't to use an optimized Kernel for my box
> but each time I re-compile I have to go through the whole re-install
> process again.
>
> Can anyone shed any light for me ?. What other information do you require
> ?.(I _think_ the release level is 2.2.15 but I'm going of memory on this one)
>
> Thanks heaps in advance.
>
>
>
>
> -------------------------------------------------------
> Paul Clyne aka: pacman / pac
> at work : [EMAIL PROTECTED]
> at play : [EMAIL PROTECTED]
>
> The future is in our hands. Which way to the future ?
> --------------------------------------------------------
--
Regards Richard
[EMAIL PROTECTED]
