hmm...
I had a similar error once....
try re-running syslinux on your new boot.img (the one with your kernel on it)
http://syslinux.zytor.com/
I have seen several reports of this problem in the forum, but no solutions.
I tried to modify the kernel in a CD-boot Knoppix (I needed devfs support, so I grabbed the Knoppix-kernel-source package, kept the same kernel config except for devfs, and recompiled). When I boot the CD, it grabe root.img, and then gives the following message:
Kernel panic : No init found. Try passing init= option to kernel
If I use the default boot.img, my slightly modified Knoppix CD boots fine. It's only when I try to use the image with my kernel that I have problems.
When I made the new boot.img, I modified as little as possible. I kept the same mroot, I just replaced the kernel.
Is there something else I'm missing? Or, does anyone else have a working boot.img that includes a kernel with devfs support?
Thanks,
Todd
hmm...
I had a similar error once....
try re-running syslinux on your new boot.img (the one with your kernel on it)
http://syslinux.zytor.com/
That is the last message but what about other messages like can the script linuxrc find your clooped image and mount it etc.
INIT not found just mean that when the linuxrc exit, the kernel will proceed to use the new root system and search for /etc/init to run and failed. So the most likely cause(as KNOPPIX doesn't not switch real root device) would be that it failed to mount the image does the KNOPPIX fs is not 'imported' in.
More messages are needed.
I would imagine that you don't have the necessary kernel modules in your initial root filesystem (I suppose that's boot.img) to mount your root filesystem. At least, that's my experience from other distributions and from the typical behaviour of "make install" on the Linux kernel sources.Originally Posted by tji
My standard workaround when trying out a custom kernel is to reuse the old initial root filesystem image for the shipped kernel and to replace the kernel and modules in that image (or rather a copy of it). I don't know how wise that is, but the standard kernel Makefiles don't really help me find a reliable alternative.Originally Posted by tji
I've run into this problen myself. To be safe you should replace the kernel modules in the miniroot and recompile cloop and replace that, but this is not the cause of your problem. I beleve that your problem is caused by the init in the miniroot being uncompatable with your new kernel. In the case of knoppix init is statically linked with ash (the initial shell). So you will need to recompile ash-knoppix against your new kernel and sources(it's on Klaus's site somewhere).
jTal
Dell PowerEdge C6320 82F9M Server Blade Module 10gb SFP+ 082F9M
$79.99
Dell PowerEdge FX2s CTO Blade 4 Slot 2U Chassis 2x 2000W
$399.00
Dell PowerEdge M620 Blade Server 2 x Xeon e5 2665 8 x 16 GB(128) RAM - No HD
$44.99
Dell PowerEdge M610 Blade Server E5620@2.2GHZ (6x)8GB RAM (2x)146GB 15K SAS HDD
$79.00
Dell PowerEdge M620 Blade Server 2x 10C E5-2690v2 64GB Ram 2x 600GB 10k HDD
$125.00
Dell PowerEdge M520 Blade Server Xeon E5-2403 NO HDD NO RAM
$40.00
Cisco UCSB-B200-M5 V05 Blade Server with 2x GOLD 6146, 3.2GHZ 64GB RAM, NO SSD
$649.00
Google Search Appliance - Dell PowerEdge R710 x2 Xeon X5690 192GB Memory 6TB HDD
$529.99
HP ProLiant BL460c Gen9 Blade 2x E5-2690v4 2.6GHz =28 Cores 32GB P246 650FLB
$223.00
HP ProLiant BL460c Gen9 Blade 2x E5-2697v3 2.6GHz =28 Cores 32GB P246 650FLB
$173.00