Has been fixed in grub2 for a while now, closing.
** Changed in: grub (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/279307
Title:
grub fails to boot on
The best thing to do is actually reading the manual of the motherboard,
or the new features introduced with the BIOS update, if you updated the
BIOS.
--
grub fails to boot on computers having a 28-bit lba and an hard disk larger
than 128 GB
https://bugs.launchpad.net/bugs/279307
You received
is there a way to actually find out that my motherboards BIOS only has
28-bit LBA support?
--
grub fails to boot on computers having a 28-bit lba and an hard disk larger
than 128 GB
https://bugs.launchpad.net/bugs/279307
You received this bug notification because you are a member of Ubuntu
Actually, the only way I fixed this issue on my pc was to use LILO with the
lba32 option, by creating an appropriate /etc/lilo.conf file(in this case,
since on my pc there was also Opensuse, I edited the /etc/lilo.conf file
created by Yast2 to make it work with Ubuntu's liloconfig, however it
The reason why I reported the bug recently is that the AGP slot of my
second-hand pc didn't work anymore, so I had to revert to my old
computer with a 28-bit lba, which of course had the same problem as
before, since I have a 160GB-large HD. Furthermore, a friend of mine
also had this problem on
I tried grub2 and grub1 couldn't boot to it (figures). Since, the
machine was basically going to be reinstalled anyway I put grub2 on the
mbr and reinstalled the latest kernels. It now works, so grub2 *might*
have this fixed (or maybe I did something else). +1 for grub2 in
jaunty.
--
grub
i can confirm this problem on upgrading to intrepid it was triggered. On my
computer there appears to be a BIOS update to fix the issue. Perhaps Grub2 has
this fixed?
Marco: how did you fix your issue?
** Changed in: grub (Ubuntu)
Status: New = Confirmed
--
grub fails to boot on
