I’m having a problem that is similar to the one posted on 970 PRO NVMe M.2 1TB SSD is not detected on Xavier dev kit. I have two new Jetson Xavier AGX 32 development boards and I’m trying to use Samsung 970 PRO NMVe M.2 1TB drives in them. I have another unit that is using a Samsung 970 EVO NVMe M.2 1TB part and it works and the EVO is recognized by my new Xaviers, but the PRO is having issues.
Here’s the output from lspci -v
0000:00:00.0 PCI bridge: NVIDIA Corporation Device 1ad0 (rev a1) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 33
Bus: primary=00, secondary=01, subordinate=ff, sec-latency=0
Memory behind bridge: 40000000-400fffff
Capabilities: <access denied>
Kernel driver in use: pcieport
0000:01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981 (prog-if 02 [NVM Express])
Subsystem: Samsung Electronics Co Ltd Device a801
Flags: bus master, fast devsel, latency 0, IRQ 33
Memory at 1b40000000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: nvme
0001:00:00.0 PCI bridge: NVIDIA Corporation Device 1ad2 (rev a1) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 35
Bus: primary=00, secondary=01, subordinate=ff, sec-latency=0
I/O behind bridge: 00000000-00000fff
Memory behind bridge: 40000000-400fffff
Capabilities: <access denied>
Kernel driver in use: pcieport
0001:01:00.0 SATA controller: Marvell Technology Group Ltd. Device 9171 (rev 13) (prog-if 01 [AHCI 1.0])
Subsystem: Marvell Technology Group Ltd. Device 9171
Flags: bus master, fast devsel, latency 0, IRQ 821
I/O ports at 100010 [size=8]
I/O ports at 100020 [size=4]
I/O ports at 100018 [size=8]
I/O ports at 100024 [size=4]
I/O ports at 100000 [size=16]
Memory at 1230010000 (32-bit, non-prefetchable) [size=512]
Expansion ROM at 1230000000 [disabled] [size=64K]
Capabilities: <access denied>
Kernel driver in use: ahci
Here is the lsblk output:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop1 7:1 0 16M 1 loop
mmcblk0 179:0 0 29.1G 0 disk
├─mmcblk0p1 179:1 0 28G 0 part /
├─mmcblk0p2 179:2 0 160K 0 part
├─mmcblk0p3 179:3 0 160K 0 part
├─mmcblk0p4 179:4 0 4M 0 part
├─mmcblk0p5 179:5 0 4M 0 part
├─mmcblk0p6 179:6 0 1.4M 0 part
├─mmcblk0p7 179:7 0 1.4M 0 part
├─mmcblk0p8 179:8 0 512K 0 part
├─mmcblk0p9 179:9 0 512K 0 part
├─mmcblk0p10 179:10 0 2.5M 0 part
├─mmcblk0p11 179:11 0 2.5M 0 part
├─mmcblk0p12 179:12 0 64K 0 part
├─mmcblk0p13 179:13 0 64K 0 part
├─mmcblk0p14 179:14 0 1.5M 0 part
├─mmcblk0p15 179:15 0 1.5M 0 part
├─mmcblk0p16 179:16 0 1M 0 part
├─mmcblk0p17 179:17 0 1M 0 part
├─mmcblk0p18 179:18 0 160K 0 part
├─mmcblk0p19 179:19 0 160K 0 part
├─mmcblk0p20 179:20 0 1M 0 part
├─mmcblk0p21 179:21 0 1M 0 part
├─mmcblk0p22 179:22 0 2M 0 part
├─mmcblk0p23 179:23 0 2M 0 part
├─mmcblk0p24 179:24 0 1M 0 part
├─mmcblk0p25 179:25 0 1M 0 part
├─mmcblk0p26 179:26 0 128K 0 part
├─mmcblk0p27 179:27 0 128K 0 part
├─mmcblk0p28 179:28 0 128M 0 part
├─mmcblk0p29 179:29 0 128M 0 part
├─mmcblk0p30 179:30 0 63M 0 part
├─mmcblk0p31 179:31 0 512K 0 part
├─mmcblk0p32 259:0 0 64K 0 part
├─mmcblk0p33 259:1 0 64K 0 part
├─mmcblk0p34 259:2 0 80M 0 part
├─mmcblk0p35 259:3 0 80M 0 part
├─mmcblk0p36 259:4 0 512K 0 part
├─mmcblk0p37 259:5 0 512K 0 part
├─mmcblk0p38 259:6 0 4K 0 part
├─mmcblk0p39 259:7 0 8M 0 part
├─mmcblk0p40 259:8 0 8M 0 part
├─mmcblk0p41 259:9 0 300M 0 part
└─mmcblk0p42 259:10 0 324.7M 0 part
mmcblk0boot0 179:32 0 8M 1 disk
mmcblk0boot1 179:64 0 8M 1 disk
mmcblk0rpmb 179:96 0 4M 0 disk
zram0 252:0 0 2G 0 disk [SWAP]
zram1 252:1 0 2G 0 disk [SWAP]
zram2 252:2 0 2G 0 disk [SWAP]
zram3 252:3 0 2G 0 disk [SWAP]
zram4 252:4 0 2G 0 disk [SWAP]
zram5 252:5 0 2G 0 disk [SWAP]
zram6 252:6 0 2G 0 disk [SWAP]
zram7 252:7 0 2G 0 disk [SWAP]
nvme0n1 259:11 0 953.9G 0 disk
Running blkid does not return the expected /dev/nvme0n1.
Any suggestions?