1. 12
  1. 2

    This article is completely incorrect about BIOS. As it happens, I have a workstation that uses BIOS and boots from NVMe..

    Also, while it mentions ARM and RISC-V, it completely misses information about POWER.

    1. 1

      While the CSM might provide the infrastructure for NVMe for BIOS calls, I really wouldn’t want to rely on them, considering NVMe postdates EFI.

      Power is a bit too varied with IPL path. While it’s tempting to just give the OpenPOWER one, I work on systems that have a completely different one.

      1. 2

        I don’t use CSM, but actual BIOS. I use coreboot with SeaBIOS and SeaBIOS supports booting from NVMe just fine. It’s not UEFI.

        1. 1

          considering NVMe postdates EFI.

          What does that have to do with anything? Even SATA post-dates the original BIOS int 13h interface (and, I think, but am not 100% sure about, the int 13h LBA extensions).

      2. 1

        A little while ago, I upgraded the motherboard in my NAS from one that was BIOS-only to one that was UEFI-only (no BIOS emulation). Unsurprisingly in retrospect, it then failed to boot. I was pleasantly surprised by how detailed the FreeBSD boot process documentation is (start from loader and follow the ‘see also’ links). I fortunately had a 16 GiB swap partition on each disk in my zpool, so I was able to (after booting from the USB install image) shrink these a little bit and create the EFI boot partitions and install the ZFS UEFI loader.