From: Dirk Behme <dirk.behme@googlemail.com>
To: Jonathan Herriott <herriojr@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: Android on N810 File System Problem
Date: Fri, 25 Apr 2008 07:42:52 +0200 [thread overview]
Message-ID: <48116F5C.9040009@googlemail.com> (raw)
In-Reply-To: <6a56d69c0804241248w5e46efe8k757c9e5fb9e3ce22@mail.gmail.com>
Jonathan,
CCing OMAP mailing list, there are more people to help.
Jonathan Herriott wrote:
> Hi,
>
> I'm trying to get android installed on an N810. I have successfully
> installed the kernel,
Which kernel (2.6.x, x == ?) do you use on N810? If I remember
correctly, with N810 people use an older kernel than the one coming
with Android SDK.
> but I am having major issues with the file
> system. I followed the tutorial you provided at
> http://elinux.org/Android_on_OMAP, but I get a segmentation fault when
> I try to init the kernel. I made sure to use the same android SDK
> version that was used to patch the kernel.
>
> My steps for reproduction are:
>
> 1) On my computer, unpack the ramdisk image to a folder.
> 2) Untar system, dev, and data to the unpacked ramdisk image.
> 3) Tar up the patched file system and scp it to /opt on the device.
> Ssh to the device and unpack the file system in /opt
> 4) Run umask 000 && chroot /opt/android /init
> 5) Receive a segmentation fault.
Can you send us the complete segementation fault output?
Regards
Dirk
next parent reply other threads:[~2008-04-25 5:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6a56d69c0804241248w5e46efe8k757c9e5fb9e3ce22@mail.gmail.com>
2008-04-25 5:42 ` Dirk Behme [this message]
2008-04-25 18:36 ` Android on N810 File System Problem Felipe Balbi
2008-04-25 18:31 ` Igor Stoppa
2008-04-25 18:52 ` Felipe Balbi
2008-04-25 18:47 ` Igor Stoppa
2008-04-25 23:29 ` Felipe Balbi
2008-04-27 9:43 ` Kalle Valo
2008-04-27 22:32 ` Felipe Balbi
2008-04-27 23:04 ` Igor Stoppa
2008-04-28 6:24 ` Jarkko Nikula
2008-04-28 23:38 ` Tony Lindgren
2008-04-29 9:00 ` Brian Swetland
2008-04-30 9:49 ` Kalle Valo
2008-04-30 10:20 ` Brian Swetland
2008-04-30 10:46 ` Felipe Balbi
2008-05-02 6:17 ` Kalle Valo
2008-05-12 12:32 ` Dirk Behme
2008-04-29 9:49 ` Jarkko Nikula
2008-04-29 22:31 ` Jonathan Herriott
2008-04-30 1:04 ` Tony Lindgren
2008-04-30 9:45 ` Kalle Valo
2008-04-25 19:31 ` Jonathan Herriott
2008-04-25 23:35 ` Jonathan Herriott
2008-04-26 7:13 ` Dirk Behme
2008-04-27 2:21 ` Jonathan Herriott
2008-04-27 6:44 ` Dirk Behme
2008-04-27 8:13 ` Jonathan Herriott
2008-04-29 9:06 ` Brian Swetland
[not found] ` <200804290948.m3T9mLHt021830@smtp.google.com>
2008-04-29 10:13 ` Questions on Android Brian Swetland
2008-05-05 12:38 ` shivananda.hebbarp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48116F5C.9040009@googlemail.com \
--to=dirk.behme@googlemail.com \
--cc=herriojr@gmail.com \
--cc=linux-omap@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.