On 2020-04-29, f.holop <min...@obiit.org> wrote:
> f.holop - Wed, 29 April 2020 at 14:57:46
>> i'll try to make a similar test with some linux live distro to see
>> if i get similar results.
>
> I have tested MX linux install ISO that also doubles as a Live distro.
>
> In the end it's apples and oranges because I use the openbsd USB key to
> boot the system from the internal drive ("boot hd1a:bsd"),
> while the Live Linux boots from the USB key and runs from RAM (so more
> like a beefed up "boot hd0a:bsd.rd")...
>
> Nevertheless linux detects the nvme drive in all cases (entering
> BIOS/not entering BIOS).Of course, because by that point it's running its own nvme driver in the kernel, not relying on bios/uefi. > This inspired me to let the openbsd USB key boot up all the way when the > internal drive was not detected in the first stage boot. The internal > drive was right there in `dmesg`, `sysctl hw`, `disklabel`, etc. I > could mount it while running off of the USB key. That's totally expected. As with Linux, by that point it's running its own nvme driver in the kernel. > "Elemental." With all these reboots I have worked out how this sorry > excuse for a BIOS's boot order mechanism works, and it's horrible: sounds pretty standard tbh :)
