I put a Kingston KC3000 NVME SSD[1] in my new machine. This diff recognizes that device:
Index: pcidevs =================================================================== RCS file: /cvs/src/sys/dev/pci/pcidevs,v retrieving revision 1.2026 diff -u -p -r1.2026 pcidevs --- pcidevs 19 Mar 2023 09:38:06 -0000 1.2026 +++ pcidevs 19 Mar 2023 16:08:11 -0000 @@ -7010,6 +7010,7 @@ product JMICRON XD_2 0x2394 xD /* Kingston */ product KINGSTON A2000 0x2263 A2000 +product KINGSTON KC3000 0x5013 KC3000 product KINGSTON NV2 0x5019 NV2 /* Kioxia */ dmesg goes from: nvme0 at pci15 dev 0 function 0 vendor "Kingston", unknown product 0x5013 rev 0x01: msix, NVMe 1.4 nvme0: KINGSTON SKC3000D2048G, firmware EIFK31.6, serial 50026B76863F2586 scsibus1 at nvme0: 2 targets, initiator 0 sd0 at scsibus1 targ 1 lun 0: <NVMe, KINGSTON SKC3000, EIFK> sd0: 1953514MB, 512 bytes/sector, 4000797360 sectors to: nvme0 at pci15 dev 0 function 0 "Kingston KC3000" rev 0x01: msix, NVMe 1.4 nvme0: KINGSTON SKC3000D2048G, firmware EIFK31.6, serial 50026B76863F2586 scsibus1 at nvme0: 2 targets, initiator 0 sd0 at scsibus1 targ 1 lun 0: <NVMe, KINGSTON SKC3000, EIFK> sd0: 1953514MB, 512 bytes/sector, 4000797360 sectors It already works fine, so I'm not sure it's worth the extra bytes added to the kernel. Paul [1]: https://www.kingston.com/en/ssd/kc3000-nvme-m2-solid-state-drive -- >++++++++[<++++++++++>-]<+++++++.>+++[<------>-]<.>+++[<+ +++++++++++>-]<.>++[<------------>-]<+.--------------.[-] http://www.weirdnet.nl/
