Kernel panic ............a big pain

[Jahanzeb]

Hello Dear Jerome Henry
Thanks u very for ur kind help.
I am sending u the following information.
N looking forward to hear from you soon.


Here is the grub.conf

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/hda5
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Red Hat Linux 9(Jahanzeb) (2.4.20-8)
root (hd0,0)
kernel /vmlinuz-2.4.20-8 ro root=LABEL=/
initrd /initrd-2.4.20-8.img

title DAO GUNJRANAWALA (Compiled by Jahanzeb)
root (hd0,0)
kernel /bzImage.myker.8aug2003 ro root=LABEL=/
initrd /initrd-2.4.20-8.8aug2003.img

And here are the contents of /boot.

-rw-r--r-- 1 root root 87241 Aug 9 19:42 2.4.20-8.8aug2003.img
-rw-r--r-- 1 root root 5824 Jan 25 2003 boot.b
-rw-r--r-- 1 root root 0 Aug 10 14:09 boot.list
-rw-r--r-- 1 root root 1195948 Aug 8 18:50 bzImage.myker.8aug2003
-rw-r--r-- 1 root root 612 Jan 25 2003 chain.b
-rw-r--r-- 1 root root 44309 Mar 14 04:01 config-2.4.20-8
-rw-r--r-- 1 root root 38820 Aug 8 18:48 config-2.4.20-8.8aug2003
drwxr-xr-x 2 root root 4096 Aug 10 14:08 grub
-rw-r--r-- 1 root root 87309 Aug 9 19:43 initrd-2.4.20-8.8aug2003.img
-rw-r--r-- 1 root root 149668 Aug 7 19:14 initrd-2.4.20-8.img
-rw-r--r-- 1 root root 473 Aug 7 19:14 kernel.h
drwx------ 2 root root 16384 Aug 7 19:06 lost+found
-rw-r--r-- 1 root root 23108 Feb 25 05:51 message
-rw-r--r-- 1 root root 21282 Feb 25 05:51 message.ja
lrwxrwxrwx 1 root root 20 Aug 7 19:14 module-info -> module-info-2.4.20-8
-rw-r--r-- 1 root root 15436 Mar 14 04:01 module-info-2.4.20-8
-rw-r--r-- 1 root root 640 Jan 25 2003 os2_d.b
lrwxrwxrwx 1 root root 19 Aug 7 19:14 System.map -> System.map-2.4.20-8
-rw-r--r-- 1 root root 520129 Mar 14 04:01 System.map-2.4.20-8
-rw-r--r-- 1 root root 541124 Aug 8 19:02 System.map-myker.8aug2003
-rw-r--r-- 1 root root 3193503 Mar 14 04:01 vmlinux-2.4.20-8
lrwxrwxrwx 1 root root 16 Aug 7 19:14 vmlinuz -> vmlinuz-2.4.20-8
-rw-r--r-- 1 root root 1122186 Mar 14 04:01 vmlinuz-2.4.20-8

[Paulo A G Fessel]

For what I've read in your previous posting, seems that ext3 driver is a module in your current kernel configuration and you haven't loaded it into the ramdisk (the "2.4.20-8.8aug2003.img" file).

For you to succeed in booting your new kernel, you must either

1) add the ext3 driver to your ramdisk. You can assure that it will be going to your ramdisk with "mkinitrd -f -v \
--with=ext3 /boot/2.4.20-8.8aug2003.img 2.4.20-8.8aug2003.img". If you need modules for your disk subsystem you must add them BEFORE ext3, since the modules inserted by
--with parameters are loaded in the EXACT order you specify in the command line.

2) recompile your kernel making ext3 built-in into the kernel. For this, you should set the "ext3 file system support" to "Y" instead of "M".

HTH
Paulo Fessel

[Jahanzeb]

Thanks Mr. Paulo Fessel, for your kind response,

I did select the ext3 in the "File systems" menu in menuconfig command.

And when I recompiled the kernel using the
"nohup make bzImage & " command.
Then I could not find the bzImage in the relevant directory [/usr/src/linux/arch/i386/boot), whereas during the first attempt of kernel recompilation, the bzImage was there.
Here are some error messages as well in the nohup.out file. I request you to review these errors N let me know that how I shuld proceed now.

gcc -D__KERNEL__ -I/usr/src/linux-2.4.20-8/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 -nostdinc -iwithprefix include -DKBUILD_BASENAME=pci -DEXPORT_SYMTAB -c pci.c
gcc -D__KERNEL__ -I/usr/src/linux-2.4.20-8/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 -nostdinc -iwithprefix include -DKBUILD_BASENAME=quirks -c -o quirks.o quirks.c
gcc -D__KERNEL__ -I/usr/src/linux-2.4.20-8/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 -nostdinc -iwithprefix include -DKBUILD_BASENAME=compat -c -o compat.o compat.c
make[3]: *** No rule to make target `/usr/src/linux-2.4.20-8/drivers/pci/devlist.h', needed by `names.o'. Stop.
make[3]: Leaving directory `/usr/src/linux-2.4.20-8/drivers/pci'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux-2.4.20-8/drivers/pci'
make[1]: *** [_subdir_pci] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.20-8/drivers'
make: *** [_dir_drivers] Error 2

I did use the find command to locate the bzImage file, but the result was in NO.

Waiting for the same quick response.

Thanks in advance.

Jahan

[Vitaly Karasik_1]

1) I suggest to re-check if you really need kernel recompilation - RH doesn't support recompileted kernels


2) if you going to recompile you kernel, I recommend you to take one of config files from "src/configs" directory and recompile your new kernel according to RH manual

http://www.redhat.com/docs/manuals/linux/RHL-7.2-Manual/custom-guide/custom-kernel.html



Regards,
Vitaly

[Jerome Henry]

Hello my dear,

Your kernel panic message indicated that you had a wrong file affectation in your boot process, or that your recompiled kernel didn't support your hardware.

Looking at your compilation error message, it's clear now that there is a hardware support problem (pci).

The trouble is that when you run make xconfig (or menuconfig), each option to choose is to check very carefully, as it influences all the kernel reaction thenafter, and the other devices reaction.

Would you mind if we would start back from the beginning ? Did your first kernel work (the 2.4.20-8) ? What would you like to change in your kernel ?

J

[Paulo A G Fessel]

Compilation issues are commonplace when you make bzImage a number of times.

The best things you can do are:

1) save your configuration file on a safe place, copying /usr/src/linux-2.4.20-8/.config to another file. I suggest you to use "/root/config" as it will be kept REALLY safe.

2) issue a "make mrproper" to clean things up.

3) copy back your config file to /usr/src/linux-2.4.20-8/.config and issue "make oldconfig ; make dep ; make bzImage ; make modules ; make modules_install".

This should clean the mess up. The powers of "make mrproper" are close to infinity; I was wrestling with IEEE488 software that didn't compile until I issued it. ;-)

HTH,
Paulo Fessel