Wow, tough crowd on this list... Pursuant to my previous email, I placed grub_printf() statements at approximately line #351 and #606 in the file loader/i386/efi/linux.c. That would be where grub_rescue_cmd_linux() and grub_rescue_cmd_initrd() get their ideas about what initrd_addr_max should be.
In both cases, 0x1fffffff is returned, which is a value carved into the kernel header of my vmlinuz file. So Grub2 is doing its job, and it seems there's some conflict between where initrd memory is on my Core 2 Duo MacMini (@ around 1gb), and where the Debian AMD64 vmlinuz-2.6.21-2-686 kernel is saying it can't be found above. I don't have any experience compiling the kernel as I've not so far had a reason to. :-) Is initrd_addr_max a configurable piece of the kernel? Again, not really sure right now where to take this info... Best, Charles _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
