- l4-hackers - example.com Site

L4linux: cpu and core [comprehension question]
by Irvanda Kurniadi 28 Apr '14

28 Apr '14

Hi hackers, I am a little bit confused about the term of cpu and core in l4linux. I have a system with 8 processor intel xeon E5606 with 4 cores in each cpu. I'm going to maximize it to become the maximum number of cores in all cpus. But I am confused in determining the l4x_cpus that what is the term cpu in here? Is it literally cpu or the number of threads that can be handled in each core? I run an openmp hello world apps over l4linux. I call the omp_get_thread_num() and I got 4 threads in the result. Are these 4 threads obtained from 4 cores in single cpu? So, if I'm right, how can I optimize to use all of the cpu existed in the system? I've tried to use l4x_cpus=8 and l4x_cpus=32, but those commands doesn't work for me. In my opinion, if I can maximize until the maximum number of cores and I have 32 threads that run concurrently, then it will be served by each core in those 8 cpus. In fiasco configuration, there is maximal supported number of CPUs. So referring to my case, the maximum is supposed to be 8, am I right? In case of thread migration in example ex_thread_migrate, I create 16 threads and will be migrated to each cpu. Here is the result: migrate | Migrated Thread00 -> CPU02 migrate | Migrated Thread01 -> CPU03 migrate | Migrated Thread02 -> CPU04 migrate | Migrated Thread03 -> CPU05 migrate | Migrated Thread04 -> CPU06 migrate | Migrated Thread05 -> CPU07 migrate | Migrated Thread06 -> CPU00 migrate | Migrated Thread07 -> CPU01 migrate | Migrated Thread08 -> CPU02 migrate | Migrated Thread09 -> CPU03 migrate | Migrated Thread10 -> CPU04 migrate | Migrated Thread11 -> CPU05 migrate | Migrated Thread12 -> CPU06 migrate | Migrated Thread13 -> CPU07 migrate | Migrated Thread14 -> CPU00 migrate | Migrated Thread15 -> CPU01 My question is do the thread00 and thread08 share the same core in CPU02 or they use different core in CPU02 which run concurrently? And also, is it normal to get the output like cpu[1] to cpu[7] goes to idle loop? Thanks, Irvanda

2 3

Re: L4Linux and L4Re communication
by Björn Döbel 25 Apr '14

25 Apr '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 25.04.2014 10:24, Irvanda Kurniadi wrote: > On Fri, Apr 25, 2014 at 4:24 PM, Björn Döbel > <doebel(a)os.inf.tu-dresden.de <mailto:doebel@os.inf.tu-dresden.de>> > wrote: > > -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > > Hi, > >> In term of running hello world in L4Linux, I can run it by >> passing -m32 -static in the compilation process. But, now I'm >> having a problem in running the mpi-based application on L4Linux >> which this apps needs the mpi library to be able to run. I have >> ported the mpi library and run the apps over L4Re by using Ned. >> So, based on the explanation above, I don't understand how to run >> the mpi-based program on top L4Linux in which the L4Linux >> definitely doesn't have mpi-library because the mpi-library is >> existed in L4Re. Is it like this, the l4linux kernel needs the >> device driver to communicate with external L4 apps (in my case >> mpi-base apps), then to trigger the communication we should make >> the kernel module (linux program to talk to the l4linux kernel). >> Am I right? Can you point one example, which is similar with my >> case, that can be followed by me? > > I see two different scenarios here: > > > 1. Your MPI application is supposed to run as a Linux application > in L4Linux - -> In this case all you need is an MPI library > installed in the Linux distribution that you boot L4Linux into. > E.g., if you are using some custom ramdisk, simply add a (Linux) > MPI library to this disk and your program will then use it. No L4 > magic necessary at all. > > > 2. Your MPI application is supposed to run directly on L4Re - -> In > this case you don't need any Linux or L4Linux in the setup. You > build your L4Re program and link it with your ported MPI library > and then it should run. > > Does that answer your question or am I missing your point? > > > Yes it does. In my case I think I only need to run my application > on L4linux, but since the beginning I misunderstood that I have to > port the library on L4. I have wasted so much time in doing > scenario 2. Sorry to hear that. > What is the differences between running application over L4linux > and running application as a task in L4Re? Good question. Let me try to explain from bottom up. 1. It all starts with Fiasco.OC, our microkernel. Fiasco runs directly on the hardware in the CPU's privileged mode. It provides kernel mechanisms, such as threads, tasks, inter-process communication and scheduling. - - - - - - - - - - - - - - - - - - - - - - - - - - - - +-------------+ Privileged CPU Mode | Fiasco.OC | +-------------+ 2. On top of Fiasco.OC we have the L4 Runtime Environment. L4Re is a set of libraries and applications that run in non-privileged (aka "user") mode and implement basic operating system services, such as memory management, device drivers etc. +------------------------+ | L4 Runtime Environment | Non-privileged +------------------------+ CPU mode - - - - - - - - - - - - - - - - - - - - - - - - - - - - +-------------+ Privileged CPU Mode | Fiasco.OC | +-------------+ 3. On top of L4Re you are free to implement your own software using L4Re's and Fiasco's primitives. This is where scenario #2 (MPI on L4Re) comes in. +-----------------+ +---------------------+ | MPI Application | | Another Application | +-----------------+ +---------------------+ +------------------------+ | L4 Runtime Environment | Non-privileged +------------------------+ CPU mode - - - - - - - - - - - - - - - - - - - - - - - - - - - +-------------+ Privileged CPU Mode | Fiasco.OC | +-------------+ In contrast to Linux this is a completely different operating system. You mostly don't see that because L4Re provides you with interfaces that are similar to Linux (e.g., a POSIX C library, a virtual file system etc.). With respect to MPI the difference here is that you have to adapt any kind of load balancing, process distribution etc. to use the respective Fiasco and L4Re services. 4. Now we have a special usage scenario: We can slightly adapt the Linux kernel and run it as an application on top of L4Re. This is called L4Linux and the approach is what we call virtualization. +----------------+ | L4Linux Kernel | +----------------+ +------------------------+ | L4 Runtime Environment | Non-privileged +------------------------+ CPU mode - - - - - - - - - - - - - - - - - - - - - - - - - - - +-------------+ Privileged CPU Mode | Fiasco.OC | +-------------+ 5. A single (L4)Linux kernel does not help you very much, because you want to run applications on top of Linux. Here the virtualization magic steps in and as a result you can run standard Linux applications on top of L4Linux without the need for any modification. Technically, these applications are L4 applications with the difference that their system calls are not sent to the Fiasco kernel but to the L4Linux kernel. The combination of the L4Linux kernel and all Linux applications running on top of it is what we call a virtual machine (VM). Linux VM .............................. . +-------------------+ . . | Linux Application | . . +-------------------+ . . +----------------+ . . | L4Linux Kernel | . . +----------------+ . .............................. +------------------------+ | L4 Runtime Environment | Non-privileged +------------------------+ CPU mode - - - - - - - - - - - - - - - - - - - - - - - - - - - +-------------+ Privileged CPU Mode | Fiasco.OC | +-------------+ This setup is how scenario #1 works. Your Linux MPI application believes it is running on a real Linux kernel and Fiasco's virtualization makes sure that everything works as expected. Kind regards, Bjoern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlNaJo8ACgkQP5ijxgQLUNmSfgCgkQUPRGJ/Vyq0DIQkEi/Dm9+2 gAcAnRdS9hHkIIp9qBYCfHHL1+Uuy2Fi =zFBP -----END PGP SIGNATURE-----

1 0

L4Linux and L4Re communication
by Irvanda Kurniadi 25 Apr '14

25 Apr '14

Hi, This thread is just a sequel from http://os.inf.tu-dresden.de/pipermail/l4-hackers/2013/006108.html > > Is it possible to run my application on top l4linux; like, > > if I want to run hello world application over l4linux (not just > > booting it over l4/fiasco)? I tried to run it by using this > > configuration: > > > > -- Start Hello loader:start( { caps = {}, l4re_bdg = L4.Dbg.Warn, > > log = {"hello","red"}, }, "rom/hello"); > > > > -- Start Linux loader:start( { caps = { log = L4.Env.log:m("rws"), > > fb = mag_svc:create(L4.Proto.Goos, "g=640x480"); vbus = > > vbus_l4linux; }, l4re_dbg = L4.Dbg.Warn, log = { "l4linux", > > "yellow" }, }, "rom/" .. lxname .. " mem=64M console=tty0 > > l4x_rd=rom/ramdisk-" .. L4.Info.arch() .. ".rd root=1:0 > > ramdisk_size=4000 init=linuxrc"); > > > > But I think it only run two different applications over l4/fiasco. > > > > Do you have any idea how to run the hello application over > > l4linux? > Bjoern said: > > The idea behind L4Linux is to run native Linux applications, so hello > world in L4Linux works just as the version you would write in your > local Linux. > > Running an application that communicates with both L4 and Linux is a > bit more involved. L4Linux applications don't talk to L4 apps > directly. The L4Linux kernel is an L4 app though, so it can do this > talking for you. The missing link then is to write a Linux device > driver that allows your Linux program to talk to the L4Linux kernel, > which then in turn communicates with an external L4 application. > > In term of running hello world in L4Linux, I can run it by passing -m32 -static in the compilation process. But, now I'm having a problem in running the mpi-based application on L4Linux which this apps needs the mpi library to be able to run. I have ported the mpi library and run the apps over L4Re by using Ned. So, based on the explanation above, I don't understand how to run the mpi-based program on top L4Linux in which the L4Linux definitely doesn't have mpi-library because the mpi-library is existed in L4Re. Is it like this, the l4linux kernel needs the device driver to communicate with external L4 apps (in my case mpi-base apps), then to trigger the communication we should make the kernel module (linux program to talk to the l4linux kernel). Am I right? Can you point one example, which is similar with my case, that can be followed by me? Thanks, Irvanda

2 2

build error: [kobject_mapdb.o] error
by Irvanda Kurniadi 25 Apr '14

25 Apr '14

Hi hackers, I have a problem in building l4/fiasco for arm. I'm using ubuntu 11.10 64-bit and want to build l4/fiasco for arm9. For cross compiler, I'm using Sourcery_G++_Lite. For the snapshot, I'm using current snapshot l4re-snapshot-2014022818. Then, when I tried to build the l4/fiasco, I got the error message shown in [1.error message]. Have you ever built l4/fiasco for arm9 over ubuntu 11.10 64-bit? I think this is just a compiler problem. If you know about this problem, please let me know to solve this problem. Thanks, Irvanda [1.error message] make[3]: Entering directory `/home/l4re-arm/obj/fiasco/arm-mp-rv-pb11mp' ... Generating version information ... Making kip.o ... Making kip-debug.o ... Making kip-arm.o ... Making l4_types.o ... Making l4_types-debug.o ... Making l4_fpage.o ... Making l4_msg_item.o ... Making l4_buf_desc.o ... Making l4_error.o ==> Archiving into libabi.a ... Making kernel.arm.lds ... Making crt0.o ... Making bootstrap.o ... Making bootstrap-arm-realview.o ==> Linking bootstrap.fiasco.o ... Making kernel_panic.o ... Making libc_backend_lock.o ... Making cpu_mask.o ... Making rcupdate.o ... Making kobject_mapdb.o In file included from /home/l4re-arm/src/kernel/fiasco/src/kern/context.cpp:22, from /home/l4re-arm/src/kernel/fiasco/src/kern/switch_lock.cpp:85, from /home/l4re-arm/src/kernel/fiasco/src/kern/helping_lock.cpp:4, from /home/l4re-arm/src/kernel/fiasco/src/kern/lock.cpp:3, from /home/l4re-arm/src/kernel/fiasco/src/kern/kobject.cpp:3, from /home/l4re-arm/src/kernel/fiasco/src/kern/kobject_mapdb.cpp:5, from auto/kobject_mapdb.cc:3: /home/l4re-arm/src/kernel/fiasco/src/lib/libk/cxx/function:34: error: 'cxx::functor<Res(Args ...)>::functor(cxx::functor<Res(Args ...)>&&)' cannot be defaulted make[3]: *** [kobject_mapdb.o] Error 1 make[3]: Leaving directory `/home/l4re-arm/obj/fiasco/arm-mp-rv-pb11mp' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/l4re-arm/obj/fiasco/arm-mp-rv-pb11mp'

2 4

Keyboard Input in L4Re Pandaboard ARM
by Erry Pradana Darajati 24 Apr '14

24 Apr '14

Hello L4 hackers I have a question about accessing standard I/O Is it possible to access keyboard using L4Re. If it's possible, can i access it using USB keyboard or do i need to access the std input from serial ? The idea of this question because i want to make a simple calculator to practice study the stdio of L4Re I am really sorry for the basic question And i am appreciating any helps and answer Thanks L4 Hackers -- *Regards,* *Erry Pradana Darajati | Student of Computer Engineering* *Politeknik Elektronika Negeri Surabaya / EEPIS, Indonesia*

2 1

Can you confirm whether or not I secure devices on L4 Linux ?
by Taeung 24 Apr '14

24 Apr '14

Hello, L4 hackers and Wei Jin :-) I'm trying to secure devices which are 'SD card' and 'Ethernet' on L4 Linux. Can you confirm whether or not I secure devices on L4 Linux ? Sorry for long my mail.. The try I've done is as follows .. 1) 'l4lx-vbus.io' file I've modified ==================== # vim:set ft=ioconfig: # configuration file for io l4linux => new System_bus() { NIC => wrap(hw-root.NIC); FLASHMEMORY => wrap(hw-root.FLASHMEMORY); } ==================== 2) 'arm-rv-eb-mc.devs' file I've modified using IRQ and MMIO information in my board's DataSheet . (My board is 'Freescale imx6 Quad SABRE SD') ==================== local Hw = Io.Hw local Res = Io.Res Io.hw_add_devices { FLASHMEMORY = Hw.Device { hid = "flashmemory"; Res.mmio(0x02198000 , 0x0219BFFF); Res.irq(56); }, NIC = Hw.Device { hid = "freescale"; Res.mmio(0x02188000, 0x0218BFFF); Res.irq(150); Res.irq(151); }, } ==================== 3) l4lx_xs.cfg I've modified. ==================== local lxname = "vmlinuz"; if L4.Info.arch() == "arm" then lxname = "vmlinuz.arm"; end loader = L4.default_loader; vbus_l4linux = loader:new_channel(); -- Start io & flash memory loader:start( { caps = { sigma0 = L4.cast(L4.Proto.Factory,L4.Env.sigma0):create(L4.Proto.Sigma0); icu = L4.Env.icu; l4linux = vbus_l4linux:svr(); }, log = { "IO", "y" }, l4re_dbg = L4.Dbg.Warn, }, "rom/io rom/arm-rv-eb-mc.devs rom/l4lx-vbus.io"); L4.default_loader:start( { caps = { log = L4.Env.log:m("rws"), vbus = vbus_l4linux; }, l4re_dbg = L4.Dbg.Warn, log = { "l4linux", "yellow" }, }, "rom/" .. lxname .. " mem=64M vmalloc=4M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 rw ramdisk_size=20480 init=/linuxrc debug"); ==================== 4) I've modified 'modules.list' 5) I found something about device on L4 Linux booting log as follows.. ==================== |Starting kernel ... L4 Bootstrapper Build: #8 Tue Apr 22 16:33:35 JST 2014, 4.6.2 20110630 (prerelease) Scanning up to 1024 MB RAM ...(omitted) l4linux | ======> L4Linux starting... <======== l4linux | Linux version 3.13.0-l4-svn46 (taeung@taeung-MS-7798) (gcc version 4.6.2 20110630 (prerelease) (Freescale MAD -- Linaro 2011.07 -4 l4linux | Binary name: rom/vmlinuz.arm | ||...(omitted) l4linux | Device scan: l4linux | Device: (noname) l4linux | Device: NIC l4linux | MEM: 02188000 - 0218bfff l4linux | IRQ: 00000096 - 00000096 l4linux | IRQ: 00000097 - 00000097 l4linux | Device: FLASHMEMORY l4linux | MEM: 02198000 - 0219bfff l4linux | IRQ: 00000038 - 00000038 l4linux | Device scan done. || ||||...(omitted) |||DMA: preallocated 256 KiB pool for atomic coherent allocations Added static device '(noname)' with 0 resources. Added static device 'NIC' with 3 resources. Added static device 'FLASHMEMORY' with 2 resources. ...(|||omitted|) mmcblk driver (I've added 'pr_info("|||mmcblk driver|");' in __init function of mmc device driver source code.) ...(|||omitted|)| |mount: mounting /dev/mmcblk0p2 on /mnt failed: No such device or address /etc/init.d/S10getconf: Couldnt mount /dev/mmcblk0p2 Initializing random number generator... random: dd urandom read with 1 bits of entropy available done. Loading libertas firmware... /lib/firmware/libertas not found! /etc/init.d/S30libertas_fw: exit: line 46: Illegal number: -2 Starting network... Cannot find device "usb0" Cannot find device "usb0" Cannot find device "wlan0" Cannot find device "wlan0" Starting dropbear sshd: OK Loading iptables rules... /etc/iptables not found! dnsmasq: unknown interface usb0 Error for wireless request "Set Mode" (8B06) : SET failed on device wlan0 ; Invalid argument. Cannot read /proc/net/wireless Error for wireless request "Set ESSID" (8B1A) : SET failed on device wlan0 ; Invalid argument. net.ipv4.ip_forward = 1 / # |==================== I guess that devices is secured through being registered in io server but network could not be run because there is not FEC ethernet driver. (For reference, my board's ethernet use 'FEC Ethernet Driver' ) However I don't know why could not run 'mount /dev/mmcblk0p1 /mnt '. Do I secure devices on L4 Linux successfully ? If I only make drivers for its to run successfully , can I access 'SD card' and 'Ethernet' on L4Linux ? Or is my guess wrong ? I would appreciate if anyone answer. - Taeung -

2 1

Fiasco.OC and qemu vexpress machine model
by Michele Paolino 24 Apr '14

24 Apr '14

Hello l4hackers, I'm trying to execute Fiasco.OC along with the hello module using qemu and the vexpress machine model. For both A9 and A15 cpus the system hangs at "Starting kernel fiasco". It seems that something (the UART driver?) prevents the system to log the kernel boot to the screen. I compiled the image using 'make qemu' in L4RE, and the vm is executed with the argument -nographic. Can you confirm this? Do you have any suggestion to solve it? Here below you can find the log of the A15 boot process: L4 Bootstrapper Build: #2 Thu Apr 10 12:50:53 CEST 2014, 4.6.3 Scanning up to 256 MB RAM Memory size is 256MB (80000000 - 8fffffff) RAM: 0000000080000000 - 000000008fffffff: 262144kB Total RAM: 256MB mod04: 810bc000-810d5580: hello mod03: 810a2000-810bb460: l4re mod02: 81070000-810a162c: moe mod01: 81066000-8106f344: sigma0 mod00: 81014000-810652e0: fiasco Moving up to 5 modules behind 81100000 moving module 00 { 81014000-810652df } -> { 811c2000-812132df } [332512] moving module 01 { 81066000-8106f343 } -> { 81214000-8121d343 } [37700] moving module 02 { 81070000-810a162b } -> { 8121e000-8124f62b } [202284] moving module 03 { 810a2000-810bb45f } -> { 81100000-8111945f } [103520] moving module 04 { 810bc000-810d557f } -> { 8111a000-8113357f } [103808] Scanning fiasco -serial_esc Scanning sigma0 Scanning moe --init=rom/hello Relocated mbi to [0x8100d000-0x8100d0e2] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x80002000 Regions of list 'regions' [ 80001000, 80001cbf] { cc0} Kern fiasco [ 80002000, 8005efff] { 5d000} Kern fiasco [ 80090000, 800963c3] { 63c4} Sigma0 sigma0 [ 80098000, 8009e17b] { 617c} Sigma0 sigma0 [ 80140000, 8016ba6b] { 2ba6c} Root moe [ 80170000, 80186f0f] { 16f10} Root moe [ 81000000, 810133f7] { 133f8} Boot bootstrap [ 81009000, 810090a6] { a7} Boot mbi [ 8100d000, 8100d1df] { 1e0} Root Multiboot info [ 8101304c, 810130a3] { 58} Boot mbi [ 81100000, 8113357f] { 33580} Root Module API Version: (87) experimental Sigma0 config ip:80090100 sp:81012de4 Roottask config ip:801401a0 sp:00000000 Starting kernel fiasco at 800013b0 Regards, Michele Paolino

2 10

L4Linux + Ubuntu
by Sai Prajeeth 23 Apr '14

23 Apr '14

Hi, I want to replace the standard Linux kernel on my Ubuntu Distro (12.04LTS) with the L4Linux kernel. Is this possible? If yes can someone give me an outline as to how to proceed?

5 11

[Resend] Why 'FEC Ethernet Driver' is not found on L4Linux build menuconfig ?
by Taeung 23 Apr '14

23 Apr '14

Hi, adam Thank you for answering. :-) Sorry, I've asked you a question with misinformation. I've misunderstood that my Freescale imx6q_sabre_sd board's Ethernet is 'Qualcomm Atheros AR8031-AL1A Gigabit Ethernet'. My board's Ethernet Controller is contained in imx6 chip. And the driver for it is 'FEC Ethernet Driver'. So, I have to using ethernet driver which is 'l4linux/drivers/net/ethernet/ freescale'. But, I've failed configure 'CONFIG_FEC=y' because there is not 'FEC Ethernet Driver' on L4 linux's build menuconfig. But there are other ethernet drivers which are 'smsc','intel','marvell'... etc. Though there is 'FEC Ethernet Driver' source code in 'l4linux/drivers/net/ethernet/freescale', why 'FEC Ethernet Driver' is not found on L4Linux build menuconfig ? How to build FEC ethernet driver for my board? -Taeung- > I'm trying to secure Ethernet environment on L4 Linux. (using > Freescale imx6 > SABRE SD board) > > My board's Ethernet is 'Qualcomm Atheros AR8031-AL1A Gigabit Ethernet'. > > I've found source code for Ethernet Driver. > Folder name is '/l4linux/drivers/net/ethernet/atheros'. > > But, the folder only contain 'ATL1c' and 'ATL1e', 'ALX', 'ATLX'. > I guess 'atheros' driver in L4 Linux don't support my ethernet driver. L4Linux has the same drivers as native Linux, so if the driver is in Linux it is also in L4Linux (in the same version). There seems to be support for this type of network in the imx6 support code. So does the network work with the native Linux of the same version?

2 1

Why 'FEC Ethernet Driver' is not found on L4Linux build menuconfig ?
by Taeung 23 Apr '14

23 Apr '14

Hi, adam Thank you for answering. :-) Sorry, I've asked you a question with misinformation. I've misunderstood that my Freescale imx6q_sabre_sd board's Ethernet is 'Qualcomm Atheros AR8031-AL1A Gigabit Ethernet'. My board's Ethernet Controller is contained in imx6 chip. And the driver for it is 'FEC Ethernet Driver'. So, I have to using ethernet driver which is 'l4linux/drivers/net/ethernet/freescale'. But, I've failed configure 'CONFIG_FEC=y' because there is not 'FEC Ethernet Driver' on L4 linux's build menuconfig. But there are other ethernet drivers which are 'smsc','intel','marvell'... etc. Though there is 'FEC Ethernet Driver' source code in 'l4linux/drivers/net/ethernet/freescale', why 'FEC Ethernet Driver' is not found on L4Linux build menuconfig ? How to build FEC ethernet driver for my board? -Taeung- Message: 3 Date: Wed, 23 Apr 2014 00:17:20 +0200 From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> To: l4-hackers(a)os.inf.tu-dresden.de Subject: Re: Can not L4 linux support 'Atheros AR8031-AL1A' Ethernet Driver ? Message-ID: <20140422221720.GC6556(a)os.inf.tu-dresden.de> Content-Type: text/plain; charset=iso-8859-1 On Tue Apr 22, 2014 at 21:55:08 +0900, Taeung wrote: > I'm trying to secure Ethernet environment on L4 Linux. (using Freescale imx6 > SABRE SD board) > > My board's Ethernet is 'Qualcomm Atheros AR8031-AL1A Gigabit Ethernet'. > > I've found source code for Ethernet Driver. > Folder name is '/l4linux/drivers/net/ethernet/atheros'. > > But, the folder only contain 'ATL1c' and 'ATL1e', 'ALX', 'ATLX'. > I guess 'atheros' driver in L4 Linux don't support my ethernet driver. L4Linux has the same drivers as native Linux, so if the driver is in Linux it is also in L4Linux (in the same version). There seems to be support for this type of network in the imx6 support code. So does the network work with the native Linux of the same version? Adam

1 0

Can not L4 linux support 'Atheros AR8031-AL1A' Ethernet Driver ?
by Taeung 23 Apr '14

23 Apr '14

Hello, L4 Hackers :-) I'm trying to secure Ethernet environment on L4 Linux. (using Freescale imx6 SABRE SD board) My board's Ethernet is 'Qualcomm Atheros AR8031-AL1A Gigabit Ethernet'. I've found source code for Ethernet Driver. Folder name is '/l4linux/drivers/net/ethernet/atheros'. But, the folder only contain 'ATL1c' and 'ATL1e', 'ALX', 'ATLX'. I guess 'atheros' driver in L4 Linux don't support my ethernet driver. Is my guess right ? - Taeung -

2 1

Re: Re: How to secure Ethernet environment on L4 Linux ?
by Taeung 21 Apr '14

21 Apr '14

Hello, Adam and L4 Hackers. Thanks for answering. When I run 'ifconfig', nothing have happened. I guess that the cause is /etc folder in ramdisk is not enough to run 'init'. Would you mind if I ask you another question ? Must also I modify 'arm-rv.io' ? or must I modify 'l4lx_xs.cfg' ? or Do not I need do it ? If I have to modify them , how to modify ? (I'm using Freescale imx6q SABRE SD board.) If you give a bit me hints, I'd appreciate. I really want to secure Ethernet on L4 Linux... For reference. I'm using 'entry L4Linux_XS' as follows ======================== entry L4Linux_XS roottask moe rom/l4lx_xs.cfg module l4re module ned module l4lx_xs.cfg module io *module arm-rv.io* module vmlinuz.arm module ramdisk-arm.rd ======================== arm-rv.io in example folder is.. ======================== hw-root { NIC => new Device() { .hid = "smsc911x"; new-res Mmio(0x4e000000 .. 0x4e000fff); new-res Irq(60); } } l4lx => new System_bus() { NIC => wrap(hw-root.NIC); } ======================== l4lx_xs.cfg is .. ======================== -- vim:set ft=lua: local lxname = "vmlinuz"; if L4.Info.arch() == "arm" then lxname = "vmlinuz.arm"; end L4.default_loader:start( { caps = { log = L4.Env.log:m("rws"), }, l4re_dbg = L4.Dbg.Warn, log = { "l4linux", "yellow" }, }, "rom/" .. lxname .. " mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-" .. L4.Info.arch() .. ".rd root=1:0 ramdisk_size=4000 init=/bin/sh"); ======================== - Taeung - Message: 1 Date: Mon, 14 Apr 2014 23:48:27 +0200 From: Adam Lackorzynski<adam(a)os.inf.tu-dresden.de> To:l4-hackers@os.inf.tu-dresden.de Subject: Re: How to secure Ethernet environment on L4 Linux ? Message-ID:<20140414214826.GC6533(a)os.inf.tu-dresden.de> Content-Type: text/plain; charset=iso-8859-1 On Fri Apr 11, 2014 at 10:28:39 +0900, Taeung wrote: > After I succeeded putting other package in ramdisk, I'm trying to take > Ethernet on L4 Linux. > > When I built L4 Linux , I've configured '[*]Network support ' and > '[*]Network device driver support'. > I've copied 'etc' folder from other file system and put it in ramdisk. > And I've put somethings about Network in ramdisk. > > Manually I've mounted '/proc' and '/sys' and tried to run command 'if -a'. > But I've failed secure Ethernet environment on L4 Linux. > To put it concretely, I was not able to run command 'ifup -a' successfully. Does ifconfig show the proper network interface? Adam

2 3

How to change root device on L4 Linux ?
by Taeung 21 Apr '14

21 Apr '14

Hello, L4 hackers :-) I want to change *root device* on L4 Linux instead of ramdisk. Root device I want is like '*/dev/mtdblock0*' or '/dev/mmcblk1p1' instead of 'rom/ramdisk-arm.rd'. So, I've configured somethings in 'L4 Linux menuconfig', additionally. Somethings are as follows .. ============================== <*> MMC/SD/SDIO card support ---> <*> The Extended 4 (ext4) filesystem [*] Ext4 POSIX Access Control Lists [*] Ext4 Security Labels ============================== kernel command line : "rom/vmlinuz.arm console=ttyLv0 root=/dev/mtdblock0 rootwait rw " ============================== But it is hangs at '*Waiting for root device /dev/mtdblock0...*'. I've heard that the solution of this is to pass-through the physical MMC device to L4Linux. Please, tell me it's concrete ways or hints about what I must study for solving this. I can't even guess what the solution mean.. please. - Taeung - ============================== ... vmlinuz.| l4x: Checks passed. vmlinuz.| NetWinder Floating Point Emulator V0.97 (double precision) vmlinuz.| JFS: nTxBlock = 506, nTxLock = 4048 vmlinuz.| msgmni has been set to 126 vmlinuz.| io scheduler noop registered vmlinuz.| io scheduler deadline registered vmlinuz.| io scheduler cfq registered (default) vmlinuz.| L4 serial driver vmlinuz.| ttyLv0 at MMIO 0x1 (irq = 0, base_baud = 230400) is a L4 vmlinuz.| l4ser_shm: L4 shared mem serial driver vmlinuz.| l4cdds: No name given, not starting. vmlinuz.| brd: module loaded vmlinuz.| l4bdds: No name given, not starting. vmlinuz.| mousedev: PS/2 mouse device common for all mice vmlinuz.| TCP: cubic registered vmlinuz.| NET: Registered protocol family 17 *vmlinuz.| Waiting for root device /dev/mtdblock0...* ==============================

3 3

Compiling packages for L4 kernel & patches
by Asus Ceaser 17 Apr '14

17 Apr '14

If I were to use the Fiasco.OC kernel on my Gentoo box, all of my Linux applications will work appropriately without any special tinkering, is this correct. And would I also be able to get packages without having to specially compile them to run on L4. I used to think that if I only had Genode that I would have to specially compile packages, but now for some reason I am unsure. Also since L4 utilizes Linux, all of the Linux patches that are out there would still be able to work for Fiasco.OC, right?

2 1

1 maximal supported CPUs
by Irvanda Kurniadi 16 Apr '14

16 Apr '14

Hi Hackers, I was trying to run ex_thread_migrate in my system. I use 8 active processor. I did config the fiasco to support the multi processor to 8 Maximal supported number of CPUs. Then I ran the thread_migrate example program. After I ran the program, there was only 1 maximal supported CPUs. I even tried to add the -smp 8 while using qemu. But, there wasn't any difference. Please let me know how to fix this. Thanks, Irvanda

2 3

How to secure Ethernet environment on L4 Linux ?
by Taeung 14 Apr '14

14 Apr '14

Hello, l4hackers After I succeeded putting other package in ramdisk, I'm trying to take Ethernet on L4 Linux. When I built L4 Linux , I've configured '[*]Network support ' and '[*]Network device driver support'. I've copied 'etc' folder from other file system and put it in ramdisk. And I've put somethings about Network in ramdisk. Manually I've mounted '/proc' and '/sys' and tried to run command 'if -a'. But I've failed secure Ethernet environment on L4 Linux. To put it concretely, I was not able to run command 'ifup -a' successfully. Please , Help me Even if you tell a bit hints to me, I thank you.

2 1

Ankh Examples
by Ayad Mostafa 09 Apr '14

09 Apr '14

hello l4 hackers, i'm experimenting with ankh and so far failed to successfully ping morpork from my host machine. it seems that receive() blocks at wait_for_data() indefinitely. i can see irq activity on displayed on screen but wait_for_data() does not unblock. i appreciate any help or ideas... software version: l4re revision r63 (2014-02-28) gcc version 4.8.2 qemu version 1.7.0 qemu command: qemu -cpu core2duo -m 128 -cdrom ./morpork.iso \ -net nic,vlan=0,macaddr=00:e0:4c:c6:45:f4,model=rtl8139 -net tap,vlan=0,ifname=tap0 -serial stdio ping command: arping -i tap0 00:E0:4C:C6:45:F4 output: [32mankh | Initialized DDELinux 2.6 [0m [32mankh | <6>net_namespace: 636 bytes [0m [32mankh | Initializing DDE page cache [0m [32mankh | ddekit_pci_init [0m [32mankh | pci bus constructor [0m [32mankh | PCI: L4 root bridge is device 31ca0 [0m [32mankh | pci_irq_enable: [36mdev 0x118004 [0m [0m [32mankh | pci_irq_enable: [36mirq 11, pin 1, devfn 0 [0m [0m [32mankh | ddekit_pci_irq_enable: [32;1mdevfn 0, pin 0 [0m [0m [32mankh | ddekit_pci_irq_enable: [32;1ml4vbus_pci_irq_enable() = 11 [0m [0m [32mankh | IRQ: set irq type of 11 to 4 [0m [32mankh | l4dde26_register_rx_callback: [36mNew rx callback @ 0x1000200. [0m [0m [32mankh | Softirq daemon starting [0m [32mankh | init_wq_head [0m [32mankh | <6>8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004) [0m [32mankh | pci_irq_enable: [36mdev 0x118004 [0m [0m [32mankh | pci_irq_enable: [36mirq 11, pin 1, devfn 0 [0m [0m [32mankh | ddekit_pci_irq_enable: [32;1mdevfn 0, pin 0 [0m [0m [32mankh | ddekit_pci_irq_enable: [32;1ml4vbus_pci_irq_enable() = 11 [0m [0m [32mankh | IRQ: set irq type of 11 to 4 [0m [32mankh | enable_dev: 0 [0m [32mankh | <6>eth0: RTL-8139C+ at 0x109000, 0x11615cM, IRQ 11 [0m [32mankh | unimplemented: pci_set_master [0m [32mankh | <6>pcnet32.c:v1.35 21.Apr.2008 tsbogend(a)alpha.franken.de [0m [32mankh | <6>Intel(R) PRO/1000 Network Driver - version 7.3.21-k3-NAPI [0m [32mankh | <6>Copyright (c) 1999-2006 Intel Corporation. [0m [32mankh | open_network_devices() [0m [32mankh | opening lo [0m [32mankh | <6>device lo entered promiscuous mode [0m [32mankh | set interface to promiscuous mode. [0m [32mankh | opening eth0 [0m [32mankh | <6>device eth0 entered promiscuous mode [0m [32mankh | set interface to promiscuous mode. [0m [32mankh | Thread 0x85 for IRQ 11 [0m [32mankh | <6>eth0: link up, 100Mbps, full-duplex, lpa 0x05E1 [0m [32mankh | Opened 2 network devices. [0m [32mankh | lo IRQ: 0x00 MAC: 00:00:00:00:00:00 MTU: 16436 [0m [32mankh | eth0 IRQ: 0x0B MAC: 00:E0:4C:C6:45:F4 MTU: 1500 [0m [32mankh | Registered @ registry. [0m [32mankh | Gooood Morning Ankh-Morpoooooork! TID = 0x5a [0m [32mankh | Creating session factory. [0m [32mankh | Configuration: debug,promisc,device=eth0,shm=shm_morpork,bufsize=16384,phys_mac [0m [32mankh | Debug mode ON. [0m [32mankh | Using promiscuous mode. [0m [32mankh | Device 'eth0' requested. [0m [32mankh | SHM area 'shm_morpork' requested. [0m [32mankh | Buffer size: 16384 [0m [32mankh | Physical MAC requested. [0m [32mankh | shmc_create: 0 [0m [32mankh | Created shmc area 'shm_morpork' [0m [32mankh | Assigning MAC address: 00:E0:4C:C6:45:F4 [0m [36mmorpork | Using shm area: 'shm_morpork' [0m [36mmorpork | argv[2] = '16384' [0m [36mmorpork | My TID = 0x93 [0m [36mmorpork | Attached shm area 'shm_morpork': 0 [0m [36mmorpork | add_chunk: area 0x10555c0, name 'tx_ring', size 16420 [0m [36mmorpork | SND: signal RX 9b, TX 9c [0m [36mmorpork | buf @ 0x301c, area 0x10555c0 (shm_morpork), size 16420 [0m [36mmorpork | owner 0, name tx_ring, signal tx_signal [0m [36mmorpork | head @ 0x103030, lock state 'unlocked', data size 16384 [0m [36mmorpork | next_rd 0 next_wr 0 filled 0, data @ 0x103051 [0m [36mmorpork | add_chunk: area 0x10555c0, name 'rx_ring', size 16420 [0m [36mmorpork | SND: signal RX 9d, TX 9e [0m [36mmorpork | buf @ 0x3074, area 0x10555c0 (shm_morpork), size 16420 [0m [36mmorpork | owner 0, name rx_ring, signal rx_signal [0m [36mmorpork | head @ 0x10707c, lock state 'unlocked', data size 16384 [0m [36mmorpork | next_rd 0 next_wr 0 filled 0, data @ 0x10709d [0m [36mmorpork | SEND RB @ 0x3018 RECV RB @ 0x3070 INFO @ 0x30c8 [0m [32mankh | l4shmc_attach("shm_morpork") = 0 [0m [32mankh | Shm_chunk::get(0xcf98, "info", 36) [0m [32mankh | ... = 0xcec8 [0m [32mankh | RCV: signal RX 9d, TX 9e [0m [32mankh | RCV: buf size 16420 [0m [32mankh | buf @ 0xcd3c, area 0xcf98 (shm_morpork), size 16420 [0m [32mankh | owner 0, name rx_ring, signal rx_signal [0m [32mankh | head @ 0x16c07c, lock state 'unlocked', data size 16384 [0m [32mankh | next_rd 0 next_wr 0 filled 0, data @ 0x16c09d [0m [32mankh | SND: attaching to signal 9e (443000) [0m [32mankh | buf @ 0x16c07c [0m [36mmorpork | activated Ankh connection. [0m [32mankh | xmit thread started, data @ 0xcf38, TID: 0xa0 [0m [32mankh | RCV: signal RX 9b, TX 9c [0m [32mankh | RCV: buf size 16420 [0m [32mankh | buf @ 0xcf04, area 0xcf98 (shm_morpork), size 16420 [0m [32mankh | owner ffffffff, name tx_ring, signal tx_signal [0m [32mankh | head @ 0x168030, lock state 'unlocked', data size 16384 [0m [32mankh | next_rd 0 next_wr 0 filled 0, data @ 0x168051 [0m [32mankh | RCV: attaching to signal 9b (448000) [0m [32mankh | 16384 ... 16384 [0m [36mmorpork | RCV: signal RX 9b, TX 9c [0m [36mmorpork | RCV: buf size 16420 [0m [36mmorpork | buf @ 0x3114, area 0x10555c0 (shm_morpork), size 16420 [0m [36mmorpork | owner 0, name tx_ring, signal tx_signal [0m [36mmorpork | head @ 0x103030, lock state 'unlocked', data size 16384 [0m [36mmorpork | next_rd 0 next_wr 0 filled 0, data @ 0x103051 [0m [36mmorpork | SND: attaching to signal 9c (41c000) [0m [36mmorpork | buf @ 0x103030 [0m [36mmorpork | sender: 0x3100 [0m [36mmorpork | RCV: signal RX 9d, TX 9e [0m [36mmorpork | RCV: buf size 16420 [0m [36mmorpork | buf @ 0x317c, area 0x10555c0 (shm_morpork), size 16420 [0m [36mmorpork | owner 0, name rx_ring, signal rx_signal [0m [36mmorpork | head @ 0x10707c, lock state 'unlocked', data size 16384 [0m [36mmorpork | next_rd 0 next_wr 0 filled 0, data @ 0x10709d [0m [36mmorpork | RCV: attaching to signal 9d (41e000) [0m [36mmorpork | receiver: 0x3168 [0m [36mmorpork | Got assigned MAC: 00:E0:4C:C6:45:F4 [0m [36mmorpork | info @ 0x10b0c8 [0m [36mmorpork | 00:E0:4C:C6:45:F4 MTU 1500 [0m [36mmorpork | RX packets: 0 dropped: 0 [0m [36mmorpork | TX packets: 0 dropped: 0 [0m [36mmorpork | RX bytes: 0 TX bytes: 0 [0m [36mmorpork | recv->wait_for_data(); [0m kind regards, ayad

3 8

Ankh Examples
by Ayad Mostafa 08 Apr '14

08 Apr '14

Hi, i also tried it using qemu development branch(version v2.0-rc0), but it is still not working. best regards ayad

1 0

newbie - trying to build
by Jack Andrews 06 Apr '14

06 Apr '14

Hi, Sorry if this is not the right forum. I'm following https://os.inf.tu-dresden.de/fiasco/build.html and i could build fiasco just fine. I made a couple of guesses about how to build L4Re because I couldn't find much info: jack@uv:~/fiasco/src/l4$ mkdir mybuild jack@uv:~/fiasco/src/l4$ make grub2iso E=hello O=mybuild MODULE_SEARCH_PATH=~/fiasco/src/kernel/fiasco/mybuild/ Processing entry 'hello' Could not find 'bootstrap' with path '/home/jack/fiasco/src/kernel/fiasco/mybuild/:/home/jack/fiasco/src/l4/mybuild/bin/amd64_opteron:/home/jack/fiasco/src/l4/mybuild/bin/amd64_opteron/l4f:/home/jack/fiasco/src/l4/mybuild/lib/amd64_opteron:/home/jack/fiasco/src/l4/mybuild/lib/amd64_opteron/l4f' make: *** [grub2iso] Error 1 I find bootstrap.o, but no 'bootstrap': jack@uv:~/fiasco/src/l4$ find ../kernel/fiasco/mybuild/ -name bootstrap\* ../kernel/fiasco/mybuild/bootstrap.o I have googled, including this list, but I haven't found the magic combination of words to get the answer. Thanks, jack. This is the kernel globalconfig.out: # # Automatically generated file; DO NOT EDIT. # Fiasco configuration # # # Target configuration # # CONFIG_IA32 is not set CONFIG_AMD64=y # CONFIG_ARM is not set CONFIG_PF_PC=y CONFIG_ABI_VF=y CONFIG_AMD64_K8=y # CONFIG_AMD64_CORE2 is not set # CONFIG_AMD64_ATOM is not set # CONFIG_AMD64_K10 is not set # CONFIG_CPU_VIRT is not set CONFIG_SCHED_APIC=y # CONFIG_WORKAROUND_AMD_FPU_LEAK is not set # # Kernel options # CONFIG_MP=y CONFIG_MP_MAX_CPUS=4 CONFIG_CONTEXT_4K=y # CONFIG_FINE_GRAINED_CPUTIME is not set CONFIG_SCHED_FIXED_PRIO=y # CONFIG_SCHED_WFQ is not set # CONFIG_SCHED_FP_WFQ is not set # CONFIG_DISABLE_VIRT_OBJ_SPACE is not set CONFIG_VIRT_OBJ_SPACE=y # # Debugging # # CONFIG_INLINE is not set CONFIG_NDEBUG=y CONFIG_NO_FRAME_PTR=y # CONFIG_STACK_DEPTH is not set # CONFIG_LIST_ALLOC_SANITY is not set # CONFIG_BEFORE_IRET_SANITY is not set # CONFIG_IRQ_SPINNER is not set # CONFIG_WATCHDOG is not set # CONFIG_SERIAL is not set # CONFIG_JDB is not set # CONFIG_POWERSAVE_GETCHAR is not set # CONFIG_WARN_NONE is not set CONFIG_WARN_WARNING=y # CONFIG_WARN_ANY is not set # # Compiling # CONFIG_CC="gcc" CONFIG_CXX="g++" CONFIG_HOST_CC="gcc" CONFIG_HOST_CXX="g++" # CONFIG_MAINTAINER_MODE is not set CONFIG_LABEL="" CONFIG_EXPERIMENTAL=y CONFIG_BIT64=y CONFIG_WARN_LEVEL=1 CONFIG_XARCH="amd64" CONFIG_IA32_TARGET="AMD Opteron" CONFIG_ABI="vf"

4 5

std::cin in Fiasco/L4Re (with 'make qemu')
by Emanuel Berg 03 Apr '14

03 Apr '14

How do I use std::cin in Fiasco/L4Re? The software compiles and links fine, only during execution (with 'make qemu'), this crashes it: Global_Scheduler::Global_Scheduler (bool read_from_file) : period_left(0), number_of_schedulers(0) { if (not read_from_file) { std::cout << "Global scheduler period: "; std::cin >> period; // ... There is no error, but there is no halt to execution (to wait for input), and the value "read" (to period) is inconsistent. -- underground experts united: http://user.it.uu.se/~embe8573

3 8

step forward on compilation
by Emanuel Berg 03 Apr '14

03 Apr '14

First: On - let's see - Fri, 28 Mar 2014 02:02:52 +0100 - I sent a message to this list with the subject "again, must know mechanics of compile" - previously, I was able to send to this list, but as for now, I can't find that message either in the group or in the web archive [1]. (I see my old posts though.) I looked for that message because I thought I build on that thread, that's how I noticed it wasn't there (?). Anyway, as for including header files, I found that you can indeed make a directory at the base package level, called "include" - and put a Makefile in it just like it is done for the other projects (but I'm unsure what the Makefile actually does - perhaps if you specify the include directory as a target in the *package* Makefile, you can drop it?). And, you can't use the C++ ".hh" extension, but ".h" works, if you include them like this: #include <l4/hs/task_scheduler.h> if your package is named "hs". In effect, this is quite the opposite of the #include "task_scheduler.hh", and then the -I flag to the compiler. As for -std=c++11, I found that you can pass that not with CFLAGS, but close - this works: CXXFLAGS += -std=c++11 [1] http://os.inf.tu-dresden.de/pipermail/l4-hackers/2014/thread.html -- underground experts united: http://user.it.uu.se/~embe8573

4 9

[Correction] Can't Fiasco.OC support multi-core-processor ?
by Taeung 03 Apr '14

03 Apr '14

Hello , L4 hackers I'm so sorry.. I amend my a question. Question 'Can't Fiasco.OC support multi-core-processor ?' is wrong.. Again, I've checked my thread and I've tested it. It's problem is about ramdisk or 'dd' command. I guess data in SD-card is some wrong. - Taeung -

1 0

Can't Fiasco.OC support multi-core-processor ?
by Taeung 03 Apr '14

03 Apr '14

Hello, L4 hackers :-) Always, I'm obliged to you. I have a question. When I configured Fiasco.OC containing option which is 'unable multi processor support' , I've succeeded booting (L4 linux + L4/Fiasco) on Freescale imx6q_sabre_sd(Cortex-a9). And, I've configured Fiasco.OC as follows.. , again. ========================= [*] Enable multi processor support (4) Maximal supported number of CPUs (NEW) [*] Fine-grained CPU time ========================= But I could not booting it successfully. It's stop at '*CPU[3]: goes to idle loop*' What's the problem ? Log I met is such as.... ========================= Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: r62 compiled with gcc 4.6.4 for i.MX6 [] Build: #1 Thu Apr 3 13:48:45 KST 2014 Per_cpu_data_alloc: (orig: 0xf0056af8-0xf0057488) Allocate 2448 bytes (2KB) for CPU[4] local storage (offset=1193508, 0xf11ea000-0xf11ea990) Number of CPUs: 4 Calibrating timer loop... Per_cpu_data_alloc: (orig: 0xf0056af8-0xf0057488) done. Allocate 2448 bytes (2KB) for CPU[1] local storage (offset=1195508, 0xf11ec000-0xf11ec990) MDB: use page size: 20 Cache config: ON ... (ellipsis) MOE: Hello world Per_cpu_data_alloc: (orig: 0xf0056af8-0xf0057488) CPU[1]: goes to idle loop Allocate 2448 bytes (2KB) for CPU[2] local storage (offset=1182508, 0xf11d9000-0xf11d9990) ... (ellipsis) BOOTFS: [11210000Per_cpu_data_alloc: (orig: 0xf0056af8-0xf0057488) -CPU[2]: goes to idle loop 1Allocate 2448 bytes (2KB) for CPU[3] local storage (offset=1158508, 0xf11af000-0xf11af990) 1Cache config: ON 5ID_PFR[01]: 00001231 000000115 ID_[DA]FR0: 00010444 00000000 1ID_MMFR[04]: 00100103 20000000 01230000 00102111 494] [C:508000] vmlinuz.arm BOOTFS: [11552000-11852000] [C:509000] ramdisk-arm.rd MOE: cmdline: moe rom/l4lx_xs.cfg MOE: Starting: rom/ned rom/l4lx_xs.cfg MOE: loading 'rom/ned' Ned says: Hi World! L4Re: unhandled exception: pc=0x10211d4 *CPU[3]: goes to idle loop* ========================= - Taeung -

1 0

Custom ramdisk
by Tim Komarov 01 Apr '14

01 Apr '14

Hello, L4 hackers! I use Pandaboard for my practising with Fiasco.OC and L4Linux. 1) I got a problem with booting L4Linux with my own ramdisk. When I use 18 mb ramdisk, I got the following error: reading image.elf 24691072 bytes read ## Starting application at 0x81000000 ... ... ,,,[Everything is usual] ,,, NET: Registered protocol family 17 List of all partitions: No filesystem could mount root, tried: ext3 ext2 ext4 cramfs Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) CPU: 0 PID: 1 Comm: swapper Not tainted 3.13.0-l4 #1 [<0200c624>] (unwind_backtrace+0x0/0xec) from [<020054c0>] (show_stack+0x10/0x14) [<020054c0>] (show_stack+0x10/0x14) from [<0222e63c>] (panic+0x7c/0x1b8) [<0222e63c>] (panic+0x7c/0x1b8) from [<022f2c40>] (mount_block_root+0x25c/0x29c) [<022f2c40>] (mount_block_root+0x25c/0x29c) from [<022f2f44>] (prepare_namespace+0x160/0) [<022f2f44>] (prepare_namespace+0x160/0x1b4) from [<022f2894>] (kernel_init_freeable+0x1) [<022f2894>] (kernel_init_freeable+0x174/0x1b8) from [<0222ccf0>] (kernel_init+0x8/0x118) [<0222ccf0>] (kernel_init+0x8/0x118) from [<020077d4>] (ret_from_fork+0x14/0x20) [<020077d4>] (ret_from_fork+0x14/0x20) from [<00000000>] ( (null)) panic: going to sleep forever, bye To make ramdisk I simply create a file, write 18 Mb of zeroes to it (with dd), create in that file ext2 partition and copy there files from ramdisk-arm.rd So, what should I do to get a proper working ramdisk? 2) Even more. If I create 20 mb ramdisk, I got this: reading image.elf 26788224 bytes read ## Starting application at 0x00000000 ... Than the booting hangs. Why so? Looking forward for your help, guys! Best wishes, Tim

2 3

I share attached this guide with you.
by Taeung 28 Mar '14

28 Mar '14

Hello, l4 hackers :-) !! I've promised a guide Document to you. It is "L4 / Fiasco porting guide on Freescale i.MX6 Quad SABRE SD(ARMv7)". I have had help from L4 Hackers. So, I was able to do booting "L4 Linux + L4/Fiasco.OC" on this board. I'm particularly grateful to /Tim Komarov /and /Ademd Ammar/ , /Adam Lackorzynski/, /Matthias Lange/. I don't know how much this document will help some beginner. I've thought that the guide Document might help them. But I share this document because I have had a big help from them. It is small but I am delighted to be able to contribute this open source community. :-) If it's contents is wrong , let me know your feedback. - Taeung -

3 2