If I remember my commands, the first attempt was how you would do it for old BIOS booting while the working attempt was for the newer UEFI booting. If on NVMe, you likely have to do UEFI booting as motherboards usually don't show NVMe drives in my experience. Always fun trying to track the headache of what changes with computers over time and glad you stuck with figuring out the solution.
Totally floored me at the end when you revealed you were doing this with version 13 instead of 15… but I thought the whole point of this video was to fix 15?
The gpart bootcode installation routines aren’t creating an entry in the EFI variables pointing to the newly installed FreeBSD loader. $GPTPARTITION/EFI/Boot/bootx64.efi is the fallback EFI boot loader location per the spec. I believe you should send an upstream bug report for this noncompliance with the spec.
What you saw done in this video was being done by the user and manually. If you see an issue with what FreeBSD's installer is doing then please open a PR if you know it to be in error. I remember a few things seemed a bit weird as the developers also have to focus on keeping it working despite the UEFI implementations not always following the spec either though I haven't followed it well enough to know what is done. Even if they deemed that they won't fix it for such compatibility reasons, it would be good to then have more confirmation out there that it is done wrong+why though if its just an issue and gets fixed then everyone is in a better state.
Thank you for your wonderful videos, because of them I fell in love with FreeBSD
Very cool thanks - just did a linux dual boot setup and now need to re-do my FreeBSD boot menu.
If I remember my commands, the first attempt was how you would do it for old BIOS booting while the working attempt was for the newer UEFI booting. If on NVMe, you likely have to do UEFI booting as motherboards usually don't show NVMe drives in my experience. Always fun trying to track the headache of what changes with computers over time and glad you stuck with figuring out the solution.
Hi Gary, you get both thumbs of me up!! 🙂 All the best, Norbert
Totally floored me at the end when you revealed you were doing this with version 13 instead of 15… but I thought the whole point of this video was to fix 15?
If there's something I'm an expert of.. its breaking FreeBSD, but I never manage to fix it ;)
2:20
subtitles are so America-centered. it mistook "spice" for "space" 😂
Yea, youtube subtitles be funny/bad like that at times.
♥️♥️♥️♥️♥️
"Promosm" 🍀
The gpart bootcode installation routines aren’t creating an entry in the EFI variables pointing to the newly installed FreeBSD loader. $GPTPARTITION/EFI/Boot/bootx64.efi is the fallback EFI boot loader location per the spec.
I believe you should send an upstream bug report for this noncompliance with the spec.
What you saw done in this video was being done by the user and manually. If you see an issue with what FreeBSD's installer is doing then please open a PR if you know it to be in error. I remember a few things seemed a bit weird as the developers also have to focus on keeping it working despite the UEFI implementations not always following the spec either though I haven't followed it well enough to know what is done. Even if they deemed that they won't fix it for such compatibility reasons, it would be good to then have more confirmation out there that it is done wrong+why though if its just an issue and gets fixed then everyone is in a better state.