Kernel panic when rebuilding kernel with exact same .config file
I have a SATA drive with LILO boot loader, and a working 32bit 220.127.116.11 kernel that was built on a Mandriva 32bit machine some time back. This Linux environment is a very simple one that boots up to a busybox shell as init by means of a "append="init=/test/test.sh" in lilo.conf, where test.sh sets up the basic Linux environment then starts a busybox shell.
The Mandriva build environment no longer exists, and has been upgraded to a 64bit Ubuntu machine instead.
I downloaded 18.104.22.168 from kernel.org, and then extracted the .config file from the working kernel.
I then used the .config file to build a new but identical 32bit kernel on the new Ubuntu build environment using make "ARCH=i386 menuconfig" followed by "make ARCH=i386 all"
I copied this new kernel to the SATA drive, edited lilo.conf and ran lilo again. However, when I try to boot up from this supposedly identical kernel, I get a kernel panic:
Why is it I have 2 kernels that are the same version, built with the .config file, but resulting in 1 booting and the other not?
Any help would be appreciated. Thanks!
It says your /test/test.sh is not there - that's probably not on the new drive.
|All times are GMT -5. The time now is 10:43 AM.|