Hi all,
I think I have asked about this before but I do not know
whats happening. I have problems booting syslinux in my GPT disk which
I have asked in a separate topic "Boot Error GPT partition" . I loaded
https://github.com/skodabenz/Tianocore_DUET_memdisk_compiled (append
options - floppy ro nopass) . Using syslinux when it was booting
properly, did not lead to loss of RAM. But now since syslinux does not
boot, I am using grub2. I mailed the grub2 devs regarding this at
http://lists.gnu.org/archive/html/bug-grub/2010-12/msg00021.html .
They mentioned it is a memdisk problem. I am not sure though. These
are the memdisk outputs
memmap_grub2.txt -
http://lists.gnu.org/archive/html/bug-grub/2010-12/txtjbbLXRY2Fh.txt
memmap_syslinux.txt -
http://lists.gnu.org/archive/html/bug-grub/2010-12/txtlMdsmhrNKx.txt
memmap_dirext.txt - When USB pendrive is used to load DUET - Actual
amoutn of RAM -
http://lists.gnu.org/archive/html/bug-grub/2010-12/txtMKcPtgbgYF.txt
Thanks for any possible help.
- Keshav
Good day again Keshav, Does GRUB2 allow you to dump the memory map from its CLI _before_ booting tianocore (or whatever it's called)? For example, if you can look at the memory map _before_ booting MEMDISK and it doesn't look any good, then MEMDISK shouldn't be responsible. What might be nice to try is loading MEMDISK and the initrd, but dumping the memory map before booting it. It's a boot-loader's responsibility (such as GRUB2 or Syslinux) where a kernel (such as MEMDISK) and an initial RAM disk (such as your Tianoxxx.img) are put in memory. If MEMDISK then goes on to shuffle things around (such as gunzipping a gzipped initrd), then it's possible that it might make different choices about where to put the decompressed image based on whatever memory was left by the boot-loader. It's also possible that the MEMDISK "payload" containing its BIOS INTerrupt hooks might be put somewhere different under GRUB2 than under Syslinux, again, due to whatever memory map it was given by the boot-loader. Another possibly interesting experiment would be to boot GRUB2 -> MEMDISK + Syslinux floppy image. On that floppy image, you could include Syslinux' MEMDUMP.COM and find out what it reports. Or MEMINFO.C32. - Shao Miller
Here is the output (image attached) from meminfo.c32 from the grub2 + memdisk loaded syslinux floppy image. Regards. Keshav -------------- next part -------------- A non-text attachment was scrubbed... Name: grub2_memdisk_floppy_syslinux.jpg Type: image/jpeg Size: 169440 bytes Desc: not available URL: <http://www.zytor.com/pipermail/syslinux/attachments/20101230/0692778f/attachment.jpg>