Eric W. Biederman wrote:
> Ollie Lho <[EMAIL PROTECTED]> writes:
>
>
>>Eric W. Biederman wrote:
>>
>>
>>>>[root@ollie winfast-elf]# nm linuxbios |grep stream
>>>>0008514c r doc_mil_stream
>>>>0008515c R estreams
>>>>0008514b R streams
>>>>
>>>>
>>>Nope streams != doc_mil_stream
>>>So adding the alignment is definentily necessary. It looks like
>>>my linuxBIOS builds were just lucky.
>>>
>>>
>>
>>With ELF image like this
>>
>>ollie mkelfImage 48:objdump -h elfImage
>>
>
> O.k. Here it gets to the new kernel but finds no memory.
>
>
>>EXT_MEM_K=0x00000000
>>ALT_MEM_K=0x00000000
>>
>>
>>But the kernel is not started at all. Any idea ??
>>
>
> mkelfImage-1.9 aka feebios/src/util/mkelfImage
>
> The newest version is needed with this version of linuxBIOS. I really
> need to do another release that prints out a banner with the version
> number. But I do know you are using an older version because I have
> different debug messages enabled by default :)
>
> Eric
>
>
Now with ELF image
ollie mkelfImage 78:objdump -h elfImage
elfImage: file format elf32-i386
Sections:
Idx Name Size VMA LMA File off Algn
0 .text 00001163 00010000 00010000 00001000 2**4
CONTENTS, ALLOC, LOAD, READONLY, CODE
1 .rodata 000002f1 00011163 00011163 00002163 2**5
CONTENTS, ALLOC, LOAD, READONLY, DATA
2 .data 00000018 00011460 00011460 00002460 2**2
CONTENTS, ALLOC, LOAD, DATA
3 .bss 000042a8 00011478 00011478 00002478 2**5
ALLOC
4 .nokill 00000028 00091000 00091000 00003000 2**0
CONTENTS, ALLOC, LOAD, CODE
5 .kernel 00154660 00100000 00100000 00004000 2**0
CONTENTS, ALLOC, LOAD, DATA
6 .ramdisk 00000000 00800000 00800000 00159000 2**0
CONTENTS, ALLOC, LOAD, DATA
7 .comment 0000003d 00000000 00000000 00159000 2**0
CONTENTS, READONLY
8 .note 00000014 00015720 00015720 0015903d 2**0
CONTENTS, READONLY
I got
Welcome to elfboot, the open sourced starter.
January 2002, Eric Biederman.
Version 0.99999
43:fill_inbuf() - ram buffer:0x00007a08
53:fill_inbuf() - nvram:0x00010000 block_count:0
Found ELF candiate at offset 0
safe_range start 0x10000 end 0x15720
safe_range Conflicts with range 4
which starts at 0x7724 ends at 0x47724
Bad memory range: [0x0000000000010000, 0x0000000000005720)
Bad ELF Image
7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00
02 00 03 00 01 00 00 00 e4 0e 01 00 34 00 00 00
b0 90 15 00 00 00 00 00 34 00 20 00 04 00 28 00
0d 00 0a 00
Where does the range 4 (0x7724 - 0x47724) come from ??
Ollie
