I just installed this NVME drive and I attempted to find it on the Xavier but its not detectable at all, are there any specific drivers I need?
Is it a SATA-based internal SSD? If so, it won’t work on the Xavier.
If it’s actually PCIe based, then you should be able to see it with “lsblk”
Its PCIe, so its odd, I did do lsblk and it couldn’t see it, now dmesg did show a PCIE message. I think it could be a kernel issue but I already have NVME enabled for the kernel.
Here is the product:
It would be much more useful to see the dmesg message than a product page link …
Sorry I still have school, i’ll post it in an hour
[ 5.161476] tegra-thermal-throttle bthrot_cdev: cdev:aux-balanced max_state:52 cutoff:1 [ 5.162786] device-mapper: uevent: version 1.0.3 [ 5.163169] device-mapper: ioctl: 4.35.0-ioctl (2016-06-23) initialised: firstname.lastname@example.org [ 5.204850] tegra194_cpufreq_probe: platform driver Initialization: pass [ 5.210939] cpuidle: Initializing cpuidle driver [ 5.224098] sdhci: Secure Digital Host Controller Interface driver [ 5.224099] sdhci: Copyright(c) Pierre Ossman [ 5.224100] sdhci-pltfm: SDHCI platform and OF driver helper [ 5.226028] sdhci-tegra 3460000.sdhci: Client registration for eMC Successful [ 5.227375] tegra-se-elp 3ad0000.se_elp: tegra_se_elp_probe: complete [ 5.229154] sdhci-tegra 3400000.sdhci: Got CD GPIO [ 5.231116] sdhci-tegra 3400000.sdhci: Client registration for eMC Successful [ 5.232894] sdhci-tegra 3400000.sdhci: wakeup init done, cdirq 254 [ 5.273012] mmc0: SDHCI controller on 3460000.sdhci [3460000.sdhci] using ADMA 64-bit with 64 bit addr [ 5.281065] gpio tegra-gpio wake8 for gpio=55(G:7) [ 5.281138] mmc1: SDHCI controller on 3400000.sdhci [3400000.sdhci] using ADMA 64-bit with 64 bit addr [ 5.366085] mmc0: periodic cache flush enabled [ 5.366099] mmc0: new HS400 Enhanced strobe MMC card at address 0001 [ 5.366551] mmcblk0: mmc0:0001 HBG4a2 29.1 GiB [ 5.366816] mmcblk0boot0: mmc0:0001 HBG4a2 partition 1 8.00 MiB [ 5.367049] mmcblk0boot1: mmc0:0001 HBG4a2 partition 2 8.00 MiB [ 5.367327] mmcblk0rpmb: mmc0:0001 HBG4a2 partition 3 4.00 MiB [ 5.369013] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 p17 p18 p19 p20 p21 p22 p23 p24 p25 p26 p27 p28 p29 p30 p31 p32 p33 p34 p35 p36 [ 5.993709] tegradc 15210000.nvdisplay: fb registered
[ 1.109420] iommu: Adding device 14180000.pcie to group 0 [ 1.110390] iommu: Adding device 14100000.pcie to group 1 [ 1.111124] iommu: Adding device 14140000.pcie to group 2 [ 1.112193] iommu: Adding device 141a0000.pcie to group 3 [ 10.509696] tegra-pcie-dw 14180000.pcie: Setting init speed to max speed [ 10.517003] OF: PCI: host bridge /pcie@14180000 ranges: [ 11.047881] tegra-pcie-dw 14180000.pcie: link is down [ 11.049036] tegra-pcie-dw 14180000.pcie: PCI host bridge to bus 0000:00 [ 11.057291] pcieport 0000:00:00.0: Signaling PME through PCIe PME interrupt [ 11.058226] pcie_pme 0000:00:00.0:pcie001: service driver pcie_pme loaded [ 11.058339] aer 0000:00:00.0:pcie002: service driver aer loaded [ 11.058499] pcie_pme 0000:00:00.0:pcie001: unloading service driver pcie_pme [ 11.058550] aer 0000:00:00.0:pcie002: unloading service driver aer [ 11.059921] tegra-pcie-dw 14180000.pcie: PCIe link is not up...! [ 11.061740] tegra-pcie-dw 14100000.pcie: Setting init speed to max speed [ 11.064292] OF: PCI: host bridge /pcie@14100000 ranges: [ 11.177022] tegra-pcie-dw 14100000.pcie: link is up [ 11.178032] tegra-pcie-dw 14100000.pcie: PCI host bridge to bus 0001:00 [ 11.234776] pcieport 0001:00:00.0: Signaling PME through PCIe PME interrupt [ 11.247924] pcie_pme 0001:00:00.0:pcie001: service driver pcie_pme loaded [ 11.248059] aer 0001:00:00.0:pcie002: service driver aer loaded [ 11.248601] tegra-pcie-dw 14140000.pcie: Setting init speed to max speed [ 11.256140] OF: PCI: host bridge /pcie@14140000 ranges: [ 11.789121] tegra-pcie-dw 14140000.pcie: link is down [ 11.790433] tegra-pcie-dw 14140000.pcie: PCI host bridge to bus 0002:00 [ 11.801385] pcieport 0002:00:00.0: Signaling PME through PCIe PME interrupt [ 11.802633] pcie_pme 0002:00:00.0:pcie001: service driver pcie_pme loaded [ 11.802705] aer 0002:00:00.0:pcie002: service driver aer loaded [ 11.802852] pcie_pme 0002:00:00.0:pcie001: unloading service driver pcie_pme [ 11.802901] aer 0002:00:00.0:pcie002: unloading service driver aer [ 11.804644] tegra-pcie-dw 14140000.pcie: PCIe link is not up...! [ 11.807072] tegra-pcie-dw 141a0000.pcie: Setting init speed to max speed [ 11.809610] OF: PCI: host bridge /pcie@141a0000 ranges: [ 12.324314] tegra-pcie-dw 141a0000.pcie: link is down [ 12.325626] tegra-pcie-dw 141a0000.pcie: PCI host bridge to bus 0003:00 [ 12.336643] pcieport 0003:00:00.0: Signaling PME through PCIe PME interrupt [ 12.338721] pcie_pme 0003:00:00.0:pcie001: service driver pcie_pme loaded [ 12.338800] aer 0003:00:00.0:pcie002: service driver aer loaded [ 12.338939] pcie_pme 0003:00:00.0:pcie001: unloading service driver pcie_pme [ 12.338981] aer 0003:00:00.0:pcie002: unloading service driver aer [ 12.340767] tegra-pcie-dw 141a0000.pcie: PCIe link is not up...!
There is no obvious error message but just no device is detected.
Do you have other pcie devices that can make sure pcie host is still working fine?
Its incompatible with the Jetson it seems after long testing. I bought a different drive so its fine now,
Can you please try patches mentioned in
In the device tree entry of respective controller, can you set ‘num-lanes’ property to ‘2’?
(if you are connecting NVMe card directly to M.2 Key-M controller, then, you need to set this in ‘pcie@14180000’ node…or if you are connecting the card to x8 slot throgh a M.2 Key-M to x8 adapter, then this modification needs to be done in ‘pcie@141a0000’ node)
This is required because, this particular card is a x2 card (NVMe cards typically have x4 capability)