Hi, I would guess you are trying to boot one of the Zoom board flavours. init=/init in your command line means that kernel will try to start / init at the end. And your NFS probably doesn't have it. You may try init=/bin/sh just to see that you can boot to shell.
Dmitry On Jan 6, 5:20 pm, "Rene Gonzalez" <[email protected]> wrote: > Hey guys, > > I got in trouble after compiling the Android kernel and file system; on > minicom shows me the next error: > > <4>Warning: unable to open an initial > console. > > Warning: unable to open an initial > console. > > <4>Failed to execute /init. Attempting > defaults... > > Failed to execute /init. Attempting > defaults... > > <0>Kernel panic - not syncing: No init found. Try passing init= option to > kernel. > > Kernel panic - not syncing: No init found. Try passing init= option to > kernel. > > The parameters and the address of configured NFS are: > > setenv bootargs console=ttyS2,115200n8 noinitrd mem=112M root=/dev/nfs rw > nfsroot=10.87.230.128:/home/reno/Android/repository/fsAndroid,nolock,wsize=1024,rsize=1024 > ip=10.87.224.163 init=/init > > setenv bootcmd 'tftpboot 0x80300000 kernel/uImage; bootm' > > And of course the two folders containing the fs are ../root/ & ../system/ > are located in home/reno/Android/repository/fsAndroid, so if any one have a > solution for this problem, please let me know... > > Best regards, > Reno. --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
