The only reason for init to exit is not being able to open sockets. You
should see a message like "init startup failure"
Did you enable network support in 2.6.39?


On Thu, Apr 14, 2011 at 3:49 PM, Mario <mario.demon...@gmail.com> wrote:

> They are both statically linked
>
> With objdump -x I've seen this difference:
> busybox (Working): Version4 EABI
> init (non working): Version5 EABI
>
> Another difference is that busybox has been compiled for a linux
> distribution, while init has been compiled for Android (so against
> bionic)
>
>
> On 14 Apr, 15:40, Jon Pry <jon...@gmail.com> wrote:
> > Is the difference between working and nonworking executables static vs
> > dynamic linking?
> >
> >
> >
> >
> >
> >
> >
> > On Thu, Apr 14, 2011 at 5:46 AM, Mario <mario.demon...@gmail.com> wrote:
> > > They are. That same filesystem works with another kernel I have.
> > > Besides, the files are executed but, before doing anything in main,
> > > they crash with either seg fault or illegal instruction
> >
> > > On 14 Apr, 10:50, hedwin <hedwin.kon...@gmail.com> wrote:
> > > > Check if the exectables in your android rootfilesystem are marked as
> > > > executable.
> >
> > > > On Thu, Apr 14, 2011 at 9:50 AM, Mario <mario.demon...@gmail.com>
> wrote:
> > > > > Hi Ravi
> > > > > Yes, it does, it's an OMAP3530 and CONFIG_ARM_THUMB is on.
> >
> > > > > On 13 Apr, 21:05, Ravi Chemudugunta <chemudugun...@gmail.com>
> wrote:
> > > > > > does your target support thumb?
> >
> > > > > > On Thu, Apr 14, 2011 at 3:42 AM, Mario <mario.demon...@gmail.com
> >
> > > 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: android-kernel+unsubscr...@googlegroups.com
> > > > > > > website:http://groups.google.com/group/android-kernel
> >
> > > > > > --
> > > > > > C-x C-s, C-x C-c
> >
> > > > > --
> > > > > unsubscribe: android-kernel+unsubscr...@googlegroups.com
> > > > > website:http://groups.google.com/group/android-kernel
> >
> > > --
> > > unsubscribe: android-kernel+unsubscr...@googlegroups.com
> > > website:http://groups.google.com/group/android-kernel
>
> --
> unsubscribe: android-kernel+unsubscr...@googlegroups.com
> website: http://groups.google.com/group/android-kernel
>

-- 
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-kernel

Reply via email to