[okl4-developer] OKLinux on x86

[Henning Schild]

On Wed, 12 Nov 2008 21:11:44 +1100
Geoffrey Lee <glee at ok-labs.com> wrote:

>On the 2.1 release, the hardware serial device is shared between the
>kernel debugger and a userlevel driver used by OK Linux.  This may be
>causing some issues.  Can you try building a production build by 
>appending enable_debug=False to the build command line, and see if you
>get any output?  The initial dmesg output and the OKL4 banner will
>go missing because the kernel serial driver will be compiled out.
>
>Otherwise, some trace output context might be quite useful in resolving
>this issue.

I used the kernel debugger and its tracing feature to compare Qemu to
the real machine. I did not find significant differences.
However i tried starting linux processes on Qemu to get a better
understanding what the spaces and clist views show.

After stacking a couple of shells on Qemu i tried the same thing on the
real machine and it actually worked as expected. So the input channel
for serial seems to work and OKLinux itself also seems to work. I
started "sleep 5" on OKLinux and watched it from within kdb. There
where 3 linux processes for 5 seconds. L_1 (init), L_6xx (sh) and
L_6yy (sleep)

So the output of the serial console seems to broken. Is there a way to
use VGA or framebuffer instead?
I'd also be fine with using a ramdisk or booting a Linux from harddisk
in order to access the box using ssh or something like. Would not be
nice to boot blind but as long as i can use OKLinux at some point i
dont care that much. Can i expect devices like harddisks or nics to work
with OKLinux?

Henning