Hello, I’m using this board with different scenarios. And now testing Quectel EP06-E modem in PCIe slot.
SW4 (12v) is OFF.
After power on with module - SIM2 led lights blue.
Already tried openwrt stable/snapshot, immortalwrt, rooter. But no any success to detect PCIe modem. lspci and lsusb utilities no show any modem.
When I used this modem with USB adapter, and connect to bpi - modem successful connected and showing as USB device.
Anyone have success to use PCIe modems with bpi4?
Hmm i am using the Quectel RM520N-GL over PCIe but i took the top one so the SW4 is not important for me… not sure about the other PCIe slots. i only know that the SIM card slot (btw all of them) are connected to the PCIe on the top side.
So you can use 3 sims with one modem but not 3 modems with 3 sims (with builtin sim slots).
If you looking on board inside, on both minipcie slots has mark SIM2 and SIM3.
But… anyway I have problem with module detection and not with sim detection
Look at this, CN12 can use the EC25 module.
Sorry some wrong informations i’ve got, and did not looked carefully enough at the board 
but this gives me also some interests about this, later i’ll try connecting a fibocom as second modem at the bottom pcie. lets see…
Yes I looked this link. Weird that ep06-e not detect as expected. But I using current openwrt firmware and tried few forks. Not sure about banana custom openwrt.
Yes it looks interesting use modems in mPCIe slots. That is why I testing. Let me know if any success, please
Just wanted to confirm that you see nothing about the device in the boot logs and running lspci doesn’t show anything? Can you provide your boot log?
Sure.
Right now i use openwrt build from source (main branch)
with kmod-mhi-* kmod-usb-serial-* packages
root@OpenWrt:~# dmesg | grep -i pci
[ 0.000000] Kernel command line: console=ttyS0,115200n1 pci=pcie_bus_perf root=/dev/fit0 rootwait
[ 0.017266] /soc/pcie@11280000: Fixed dependency cycle(s) with /soc/pcie@11280000/interrupt-controller
[ 0.017371] /soc/pcie@11290000: Fixed dependency cycle(s) with /soc/pcie@11290000/interrupt-controller
[ 0.017467] /soc/pcie@11300000: Fixed dependency cycle(s) with /soc/pcie@11300000/interrupt-controller
[ 0.017561] /soc/pcie@11310000: Fixed dependency cycle(s) with /soc/pcie@11310000/interrupt-controller
[ 0.035728] PCI: CLS 0 bytes, default 64
[ 0.072797] mtk-pcie-gen3 11280000.pcie: host bridge /soc/pcie@11280000 ranges:
[ 0.072815] mtk-pcie-gen3 11280000.pcie: Parsing ranges property...
[ 0.072829] mtk-pcie-gen3 11280000.pcie: IO 0x0020000000..0x00201fffff -> 0x0020000000
[ 0.072843] mtk-pcie-gen3 11280000.pcie: MEM 0x0020200000..0x0027ffffff -> 0x0020200000
[ 0.072944] mtk-pcie-gen3 11290000.pcie: host bridge /soc/pcie@11290000 ranges:
[ 0.072955] mtk-pcie-gen3 11290000.pcie: Parsing ranges property...
[ 0.072965] mtk-pcie-gen3 11290000.pcie: IO 0x0028000000..0x00281fffff -> 0x0028000000
[ 0.072975] mtk-pcie-gen3 11290000.pcie: MEM 0x0028200000..0x002fffffff -> 0x0028200000
[ 0.072994] /soc/pcie@11290000: Failed to get clk index: 0 ret: -517
[ 0.073003] mtk-pcie-gen3 11290000.pcie: failed to get clocks
[ 0.073068] mtk-pcie-gen3 11300000.pcie: host bridge /soc/pcie@11300000 ranges:
[ 0.073078] mtk-pcie-gen3 11300000.pcie: Parsing ranges property...
[ 0.073087] mtk-pcie-gen3 11300000.pcie: IO 0x0030000000..0x00301fffff -> 0x0030000000
[ 0.073096] mtk-pcie-gen3 11300000.pcie: MEM 0x0030200000..0x0037ffffff -> 0x0030200000
[ 0.073113] /soc/pcie@11300000: Failed to get clk index: 0 ret: -517
[ 0.073121] mtk-pcie-gen3 11300000.pcie: failed to get clocks
[ 0.073193] mtk-pcie-gen3 11310000.pcie: host bridge /soc/pcie@11310000 ranges:
[ 0.073203] mtk-pcie-gen3 11310000.pcie: Parsing ranges property...
[ 0.073212] mtk-pcie-gen3 11310000.pcie: IO 0x0038000000..0x00381fffff -> 0x0038000000
[ 0.073222] mtk-pcie-gen3 11310000.pcie: MEM 0x0038200000..0x003fffffff -> 0x0038200000
[ 0.073238] /soc/pcie@11310000: Failed to get clk index: 0 ret: -517
[ 0.073246] mtk-pcie-gen3 11310000.pcie: failed to get clocks
[ 1.972647] mtk-pcie-gen3 11280000.pcie: host bridge /soc/pcie@11280000 ranges:
[ 1.979957] mtk-pcie-gen3 11280000.pcie: Parsing ranges property...
[ 1.986240] mtk-pcie-gen3 11280000.pcie: IO 0x0020000000..0x00201fffff -> 0x0020000000
[ 1.994682] mtk-pcie-gen3 11280000.pcie: MEM 0x0020200000..0x0027ffffff -> 0x0020200000
[ 2.320303] mtk-pcie-gen3 11280000.pcie: PCIe link down, current LTSSM state: detect.quiet (0x1)
[ 2.329100] mtk-pcie-gen3 11280000.pcie: probe with driver mtk-pcie-gen3 failed with error -110
[ 2.338126] mtk-pcie-gen3 11290000.pcie: host bridge /soc/pcie@11290000 ranges:
[ 2.345440] mtk-pcie-gen3 11290000.pcie: Parsing ranges property...
[ 2.351709] mtk-pcie-gen3 11290000.pcie: IO 0x0028000000..0x00281fffff -> 0x0028000000
[ 2.360141] mtk-pcie-gen3 11290000.pcie: MEM 0x0028200000..0x002fffffff -> 0x0028200000
[ 2.680302] mtk-pcie-gen3 11290000.pcie: PCIe link down, current LTSSM state: detect.quiet (0x1)
[ 2.689083] mtk-pcie-gen3 11290000.pcie: probe with driver mtk-pcie-gen3 failed with error -110
[ 2.697946] mtk-pcie-gen3 11300000.pcie: host bridge /soc/pcie@11300000 ranges:
[ 2.705256] mtk-pcie-gen3 11300000.pcie: Parsing ranges property...
[ 2.711521] mtk-pcie-gen3 11300000.pcie: IO 0x0030000000..0x00301fffff -> 0x0030000000
[ 2.719950] mtk-pcie-gen3 11300000.pcie: MEM 0x0030200000..0x0037ffffff -> 0x0030200000
[ 3.040295] mtk-pcie-gen3 11300000.pcie: PCIe link down, current LTSSM state: detect.active (0x1000001)
[ 3.049681] mtk-pcie-gen3 11300000.pcie: probe with driver mtk-pcie-gen3 failed with error -110
[ 3.058527] mtk-pcie-gen3 11310000.pcie: host bridge /soc/pcie@11310000 ranges:
[ 3.065838] mtk-pcie-gen3 11310000.pcie: Parsing ranges property...
[ 3.072103] mtk-pcie-gen3 11310000.pcie: IO 0x0038000000..0x00381fffff -> 0x0038000000
[ 3.080537] mtk-pcie-gen3 11310000.pcie: MEM 0x0038200000..0x003fffffff -> 0x0038200000
[ 3.400305] mtk-pcie-gen3 11310000.pcie: PCIe link down, current LTSSM state: detect.quiet (0x1)
[ 3.409084] mtk-pcie-gen3 11310000.pcie: probe with driver mtk-pcie-gen3 failed with error -110
root@OpenWrt:~# lspci
root@OpenWrt:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux 6.12.44 xhci-hcd xHCI Host Controller
Bus 001 Device 002: ID 2109:2822 VIA Labs, Inc. USB2.0 Hub
Bus 001 Device 003: ID 2109:8822 VIA Labs, Inc. USB Billboard Device
Bus 002 Device 001: ID 1d6b:0003 Linux 6.12.44 xhci-hcd xHCI Host Controller
Bus 002 Device 002: ID 2109:0822 VIA Labs, Inc. USB3.1 Hub
there it looks like something found. but after reboot it shows again detect.quiet
not sure why it sometimes show detect.active … anyway no device detected correctly
I have some progress 
Switch modem usb mode to 2.0 with AT command:
AT+QUSBCFG="SS",0
After this setting modem recognized on startup and system shows device with lsusb command.
But I think it not as good as usb3/pcie mode (usb2 limitations?). Why modem trying to detect as USB device in mPCIe slot? And why usb3 is not possible?
Any suggestions to improve this?