LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware - Installation (https://www.linuxquestions.org/questions/slackware-installation-40/)
-   -   Win10, slack-curr,FreeBSD UEFI boot order (chainload FBSD, maybe) (https://www.linuxquestions.org/questions/slackware-installation-40/win10-slack-curr-freebsd-uefi-boot-order-chainload-fbsd-maybe-4175663386/)

BW-userx 10-29-2019 08:38 PM
Win10, slack-curr,FreeBSD UEFI boot order (chainload FBSD, maybe)
 
I finally got a UEFI installable WIN10 usb stick. Installed Win10, SLack-current UEFI w/o CMS.

installed efibootmgr how do I get it to get slack as first default boot?
every way this HP 840 g2 has its pick a sopt to try and boot uefi WINDOWS is first in order.

I have to elect the option to move down the line and find then select slacks UEFI..

when I installed this I did not install elio. I opt out and then booted again using the slack usb option to find all bootable OSes then used that to boot into the fresh install, then did this to get uefi grub
Code:
"grub-install --target=x86_64-efi /dev/sdb"
grub-mkconfig -o /boot/grub/grub.cfg
which gives me the
[/code]
mnt/EFI/slackware-14.2+/bootx64.efi
[/code]
which I had mounted when I did that, looking at it maybe it does not need to be mounted to get to it?????
Code:
# mount /dev/sdXy -t vfat /boot/efi
where X = drive and y = partition
# modprobe efivars
# efibootmgr -c -g -d /dev/sdX -p Y -w -L "Linux" -l '\EFI\Linux\bootx64.efi'
assuming that the grubx64.efi file had been copied to \EFI\Linux\bootx64.efi
where I changed it to
Code:
efibootmgr -c -g -d /dev/sdb  -L "Linux" -l '\mnt\EFI\Linux\bootx64.efi'

Code:
bash-5.0# efibootmgr -v
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000,0001
Boot0000* PCIe/M.2 SSD Drive        BBS(HD,,0x0).......................................................................
      dp: 05 01 09 00 02 00 00 00 00 / 7f ff 04 00
    data: 00 00 00 00 00 00 1f 00 00 00 02 00 00 00 01 01 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 13 00 00 00 00 00 00 00 02 00
Boot0001* Notebook Hard Drive        BBS(HD,,0x0).......................................................................
      dp: 05 01 09 00 02 00 00 00 00 / 7f ff 04 00
    data: 01 00 00 00 00 00 1f 00 00 00 02 00 00 00 01 01 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11 00 00 00 00 00 00 00 01 00
Boot0002* Linux        HD(1,GPT,b76085ae-9dfd-46ef-982a-91fe073e973e,0x800,0x64000)/File(\EFI\\boot\efi\grub.efi)L.slackware-14.2+.mnt/EFI/slackware-14.2+/bootx64.efi....................
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 40 06 00 00 00 00 00 ae 85 60 b7 fd 9d ef 46 98 2a 91 fe 07 3e 97 3e 02 02 / 04 04 34 00 5c 00 45 00 46 00 49 00 5c 00 5c 00 62 00 6f 00 6f 00 74 00 5c 00 65 00 66 00 69 00 5c 00 67 00 72 00 75 00 62 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
    data: 4c 00 73 6c 61 63 6b 77 61 72 65 2d 31 34 2e 32 2b 00 6d 6e 74 2f 45 46 49 2f 73 6c 61 63 6b 77 61 72 65 2d 31 34 2e 32 2b 2f 62 6f 6f 74 78 36 34 2e 65 66 69 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Boot0003* Windows Boot Manager        HD(1,GPT,b76085ae-9dfd-46ef-982a-91fe073e973e,0x800,0x64000)/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.}...3................
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 40 06 00 00 00 00 00 ae 85 60 b7 fd 9d ef 46 98 2a 91 fe 07 3e 97 3e 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 69 00 63 00 72 00 6f 00 73 00 6f 00 66 00 74 00 5c 00 42 00 6f 00 6f 00 74 00 5c 00 62 00 6f 00 6f 00 74 00 6d 00 67 00 66 00 77 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
    data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 34 00 37 00 39 00 35 00 7d 00 00 00 33 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
bash-5.0#
I am going to post this so I do not have to write everything all over again in case this does not work, I am going to do that mgr line again.
Code:

bash-5.0# ls /boot/efi/EFI
Boot  Microsoft  slackware-14.2+

bash-5.0# ls /boot/efi/EFI/slackware-14.2+
grubx64.efi

bash-5.0# ls /boot/efi/EFI/Boot
bootx64.efi

bash-5.0# ls /boot/efi/EFI/Microsoft
Boot  Recovery
this /boot/efi/EFI/Boot/bootx64.efi
boots WIN10

Code:
bash-5.0# mount /dev/sdb1 -t vfat /boot/efi
mount: /boot/efi: /dev/sdb1 already mounted on /boot/efi.
bash-5.0# modprobe efivars
bash-5.0# efibootmgr -c -g -d /dev/sdb -p Y -w -L "Linux" -l '\EFI\Linux\bootx64.efi'
invalid numeric value Y
why is the slashes backwards?
Code:
bash-5.0# ls /boot/efi/EFI/Microsoft
Boot  Recovery
bash-5.0# efibootmgr -c -g -d /dev/sdb -w -L "Linux" -l '\EFI\Linux\bootx64.efi'
efibootmgr: ** Warning ** : Boot0002 has same label Linux
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0004,0000,0001
Boot0000* PCIe/M.2 SSD Drive        BBS(HD,,0x0).......................................................................
Boot0001* Notebook Hard Drive        BBS(HD,,0x0).......................................................................
Boot0002* Linux        HD(1,GPT,b76085ae-9dfd-46ef-982a-91fe073e973e,0x800,0x64000)/File(\EFI\\boot\efi\grub.efi)L.slackware-14.2+.mnt/EFI/slackware-14.2+/bootx64.efi....................
Boot0003* Windows Boot Manager        HD(1,GPT,b76085ae-9dfd-46ef-982a-91fe073e973e,0x800,0x64000)/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.}...3................
Boot0004* Linux        HD(1,GPT,b76085ae-9dfd-46ef-982a-91fe073e973e,0x800,0x64000)/File(\EFI\Linux\bootx64.efi)

DELETED SOME ENTRIES and added again
Code:
bash-5.0# efibootmgr -Bb 0002
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0004,0000,0001
Boot0000* PCIe/M.2 SSD Drive        BBS(HD,,0x0).......................................................................
Boot0001* Notebook Hard Drive        BBS(HD,,0x0).......................................................................
Boot0003* Windows Boot Manager        HD(1,GPT,b76085ae-9dfd-46ef-982a-91fe073e973e,0x800,0x64000)/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.}...3................
Boot0004* Linux        HD(1,GPT,b76085ae-9dfd-46ef-982a-91fe073e973e,0x800,0x64000)/File(\EFI\Linux\bootx64.efi)
bash-5.0# efibootmgr -Bb 0004
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000,0001
Boot0000* PCIe/M.2 SSD Drive        BBS(HD,,0x0).......................................................................
Boot0001* Notebook Hard Drive        BBS(HD,,0x0).......................................................................
Boot0003* Windows Boot Manager        HD(1,GPT,b76085ae-9dfd-46ef-982a-91fe073e973e,0x800,0x64000)/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.}...3................
bash-5.0# efibootmgr -v
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000,0001
Boot0000* PCIe/M.2 SSD Drive        BBS(HD,,0x0).......................................................................
      dp: 05 01 09 00 02 00 00 00 00 / 7f ff 04 00
    data: 00 00 00 00 00 00 1f 00 00 00 02 00 00 00 01 01 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 13 00 00 00 00 00 00 00 02 00
Boot0001* Notebook Hard Drive        BBS(HD,,0x0).......................................................................
      dp: 05 01 09 00 02 00 00 00 00 / 7f ff 04 00
    data: 01 00 00 00 00 00 1f 00 00 00 02 00 00 00 01 01 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11 00 00 00 00 00 00 00 01 00
Boot0003* Windows Boot Manager        HD(1,GPT,b76085ae-9dfd-46ef-982a-91fe073e973e,0x800,0x64000)/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.}...3................
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 40 06 00 00 00 00 00 ae 85 60 b7 fd 9d ef 46 98 2a 91 fe 07 3e 97 3e 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 69 00 63 00 72 00 6f 00 73 00 6f 00 66 00 74 00 5c 00 42 00 6f 00 6f 00 74 00 5c 00 62 00 6f 00 6f 00 74 00 6d 00 67 00 66 00 77 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
    data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 34 00 37 00 39 00 35 00 7d 00 00 00 33 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
bash-5.0# ls /boot/EFI
ls: cannot access '/boot/EFI': No such file or directory
bash-5.0# ls /boot/efi
EFI
bash-5.0# ls /boot/efi/EFI
Boot  Microsoft  slackware-14.2+
bash-5.0# ls /boot/efi/EFI/slackware-14.2+
grubx64.efi
bash-5.0# efibootmgr -c -g -d /dev/sdb -p -L "slackware-14.2+"    '\EFI\slackware-14.2+\grubx64.efi'
invalid numeric value -L

bash-5.0# efibootmgr -c -g -d /dev/sdb -w -L "slackware-14.2+"    '\EFI\slackware-14.2+\grubx64.efi'
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0002,0000,0001
Boot0000* PCIe/M.2 SSD Drive        BBS(HD,,0x0).......................................................................
Boot0001* Notebook Hard Drive        BBS(HD,,0x0).......................................................................
Boot0003* Windows Boot Manager        HD(1,GPT,b76085ae-9dfd-46ef-982a-91fe073e973e,0x800,0x64000)/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.}...3................
Boot0002* slackware-14.2+        HD(1,GPT,b76085ae-9dfd-46ef-982a-91fe073e973e,0x800,0x64000)/File(\EFI\\boot\efi\grub.efi)\EFI\slackware-14.2+\grubx64.efi
bash-5.0#
bash-5.0# efibootmgr -v
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0002,0000,0001
Boot0000* PCIe/M.2 SSD Drive        BBS(HD,,0x0).......................................................................
      dp: 05 01 09 00 02 00 00 00 00 / 7f ff 04 00
    data: 00 00 00 00 00 00 1f 00 00 00 02 00 00 00 01 01 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 13 00 00 00 00 00 00 00 02 00
Boot0001* Notebook Hard Drive        BBS(HD,,0x0).......................................................................
      dp: 05 01 09 00 02 00 00 00 00 / 7f ff 04 00
    data: 01 00 00 00 00 00 1f 00 00 00 02 00 00 00 01 01 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11 00 00 00 00 00 00 00 01 00
Boot0002* slackware-14.2+        HD(1,GPT,b76085ae-9dfd-46ef-982a-91fe073e973e,0x800,0x64000)/File(\EFI\\boot\efi\grub.efi)\EFI\slackware-14.2+\grubx64.efi
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 40 06 00 00 00 00 00 ae 85 60 b7 fd 9d ef 46 98 2a 91 fe 07 3e 97 3e 02 02 / 04 04 34 00 5c 00 45 00 46 00 49 00 5c 00 5c 00 62 00 6f 00 6f 00 74 00 5c 00 65 00 66 00 69 00 5c 00 67 00 72 00 75 00 62 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
    data: 5c 45 46 49 5c 73 6c 61 63 6b 77 61 72 65 2d 31 34 2e 32 2b 5c 67 72 75 62 78 36 34 2e 65 66 69
Boot0003* Windows Boot Manager        HD(1,GPT,b76085ae-9dfd-46ef-982a-91fe073e973e,0x800,0x64000)/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.}...3................
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 40 06 00 00 00 00 00 ae 85 60 b7 fd 9d ef 46 98 2a 91 fe 07 3e 97 3e 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 69 00 63 00 72 00 6f 00 73 00 6f 00 66 00 74 00 5c 00 42 00 6f 00 6f 00 74 00 5c 00 62 00 6f 00 6f 00 74 00 6d 00 67 00 66 00 77 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
    data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 34 00 37 00 39 00 35 00 7d 00 00 00 33 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
bash-5.0#
I hope one can understand that..
what is this meaning.
Code:
efibootmgr -v
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0002,0000,0001
Boot0000* PCIe/M.2 SSD Drive
bootorder, 0002 is Slack, 0003 is WIN10, Boot0001* Notebook Hard Drive, Boot0000* PCIe/M.2 SSD Drive
which 0000 is current, and I am in slack current.

(NE ways, I'm rebooting to see the damage I might have done.)


Code:
bash-5.0# ls /boot/efi/EFI/
Boot  Linux  Microsoft        slackware-14.2+
bash-5.0# ls /boot/efi/EFI/Boot
bootx64.efi
in that Boot dir i for windows 10
I copied a SLack one off the USB Stick in to it to replace it, it gave me

grub>
it don't like that. only if I travel down to this vis the boot screen , then I can boot slack .. it resideds in the same location as Windows /boot/efi/EFI/slackware-14.2+/grubx64.efi

colorpurple21859 10-29-2019 08:54 PM
try this:
F10 at first boot to get into your bios settings, tab over to boot order, make os boot manager first in boot order, highlight os boot manager enter, use f5 f6 keys to move linux entry to top, f10 key to save, escspe out, exit and save. It is something like that

BW-userx 10-29-2019 09:27 PM
4 Attachment(s)
Quote:
Originally Posted by colorpurple21859 (Post 6052086)
try this:
F10 at first boot to get into your bios settings, tab over to boot order, make os boot manager first in boot order, highlight os boot manager enter, use f5 f6 keys to move linux entry to top, f10 key to save, escspe out, exit and save. It is something like that
I do not get that boot manager anymore,.. :( I am booting off the m.2 and not that 2.5..

Images should be in order of going through selections needed to boot slack uefi

1st photo, uses the /boot/efi/EFI/Boot/bootx64.efi file that is owned by Win10

if I can get it to work with SLacks bootx64.efi then vola I can switch my BIOS to not give me a wait state for multi boot in my BIOS then it will/should slip into slack grub boot that will ahve the options for slack win10

and I still have to figure out FreeBSD efi chain load, it too is having Issues with w 1080p screen. it boots 1024x768 efi boot screen


I am done for tonight, bed time. tomorrow I'll try some more Ideas.

colorpurple21859 10-29-2019 09:38 PM
Quote:
efibootmgr: ** Warning ** : Boot0002 has same label Linux
to prevent this
do this, you don't have to mount the efi partition for this to work
Code:
efibootmgr -c -d /dev/sdb -p 1 -l \\EFI\\slackware-14.2+\\bootx64.efi -L "Slackware"
change the sdb and 1 to match the drive and partition that /EFI/slackware-14.2+/bootx64.efi is located
use efibootmanager to change boot order then
efibootmgr -n -b xxxx to let slackware boot on the next reboot.

colorpurple21859 10-29-2019 09:45 PM
something to check
run gdisk your drive similar to this
Code:
gdisk /dev/sda
Found valid GPT with protective MBR; using GPT.

Command (? for help): v
this will be message if this is part of the problem


Code:
Warning: The 0xEE protective partition in the MBR is marked as active. This is technically a violation of the GPT specification, and can cause some EFIs to ignore the disk, but it is required to boot from a GPT disk on some BIOS-based computers. You can clear this flag by creating a fresh protective MBR using
the 'n' option on the experts' menu.

BW-userx 10-30-2019 06:47 AM
Quote:
Originally Posted by colorpurple21859 (Post 6052096)
something to check
run gdisk your drive similar to this
Code:
gdisk /dev/sda
Found valid GPT with protective MBR; using GPT.

Command (? for help): v
this will be message if this is part of the problem


Code:
Warning: The 0xEE protective partition in the MBR is marked as active. This is technically a violation of the GPT specification, and can cause some EFIs to ignore the disk, but it is required to boot from a GPT disk on some BIOS-based computers. You can clear this flag by creating a fresh protective MBR using
the 'n' option on the experts' menu.
Code:
bash-5.0# gdisk /dev/sdb
GPT fdisk (gdisk) version 1.0.4

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.

BW-userx 10-30-2019 06:49 AM
Quote:
Originally Posted by colorpurple21859 (Post 6052093)
to prevent this
do this, you don't have to mount the efi partition for this to work
Code:
efibootmgr -c -d /dev/sdb -p 1 -l \\EFI\\slackware-14.2+\\bootx64.efi -L "Slackware"
change the sdb and 1 to match the drive and partition that /EFI/slackware-14.2+/bootx64.efi is located
use efibootmanager to change boot order then
efibootmgr -n -b xxxx to let slackware boot on the next reboot.
there is NO bootx64.efi file in that dir. just this,
Code:
ls /boot/efi/EFI/slackware-14.2+
grubx64.efi
it's missing the bootx64.efi

colorpurple21859 10-30-2019 06:59 AM
change it to grubx64.efi, I was doing copy and pasting from where I had done something similar and forgot to change it to grubx64.efi.

from you gdisk ouput, you don't have the protective mbr problem. I came across that issue after I had installed fedora in legacy mode a while back.

BW-userx 10-30-2019 07:15 AM
this is what I got so far...
 
because this BIOS is stupid crazy. when using the M.2 stick for the main boot, it is dev/sdb for one, and therefore not allowed the boot manager for uefi. so work around needs to be put into place.

when I installed grub efi it did not give me a bootx64.efi
I got a grubx64.efi

after figuring out that it is windows 10 that is using the ../Boot/bootx64.efi. I moved that one into a different name. then copied over grubx64.efi into ../Boot giving it that default named.
Code:
bash-5.0# ls /boot/efi/EFI/Boot
bootx64.efi  ms-win10-bootx64.efi

cp -v  /boot/efi/EFI/slackware-14.2+/grubx64.efi /boot/efi/EFI/Boot/bootx64.efi
my little wrapper to deal with this updating grub, then copying over the resutls
Code:
bash-5.0$ cat /usr/local/bin/update-grub

sudo grub-mkconfig -o /boot/grub/grub.cfg
cp -v  /boot/efi/EFI/slackware-14.2+/grubx64.efi /boot/efi/EFI/Boot/bootx64.efi
mark it executable to it runs when called.

Now on to figuring out how to chain load FreeBSD efi style. the other way no longer worked. but I will most likely make sure of that too.


so it looks to be 1/2 completed here.

colorpurple21859 10-30-2019 07:37 AM
I've seen that where the uefi bios will only boot the bootx64.efi file.

BW-userx 10-30-2019 07:55 AM
Quote:
Originally Posted by colorpurple21859 (Post 6052206)
I've seen that where the uefi bios will only boot the bootx64.efi file.
somewhere is a previous post I put where I copied in the bootx64.efi off the stick and it gave me the good ole grub> prompt. so I after a bunch of configurations figuring out what this system is doing without a boot manager due to M.2 sdb being used. I figured it was just a name switch, being that I had a grubx64.efi and bootx64.efi seemed to be doing the same thing, loading grub.

I tried symlinking it but it would not let me, so I did the move it over and rename it trick. which is working. Now I am having a hair pulling experience (not that bad, but yeah) trying to figure out how to boot FreeBSD off of Linux grub now. with the ole style 40_custom entry not working any more due to it now also being efi boot, which works off the BIOS, I just need to get it to work off of Linux (slacks) grub boot menu.

BW-userx 10-30-2019 08:28 AM
Got It!
 
chainload efi FreeBSD
40_custiom
Code:
menuentry "FreeBSD 12" {
  set root=(hd1,7)
  chainloader /boot/boot1.efi
}
and I found out i did not need to copy over the grubx64.efi file each time after updating grub..


All times are GMT -5. The time now is 04:18 PM.