Hi All
Issue is solved now.
Change is regarding TLS (Thread Local Storage) which is the register
found in recent kernel of ARM. Earlier version of ARM does emulation
of TLS.
Android also makes an assumption that the kernel Emulates the TLS.
So irrespective of the physical presence of the TLS regi
Hi Thangamani Arun,
Thanks for response. I tried out all options/checking as per your
suggestion, still problem is same.
Regards
Manjunatha Srinivasan N
On Jul 17, 12:11 pm, தங்கமணி அருண் wrote:
> > I am getting following error on mounting android filesystem through
> > NFS on OMAP board:
>
> a
>
>
> I am getting following error on mounting android filesystem through
> NFS on OMAP board:
>
and add "rootdelay=6" in your boot args
> Kernel panic - not syncing: Attempted to kill init!
>
> I populated the root filesystem (/root-for-nfs) as below:
>
check /etc/exports on nfs-server. it sh
Hi Vinay
sorry for late response.
i compiled both kernel and file system with aem-eabi- toolchain only.
But still problem is same.
I believe building busybox open source with new Android.mk file under
external directory is enough to get init ?
Regards
Manjunatha Srinivasan N
On Jul 3, 5:01 pm,
Which is this arm-eabi tool chain in the android sources? I mean is
this the same as codesourcery arm-none-linux-gnueabi?
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~--
On Jul 3, 5:01 pm, Vinay Rao wrote:
> Hi,
>
> Even i had faced the same problem.
> I did the following.
> 1) Booted the Linux kernel using BUSYBOX init.
> 2) Then tried executing ANDROID init manually.
> My Init was giving SEGFAULT.
> The problem was with my tool chain. I was supposed to use ar
Hi,
Even i had faced the same problem.
I did the following.
1) Booted the Linux kernel using BUSYBOX init.
2) Then tried executing ANDROID init manually.
My Init was giving SEGFAULT.
The problem was with my tool chain. I was supposed to use arm-eabi tool
chain which i wasn't using.
I compiled my a
Till the problem is there.
On Jul 3, 4:00 pm, manjunatha wrote:
> Hi
>
> Thanks for immediate help.
>
> Here is the following boot args i used to give:
>
> setenv bootargs display=15 console=ttyS0,115200n8 noinitrd ip= ip>omap:eth0:off root=/dev/nfs
> nfsroot=:/fs,nolock rw devfs=mount
> an
Hi
Thanks for immediate help.
Here is the following boot args i used to give:
setenv bootargs display=15 console=ttyS0,115200n8 noinitrd ip=omap:eth0:off root=/dev/nfs
nfsroot=:/fs,nolock rw devfs=mount
androidboot.console=ttyS0 rootdelay=3 init=/init
My android resource for OMAP is from
Hi,
Your boot loader bootargs may be wrong check it once.
Regards,
Vinay R Rao
On Thu, Jul 2, 2009 at 7:36 PM, manjunatha
wrote:
>
> Hi
>
> I am getting following error on mounting android filesystem through
> NFS on OMAP board:
>
> Kernel panic - not syncing: Attempted to kill init!
>
> I pop
10 matches
Mail list logo
