Re: [Etherboot-developers] [COMMIT] 5.1.2+ boot from disk.

[<ke...@us...>]

>In this case the first 512 bytes was being placed at 0x92200.  One segment
>of the NBI file had image from 0x90200 to 0x91600 and BSS from 91600 to
>9A000, so the BSS overlapped the 0x92200 region reserved for the
>directory.
>
>This was generated with mknbi-1.2.7.

That's not where mknbi places them. The Etherboot image goes to 0x94000
and the bss follows the text and data.

Please do a mknbi on the image to show what addresses and sizes the
segments have.

The load map is:

0x07C00-0x07FFF   0.5 kB        floppy boot sector if loaded from floppy
0x0F???-0x0FFFF     ? kB        large Etherboot data buffers (deprecated)
0x10000-0x8FFFF 512.0 kB        kernel (from tagged image)
0x90000-0x901FF   0.5 kB        Linux floppy boot sector (from Linux image)
0x90200-0x921FF   8.0 kB        kernel setup (from Linux image)
0x92200-0x923FF   0.5 kB        tagged image header ("directory")
0x92400-0x927FF   1.0 kB        kernel parameters (generated by mknbi)
0x92800-0x93FFF   6.0 kB        this program (generated by mknbi)
0x94000-0x9FFFF  48.0 kB        Etherboot (top few kB may be used by BIOS)
                                Normally Etherboot starts at 0x94000
0x100000-                       kernel (if bzImage) (from tagged image)
after bzImage kernel            ramdisk (optional) (from tagged image)
                                moved to below top of memory by this program
                                but not higher than 896kB or what the
                                limit in setup.S says