Launch of L4Linux

[Adam Lackorzynski]

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
-- 
Adam                 adam at os.inf.tu-dresden.de
  Lackorzynski         http://os.inf.tu-dresden.de/~adam/