On 08/02/2021 13:55, Johannes Brakensiek wrote:
On 8 Feb 2021, at 14:45, Mark Cave-Ayland wrote:This path looks wrong - according to the aliases listing at https://www.mail-archive.com/misc@openbsd.org/msg164291.html <https://www.mail-archive.com/misc@openbsd.org/msg164291.html> the unit address of the k2-sata device which is a child of the k2-sata-root device should be 0, whereas above it is given as -1? Perhaps something in ofpathname is subtracting 1 from the unit address of 0 when it shouldn't. Does the following alternative work? nvsetenv boot-device "/ht@0,f2000000/pci@5/k2-sata-root@c/@0/@0:2,\grub"This sounds reasonable. I had no luck with the env value set by the installer as well and changed it to the alias |hd:2,\grub| manually. Think the regular boot device will be |hd| in most cases. You may get the alias list using the command |devalias| in Open Firmware. Don’t know if there is a way to get this list from a running Linux.
Open Firmware aliases are resolved before they are placed into the bootpath property for the guest OS, so the booted kernel has no knowledge of them. In theory you could ask the PROM for the list of aliases, but since there are multiple representations of a single device node a simple string comparison between the aliases and bootpath wouldn't work reliably.
ATB, Mark.
