On Tue, Jun 17, 2008 at 3:01 PM, David Holloway [EMAIL PROTECTED] wrote:
Intended for Robert Millan, et. al.
I have an Intel 1U server board that fails with the current version of grub
with the message too little memory, as in line 312 of CVS version 1.4 of
grub2/kern/efi/mm.c
The board is
David Holloway wrote:
Intended for Robert Millan, et. al.
I have an Intel 1U server board that fails with the current version of
grub with the message too little memory, as in line 312 of CVS
version 1.4 of grub2/kern/efi/mm.c
The board is described here:
On Tue, Jun 17, 2008 at 12:01:57AM -0700, David Holloway wrote:
Intended for Robert Millan, et. al.
Me? But I barely know anything about EFI :-)
--
Robert Millan
GPLv2 I know my rights; I want my phone call!
DRM What good is a phone call… if you are unable to speak?
(as seen on /.)
Straight from the public UEFI docs:
If the MemoryMap buffer is too small, the EFI_BUFFER_TOO_SMALL error
code is returned and
the MemoryMapSize value contains the size of the buffer needed to
contain the current
memory map. The actual size of the buffer allocated for the consequent
call
On Tue, Jun 17, 2008 at 3:01 PM, David Holloway [EMAIL PROTECTED] wrote:
/ Intended for Robert Millan, et. al./
/ I have an Intel 1U server board that fails with the current version of grub/
/ with the message too little memory, as in line 312 of CVS version 1.4 of/
/ grub2/kern/efi/mm.c/
/ The
Exactly on target. Then we need a more robust and permanent
solution I think right?
How about asking with 0 sized buffer first knowing it will fail then
asking with a rounded-up buffer the 2nd time.
I can coded it, but I can't check it in of course.
http://www.uefi.org/specs/
You