Vladimir,
The 2.00rc1 version of grub2 still doesn't fix the efi memory map
buffer size I've been working on (though I can see you are now
allocating the efi memory map buffer very shortly before you are
calling grub_efi_finish_boot_services()).
Increasing the
Vladimir,
The 2.00rc1 version of grub2 still doesn't fix the efi memory map
buffer size I've been working on (though I can see you are now
allocating the efi memory map buffer very shortly before you are
calling grub_efi_finish_boot_services()).
Increasing the mmap_size in
Well, this works, too (on top of HEAD from 7 june).
--- ../../grub/grub-core/loader/i386/linux.c 2012-05-31
12:59:19.0 -0400
+++ grub-core/loader/i386/linux.c 2012-06-12 20:47:51.455718055 -0400
@@ -139,7 +139,7 @@ find_efi_mmap_size (void)
/* Increase the size a bit
-Original Message-
From: grub-devel-bounces+stuart_hayes=dell@gnu.org [mailto:grub-
devel-bounces+stuart_hayes=dell@gnu.org] On Behalf Of Vladimir 'f-
coder/phcoder' Serbinenko
Sent: Wednesday, June 27, 2012 3:51 PM
To: Hayes, Stuart
Cc: bug-grub@gnu.org; grub-de
-
- mmap_size = (1 12);
- while (1)
-{
- int ret;
- grub_efi_memory_descriptor_t *mmap;
- grub_efi_uintn_t desc_size;
-
- mmap = grub_malloc (mmap_size);
- if (! mmap)
- return 0;
-
- ret = grub_efi_get_memory_map (mmap_size, mmap,
On 07.06.2012 21:02, stuart_ha...@dell.com wrote:
Vladimir,
On 27 May you had asked me to test a patch to see if it fixed the
x86_64 EFI boot issue I was seeing
(http://lists.gnu.org/archive/html/grub-devel/2012-05/msg00064.html).
This patch apparently moved the linux real mode
It looks like the problem is that we set video mode. Other than that we
do only mmap iterating and allocating the memory in question. How about
this patch (not tested):
=== modified file 'grub-core/loader/i386/linux.c'
--- grub-core/loader/i386/linux.c 2012-05-31 12:06:11 +
+++
I'm sorry, somehow your earlier message on the ML never showed up in my mail
box. I found it on the archive, and I'll address your concerns. Should I open
a new bug (it won't let me reply on the closed bug), or just respond on the ML?
Thank you,
Stuart
-Original Message-
From:
