Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Another GRUB2 UEFI problem
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
calif
Tux's lil' helper
Tux's lil' helper


Joined: 29 Nov 2009
Posts: 101

PostPosted: Tue Feb 16, 2016 11:43 pm    Post subject: Another GRUB2 UEFI problem Reply with quote

Hello, I have a problem with installing GRUB2.

I have EFI support built into the kernel: https://bpaste.net/show/d93c66bd55d9

I installed grub2 having
Quote:
GRUB_PLATFORMS="efi-64"
.

I have /dev/sdb1 mounted as /boot with vfat 32:
Quote:
/dev/sdb1 /boot vfat noauto,noatime 1 2


I'm installing it using (handbook):
Quote:
grub2-install --target=x86_64-efi --efi-directory=/boot


It returns the following:
Quote:
# grub2-install --target=x86_64-efi --efi-directory=/boot
Installing for x86_64-efi platform.
efibootmgr: Could not set variable Boot0002: No space left on device
efibootmgr: Could not prepare boot variable: No space left on device
Installation finished. No error reported.


What does that mean?
There is a lot of space left on /dev/sdb1:
Quote:
/dev/sdb1 500M 31M 469M


What should I do?
Back to top
View user's profile Send private message
khayyam
Watchman
Watchman


Joined: 07 Jun 2012
Posts: 6228
Location: Room 101

PostPosted: Wed Feb 17, 2016 12:47 am    Post subject: Re: Another GRUB2 UEFI problem Reply with quote

calif wrote:
Code:
efibootmgr: Could not set variable Boot0002: No space left on device
efibootmgr: Could not prepare boot variable: No space left on device
Installation finished. No error reported.

calif ... the error doesn't refer to the ESP, but to efivarfs, >=sys-boot/efibootmgr-0.11.0 uses this kernel feature (or mis-feature) and (from the number of reports I've read) it's not altogether stable. I'd suggest you use =sys-boot/efibootmgr-0.5.4-r1 ... though from the above "no error reported" it may not be critical, did you attempt to reboot?

best ... khay
Back to top
View user's profile Send private message
calif
Tux's lil' helper
Tux's lil' helper


Joined: 29 Nov 2009
Posts: 101

PostPosted: Wed Feb 17, 2016 9:50 am    Post subject: Reply with quote

That's waaaay to weird... UEFI, why?! :))

Anyway, I have a question before I start repairing my GRUB (again), does this matter if I have my sdb1 (UEFI) partition as /boot or only /boot/efi?

What should the whole /boot/efi actually contain?

The Gentoo Installation Handbook says (https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Kernel#Compiling_and_installing) that we should copy our kernel to the /boot/efi/boot dir, is this really necessary when actually, grub2-install creates its own file there? It also says that we should have 2 partitions sda1 (what is like 3MB big) and standard /boot partition - what are thoooose, why do we need the first one?

Also, on the other hand the Grub2 wiki doc (https://wiki.gentoo.org/wiki/GRUB2#UEFI_with_GPT) says nothing about those 2 partitions, nor about copying the kernel..

I'm so lost :) please help.
Back to top
View user's profile Send private message
khayyam
Watchman
Watchman


Joined: 07 Jun 2012
Posts: 6228
Location: Room 101

PostPosted: Wed Feb 17, 2016 12:49 pm    Post subject: Reply with quote

calif wrote:
That's waaaay to weird... UEFI, why?! :))

calif ... you need only look at the names involved, and draw your own conclusions.

calif wrote:
Anyway, I have a question before I start repairing my GRUB (again), does this matter if I have my sdb1 (UEFI) partition as /boot or only /boot/efi?

It doesn't, no, you can use the ESP (EFI System Partition) as /boot, or have boot on / and mount the ESP to /boot/efi. Other than /boot/efi there is nothing else needed in /boot ... so the choice is yours.

calif wrote:
What should the whole /boot/efi actually contain?

EFI executables (and supporting files) ... the content, or its organisation, its entirely up to you. The only directory explicitly mentioned in the efi standard is {ESP}/efi/boot which can contain a 'bootx64.efi' or 'bootia32.efi' which acts as the 'default' efi executable (though not all efi implementations follow the standard ITR). Any other paths/names are arbitrary, you're providing this to efibootmgr, which writes it to NVRAM (and so at boot the specific path to the executable to be used is known). I have the following:

Code:
# mount /boot
# print -rl /boot/**/*(/)
/boot/efi
/boot/efi/boot
/boot/efi/grub2
/boot/efi/linux
/boot/efi/refind
/boot/efi/refind/drivers_ia32
/boot/efi/refind/icons
/boot/efi/shell
# print -rl /boot/**/*.efi
/boot/efi/grub2/grub2.efi
/boot/efi/linux/vmlinuz-3.13.11-ck.efi
/boot/efi/linux/vmlinuz-4.3.4-ck.efi
/boot/efi/refind/drivers_ia32/ext2_ia32.efi
/boot/efi/refind/drivers_ia32/ext4_ia32.efi
/boot/efi/refind/drivers_ia32/hfs_ia32.efi
/boot/efi/refind/drivers_ia32/iso9660_ia32.efi
/boot/efi/refind/refind_ia32.efi
/boot/efi/shell/shellia32.efi

Of which only rEFInd and the efi_stub kernels are actually used (in fact, refind is the executable set via efibootmgr, the others (ie, efi_stub, efi shell, grub2) are either called by refind, or explicitly excluded from being presented at boot time.

calif wrote:
The Gentoo Installation Handbook says (https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Kernel#Compiling_and_installing) that we should copy our kernel to the /boot/efi/boot dir, is this really necessary when actually, grub2-install creates its own file there? It also says that we should have 2 partitions sda1 (what is like 3MB big) and standard /boot partition - what are thoooose, why do we need the first one?

Personally I wouldn't use efi/boot, but as I said above it's up to you how you organise the directory structure, and the paths used. I don't know why the handbook suggests using it because it doesn't matter, and as per the standard, efi/boot is for the 'default' loader, which if you're using grub2 isn't the kernel (and as you noticed 'grub2-install' then uses this same location). If you want my advice use rEFInd rather than grub2, and avoid all the sillyness ;)

In this section of the handbook (which I'll admit I haven't read) it is suggesting you create a 3mb ESP, and then store all the 'boot' stuff (kernel, grub2, etc) under /boot (ext2). That's (mostly) fine, you can do it that way, but (as I remember) the standard states that the ESP should be 200mb, and as your machine probably came with an ESP already formated, I don't see the point in not using it as is, and note some efi implementations baulk if the ESP is less than some number of mb (I've read of this happening). So, I'd suggest you don't follow the handbook ITR, and store everything (bootloaders, kernels, initramfs, etc) on the ESP. The only downside is that its vfat, and running 'make install' will use /boot ... but if you have other OSes, then they will be using the ESP for such things, so it makes sense (somewhat) to keep these in the same location.

calif wrote:
Also, on the other hand the Grub2 wiki doc (https://wiki.gentoo.org/wiki/GRUB2#UEFI_with_GPT) says nothing about those 2 partitions, nor about copying the kernel.

Yeah, well, that is because there is nothing as fun as making things more complicated than they need be ;) You can ignore most of the suggestions, as whatever you are supplying as '--loader' to efibootmgr is what gets loaded. If you don't have a particular love, or need, for grub then you might think about another loader.

calif wrote:
I'm so lost :) please help.

As it says on the jacket cover, "don't panic" ;)

best ... khay
Back to top
View user's profile Send private message
v_andal
Guru
Guru


Joined: 26 Aug 2008
Posts: 523
Location: Germany

PostPosted: Wed Feb 17, 2016 1:03 pm    Post subject: Reply with quote

Basically, UEFI expects single EFI partition to contain image that it shall load. Then it is up to that image to do anything useful. The path to the image is stored in EFI variables. These variables are accessible only if computer is booted in EFI mode. It's kind of chicken-egg problem: to install efi-aware boot loader you have to boot efi-aware boot loader. The Sysresccd (https://www.system-rescue-cd.org/SystemRescueCd_Homepage) that I'm using for installation provides such boot-loader. It also provides efibootmgr. So, after booting this CD you can run "efibootmgr -v" to see if EFI variables are available. This command reports current EFI settings, like which bootable images are registered with EFI and where they are located.

Now, not all EFIs support changing of variables, in fact, so far out of 3 my PCs with UEFI, not a single one supports that. In this case, the only solution is to copy the bootable image to the path already known to UEFI.

The "bootable image" can be grub, linux kernel, rEFInd or whatever you find.

The "/boot/efi" is the default path expected by efibootmgr. You can specify different path using options. So you don't have to mount EFI partition at this path.

The /boot itself does not have to be separate partition. The kernel image does not have to be in EFI partition. Configure grub so that it finds your kernel.

Probably, it would be easier for you to use rEFInd (http://www.rodsbooks.com/refind/) instead of grub. It is smart enough to find all your kernels.
Back to top
View user's profile Send private message
calif
Tux's lil' helper
Tux's lil' helper


Joined: 29 Nov 2009
Posts: 101

PostPosted: Wed Feb 17, 2016 3:34 pm    Post subject: Reply with quote

According to: https://wiki.gentoo.org/wiki/Refind#Manual_installation

does /boot/efi/EFI also mean "this is the default", just like /boot/efi/boot? Or is it the "executable's" name to say that?

Anyway, khayyam, looks like you have no "default" image, how does this work?

Also, it looks like I have my Windows10 image on another disk (probably /dev/sdc), does it mean I have another ESP partition? Should I use it to install the bootloader there?

I understand more, thanks to both of you, but it's still not so clear for me - anyway my plan is to:
- format my /dev/sdb1 as vfat -F 32 and make it mounting on /boot
- install rEFInd according to https://wiki.gentoo.org/wiki/Refind#Manual_installation
- generate my vmlinuz image and copy it to /boot/efi/gentoo/
- hope that rEFInd can see my copied vmlinuz from efi/gentoo as well as Windows10 image on (probably) another disk

Well, let's start, see you on the other side. :)


@EDIT:

And there it is, the fail... Again it returned the "not enough space" error when using efibootmgr to install rEFInd. And then - there is Windows starting after the reboot - probably due to the /EFI/Boot/bootx64.efi I'm talking about below...

Anyway: I noticed I have another EFI parition which contains /EFI/Boot/bootx64.efi with my Windows10 on /dev/sdc2. Should I use this partition instead of creating a new one?

The next plan is to:
- backup /dev/sdc2 containing my current windows10 image
- move /EFI/Boot/bootx64.efi to /EFI/Windows/windows.efi
- then install rEFInd under /EFI/refind
- then use /dev/sdc2 as /boot under gentoo and add my image
- then fight with efibootmgr :)
Back to top
View user's profile Send private message
khayyam
Watchman
Watchman


Joined: 07 Jun 2012
Posts: 6228
Location: Room 101

PostPosted: Wed Feb 17, 2016 8:22 pm    Post subject: Reply with quote

calif wrote:
According to: https://wiki.gentoo.org/wiki/Refind#Manual_installation

does /boot/efi/EFI also mean "this is the default", just like /boot/efi/boot? Or is it the "executable's" name to say that?

calif ... what the author of that particular wiki page is doing is mounting the ESP to /boot/efi ... and so there is another 'efi' directory within that volume (note, vfat is case-insensitive). That's how s/he arrives at /boot/efi/efi/. As for defaults, well, if you mount the ESP to /boot then you are going to end up with that path ... but this doesn't matter, because the firmware would see {ESP}/efi/boot ... regardless.

calif wrote:
Anyway, khayyam, looks like you have no "default" image, how does this work?

That is the "default" location for "a" loader ... so /efi/boot/bootia64.efi ... if the loader is there, and this particular firmware follows the standard, then it should load it ... without your having to add an entry for it in NVRAM. So, by "default" we mean where it will look, not where you should place it. As I explained above, if you run 'efibootmgr --create --part 1 --label "foo" --loader "\efi\foo\fooloader.efi" then this will be what gets loaded, if there is nothing defined, then it will, or should, look in the default location.

calif wrote:
Also, it looks like I have my Windows10 image on another disk (probably /dev/sdc), does it mean I have another ESP partition? Should I use it to install the bootloader there?

I really can't tell you, I've never touched windows. If you have rEFInd then it will detect whatever loader windows provided, regardless of where it is on disk, and provide it as a selection at boot. Probably you could use the ESP on sdc but (knowing microsoft) they may have the ms_loader.efi on the same partition as the install, or, have it so that bad things™ happen if you so much as touch the ESP. I'm guessing ... but without someone more knowledgeable commenting otherwise I'd suggest you leave it alone.

calif wrote:
I understand more, thanks to both of you, but it's still not so clear for me - anyway my plan is to:
- format my /dev/sdb1 as vfat -F 32 and make it mounting on /boot
- install rEFInd according to https://wiki.gentoo.org/wiki/Refind#Manual_installation
- generate my vmlinuz image and copy it to /boot/efi/gentoo/
- hope that rEFInd can see my copied vmlinuz from efi/gentoo as well as Windows10 image on (probably) another disk

rEFInd will scan the disks and provide any loader with the suffix *.efi ... so, other than your not having mentioned that your vmlinuz should be vmlinuz.efi that all sounds fine.

calif wrote:
@EDIT: And there it is, the fail... Again it returned the "not enough space" error when using efibootmgr to install rEFInd. And then - there is Windows starting after the reboot - probably due to the /EFI/Boot/bootx64.efi I'm talking about below...

"It" being which version of efibootmgr?

calif wrote:
Anyway: I noticed I have another EFI parition which contains /EFI/Boot/bootx64.efi with my Windows10 on /dev/sdc2. Should I use this partition instead of creating a new one?

No. Please provide the output of 'efibootmgr -v'

best ... khay
Back to top
View user's profile Send private message
calif
Tux's lil' helper
Tux's lil' helper


Joined: 29 Nov 2009
Posts: 101

PostPosted: Wed Feb 17, 2016 8:48 pm    Post subject: Reply with quote

After soooo many tries I got something working.

I installed grub under /boot/efi/boot/bootx64.efi - and it works.
Also I have /boot/efi/gentoo/gentoox64.efi with my vmlinuz.

Well, it looks like "my" box accepts only boot~.efi images and you can't create your own entries using efibootmgr-0.12.

I got it working with grub, but rEFInd sounds way better, so I'm going to change install it under /boot/efi/boot/bootx64.efi and we'll see what happens.

Here is my efibootmgr -v output:

Code:
BootCurrent: 0016
Timeout: 1 seconds
BootOrder: 0015,0000,0016,0017,0003,0004,0005,0018
Boot0000* Windows Boot Manager   HD(2,GPT,2a151301-41a5-4825-8940-a37d6a6d891b,0xe1800,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...,................
Boot0003* ST2000DM001-1ER164   BBS(HD,,0x0)AMBO
Boot0004* Samsung SSD 850 EVO 250GB   BBS(HD,,0x0)AMBO
Boot0005* PLEXTOR PX-256M6S   BBS(HD,,0x0)AMBO
Boot0015* ubuntu   HD(1,GPT,a2befeec-b9fa-4315-85ed-90bfcd01e4da,0x800,0xfa000)/File(\EFI\UBUNTU\GRUBX64.EFI)
Boot0016* UEFI OS   HD(1,GPT,a2befeec-b9fa-4315-85ed-90bfcd01e4da,0x800,0xfa000)/File(\EFI\BOOT\BOOTX64.EFI)
Boot0017* UEFI: General USB Flash Disk 1100   PciRoot(0x0)/Pci(0x14,0x0)/USB(1,0)/HD(1,MBR,0x4294967200,0x2ef0ac,0x11c0)AMBO
Boot0018* General USB Flash Disk 1100   BBS(HD,,0x0)AMBO


I have no idea what \EFI\UBUNTU is... there's no such thing in my /boot/efi. And as I said earlier, \EFI\BOOT is my grub2 - and I want to switch that to rEFInd.

I'm not so sure if I'm going to do this today, so please - let me do this tomorrow and hopefully I can mark is as solved then. :)

Thanks for your kind help!
Back to top
View user's profile Send private message
khayyam
Watchman
Watchman


Joined: 07 Jun 2012
Posts: 6228
Location: Room 101

PostPosted: Wed Feb 17, 2016 9:18 pm    Post subject: Reply with quote

calif wrote:
I installed grub under /boot/efi/boot/bootx64.efi - and it works. Also I have /boot/efi/gentoo/gentoox64.efi with my vmlinuz.

calif ... are you trying to add entries for every loader? You shouldn't ... just one for your bootloader/bootmanager (which should be the first in 'BootOrder'), this should then offer other efi executables as a boot selection.

calif wrote:
Well, it looks like "my" box accepts only boot~.efi images and you can't create your own entries using efibootmgr-0.12.

I did say to try =sys-boot/efibootmgr-0.5.4-r1 ... I don't think the issue is with your firmware.

calif wrote:
I got it working with grub, but rEFInd sounds way better, so I'm going to change install it under /boot/efi/boot/bootx64.efi and we'll see what happens.

You can do that but I don't think you really need to, you should be able to provide an entry for it via efibootmgr. So, for example ...

Code:
# efibootmgr --bootnum 0015 --delete-bootnum # remove 'ubuntu' entry
# efibootmgr --bootnum 0016 --delete-bootnum # remove 'BOOTX64.EFI', ie 'grub2', entry
# efibootmgr --disk /dev/sda --create --part 1 --label "rEFInd" --loader "\efi\refind\refind_x64.efi"

calif wrote:
I have no idea what \EFI\UBUNTU is... there's no such thing in my /boot/efi. And as I said earlier, \EFI\BOOT is my grub2 - and I want to switch that to rEFInd.

You've booted ubuntu on that machine at some point, so the entry remained (so too with other external disks, installers, etc, you've booted, you can --delete-bootnum them).

calif wrote:
I'm not so sure if I'm going to do this today, so please - let me do this tomorrow and hopefully I can mark is as solved then. :)

ok, the above should cover it ...

calif wrote:
Thanks for your kind help!

np, you're welcome ... khay
Back to top
View user's profile Send private message
v_andal
Guru
Guru


Joined: 26 Aug 2008
Posts: 523
Location: Germany

PostPosted: Sat Mar 05, 2016 2:49 pm    Post subject: Reply with quote

khayyam wrote:

I did say to try =sys-boot/efibootmgr-0.5.4-r1 ... I don't think the issue is with your firmware.


Out of curiosity I've tried to use =sys-boot/efibootmgr-0.5.4-r1 to modify EFI on my computer. It failed. Well, it does add new entry, and it does set the boot order. But when I reboot, the EFI ignores new order and restores old one. So it keeps booting entry 0000, which is set for Microsoft boot. The added entry does not get deleted, but it is useless, since it is not possible to set the boot order. So everything works exactly as with version 0.12.
Back to top
View user's profile Send private message
khayyam
Watchman
Watchman


Joined: 07 Jun 2012
Posts: 6228
Location: Room 101

PostPosted: Sat Mar 05, 2016 8:39 pm    Post subject: Reply with quote

v_andal wrote:
khayyam wrote:
I did say to try =sys-boot/efibootmgr-0.5.4-r1 ... I don't think the issue is with your firmware.

Out of curiosity I've tried to use =sys-boot/efibootmgr-0.5.4-r1 to modify EFI on my computer. It failed. Well, it does add new entry, and it does set the boot order. But when I reboot, the EFI ignores new order and restores old one. So it keeps booting entry 0000, which is set for Microsoft boot. The added entry does not get deleted, but it is useless, since it is not possible to set the boot order. So everything works exactly as with version 0.12.

v_andal ... I suspect this is because efivarfs is enabled, and as =sys-boot/efibootmgr-0.5.4-r1 doesn't use it, the values there are not modified, and are written to NVRAM on shutdown. Try disabling efivarfs, and setting BootOrder to your bootloader/bootmanager.

best ... khay
Back to top
View user's profile Send private message
v_andal
Guru
Guru


Joined: 26 Aug 2008
Posts: 523
Location: Germany

PostPosted: Mon Mar 07, 2016 8:23 am    Post subject: Reply with quote

khayyam wrote:
I suspect this is because efivarfs is enabled, and as =sys-boot/efibootmgr-0.5.4-r1 doesn't use it, the values there are not modified, and are written to NVRAM on shutdown. Try disabling efivarfs, and setting BootOrder to your bootloader/bootmanager.


Sorry, but how do I disable efivars?
Back to top
View user's profile Send private message
khayyam
Watchman
Watchman


Joined: 07 Jun 2012
Posts: 6228
Location: Room 101

PostPosted: Mon Mar 07, 2016 1:08 pm    Post subject: Reply with quote

v_andal wrote:
khayyam wrote:
I suspect this is because efivarfs is enabled, and as =sys-boot/efibootmgr-0.5.4-r1 doesn't use it, the values there are not modified, and are written to NVRAM on shutdown. Try disabling efivarfs, and setting BootOrder to your bootloader/bootmanager.

Sorry, but how do I disable efivars?

v_andal ... not efivars, but efivarfs ... so CONFIG_EFIVAR_FS=n

best ... khay
Back to top
View user's profile Send private message
v_andal
Guru
Guru


Joined: 26 Aug 2008
Posts: 523
Location: Germany

PostPosted: Mon Mar 14, 2016 6:31 pm    Post subject: Reply with quote

Ok. I've removed support for efivarsfs from kernel. It didn't help a bit. The boot order settings are lost at reboot and boot entry 0 is booted instead on the one I'm creating. I'm telling you, it is just screwed up EFI :(

There's one thing though that might give some clue. When I compare Boot0000 that boots by default and the Boot0007 that is created by efibootmgr, then they look very different, even though point to the same device and partition.

Code:

Boot0000* Windows Boot Manager   ACPI(a0341d0,0)PCI(1f,2)03120a00000000000000HD(2,1f4800,82000,31948914-b49f-482c-8106-c5e2f1edd905)File(\EFI\Microsoft\Boot\bootmgfw.efi)RC
Boot0007* rEFInd   HD(2,1f4800,82000,31948914-b49f-482c-8106-c5e2f1edd905)File(\efi\refind\bootx64.efi)


Could it be, that EFI simply does not like the format of specification for new entries, so it just overrides them?
Back to top
View user's profile Send private message
saellaven
Guru
Guru


Joined: 23 Jul 2006
Posts: 509

PostPosted: Mon Mar 14, 2016 7:40 pm    Post subject: Reply with quote

Do you have the option of setting your boot order via your BIOS? Here's what my working system looks like

Code:

# efibootmgr -v
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000,0003,0006,0004,0005
Boot0000* Gentoo        VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0003* UEFI OS       HD(1,GPT,fadbf57a-0f43-4762-acef-d669667a0063,0x800,0x32000)/File(\EFI\BOOT\BOOTX64.EFI)
Boot0004* CD/DVD Drive  BBS(CDROM,,0x0)AMGOAMNO........u.H.L.-.D.T.-.S.T. .B.D.-.R.E. . .W.H.1.4.N.S.4.0...................A................................>..Gd-.;.A..MQ..L.9.K.D.2.I.3.2.E.2.7. .0. . . . . . . . .....AMBO
Boot0005* Hard Drive    BBS(HD,,0x0)AMGOAMNO........o.W.D.C. .W.D.1.0.0.2.F.A.E.X.-.0.0.Z.3.A.0...................A..........................>..Gd-.;.A..MQ..L. . . . .W. .-.D.C.W.T.A.C.R.4.1.0.4.7.9.....AMBOAMNO........o.W.D.C. .W.D.2.0.0.3.F.Z.E.X.-.0.0.Z.4.S.A.0...................A..........................>..Gd-.;.A..MQ..L. . . . .W. .-.D.M.W.1.C.1.F.2.0.4.6.3.1.....AMBOAMNO........o.S.a.m.s.u.n.g. .S.S.D. .8.5.0. .E.V.O. .2.5.0.G.B...................A..........................>..Gd-.;.A..MQ..L.2.S.5.R.X.N.H.A.3.1.2.6.0.9. .P. . . . .....AMBOAMNO........o.W.D.C. .W.D.6.4.0.1.A.A.L.S.-.0.0.L.3.B.2...................A..........................>..Gd-.;.A..MQ..L. . . . .W. .-.D.M.W.S.A.7.Y.0.5.3.0.2.2.....AMBOAMNO........y.G.e.n.e.r.i.c. .U.S.B. .S.D. .R.e.a.d.e.r...................A..................................@..Gd-.;.A..MQ..L.G.e.n.e.r.i.c. .U.S.B. .S.D. .R.e.a.d.e.r.....AMBOAMNO........].G.e.n.e.r.a.l. .U.D.i.s.k...................A......................0..Gd-.;.A..MQ..L.G.e.n.e.r.a.l. .U.D.i.s.k.....AMBO
Boot0006* UEFI: General UDisk   PciRoot(0x0)/Pci(0x12,0x2)/USB(3,0)/HD(1,MBR,0x49,0xac,0xf800)AMBO


Boot0005 is the legacy/non-UEFI option and option of last resort, mainly from when I was trying to get UEFI booting working... I left it just as an extra option just in case my SSD with my EFI partition on it dies.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum