kernel panic with insmod errors

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I downloaded 2.6.10 kernel source tarball and compiled it successfully
by doing the following:

make xconfig
make mrproper
make dep
make clean
make bzImage
make modules_install (this one dumped bunch of depmod: errors about
some symbols but copied the files properly to /lib/modules/2.6.xxx/)
cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.xxx
cp System.map /boot/System.map-2.6.xxx

After that I have added an entry grub.conf file to point to my new
kernel. However, I am not sure about the initrd line so I just left it
unchanged (same as old entry I had already - so it was pointing to old
initrd.img file still).

After this when I rebooted, I chose the kernel that I just compiled
from the GRUB menu but while booting it, there were few insmod errors
and then kernel panics saying it was unable to mount the root fs (/).
Is this because the new grub is pointing to old initrd line ? How do I
make new initrd.img for the kernel I just compiled ? I have compiled
the kernel with SCSI drivers builtin along with loop back support. How
do I know whether all needed modules are compiled ? I see that some
modules that I have compiled into the kernel also are failing with
insmod before the kernel panics.

Can someone help me out or point me to the proper news group ? Please
let me know if you need more information.

Thanks,
Sarath

--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux