It's Black Friday. People will see these KLEVV NVME's on sale, ergo this post. You may get this for Christmas.
Short version: Take the other NVME out; install Artix; put the other NVME back in. Done.
The KLEVV NVME's seem to work OK with other NVME's EXCEPT when installing Artix. When installing Artix (202308 and 2024 S6 ISO's) you get a "NVME [0 | 1] not ready. Aborting resets CSTS=0X1" error.
Reordering the NVME slots used is potentially a waste of your time.
Take the other NVME out (Crucial or PNY, in my case) and go through the ISO part of the install. After that, you can put the other NVME back in. This worked for me. It continues to work to finish the install, reboot, Pacman installs, normal operation, etc. thereafter.
If you already know the mechanics of this, just call me a newbie and have a Merry Christmas.
It's not Artix issue, not even a linux or OS issue. It's most likely mobo issue. This is because I've been through similar bullshit. Most AM4 boards have weird bios limitations when it comes to sharing PCI-E lanes. Although my story is somewhat different:
Take a look here (B450 Pro4):
(https://i.imgur.com/ChyJcoe.png)
When you occupy the top M.2 (M2_1) NVME slot, your 2nd x4 PCI-E (PCIE4) slot will be disabled.
When you occupy the bottom M.2 (M2_2) NVME slot, 2 SATA ports out of 6 will be disabled.
What they won't tell you is that you sometimes can't combine 2 NVME drives at once. I had 2 M.2 NVME drives, one slower at 512GB PCI-E x4 3.0 and one faster 1GB PCI-E x4 5.0, the vendor doesn't matter in this instance. Whatever I tried I couldn't get both drives detected at the same time. I had spare M.2 > PCI-E adapter that I used on my Intel Xeon x58 build with clover:
(https://i.imgur.com/2iI3ttg.jpeg)
What worked was:
1. Enabling SATA Hotplug
2. Getting the faster drive recognised first in UEFI with the PCI-E > M.2 adapter above at PCI-E x4 slot.
3. Boot to bios and shutdown
4. Plug the slower drive at the bottom M.2 NVME (M2_2) slot
5. At this point NONE of the SATA devices will work when you plug them when pc is off and coldboot but both NVME drives are now working fine, so you need to boot to OS (Linux/Windows - whatever) and now you need to plug your SATA devices one by one.
This humiliation ritual took over a week of troubleshooting half a year ago. But at least everything works...
So, whatever you experience now is probably attributed to how NVME devices are enumerated by UEFI.