On 16.03.2011 16:13, Lennart Sorensen wrote:
> I am trying to figure out why grub2 (from Debian Squeeze) gives an 'out
> of disk' error when trying to boot from the HD after doing an install.
> It ends up at a grub rescue prompt, given it can't even read the disk
> well enough to load the full grub. Doing ls shows the disks, and I can
> show the root directory of a partition, but anything further seems to
> hit the same 'out of disk' error.
>
>
ls -l should show how big it thinks the disk is. Compare it with its
real size
> The system is a Compulab CM-iTC which uses an intel tunnelcreek atom
> (the new one) with a phoenix bios. So far Compulab's response when told
> it won't boot grub2 was "We know, but syslinux works fine.", which to
> me is not a solution at all. The same system also hangs the Linux 2.6.32
> kernel unless 'edd=off' is added to the kernel command line.
>
>
Looks like int13 is borked. Perhaps it's borked in a way which prevents
GRUB from detecting 13/42 function. You can try to force int13/42 by:
=== modified file 'grub-core/disk/i386/pc/biosdisk.c'
--- grub-core/disk/i386/pc/biosdisk.c 2011-01-04 14:42:47 +0000
+++ grub-core/disk/i386/pc/biosdisk.c 2011-03-16 15:28:26 +0000
@@ -145,6 +145,8 @@
{
struct grub_bios_int_registers regs;
+ return 1;
+
regs.edx = drive & 0xff;
regs.eax = 0x4100;
regs.ebx = 0x55aa;
> So any suggestions on how to go about debuagging this? Or even any
> ideas why grub would give such an error.
>
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
