This will be fairly short as I'm still suck on the nvme issue.

After armbian I tried ironrobin's arch iso and same issue, no nvme visible. After a bit more debugging I found that the system thinks nothing is plugged into the pci slot so there's nothing to initialize.

Here's what my log looks like:

[    4.055956] pci_bus 0002:00: root bus resource [bus 00-ff]
[    4.055974] pci_bus 0002:00: root bus resource [io  0x100000-0x1fffff] (bus address [0x0000-0xfffff])
[    4.055987] pci_bus 0002:00: root bus resource [mem 0x3c300000-0x3dffffff]
[    4.056036] pci 0002:00:00.0: [17cb:010e] type 01 class 0x060400
[    4.056063] pci 0002:00:00.0: reg 0x10: [mem 0x00000000-0x00000fff]
[    4.056163] pci 0002:00:00.0: PME# supported from D0 D3hot D3cold
[    4.057651] pci 0002:00:00.0: BAR 0: assigned [mem 0x3c300000-0x3c300fff]
[    4.057656] pci 0002:00:00.0: PCI bridge to [bus 01-ff]
[    4.058091] pcieport 0002:00:00.0: PME: Signaling with IRQ 202
[    4.060058] pcieport 0002:00:00.0: AER: enabled with IRQ 202

And here's what it should look like on a system where it works:

[    1.387786] pci_bus 0002:00: root bus resource [bus 00-ff]
[    1.387793] pci_bus 0002:00: root bus resource [io  0x100000-0x1fffff] (bus address [0x0000-0xfffff])
[    1.387795] pci 0006:00:00.0: [17cb:010e] type 01 class 0x060400
[    1.387798] pci_bus 0002:00: root bus resource [mem 0x3c300000-0x3dffffff]
[    1.387813] pci 0006:00:00.0: reg 0x10: [mem 0x00000000-0x00000fff]
[    1.387826] pci 0002:00:00.0: [17cb:010e] type 01 class 0x060400
[    1.387844] pci 0002:00:00.0: reg 0x10: [mem 0x00000000-0x00000fff]
[    1.387916] pci 0006:00:00.0: PME# supported from D0 D3hot D3cold
[    1.387933] pci 0002:00:00.0: PME# supported from D0 D3hot D3cold
[    1.393048] pci 0002:01:00.0: [1987:5013] type 00 class 0x010802
[    1.393061] pci 0006:01:00.0: [17cb:1103] type 00 class 0x028000
[    1.393237] pci 0002:01:00.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
[    1.393244] pci 0006:01:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit]
[    1.394377] pci 0006:01:00.0: PME# supported from D0 D3hot D3cold
[    1.406022] pci 0002:00:00.0: BAR 14: assigned [mem 0x3c300000-0x3c3fffff]
[    1.406032] pci 0002:00:00.0: BAR 0: assigned [mem 0x3c400000-0x3c400fff]
[    1.406039] pci 0002:01:00.0: BAR 0: assigned [mem 0x3c300000-0x3c303fff 64bit]
[    1.406084] pci 0002:00:00.0: PCI bridge to [bus 01-ff]
[    1.406088] pci 0002:00:00.0:   bridge window [mem 0x3c300000-0x3c3fffff]
[    1.407254] pcieport 0002:00:00.0: PME: Signaling with IRQ 198
[    1.408653] pcieport 0002:00:00.0: AER: enabled with IRQ 198
[    1.409064] nvme nvme0: pci function 0002:01:00.0
[    1.409078] nvme 0002:01:00.0: enabling device (0000 -> 0002)

I thought maybe there's a bug in detecting the device correctly so I tried to manually tell the system to load the hardware with the nvme driver:

# echo 0002:00:00.0 > /sys/bus/pci/drivers/pcieport/unbind
# echo 0002:00:00.0 > /sys/bus/pci/drivers/nvme/bind

But that didn't work either, it fails with:

bash: echo: write error: No such device

Which probably means driver refuses to work with device due to some check.

At this point there's not much to do. I'll try booting later with another drive but overall this is fairly frustrating since I seem to be the only one who is encountering such an issue despite everyone using the same hardware. I'm on the same 1.57 firmware and there aren't any settings in the UEFI that are related to this. If there are no updates for a while it doesn't mean I'm not trying, just that there's nothing to report.