Re: Memory Map information: GRUB2 vs. Legacy GRUB (GRUB1)

[Vladimir 'phcoder' Serbinenko]

> However, when I boot using GRUB2, the Memory Map seems to have been
> written over.
>
> Some observations:
>  1) Legacy GRUB seems to use a combination of ELF and Multiboot header
> information to boot the OS image; however, GRUB2 using the "multiboot"
> kernel type will use strictly Multiboot protocol.
Both booters behave the same way about this. Loading ELF is a part of multiboot
>  2) The Memory Map information under GRUB2 seems to be "zeroed" which
> leads me to believe that there must be something different in the way
> Legacy GRUB and GRUB2 handle Data and BSS segments (ie: initializing
> data by zeroing out).
The most common reason is the OS zeroing it out. Legacy put the memory
map in lowmem. GRUB2 puts it just after the kernel image. Some kernels
may overwrite it during an initialisation phase.
>
> I am using GRUB2 version 1.96 from the Fedora RPM repository; hence, I
> wanted to know if a later SVN version has a fix or is there a change in
> the specifications.
Specifications are the same but we fixed a lot of bugs.
>
> Peace,
> Frank
>
>
>
>
> _______________________________________________
> Grub-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/grub-devel
>



-- 
Regards
Vladimir 'phcoder' Serbinenko

Personal git repository: http://repo.or.cz/w/grub2/phcoder.git