L4Linux direct access

[Adam Lackorzynski]

On Thu Feb 09, 2012 at 11:23:27 +0100, Riccardo Cecolin wrote:
> I had to disable the "use vCPU execution model" to get that output. I added
> console=ttyLv0 and enabled support for it into the l4linux config, then
> with bash as init i could see  "allow_cli: allow_cli: No such file or
> directory" in the log.
> So i removed it from the command line and now i get a working bash! After
> mounting /proc lspci works fine too.
> 
> When trying with the default init i never get the login prompt, it freezes
> after "No user config loaded!", so something is still wrong (this with
> drops-rd.rd).

The issue is that this ramdisk's inittab is not configured to show a
prompt on ttyLv0, that's why no more output there. The login-prompt will
only be on tty0 (e.g. the framebuffer).

> If i load the other root image with an rc.local which executes "startx" i
> get the following error: xf86EnableIOPorts: failed to set IOPL for I/O
> (Operation not permitted). A previous mail in this list states that this is
> solved with that "allow_cli" parameter, but I need now some advice about
> where to put it, assuming that it is still a valid solution.

allow_cli is not valid anymore with any recent version.
The easiest way to use X is to configure X for the fbdev driver so it
uses the framebuffer.





Adam
-- 
Adam                 adam at os.inf.tu-dresden.de
  Lackorzynski         http://os.inf.tu-dresden.de/~adam/