the init program cannot be a shell script as far as I know. It really must be an executable that the kernel should be able to launch directly.
On Tue, Mar 31, 2009 at 12:02 PM, huymq85 <[email protected]> wrote: > > I have created a kernel image (zImage) from samsung-s3c6410-android. > 1.0 using toolchian kandroid-1.1.2.1-20080530.glibc and it is loaed > well. > > boot option in zImage: > > Creating 4 MTD partitions on "NAND 128MiB 3,3V 8-bit": > > 0x00000000-0x00040000 : "Bootloader" > > 0x00040000-0x00400000 : "Kernel" > > 0x00400000-0x03400000 : "Root - Cramfs" > > 0x03400000-0x08000000 : "File System" > > root=/dev/mtdblock2 rootfstype=cramfs init=/start.sh > console=ttySAC0,115200 > > but I have a problem when init root file syetm: > my file system: > data > dev > etc > init ( exec file) > proc > sbin > start (sh file) > sys > system > tmp > var > then , I made a cramfs file from them: cramfs.image > > last, I wrote it into the board (s3c6410): > > tftp c000000 cramfs.image > > nand erase 400000 3000000 > nand write c0000000 400000 3000000 > > but it can not init, although I changed to ./start, start: > > Failed to execute /start.sh. Attempting defaults... > > Kernel panic - not syncing: No init found. Try passing init= option > to kernel. > > please tell me what is wrong? > > thanks you very much > > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
