On Sat, Feb 02, 2008 at 10:44:35PM -0500, George Lengel wrote:
Robert Millan wrote:
Sounds like grub_boot_drive not having the right info. It works when
received
via multiboot, but not from boot.img.
Does the attached patch fix your problem? Just a guess ...
Hello,
Thanks for the try. It did not appear to make a difference, though I
cannot rule out I did not apply the patch and recompile correctly. I
hope I did though and everything I checked indicated I was using my
compiled version and not the original Debian package.
You need to be sure. It's hard enough to try guessing what the problem may
be, to make it even harder this way.
Is there something
I can check so we can be convinced I am using the patched version?
Try:
diff -ur grub2/kern/i386/pc/init.c tmp/kern/i386/pc/init.c
--- grub2/kern/i386/pc/init.c 2008-01-23 12:25:52.000000000 +0100
+++ tmp/kern/i386/pc/init.c 2008-02-03 11:58:31.000000000 +0100
@@ -232,6 +232,8 @@
if (! grub_os_area_addr)
grub_fatal ("no upper memory");
+
+ grub_printf ("%p\n", grub_boot_drive);
}
void
this will also tell you the grub_boot_drive value (let us know).