fiasco can't start correctly
Adam Lackorzynski
adam at os.inf.tu-dresden.de
Tue May 27 17:08:27 CEST 2008
On Tue May 27, 2008 at 11:45:48 +0800, fei li wrote:
> Hi
> I tested it again, now i get the results
>
> L4 Bootstrapper
> move modules to 2000000 with offset ed0000
> move module 4 start 126e000 (ELF) -> 213e000
> move module 3 start 11d0000 (ELF) -> 20a0000
> move module 2 start 119c000 (ELF) -> 206c000
> move module 1 start 1130000 (ELF) -> 2000000
> Scanning /main
> Scanning /sigma0
> Scanning /roottask
> Bootloader MMAP:
> [ 0, 9fc00) RAM (1)
> [ 9fc00, a0000) reserved (2)
> [ e8000, 100000) reserved (2)
> [ 100000, 7ff0000) RAM (1)
> [ 7ff0000, 8000000) ACPI (3)
> [ fffc0000, 100000000) reserved (2)
> Relocated mbi to [0x76000-0x760b8]
> Loading /main
> Loading /sigma0
> Loading /roottask
> find kernel info page...
> found kernel info page at 0x1000
> [ 1000, 75fff] Kern /main
> [ 76000, 761b5] Root Multiboot info
> [ 9fc00, 9ffff] Arch BIOS
> [ e8000, fffff] Arch BIOS
> [ 100000, 10a6df] Sigma0 /sigma0
> [ 110000, 2c6fff] Root /roottask
> [ 2d0080, 2daf57] Boot bootstrap
> [ 300000, 34a8af] Kern /main
> [ 213e000, 2187e07] Root Modules Memory
> [ 7ff0000, 7ffffff] Arch BIOS
> [ fffc0000, ffffffff] Arch BIOS
> API Version: (87) experimental
> Sigma0 config ip:0000000000104780 sp:00000000002da990
> Roottask config ip:0000000000110000 sp:0000000000000000
> Starting kernel /main at 0000000000300ad0
>
> I don't know the kernel is 32-bit or 64-bit, how to check it? I compare the
> two results and find that the newer has "elf" signs, I don't know what to do
> next.
'file' or 'readelf' are possible tools for this but the output looks ok.
This whole thing works for me. You could send me your main file to have
a closer look at it.
Adam
--
Adam adam at os.inf.tu-dresden.de
Lackorzynski http://os.inf.tu-dresden.de/~adam/
More information about the l4-hackers
mailing list