(1) u can pull init.rc from emulator, compare it with your init.rc and check.
you enable logcat and you will come to know. (2) #logcat service for logging kernel message service logcat /system/bin/logcat -f /dev/kmsg oneshot (3) dmesg can be used only when the root file system is up. On Fri, May 13, 2011 at 5:30 PM, hedwin <[email protected]> wrote: > What is the status of booting android (gingerbread) using 2.6.39? > > I am using 2.6.37 but when init starts zygoto, zygoto stops for some > reason, there is nothing in logcat or dmesg that provides any clue. > I think I might have forgotten something in the kernel config not sure what > though. > Anyone encountered the same issue? > > Hedwin > > > On Thu, May 12, 2011 at 11:32 PM, Jon Pry <[email protected]> wrote: > >> I am having the same problem. What stuff did you remove from the config? >> >> Thanks, >> >> Jon Pry >> >> >> On Fri, Apr 15, 2011 at 9:03 AM, Mario <[email protected]> wrote: >> >>> Ok, I solved the issue. >>> >>> Now init starts-up! >>> The issue turned out to be related with the config file of the kernel. >>> I don't know why, after removing support for unrelated boards (among >>> which OMAP4 and other stuff) I was able to run the binaries. >>> >>> Thanks guys, have a nice day! >>> >>> On 15 Apr, 10:40, hedwin <[email protected]> wrote: >>> > @Mario, do you use the android provided toolchain or an external one. >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > On Fri, Apr 15, 2011 at 10:39 AM, hedwin <[email protected]> >>> wrote: >>> > > I am using 37 kernel version but have the same problem, after >>> removing >>> > > critical to start the servicemanager it showed that >>> > > zygote is constantly restarting. >>> > >>> > > On Thu, Apr 14, 2011 at 5:01 AM, AlanLance <[email protected]> >>> wrote: >>> > >>> > >> I can booting Gingerbread with kernel 2.6.39, but got below message >>> > >> and reboot. >>> > >>> > >> init: starting 'debuggerd' >>> > >> init: starting 'ril-daemon' >>> > >> init: starting 'zygote' >>> > >> init: starting 'media' >>> > >> init: waitpid returned pid 573, status = 0000000b >>> > >> init: process 'servicemanager', pid 573 exited >>> > >> init: process 'servicemanager' killing any children in process group >>> > >> init: critical process 'servicemanager' exited 4 times in 4 minutes; >>> > >> rebooting into recovery mode >>> > >> init: Created socket '/dev/socket/vold' with mode '660', user '0', >>> > >> group '1009' >>> > >> init: Created socket '/dev/socket/dnsproxyd' with mode '660', user >>> > >> '0', group '3003' >>> > >> init: Created socket '/dev/socket/netd' with mode '660', user '0', >>> > >> group '1000' >>> > >> init: Created socket '/dev/socket/rild-debug' with mode '660', user >>> > >> '1001', group '1000' >>> > >> init: Created socket '/dev/socket/rild' with mode '660', user '0', >>> > >> group '1001' >>> > >> init: Created socket '/dev/socket/zygote' with mode '666', user '0', >>> > >> group '0' >>> > >> Restarting system with command 'recovery'. >>> > >>> > >> Alan >>> > >>> > >> On 4月14日, 上午3時05分, Ravi Chemudugunta <[email protected]> >>> wrote: >>> > >> > does your target support thumb? >>> > >>> > >> > On Thu, Apr 14, 2011 at 3:42 AM, Mario <[email protected]> >>> > >> wrote: >>> > >> > > Hello >>> > >> > > I'm trying to boot my board with linux kernel 2.6.39 but I'm >>> getting >>> > >> > > this message: >>> > >>> > >> > > "Kernel panic - not syncing: Attempted to kill init!" >>> > >>> > >> > > The kernel is taken from git:// >>> > >> android.git.kernel.org/kernel/common.git, >>> > >> > > branch remotes/origin/android-2.6.39, >>> > >> > > and I already provided to enable the following options (among >>> > >> > > others): >>> > >> > > CONFIG_AEABI >>> > >> > > CONFIG_ASHMEM >>> > >>> > >> > > If I run the busybox shell instead of init >>> (init=/data/busybox/ash) I >>> > >> > > see that it's not possible to run android binaries (init, >>> /system/bin/ >>> > >> > > *): I get segmentation faults, but I'm able to run pure linux >>> binaries >>> > >> > > (everything inside busybox). >>> > >>> > >> > > So I guess the problem is in my kernel not being able to >>> interpret >>> > >> > > android binaries. >>> > >>> > >> > > What could I try to solve this issue? >>> > >>> > >> > > Thanks >>> > >> > > Mario >>> > >>> > >> > > -- >>> > >> > > unsubscribe: [email protected] >>> > >> > > website:http://groups.google.com/group/android-kernel >>> > >>> > >> > -- >>> > >> > C-x C-s, C-x C-c >>> > >>> > >> -- >>> > >> unsubscribe: [email protected] >>> > >> website:http://groups.google.com/group/android-kernel >>> >>> -- >>> unsubscribe: [email protected] >>> website: http://groups.google.com/group/android-kernel >>> >> >> -- >> unsubscribe: [email protected] >> website: http://groups.google.com/group/android-kernel >> > > -- > unsubscribe: [email protected] > website: http://groups.google.com/group/android-kernel > -- unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel
