About build of L4Linux

[Adam Lackorzynski]

On Sat Jul 21, 2007 at 11:28:37 +0900, Lin wrote:
> > > I'm using serial console(ttyLv0) now, and see the same messages as tty1.
> > > In this case, should I see login-prompt on serial console too ?
> >
> > No.
> >
> > On Linux (and most Unices) there's a file called /etc/inittab which
> > tells /sbin/init what to do. There are entries which define how the
> > getties are started. The getties are those programs that give you the
> > prompt. They have an argument that specifies the console they work on.
> > The inittab in the ramdisk defines tty1, tty2, tty3, tty4, tty5 and tty6
> > for the getties. If you want to have the prompt on ttyLv0, you need to
> > modify the /etc/inittab on the ramdisk accordingly.
> >
> > > I have not gotten any prompts until now.
> > > My current settings is ...
> > >
> > >   [L4Linux Configuration]
> > >     Using given .config.
> > >     (L4Linux DOpE                     - disable)
> > >     (L4Linux serial console support   - enable )
> > >     (Linux   keyboard and VGA support - disable)
> > >     (Linux   serial support           - disable)
> >
> > That config gives you no tty1. You either need to enable dope to get a
> > framebuffer and thus tty1 or without dope enable the keyboard and
> > VGA to get tty1.
> 
> Thanks for your particular explanation.
> I have not seen the boot process of Linux in detail until now... I'll
> study harder.
> 
> 
> I enabled keyboard and VGA support in Linux configuration and changed
> "console=ttyLv0" to "console=tty1" in the kernel command line.
> Then, I got the login prompt on tty1 and could use bash of the ramdisk
> on L4Linux finally ! :)
> It seems to operate well.
> I also tried using DOpE on tty1 without keyboard and VGA, then it works.

Good!

> With keyboard and VGA support enabled, I get the following prompt on
> the serial console (not on tty1).
> (When I use DOpE, it doesn't appear because keyboard and VGA are disabled.)
> 
> #########################################################################
> .....
> l4lx    | l4env_rd_path: /boot/L4Linux/ramdisk
> l4lx    | Loading: /boot/L4Linux/ramdisk
> l4lx    | INITRD: Size of RAMdisk is 16384KiB
> l4lx    | RAMdisk from 10800000 to 11800000 [16384KiB]
> l4lx    | l4lx_thread_create: Created thread 0d.05 (timer.i0)
> l4lx    | l4lx_thread_create: Created thread 0d.06 (Idler)
> l4lx    | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 14.
> l4lx    | l4lx_thread_create: Created thread 0d.07 (IRQ14)
> l4lx    | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 12.
> l4lx    | l4lx_thread_create: Created thread 0d.08 (IRQ12)
> l4lx    | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 1.
> l4lx    | l4lx_thread_create: Created thread 0d.09 (IRQ1)
> 
>     --l4io_search_mem_region nope----------------------------IP: 0040e87d
> [l4lx.server] (d.04) jdb:
> #########################################################################
> 
> If I type "g" on above prompt, the sequence re-runs and then I get the
> login prompt finally.

This is just some debugging notice as some driver within L4Linux is
requesting an io memory region that the IO manager in L4Env doesn't know
anything about. The request thus just fails (so pressing g is ok in this
case). There should be a message somewhere of the type:
l4io_search_mem_region for phys_addr = xxxx which should state which
physical address was requested.

> The messages on tty1 at this time are the following.
> 
> #########################################################################
> .....
> io scheduler noop registerd
> io scheduler anticipatory registered (default)
> io scheduler deadline registered
> io scheduler cfq registered
> vga16fb: mapped to 0x000a0000
> #########################################################################
> 
> Is this input always needed ? I don't think so.

I don't think you need the vga16fb.

> Are there any problem in my kernel configuration or boot settings ?
> My now kernel configuration is the same as the recent mail (based on
> the given .config) :

Would be good to know the message from the failed io memory request.

> > ###### L4Linux Kernel Configuration ######
> >
> > o Device Drivers --->
> >  o Input device support --->
> >     o [*]   Keyboards --->
> >       o --- Keyboards
> >       o <*>   AT keyboard
> >  o Graphics support --->
> >     o <*> Support for frame buffer devices
> >     o <*>   VGA 16-color graphics support
> >     o [*]   VESA VGA graphics support
> >     o Console display driver support --->
> >       o [*] VGA text console
> >
> > ##########################################
> 
> 
> 
> Thanks and Regards,
> Lin
> 
> _______________________________________________
> l4-hackers mailing list
> l4-hackers at os.inf.tu-dresden.de
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Adam
-- 
Adam                 adam at os.inf.tu-dresden.de
  Lackorzynski         http://os.inf.tu-dresden.de/~adam/