Opened 2 years ago

Last modified 2 years ago

#17753 new bug

SiFive Unmatched, odd EFI boot behavior with NVMe

Reported by: kallisti5 Owned by:
Priority: normal Milestone: Unscheduled
Component: System/Boot Loader/EFI Version: R1/beta3
Keywords: unmatched Cc:
Blocked By: Blocking:
Platform: riscv64

Description (last modified by kallisti5)

Configuration A:

  • u-boot on sd card
  • Haiku riscv64 + EFI bootriscv64.efi on USB drive

Result: System boots as expected, No issues.

Configuration A.1:

  • u-boot on sd card
  • Haiku riscv64 + EFI bootriscv64.efi on USB drive
  • NVMe with no partitions

Result: System boots as expected, No issues. NVMe can be partitioned from Haiku.

Configuration B:

  • u-boot on sd card
  • Haiku riscv64 + EFI bootriscv64.efi on USB drive
  • NVMe with empty GPT BFS partition

Result: EFI bootloader crashes at startup. (see attachment)

Configuration C:

  • u-boot on sd card
  • Haiku riscv64 + EFI bootriscv64.efi on USB drive
  • NVMe with empty GPT ext4 partition

Result: EFI bootloader finds no Haiku partitions to boot from. (see attachment)

This ticket is likely less related to NVMe and more related to the EFI discovery of disks between EFI and u-boot.

Attachments (2)

configuration_b.txt​ (12.7 KB ) - added by kallisti5 2 years ago.
configuration_c.txt​ (10.5 KB ) - added by kallisti5 2 years ago.

Download all attachments as: .zip

Change History (3)

by kallisti5, 2 years ago

Attachment: configuration_b.txt​ added

by kallisti5, 2 years ago

Attachment: configuration_c.txt​ added

comment:1 by kallisti5, 2 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.