Totally agree, too little or niche market! I 'm thinking about soldering simcard directly on these cheap minipci lte modem and use a regular usb2.0 cable, what a joke!

OK, I did not look into further details, I don't have any of this HW. I only have same experience 10 years ago, 4G module works in USB adapter, did not get it to work in mPCIE slot. I am not sure if a DeviceTree patch/change can fix it, don't know enough of that description principles. As indicated, SeeedStudio can read this, it is their HW, maybe they should fix it for you.

Thanks for your input, I never really use gpio lib and i don't know if gpio over i2c is userland playable or there are reserved to the kernel. The fact on the schematic is VSYS_3V3_EXP is the first rail powering up because it's supply I2Cs bus and the GPIO over I2C to switch ON or reseting thing. VCC5V0_DEVICE_S0 For FAN & HDMI & USB & TYPE-C, USB HUB (Total: 3A) switch on by RK806S over I2C (PMIC_PWR_CTRL2) VSYS_3V3_EXP For CSI & DSI & RPi 40Pin (Total: 4A) <======== I2Cs GPIO (LTE RESET), Minipcie is supplied here! , switch on by RK3576 gpio (VSYS_3V3_EXP_EN) VCC3V3_PCIE For PCIE-M.2 (nvme), switch on by RK3576 gpio (PCIE_PWREN_H_GPIO0B5) The design flaw is here : you need I2C up to put LTE modem (already on by the same I2C power supply) in reset state before switch on USB PHY, then release LTE_RESET. Why they didn't put LTE modem supply, triggering a 3.3vcc mosfet from USB 5V rail ready signal after usb init like normal usb device, too easy?

One thing that helped me in a similar situation was checking that the running kernel version matched the headers exactly with uname -r. A mismatch there can be really confusing. If you've recently upgraded the kernel, a reboot before installing the headers is worth trying too.

Hey guys, I just wanted some help from you regarding my X96Q. It is a 1+8GB Model with PCB Revision V1.1. It has a H313 processor but sunxi-fel reports H616. A few weeks ago I repaired the USB port of this box and I was successful in it and everything worked perfectly after that(the device booted up to android and worked perfectly) but Then I started to play with that Hidden button in AV port and I randomly clicked it and I thought it would be harmless but after that the device stuck in Red LED and didn't booted anything(possibly an EMMC Corruption). I tried Phoneix Suit first but it stuck on ram init. Then I brought a CP2102 Adapter to read the serial logs, and it turned out to be a Dram calibration errors where: Boot0 starts > Initializes The Emmc, the Board and the CPU -> Then the PMU(reported as AXP806 but physically AXP305) sets ram voltage to 1500mV -> Then it tries to Dram training -> fails and throws [...] "Read calibration error" multiple times —> keeps retrying until it gives up with "[...] Restraining final error." I investigated further and found that my emmc chip's critical sectors are corrupted. I used sunxi-fel to read the emmc and found that it fails to read after 16MB mark, means emmc got corrupted when I repeatedly pressed the AV port button. Now I tried a Armbian via sd card and it says: [...] Your Current DRAM Config isnt supported... Retrying... And keeps doing In a endless retry loop. Same for Miniarch, Armbian and many other builds... Any idea what's the problem with my box?