[okl4-developer] OKLinux on x86

[Geoffrey Lee]

On Mon, Nov 10, 2008 at 07:41:43PM +0100, Henning Schild wrote:
> Hello.
> 

Henning - 

> I am interested in OKLinux and wanted to try it. I like the
> build system which generates images without the need to configure
> anything. However all the images it generated for x86 could only be
> used in qemu but not on real machines.
> The boot process hangs when OKLinux is about to start the init process.
> 
> ...
> > NET: Registered protocol family 17
> > VFS: Mounted root (ext2 filesystem) readonly.
> > vserial: init done (handle: 0, owner: 18001, mask: 2)
> > L
> 
> I tried a PentiumD, PhenomX4 and to lock out MP problems i also tried
> a P2. The problem is not specific to one release. I used all x86
> releases i could find (2.1, 2.1.1-fix.7 and 2.1.1-patch.9), none of them
> worked.

The 2.1 release only supports uniprocessor configurations for 
x86 so I don't think it is an MP issue.

> 
> I guess the problem is somehow related to missing interrupts in
> oklinux. Using the releases in qemu seems to work fine in the first
> place but working with it is quite hard since a lot of
> keystrokes are missed.


This is a separate issue.  There was an issue introduced quite
close to the 2.1 release which affected OK Linux, set 

kdb_breakin = False 

in the platform description located in platforms/pc99/tools/machines.py 
to fix this.

> 
> I applied this patch to all the releases in order to build them
>  http://lists.okl4.org/pipermail/developer/2008-October/001834.html
> 
> OKL4 obviously has its focus on ARM, i still hope anyone is using it on
> x86 and can assist me.

I have booted 2.1 on hardware before, so that should work.  Do I
understand correctly that you have also tried to run it under the 
QEMU emulator as well and it works under QEMU?  If you did succeed 
in getting it running on QEMU, is the image that you run on QEMU 
identical to the image that you run on hardware, including the root
filesystem settings?  How did you setup your hardware to boot OKL4?  
Since you did actually manage to get some output on hardware I think 
it's probably OK but I'd just like to make sure anyway.  Finally,
which toolchain are you using to build your software?

It might be a good idea at this point to break into the debugger
(Ctrl-k).  Once you are in the debugger, you can turn on tracepoints.
Hit r for the tracepoint menu then E to turn on tracepoints, then
you can enable all tracepoints or just some specific ones (hit ? for
help).  That'll tell you what the system is doing.


> 
> regards,
> Henning Schild

	-gl

> 
> _______________________________________________
> Developer mailing list
> Developer at okl4.org
> https://lists.okl4.org/mailman/listinfo/developer
> 

--