[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Mismatch between grub2 memmap and syslinux memmap while using memdisk
From: |
KESHAV P.R. |
Subject: |
Mismatch between grub2 memmap and syslinux memmap while using memdisk |
Date: |
Wed, 22 Dec 2010 13:19:46 +0530 |
Hi,
I am trying to boot a floppy image in my Dell Laptop using
memdisk from syslinux . When memdisk is loaded from grub2 (linux16 and
initrd16), nearly 2 GB of ram is not usable out of 4 GB RAM. This is
the floppy image used
https://github.com/skodabenz/Tianocore_DUET_memdisk_compiled/blob/master/Tiano_EDK2_DUET_X64.img
and this is the grub2 config file
menuentry "Boot DUET " {
linux16 ${prefix}/memdisk floppy ro nopass
initrd16 ${prefix}/Tiano_EDK2_DUET_X64.img
}
I have attached the memmap outputs (from EFI shell) while loading the
image directly (memmap_direct.txt), memdisk through syslinux
(memmap_syslinux.txt), memdisk through grub2 (memmap_grub2.txt).
Loading memdisk through syslinux, ram space covered for the memdisk
and floppy image is only about 8 MB. Is this due to the way grub
allocates memory for initrd? Where is the bug? Memdisk or Grub2. I
think since memdisk works perfectly with syslinux, this has something
to do with grub2. Regards
Keshav
memmap_grub2.txt
Description: Text document
memmap_syslinux.txt
Description: Text document
memmap_direct.txt
Description: Text document
- Mismatch between grub2 memmap and syslinux memmap while using memdisk,
KESHAV P.R. <=