Hi,
Thank you for your answer Adam.
Nothing happens when I press ESC. I also tried to send ESC with the QEMU monitor using "sendkey esc" which has also no effect.
Same thing with the Hello World.
I really don't know what could cause this problem but I think it may have something to do with capabilities (just a guess).
I have to say that my QEMU works fine, I tested it with another Linux. My .dtb is good too.
Do you have any ideas or suggestions ?
I was also wondering about the "libio: Warning: Query of 'vbus' failed!" during the boot of L4Linux. I don't think it is a problem (due to the fact that I'm not using any IPC) but I'm not sure.
Thank you for all the help,
Louis.
-----------------------------------------------------------------
I am actually trying to launch L4Linux on Fiasco.OC+L4RE on Xilinx Zynq using QEMU but I get an error at the end of the boot of L4Linux :
*/bin/sh: can't access tty; job control turned off*
This is a standard message when launching the shell with init=/bin/sh, it's not L4Linux specific.
*/ #*
Even if I have a shell prompt I can?t type anything, that?s why I am sending this email.
Does pressing ESC get you into Fiasco's jdb?
Otherwise the configs do not show me anything obvious wrong right now.
I am aware that my problem is very similar to this one http://os.inf.tu-dresden.de/pipermail/l4-hackers/2013/005920.html but I tried every solution you suggested.
I am working under *Ubuntu 64bits 14.04* and I am compiling with *arm-linux-gnueabi-gcc 4.7.3*.
To emulate the *Xilinx Zynq*, I?m using *QEMU emulator version 2.0.50* configured this way :
*./configure --target-list="arm-softmmu,microblazeel-softmmu" --enable-fdt --disable-kvm*
To launch QEMU, here is my command line :
*qemu-system-arm -M arm-generic-fdt -dtb ~/Documents/zynq-zc706.dtb
-kernel
~/Documents/gitL4/l4-hypervisor/build/l4/images/bootstrap.elf -serial mon:stdio*
Zynq is ARM so I?m using this ramdisk : http://os.inf.tu-dresden.de/download/ramdisk-arm.rd
Hi,
On Tue Feb 10, 2015 at 17:02:49 +0100, Piwe li wrote:
Nothing happens when I press ESC. I also tried to send ESC with the QEMU monitor using "sendkey esc" which has also no effect.
Same thing with the Hello World.
I really don't know what could cause this problem but I think it may have something to do with capabilities (just a guess).
I have to say that my QEMU works fine, I tested it with another Linux. My .dtb is good too.
Do you have any ideas or suggestions ?
Does fiasco have the -serial_esc argument in the modules.list file?
I was also wondering about the "libio: Warning: Query of 'vbus' failed!" during the boot of L4Linux. I don't think it is a problem (due to the fact that I'm not using any IPC) but I'm not sure.
Indeed, this has nothing to do with ESC.
Adam
Hi,
Does fiasco have the -serial_esc argument in the modules.list file?
Yes, it has. Here is my modules.list :
modaddr 0x01100000
default-kernel fiasco -serial_esc default-bootstrap bootstrap
entry L4Linux ARM roottask moe rom/l4lx.cfg module l4re module ned module l4lx.cfg module io module arm-rv.io module vmlinuz.arm module ramdisk-arm.rd
In fact, I can't type anything in my L4Linux. That's why I was thinking it may have something to do with capabilities but I think my l4lx.cfg is fine :
-- 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");
Indeed, this has nothing to do with ESC.
Adam
Thanks a lot for your help,
Louis.
On Tue Feb 10, 2015 at 23:52:53 +0100, Piweli wrote:
Hi,
Does fiasco have the -serial_esc argument in the modules.list file?
Yes, it has. Here is my modules.list :
Ok. Is that Qemu or real hardware? If real hardware, tried switching off hardware flow control in your terminal program?
Adam
On Wed Feb 11, 2015 at 00:17:33 +0100, Piweli wrote:
Le 11/02/2015 00:12, Adam Lackorzynski a écrit :
Ok. Is that Qemu or real hardware? If real hardware, tried switching off
It's QEMU
Ok, with zynq as the platform. Could you try some of the more standard platforms, such as vexpress-a9 for example and check whether those work?
Adam
l4-hackers@os.inf.tu-dresden.de