[SOLVED] Win10, slack-curr,FreeBSD UEFI boot order (chainload FBSD, maybe)
Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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
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
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)
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
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
Last edited by colorpurple21859; 10-29-2019 at 09:23 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
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.
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.
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.
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.
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,
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
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
I am booting off the m.2 and not that 2.5.. 
