Booting L4Linux on Raspberry Pi 2

[Antoine DEBUT]

Hello l4-hackers,

Since I was able to correctly set up my l4re for the Raspberry Pi 2
thanks to Adam, I did a bunch of tests on the board with custom
programs and following the examples on the l4/pkg/examples directory.

Therefore, I am now struggling with the ultimate test: booting and
using L4Linux.

I am trying to boot a vanilla L4Linux, using the entry 'L4Linux-basic'
given in the default modules.list.

Upon booting, L4Linux delivers this error :

[...]
l4linux | List of all partitions:
l4linux | 0100            4000 ram0  (driver?)
l4linux | 0101            4000 ram1  (driver?)
l4linux | 0102            4000 ram2  (driver?)
l4linux | 0103            4000 ram3  (driver?)
l4linux | 0104            4000 ram4  (driver?)
l4linux | 0105            4000 ram5  (driver?)
l4linux | 0106            4000 ram6  (driver?)
l4linux | 0107            4000 ram7  (driver?)
l4linux | 0108            4000 ram8  (driver?)
l4linux | 0109            4000 ram9  (driver?)
l4linux | 010a            4000 ram10  (driver?)
l4linux | 010b            4000 ram11  (driver?)
l4linux | 010c            4000 ram12  (driver?)
l4linux | 010d            4000 ram13  (driver?)
l4linux | 010e            4000 ram14  (driver?)
l4linux | 010f            4000 ram15  (driver?)
l4linux | No filesystem could mount root, tried:  ext3 ext2 ext4 cramfs
l4linux | Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(1,0)
l4linux | CPU: 0 PID: 1 Comm: swapper Not tainted 4.3.0-l4 #2 l4linux |
Hardware name: L4
l4linux | [<0200cb88>] (unwind_backtrace) from [<0200583c>]
(show_stack+0x10/0x14)
l4linux | [<0200583c>] (show_stack) from [<020627a4>] (panic+0x7c/0x1cc)
l4linux | [<020627a4>] (panic) from [<02354df0>]
(mount_block_root+0x25c/0x29c)
l4linux | [<02354df0>] (mount_block_root) from [<023550f4>]
(prepare_namespace+0x160/0x1b4)
l4linux | [<023550f4>] (prepare_namespace) from [<02354a40>]
(kernel_init_freeable+0x178/0x1c0)
l4linux | [<02354a40>] (kernel_init_freeable) from [<0227409c>]
(kernel_init+0x8/0xec)
l4linux | [<0227409c>] (kernel_init) from [<02007e34>]
(ret_from_fork+0x14/0x20)
l4linux | [<02007e34>] (ret_from_fork) from [<00000000>] (  (null))
l4linux | ---[ end Kernel panic - not syncing: VFS: Unable to mount
root fs on unknown-block(1,0)
l4linux | ------------[ cut here ]------------
l4linux | WARNING: CPU: 0 PID: 1
at /home/adebut/Documents/L4Hyperviseur-LBNV/l4re-snapshot-2015123115/src/l4linux/arch/l4/kernel/main.c:2148
l4x_blink+0x10/0x50()
l4linux | Modules linked in:
l4linux | CPU: 0 PID: 1 Comm: swapper Not tainted 4.3.0-l4 #2
l4linux | Hardware name: L4
l4linux | [<0200cb88>] (unwind_backtrace) from [<0200583c>]
(show_stack+0x10/0x14)
l4linux | [<0200583c>] (show_stack) from [<0201dee4>]
(warn_slowpath_common+0x78/0xb0)
l4linux | [<0201dee4>] (warn_slowpath_common) from [<0201dfb8>]
(warn_slowpath_null+0x1c/0x24)
l4linux | [<0201dfb8>] (warn_slowpath_null) from [<02001af0>]
(l4x_blink+0x10/0x50)
l4linux | [<02001af0>] (l4x_blink) from [<0206289c>] (panic+0x174/0x1cc)
l4linux | [<0206289c>] (panic) from [<02354df0>]
(mount_block_root+0x25c/0x29c)
l4linux | [<02354df0>] (mount_block_root) from [<023550f4>]
(prepare_namespace+0x160/0x1b4)
l4linux | [<023550f4>] (prepare_namespace) from [<02354a40>]
(kernel_init_freeable+0x178/0x1c0)
l4linux | [<02354a40>] (kernel_init_freeable) from [<0227409c>]
(kernel_init+0x8/0xec)
l4linux | [<0227409c>] (kernel_init) from [<02007e34>]
(ret_from_fork+0x14/0x20)
l4linux | [<02007e34>] (ret_from_fork) from [<00000000>] (  (null))
l4linux | ---[ end trace 5ed140c2c802ee32 ]---
l4linux | panic: going to sleep forever, bye
l4linux | panic: going to sleep forever, bye

I cannot find any related mail on this mailing list, and therefore must
ask you for some help.
Could this be a partition misconfiguration ? Or is it related to
the '(driver?)' warning on the partition list ?

I have attached my globalconfig.out for Fiasco and the l4lx.cfg file
that I am using, built l4linux for Arm architecture and ARMv7, and is
using the l4re-snapshot-2015123115 with its ramdisk associated and
U-boot.

Thanks in advance for your help,

-- 
Antoine Debut 
EPITA 2016 - GISTRE
-------------- next part --------------
A non-text attachment was scrubbed...
Name: globalconfig.out
Type: application/octet-stream
Size: 1962 bytes
Desc: not available
URL: <http://os.inf.tu-dresden.de/pipermail/l4-hackers/attachments/20160309/9cf173a8/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: l4lx.cfg
Type: application/octet-stream
Size: 310 bytes
Desc: not available
URL: <http://os.inf.tu-dresden.de/pipermail/l4-hackers/attachments/20160309/9cf173a8/attachment-0001.obj>