L4Android boot process not completed successfully ("cannot find /system/...")

Itamar O itamarost at gmail.com
Mon Jun 24 06:51:58 CEST 2013


On Sun, Jun 23, 2013 at 9:54 PM, Matthias Lange <
mlange at sec.t-labs.tu-berlin.de> wrote:

> On 23.06.2013, at 08:34, Itamar O wrote:
>
> On Thu, Jun 20, 2013 at 9:28 AM, Matthias Lange <
> mlange at sec.t-labs.tu-berlin.de> wrote:
>
>>
>> On 20.06.2013, at 06:49, Itamar O wrote:
>>
>> On Wed, Jun 19, 2013 at 10:57 PM, Matthias Lange <
>> mlange at sec.t-labs.tu-berlin.de> wrote:
>>
>>> On Sun, Jun 16, 2013 at 10:57:55PM +0300, Itamar O wrote:
>>> > On Sun, Jun 16, 2013 at 10:22 PM, Matthias Lange <
>>> > mlange at sec.t-labs.tu-berlin.de> wrote:
>>> >
>>> > > On 15.06.2013, at 19:13, Itamar O wrote:
>>>
>>
> [...]
>>>
>>
>> These lines look ok. However can you change the Linux cmdline parameter
>> androidboot.hardware to "l4android" instead of "l4". And please check
>> whether the /l4bdds0 device node exists on the ramdisk.
>>
>> Matthias.
>>
>
> I changed "l4" to "l4android" in the cmdline parameters (same results when
> trying to run).
> However, I'm not sure how to check the content of the ramdisk. Could you
> please point me in the right direction?
>
>
> You can try mounting the ramdisk as a loopback device.
>
> Matthias.
>
>
OK, when I mount the rootfs image (that I downloaded from the L4Android
site), I can see the l4bdds[0,1,2] nodes (see below).
But looking at init.rc, I don't see anywhere these nodes are used in any
way, or anything mounted on /system.
Is this normal?

itamar at bender:~/AndroidWorkspace$ ll images/
total 89560
drwxr-xr-x 2 itamar itamar     4096 2013-06-15 15:31 ./
drwxr-xr-x 7 itamar itamar     4096 2013-06-15 15:31 ../
-rwxrw-rw- 1 itamar itamar  1048576 2013-06-24 07:30 root-x86-ginger.img*
-rwxrw-rw- 1 itamar itamar 90652672 2011-10-30 23:11 system-x86-ginger.img*
itamar at bender:~/AndroidWorkspace$ sudo mount images/root-x86-ginger.img
/mnt/android/root -o loop
itamar at bender:~/AndroidWorkspace$ ll /mnt/android/root
total 260
drwxr-xr-x 9 root root   1024 2011-10-30 17:23 ./
drwxr-xr-x 3 root root   4096 2013-06-15 13:22 ../
drwxr-xr-x 2 1003 1003   1024 2011-10-30 13:22 data/
-rw-r--r-- 1 1003 1003    118 2011-10-30 13:22 default.prop
drwxr-xr-x 2 1003 1003   1024 2011-10-30 13:22 dev/
-rwxr-xr-x 1 1003 1003 177758 2011-10-30 13:29 init*
-rw-r--r-- 1 1003 1003  15431 2011-10-30 12:45 init.rc
brwxr-xr-x 1 root root 254, 0 2011-07-07 15:52 l4bdds0
brwxr-xr-x 1 root root 254, 1 2011-07-07 15:52 l4bdds1
brwxr-xr-x 1 root root 254, 2 2011-07-07 15:52 l4bdds2
drwx------ 2 root root  52224 2011-10-30 17:23 lost+found/
drwxr-xr-x 2 1003 1003   1024 2011-10-30 13:22 proc/
drwxr-xr-x 2 1003 1003   1024 2011-10-30 13:29 sbin/
drwxr-xr-x 2 1003 1003   1024 2011-10-30 13:22 sys/
drwxr-xr-x 2 1003 1003   1024 2011-10-30 13:22 system/
-rw-r--r-- 1 1003 1003   3865 2011-10-30 12:55 ueventd.rc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.l4android.org/pipermail/l4android-dev/attachments/20130624/f69ab147/attachment.html>


More information about the l4android-dev mailing list