[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#695328: [testing/wheezy] UEFI installed system fails to boot



On 2012-12-29T16:28:59-0800, Kenyon Ralph <kenyon@kenyonralph.com> wrote:
> This is probably part of the problem: on the installed system,
> /boot/efi is empty. Rerunning grub-install doesn't change that.

Actually, /boot/efi contains EFI/debian/grubx64.efi. For some reason,
rescue mode was showing that /boot/efi was mounted, but it actually
wasn't. umounting it and then mount -va properly mounted /boot/efi.
Then grub-install /dev/sda seems to have created a correct EFI boot
entry:

BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0000,0001,0002,0003
Boot0000* debian	HD(1,800,f3800,f8636d01-62af-4d23-9ab6-5b22c5ffd5e6)File(\EFI\debian\grubx64.efi)
Boot0001* SATA : PORT 6G 0 : INTEL SSDSC2CW120A3 : PART 0 : Boot Drive	BIOS(2,0,00)AMBO
Boot0002* USB :  0.00 : PART 0 : Boot Drive	BIOS(2,0,00)AMBO
Boot0003* UEFI : USB :  0.00 : PART 1 : OS Bootloader	ACPI(a0341d0,0)PCI(1d,0)USB(1,0)USB(1,0)HD(2,6f800,380,13a64ed1)AMBO

But the system still doesn't boot.

I retried installation using the 2012-12-29T22:11 build of
debian-testing-amd64-netinst.iso, followed by rescue mode, umount
/boot/efi, mount -va, grub-install /dev/sda, resulting in a good
Boot0000 line like above. System still doesn't boot. Strangely,
booting again into rescue mode, the Boot0000 line reverts back to
Vendor(99e275e7-75a0-4b37-a2e6-c5385e6c00cb,), even after mounting
/boot/efi properly.

I have a feeling that using grub2 2.00 (like Ubuntu uses) would work.
I'll try to build an installer including that if I can figure it out.

-- 
Kenyon Ralph

Attachment: signature.asc
Description: Digital signature


Reply to: