Totally forgot to mention that. It’s tucked away inside a box, so I keep forgetting, it’s actually a Connectech carrier board.
And regarding the device tree, this is what I’m afraid of. I’ve no idea how to fiddle with those settings so I’m a bit stuck here. Was hoping I just didn’t mount the M2 drive properly, but it seems this would take a little bit more work to fix.
Not sure what get flashed to the board, I assumed everything is included in the Yocto build which another company build. I’m pretty sure it’s a customized device tree. I could possibly dig out the information - problem is I’m not really sure what to look for since I’m pretty new to this.
Just wanted to make sure it wasn’t an easy fix I overlooked - like mounting the device somehow. But I guess output of the commands I posted suggests that the board is NOT setup to detect an M2 drive.
I really don’t think this could be done by a end user. The debug of why a PCIe device may require kernel knowledge and also we may need to check the schematic of this carrier board.
As you are not the board vendor, it is unlikely you would have the schematic…
It is not related to any “mounting device”. The detection of a device is step by step. First, the lowest hardware interface needs to detect it. In your case, it means lspci shall see this device first. Afterwards it is device driver, for example, for nvme, the nvme driver needs to be enabled. That was what Honey_Patouceul tries to ask.
As your lspci does not have it, there is no need to check if nvme driver is missing.