FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo User

 
 
LinkBack Thread Tools
 
Old 10-13-2012, 09:38 AM
Michael Hampicke
 
Default UEFI boot, again

>> I just remembered another step that I missed - I dont have the syntax
>> but "efibootmgr" - google for the correct options.
>
> Yes ;-)
>
> I do that for days now. What puzzles me:
>
> I get the entries into EFI: when I boot I see the entries created by
> efibootmgr, but when I chose one of the entries pointing to "GRUB2" or
> "gentoo" the PC tells me that the disk isn't bootable.
>
> And I still don't know what is missing. AFAIK that EFI system partition
> is allowed to be within the first 2 TB of the disk (easy on my 1 TB
> hdd), has to have the boot-flag set (in parted-terms), and must be type
> EF02. When EFI doesn't find something bootable on the disk, my
> interpretation is that it can't find that partition?

Maybe the boot entry in the EFI firmware is wrong. That's what mine
looks like:

# efibootmgr -v
BootCurrent: 0000
Timeout: 2 seconds
BootOrder: 0000,0002,0003,0004
Boot0000* grub2
HD(1,800,40000,2693e7bd-d35e-4a39-9bb9-365ee533d690)File(EFIgrub2grubx64.efi)
Boot0002* Hard Drive BIOS(2,0,00)USB DISK 1100.
Boot0003* Network Card BIOS(6,0,00)Realtek PXE B05 D00.
Boot0004* Removable Drive BIOS(1,0,00)HTC Android Phone 0000.
 
Old 10-13-2012, 09:41 AM
Bill Kenworthy
 
Default UEFI boot, again

On Sat, 2012-10-13 at 11:06 +0200, Stefan G. Weichinger wrote:
> Am 2012-10-13 00:52, schrieb Bill Kenworthy:
>
> > another "feature" is you have to be booted via efi so the variables are
> > available so it can install itself - sorta catch 22
>
> Yes, I know that. No problem, when I boot from that stick, I do that via
> EFI, so I get the correct environment.
>
> > I just remembered another step that I missed - I dont have the syntax
> > but "efibootmgr" - google for the correct options.
>
> Yes ;-)
>
> I do that for days now. What puzzles me:
>
> I get the entrompties into EFI: when I boot I see the entries created by
> efibootmgr, but when I chose one of the entries pointing to "GRUB2" or
> "gentoo" the PC tells me that the disk isn't bootable.
>
> And I still don't know what is missing. AFAIK that EFI system partition
> is allowed to be within the first 2 TB of the disk (easy on my 1 TB
> hdd), has to have the boot-flag set (in parted-terms), and must be type
> EF02. When EFI doesn't find something bootable on the disk, my
> interpretation is that it can't find that partition?
>
> S
>
>

Do an "ls" from the grub prompt ... when booted from the usb stick grub
will renumber the devices in a different order. You will need to use
"ls" to find out what the current grub order is, edit the grub menu
(i.e., "e" when at the menu selection) and press F10 (I think) when done
to boot. The reason is grub will set itself up with the usbstick as
root, whereas once you boot with the correct mapping you can reissue the
commands to write them properly.

BillK
 
Old 10-13-2012, 10:13 AM
"Stefan G. Weichinger"
 
Default UEFI boot, again

Am 2012-10-13 11:38, schrieb Michael Hampicke:
>>> I just remembered another step that I missed - I dont have the syntax
>>> but "efibootmgr" - google for the correct options.
>>
>> Yes ;-)
>>
>> I do that for days now. What puzzles me:
>>
>> I get the entries into EFI: when I boot I see the entries created by
>> efibootmgr, but when I chose one of the entries pointing to "GRUB2" or
>> "gentoo" the PC tells me that the disk isn't bootable.
>>
>> And I still don't know what is missing. AFAIK that EFI system partition
>> is allowed to be within the first 2 TB of the disk (easy on my 1 TB
>> hdd), has to have the boot-flag set (in parted-terms), and must be type
>> EF02. When EFI doesn't find something bootable on the disk, my
>> interpretation is that it can't find that partition?
>
> Maybe the boot entry in the EFI firmware is wrong. That's what mine
> looks like:
>
> # efibootmgr -v
> BootCurrent: 0000
> Timeout: 2 seconds
> BootOrder: 0000,0002,0003,0004
> Boot0000* grub2
> HD(1,800,40000,2693e7bd-d35e-4a39-9bb9-365ee533d690)File(EFIgrub2grubx64.efi)
> Boot0002* Hard Drive BIOS(2,0,00)USB DISK 1100.
> Boot0003* Network Card BIOS(6,0,00)Realtek PXE B05 D00.
> Boot0004* Removable Drive BIOS(1,0,00)HTC Android Phone 0000.

look at mine!

->



# efibootmgr -v
BootCurrent: 0008
Timeout: 0 seconds
BootOrder: 0000,0001,0002,0008,0004,0005,0006,0007
Boot0000* GRUB2
HD(5,4d401800,64000,0c67029a-25de-4e23-b2be-6c502742189e)File(EFIGRUB2grubx64.efi)
Boot0001* USB Floppy/CD
Vendor(b6fef66f-1495-4584-a836-3492d1984a8d,0500000001)AMBO
Boot0002* USB Hard Drive
Vendor(b6fef66f-1495-4584-a836-3492d1984a8d,0200000001)AMBO
Boot0004 ATAPI CD-ROM Drive
Vendor(b6fef66f-1495-4584-a836-3492d1984a8d,0300000001)AMBO
Boot0005 Unknown Device BIOS(3,0,00)AMGOAMNO........o.h.p. . . . . . .
.C.D.D.V.D.W.
.T.S.-.H.6.5.3.T.N....................A................ ...........>..Gd-.;.A..MQ..L.8.R.G.L.G.6.B.F.7.A.4.8.2.4.
. . . . . ......AMBO
Boot0006 USB Floppy/CD
Vendor(b6fef66f-1495-4584-a836-3492d1984a8d,0500000000)AMBO
Boot0007 Hard Drive
BIOS(2,0,00)AMGOAMNO........o.S.T.3.1.0.0.0.5.2.4. A.S....................A........................ ...>..Gd-.;.A..MQ..L.
. . . . . . . . . . .
.V.9.D.P.1.H.0.D......AMBOAMNO........o.H.i.t.a.c .h.i.
.H.D.S.7.2.1.0.1.0.C.L.A.6.3.2................... .A...........................>..Gd-.;.A..MQ..L.
. . . . .
.P.J.9.2.0.4.8.J.1.3.S.4.V.G......AMBOAMNO....... ..J.e.t.F.l.a.s.h.T.S.5.1.2.M.J.F.V.3.0.
.8...0.7....................A.................... ...............F..Gd-.;.A..MQ..L.J.e.t.F.l.a.s.h.T.S.5.1.2.M.J.F.V.3.0.
.8...0.7......AMBO
Boot0008* UEFI: JetFlashTS512MJFV30 8.07
ACPI(a0341d0,0)PCI(1a,0)USB(1,0)USB(1,0)USB(2,0)HD (1,800,f47fe,000195b8)AMBO
 
Old 10-13-2012, 10:51 AM
Michael Hampicke
 
Default UEFI boot, again

Am 13.10.2012 12:13, schrieb Stefan G. Weichinger:
> Am 2012-10-13 11:38, schrieb Michael Hampicke:
>>>> I just remembered another step that I missed - I dont have the syntax
>>>> but "efibootmgr" - google for the correct options.
>>>
>>> Yes ;-)
>>>
>>> I do that for days now. What puzzles me:
>>>
>>> I get the entries into EFI: when I boot I see the entries created by
>>> efibootmgr, but when I chose one of the entries pointing to "GRUB2" or
>>> "gentoo" the PC tells me that the disk isn't bootable.
>>>
>>> And I still don't know what is missing. AFAIK that EFI system partition
>>> is allowed to be within the first 2 TB of the disk (easy on my 1 TB
>>> hdd), has to have the boot-flag set (in parted-terms), and must be type
>>> EF02. When EFI doesn't find something bootable on the disk, my
>>> interpretation is that it can't find that partition?
>>
>> Maybe the boot entry in the EFI firmware is wrong. That's what mine
>> looks like:
>>
>> # efibootmgr -v
>> BootCurrent: 0000
>> Timeout: 2 seconds
>> BootOrder: 0000,0002,0003,0004
>> Boot0000* grub2
>> HD(1,800,40000,2693e7bd-d35e-4a39-9bb9-365ee533d690)File(EFIgrub2grubx64.efi)
>> Boot0002* Hard Drive BIOS(2,0,00)USB DISK 1100.
>> Boot0003* Network Card BIOS(6,0,00)Realtek PXE B05 D00.
>> Boot0004* Removable Drive BIOS(1,0,00)HTC Android Phone 0000.
>
> look at mine!
>
> ->
>
>
>
> # efibootmgr -v
> BootCurrent: 0008
> Timeout: 0 seconds
> BootOrder: 0000,0001,0002,0008,0004,0005,0006,0007
> Boot0000* GRUB2
> HD(5,4d401800,64000,0c67029a-25de-4e23-b2be-6c502742189e)File(EFIGRUB2grubx64.efi)
> Boot0001* USB Floppy/CD
> Vendor(b6fef66f-1495-4584-a836-3492d1984a8d,0500000001)AMBO
> Boot0002* USB Hard Drive
> Vendor(b6fef66f-1495-4584-a836-3492d1984a8d,0200000001)AMBO
> Boot0004 ATAPI CD-ROM Drive
> Vendor(b6fef66f-1495-4584-a836-3492d1984a8d,0300000001)AMBO
> Boot0005 Unknown Device BIOS(3,0,00)AMGOAMNO........o.h.p. . . . . . .
> .C.D.D.V.D.W.
> .T.S.-.H.6.5.3.T.N....................A................ ...........>..Gd-.;.A..MQ..L.8.R.G.L.G.6.B.F.7.A.4.8.2.4.
> . . . . . ......AMBO
> Boot0006 USB Floppy/CD
> Vendor(b6fef66f-1495-4584-a836-3492d1984a8d,0500000000)AMBO
> Boot0007 Hard Drive
> BIOS(2,0,00)AMGOAMNO........o.S.T.3.1.0.0.0.5.2.4. A.S....................A........................ ...>..Gd-.;.A..MQ..L.
> . . . . . . . . . . .
> .V.9.D.P.1.H.0.D......AMBOAMNO........o.H.i.t.a.c .h.i.
> .H.D.S.7.2.1.0.1.0.C.L.A.6.3.2................... .A...........................>..Gd-.;.A..MQ..L.
> . . . . .
> .P.J.9.2.0.4.8.J.1.3.S.4.V.G......AMBOAMNO....... ..J.e.t.F.l.a.s.h.T.S.5.1.2.M.J.F.V.3.0.
> .8...0.7....................A.................... ...............F..Gd-.;.A..MQ..L.J.e.t.F.l.a.s.h.T.S.5.1.2.M.J.F.V.3.0.
> .8...0.7......AMBO
> Boot0008* UEFI: JetFlashTS512MJFV30 8.07
> ACPI(a0341d0,0)PCI(1a,0)USB(1,0)USB(1,0)USB(2,0)HD (1,800,f47fe,000195b8)AMBO
>
>
>

Looks good, could you cross-check if the GUID is correct? My EFI
partition is the first one on my ssd, so I use # sgdisk -i1 /dev/sda to
check. The value you are looking for is "Partition unique GUID" - should
be the same to what efibootmgr displays
(0c67029a-25de-4e23-b2be-6c502742189e)
 
Old 10-13-2012, 01:07 PM
"Stefan G. Weichinger"
 
Default UEFI boot, again

Am 13.10.2012 12:51, schrieb Michael Hampicke:
>
> Looks good, could you cross-check if the GUID is correct? My EFI
> partition is the first one on my ssd, so I use # sgdisk -i1 /dev/sda to
> check. The value you are looking for is "Partition unique GUID" - should
> be the same to what efibootmgr displays
> (0c67029a-25de-4e23-b2be-6c502742189e)

That is the ID of /dev/sda5:

# sgdisk -i5 /dev/sda
Partition GUID code: C12A7328-F81F-11D2-BA4B-00A0C93EC93B (EFI System)
Partition unique GUID: 0C67029A-25DE-4E23-B2BE-6C502742189E
First sector: 1296046080 (at 618.0 GiB)
Last sector: 1296455679 (at 618.2 GiB)
Partition size: 409600 sectors (200.0 MiB)
Attribute flags: 0000000000000000
Partition name: 'EFI System'

This is the EFI-system-partition on /dev/sda.
Should it point there?

In my case sda1 is a Linux RAID partition, which is part of md0, which
once was my / (too small now).

What I tried to achieve:

sda5: EFI system ( -> /boot/efi )

gentoo-root on /dev/md3 (consists of sda6 and sdb3)

I know this looks like a mess, and somehow it is.

But right now I see something else:

Boot0000* GRUB2
HD(5,4d401800,64000,0c67029a-25de-4e23-b2be-6c502742189e)File(EFIGRUB2grubx64.efi)

would point at my /dev/sda5 and the file EFIGRUB2grubx64.efi in
there, right?

After all my fiddling around right now it is named

/boot/efi/EFI/grub2/grubx64.efi

case-sensitive? Vfat ... ? I just rename it and give it a try ;-)

What about that ugly Boot0007 in my listing?

S
 
Old 10-13-2012, 02:35 PM
Michael Hampicke
 
Default UEFI boot, again

Am 13.10.2012 15:07, schrieb Stefan G. Weichinger:
> Am 13.10.2012 12:51, schrieb Michael Hampicke:
>>
>> Looks good, could you cross-check if the GUID is correct? My EFI
>> partition is the first one on my ssd, so I use # sgdisk -i1 /dev/sda to
>> check. The value you are looking for is "Partition unique GUID" - should
>> be the same to what efibootmgr displays
>> (0c67029a-25de-4e23-b2be-6c502742189e)
>
> That is the ID of /dev/sda5:
>
> # sgdisk -i5 /dev/sda
> Partition GUID code: C12A7328-F81F-11D2-BA4B-00A0C93EC93B (EFI System)
> Partition unique GUID: 0C67029A-25DE-4E23-B2BE-6C502742189E
> First sector: 1296046080 (at 618.0 GiB)
> Last sector: 1296455679 (at 618.2 GiB)
> Partition size: 409600 sectors (200.0 MiB)
> Attribute flags: 0000000000000000
> Partition name: 'EFI System'
>
> This is the EFI-system-partition on /dev/sda.
> Should it point there?
>
> In my case sda1 is a Linux RAID partition, which is part of md0, which
> once was my / (too small now).
>
> What I tried to achieve:
>
> sda5: EFI system ( -> /boot/efi )
>
> gentoo-root on /dev/md3 (consists of sda6 and sdb3)
>
> I know this looks like a mess, and somehow it is.
>
> But right now I see something else:
>
> Boot0000* GRUB2
> HD(5,4d401800,64000,0c67029a-25de-4e23-b2be-6c502742189e)File(EFIGRUB2grubx64.efi)
>
> would point at my /dev/sda5 and the file EFIGRUB2grubx64.efi in
> there, right?

Yes, correct. Everything so far looks okay to me. So when you book in
EFI mode you should get at least a grub shell - even if your grub.cfg is
missing or incorrect. But on the other hand, UEFI is a bitch, took me
several days in trial and error to get it running when I first tested it
(this was with unstable grub then, I even hat to create my own grub
image with grub2-mkimage)

>
> After all my fiddling around right now it is named
>
> /boot/efi/EFI/grub2/grubx64.efi
>
> case-sensitive? Vfat ... ? I just rename it and give it a try ;-)

vfat is not case sensitive, so this should be no problem.

>
> What about that ugly Boot0007 in my listing?

Maybe some internal rescue partition or something like that. Looks
strange to me too.
 
Old 10-15-2012, 05:37 PM
"Stefan G. Weichinger"
 
Default UEFI boot, again

Am 13.10.2012 16:35, schrieb Michael Hampicke:

>> After all my fiddling around right now it is named
>>
>> /boot/efi/EFI/grub2/grubx64.efi
>>
>> case-sensitive? Vfat ... ? I just rename it and give it a try ;-)
>
> vfat is not case sensitive, so this should be no problem.
>
>>
>> What about that ugly Boot0007 in my listing?
>
> Maybe some internal rescue partition or something like that. Looks
> strange to me too.


I gave up for now. Re-added SSD, MBR-partitioned.

The BIOS in the HP Elite 7300 only boots via BIOS if there is at least
one disk MBR-partitioned in there (with active boot-flag, I assume).

This EFI-stuff has to wait for times when I have more energy for this, I
got work to do as well ;-)

Thanks all, Stefan
 

Thread Tools




All times are GMT. The time now is 10:19 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org