Hi all,
I trying to launch L4Linux over Fiasco.OC+L4RE but here is my serial output:
INITRD: Freeing memory. l4x: Checks passed. NetWinder Floating Point Emulator V0.97 (double precision) msgmni has been set to 126 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) L4 serial driver ttyLv0 at MMIO 0x1 (irq = 211) is a L4 l4ser_shm: L4 shared mem serial driver l4cdds: No name given, not starting. brd: module loaded l4bdds: No name given, not starting. mousedev: PS/2 mouse device common for all mice TCP: cubic registered NET: Registered protocol family 17 RAMDISK: ext2 filesystem found at block 0 RAMDISK: Loading 3072KiB [1 disk] into ram disk... done. VFS: Mounted root (ext2 filesystem) readonly on device 1:0. Freeing init memory: 112K /bin/sh: can't access tty; job control turned off # io | Dev_factory: register factory for N2Hw6DeviceE io | GTF: register factory for 7Pci_dev io | GTF: register factory for N2Hw12Msi_resourceE io | Dev_factory: register factory for N2Hw11Gpio_deviceE io | Io service io | Ready. Waiting for request.
[ ...Launching µC/OS-II part... ]
So all I got from L4Linux is "/bin/sh: can't access tty; job control turned off"
What does that mean ? I also have to say that I use the ramdisk.rd from the official website (http://os.inf.tu-dresden.de/L4/LinuxOnL4/download/drops-rd.rd), is this correct ?
This is the content of my modules.list file:
modaddr 0x1100000
entry l4LinuxUcos kernel fiasco -serial_esc roottask moe rom/l4lx_ucos.cfg module l4re module ned module io module l4lx_ucos.cfg module vmlinuz.arm module ramdisk-arm.rd module l4ucos module beagle.devs module beagle.io
And here is my l4lx configuration file:
loader:start( { caps = { log = L4.Env.log:m("rws"), calc_server = calc_server, }, l4re_dbg = L4.Dbg.Warn, log = { "l4linux", "yellow" }, mem = L4.Env.mem_alloc:create(L4.Proto.Factory, 100*1024*1024):m("rws"), scheduler = L4.Env.user_factory:create(L4.Proto.Scheduler, 0x80, 0x70) }, "rom/" .. lxname .. " mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-" .. L4.Info.arch() .. ".rd root=1:0 ramdisk_size=17000 init=/bin/sh earlyprintk=1");
Thanks in advance,
On Wed Jul 17, 2013 at 10:41:52 +0200, Maximin Coste wrote:
I trying to launch L4Linux over Fiasco.OC+L4RE but here is my serial output:
INITRD: Freeing memory. l4x: Checks passed. NetWinder Floating Point Emulator V0.97 (double precision) msgmni has been set to 126 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) L4 serial driver ttyLv0 at MMIO 0x1 (irq = 211) is a L4 l4ser_shm: L4 shared mem serial driver l4cdds: No name given, not starting. brd: module loaded l4bdds: No name given, not starting. mousedev: PS/2 mouse device common for all mice TCP: cubic registered NET: Registered protocol family 17 RAMDISK: ext2 filesystem found at block 0 RAMDISK: Loading 3072KiB [1 disk] into ram disk... done. VFS: Mounted root (ext2 filesystem) readonly on device 1:0. Freeing init memory: 112K /bin/sh: can't access tty; job control turned off # io | Dev_factory: register factory for N2Hw6DeviceE io | GTF: register factory for 7Pci_dev io | GTF: register factory for N2Hw12Msi_resourceE io | Dev_factory: register factory for N2Hw11Gpio_deviceE io | Io service io | Ready. Waiting for request.
[ ...Launching µC/OS-II part... ]
So all I got from L4Linux is "/bin/sh: can't access tty; job control turned off"
Actually it looks pretty good, the prompt is there, ready to receive input. The message from sh is normal, nothing to worry about.
What does that mean ? I also have to say that I use the ramdisk.rd from the official website (http://os.inf.tu-dresden.de/L4/LinuxOnL4/download/drops-rd.rd), is this correct ?
That's fine.
And here is my l4lx configuration file:
loader:start( { caps = { log = L4.Env.log:m("rws"), calc_server = calc_server, }, l4re_dbg = L4.Dbg.Warn, log = { "l4linux", "yellow" }, mem = L4.Env.mem_alloc:create(L4.Proto.Factory, 100*1024*1024):m("rws"), scheduler = L4.Env.user_factory:create(L4.Proto.Scheduler, 0x80, 0x70) }, "rom/" .. lxname .. " mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-" .. L4.Info.arch() .. ".rd root=1:0 ramdisk_size=17000 init=/bin/sh earlyprintk=1");
Just use the 'log' outside of caps and make that 'log = L4.Env.log', then the input in L4Linux should work.
Adam
2013/7/18 Adam Lackorzynski adam@os.inf.tu-dresden.de:
Actually it looks pretty good, the prompt is there, ready to receive input. The message from sh is normal, nothing to worry about.
Good to hear !
What does that mean ? I also have to say that I use the ramdisk.rd from the official website (http://os.inf.tu-dresden.de/L4/LinuxOnL4/download/drops-rd.rd), is this correct ?
Just use the 'log' outside of caps and make that 'log = L4.Env.log', then the input in L4Linux should work.
Now it complains about /bin/sh missing as init argument. Does TUDO ramdisk doesn't provide an /bin/sh interpretor ? Do I have to use solutions like BusyBox ?
Thanks for all the help,
On Mon Jul 22, 2013 at 15:10:34 +0200, Maximin Coste wrote:
2013/7/18 Adam Lackorzynski adam@os.inf.tu-dresden.de:
What does that mean ? I also have to say that I use the ramdisk.rd from the official website (http://os.inf.tu-dresden.de/L4/LinuxOnL4/download/drops-rd.rd), is this correct ?
Just use the 'log' outside of caps and make that 'log = L4.Env.log', then the input in L4Linux should work.
Now it complains about /bin/sh missing as init argument. Does TUDO ramdisk doesn't provide an /bin/sh interpretor ? Do I have to use solutions like BusyBox ?
Principally you can take whatever ramdisk you like to use. Concerning the provided ramdisk, it contains a busybox and also a proper /bin/sh link/binary. I'm not sure what's the difference to your previous run. Maybe you could copy the relevant output here to have a look.
Adam
2013/7/22 Adam Lackorzynski adam@os.inf.tu-dresden.de:
Principally you can take whatever ramdisk you like to use. Concerning the provided ramdisk, it contains a busybox and also a proper /bin/sh link/binary. I'm not sure what's the difference to your previous run. Maybe you could copy the relevant output here to have a look.
Here is my output:
l4linux | RAMDISK: ext2 filesystem found at block 0 l4linux | RAMDISK: Loading 16384KiB [1 disk] into ram disk... done. l4linux | VFS: Mounted root (ext2 filesystem) readonly on device 1:0. l4linux | Freeing init memory: 112K l4linux | request_module: runaway loop modprobe binfmt-464c l4linux | Failed to execute /bin/sh. Attempting defaults... l4linux | request_module: runaway loop modprobe binfmt-464c l4linux | request_module: runaway loop modprobe binfmt-464c l4linux | Kernel panic - not syncing: No init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance. l4linux | [<0100b3f0>] (unwind_backtrace+0x0/0xf0) from [<011d38ec>] (panic+0x7c/0x1c4) l4linux | [<011d38ec>] (panic+0x7c/0x1c4) from [<011d1d98>] (kernel_init+0xc0/0xe8) l4linux | [<011d1d98>] (kernel_init+0xc0/0xe8) from [<010067d4>] (ret_from_fork+0x14/0x20) l4linux | [<010067d4>] (ret_from_fork+0x14/0x20) from [<00000000>] ( (null)) l4linux | panic: going to sleep forever, bye l4linux | panic: going to sleep forever, bye io | Dev_factory: register factory for N2Hw6DeviceE etc.
On Thu Jul 25, 2013 at 14:52:49 +0200, Maximin Coste wrote:
2013/7/22 Adam Lackorzynski adam@os.inf.tu-dresden.de:
Principally you can take whatever ramdisk you like to use. Concerning the provided ramdisk, it contains a busybox and also a proper /bin/sh link/binary. I'm not sure what's the difference to your previous run. Maybe you could copy the relevant output here to have a look.
Here is my output:
l4linux | RAMDISK: ext2 filesystem found at block 0 l4linux | RAMDISK: Loading 16384KiB [1 disk] into ram disk... done. l4linux | VFS: Mounted root (ext2 filesystem) readonly on device 1:0. l4linux | Freeing init memory: 112K l4linux | request_module: runaway loop modprobe binfmt-464c l4linux | Failed to execute /bin/sh. Attempting defaults... l4linux | request_module: runaway loop modprobe binfmt-464c l4linux | request_module: runaway loop modprobe binfmt-464c l4linux | Kernel panic - not syncing: No init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
That binfmt-464c error typically happens when the Linux cannot execute init/sh for some reason. Is it maybe a different ramdisk or so?
Adam
2013/7/25 Adam Lackorzynski adam@os.inf.tu-dresden.de:
That binfmt-464c error typically happens when the Linux cannot execute init/sh for some reason. Is it maybe a different ramdisk or so?
It's the TUDOS ramdisk from the official website.
On Thu Jul 25, 2013 at 23:55:57 +0200, Maximin Coste wrote:
2013/7/25 Adam Lackorzynski adam@os.inf.tu-dresden.de:
That binfmt-464c error typically happens when the Linux cannot execute init/sh for some reason. Is it maybe a different ramdisk or so?
It's the TUDOS ramdisk from the official website.
You're on ARM right? drops-rd.rd is x86 if you used that one. Better use that one: http://os.inf.tu-dresden.de/download/ramdisk-arm.rd
Adam
2013/7/28 Adam Lackorzynski adam@os.inf.tu-dresden.de:
You're on ARM right? drops-rd.rd is x86 if you used that one. Better use that one: http://os.inf.tu-dresden.de/download/ramdisk-arm.rd
It's the one I use. I tried one more time, same error ouput.
On Sun Jul 28, 2013 at 03:59:58 +0200, Maximin Coste wrote:
2013/7/28 Adam Lackorzynski adam@os.inf.tu-dresden.de:
You're on ARM right? drops-rd.rd is x86 if you used that one. Better use that one: http://os.inf.tu-dresden.de/download/ramdisk-arm.rd
It's the one I use. I tried one more time, same error ouput.
Hmm, could you post your L4Linux .config?
Adam
l4-hackers@os.inf.tu-dresden.de