FM350-GL and BE14 finally works on BPI-R4

Banana Pi Router design BPI-R4/BPI-R4 Pro(MT7988)
35 
OpenWrt 24.10.2, r28739-d9340319c6
 -----------------------------------------------------
root@OpenWrt:~# logread -f
Sat Jul  5 21:00:24 2025 daemon.info [2654]: <inf> [modem0] SIM is ready, and no need for the after SIM unlock step...
Sat Jul  5 21:00:24 2025 daemon.info [2654]: <inf> [modem0/sim0] loaded sim type: physical
Sat Jul  5 21:00:24 2025 daemon.info [2654]: <inf> [modem0/sim0] loaded SIM identifier: ###
Sat Jul  5 21:00:24 2025 daemon.info [2654]: <inf> [modem0/sim0] loaded IMSI: ###
Sat Jul  5 21:00:24 2025 daemon.info [2654]: <inf> [modem0/sim0] loaded operator identifier: 25099
Sat Jul  5 21:00:24 2025 daemon.info [2654]: <inf> [modem0/sim0] loaded operator name: Beeline
Sat Jul  5 21:00:24 2025 daemon.info [2654]: <inf> [modem0/sim0] loaded removability: removable
Sat Jul  5 21:00:24 2025 daemon.notice [2654]: <msg> [modem0] state changed (unknown -> disabled)
Sat Jul  5 21:00:24 2025 daemon.info ModemManager[2619]: hotplug: interface 'LTE' set '/sys/devices/platform/soc/11280000.pcie/pci0003:00/0003:00:00.0/0003:01:00.0' state available
Sat Jul  5 21:00:24 2025 daemon.notice netifd: Interface 'LTE' is setting up now
Sat Jul  5 21:00:24 2025 daemon.notice netifd: LTE (5320): modem available at /org/freedesktop/ModemManager1/Modem/0
Sat Jul  5 21:00:24 2025 daemon.info [2654]: <inf> [modem0] processing user request to enable modem...
Sat Jul  5 21:00:24 2025 daemon.notice [2654]: <msg> [modem0] state changed (disabled -> enabling)
Sat Jul  5 21:00:24 2025 daemon.notice [2654]: <msg> [modem0] power state updated: on
Sat Jul  5 21:00:24 2025 daemon.info [2654]: <inf> [modem0] checking if SIM was swapped...
Sat Jul  5 21:00:24 2025 daemon.info [2654]: <inf> [modem0] SIM identifier has not changed: ###
Sat Jul  5 21:00:24 2025 daemon.info [2654]: <inf> [modem0] SIM imsi has not changed: ###
Sat Jul  5 21:00:24 2025 daemon.notice [2654]: <msg> [modem0] 3GPP packet service state changed (unknown -> detached)
Sat Jul  5 21:00:24 2025 daemon.notice [2654]: <msg> [modem0] 3GPP packet service state changed (detached -> unknown)
Sat Jul  5 21:00:24 2025 daemon.notice [2654]: <msg> [modem0] 3GPP packet service state changed (unknown -> detached)
Sat Jul  5 21:00:24 2025 daemon.notice [2654]: <msg> [modem0] 3GPP packet service state changed (detached -> unknown)
Sat Jul  5 21:00:24 2025 user.notice podkop: 2025-07-05 21:00:24 DNS is unavailable [2/60]
Sat Jul  5 21:00:24 2025 daemon.info [2654]: <inf> [modem0] enabled modem
Sat Jul  5 21:00:24 2025 daemon.notice [2654]: <msg> [modem0] state changed (enabling -> enabled)
Sat Jul  5 21:00:24 2025 daemon.notice [2654]: <msg> [modem0] 3GPP registration state changed (unknown -> idle)
Sat Jul  5 21:00:24 2025 daemon.info [2654]: <inf> [modem0] consolidated registration state: cs 'idle', ps 'idle', eps 'idle', 5gs 'idle' --> 'idle'
Sat Jul  5 21:00:24 2025 daemon.notice [2654]: <msg> [modem0] 3GPP packet service state changed (unknown -> detached)
Sat Jul  5 21:00:24 2025 daemon.notice netifd: LTE (5320): successfully enabled the modem
Sat Jul  5 21:00:24 2025 daemon.warn [2654]: <wrn> [modem0] couldn't load operator code: Current operator MCC/MNC is still unknown
Sat Jul  5 21:00:24 2025 daemon.warn [2654]: <wrn> [modem0] couldn't load operator name: Current operator name is still unknown
Sat Jul  5 21:00:24 2025 daemon.warn [2654]: <wrn> [modem0] couldn't reload extended signal information: No signal details given
Sat Jul  5 21:00:24 2025 daemon.notice [2654]: <msg> [modem0] 3GPP packet service state changed (detached -> unknown)
Sat Jul  5 21:00:24 2025 daemon.notice netifd: LTE (5320): setting allowed mode to 'any'
Sat Jul  5 21:00:24 2025 daemon.notice [2654]: <msg> [modem0] 3GPP packet service state changed (unknown -> detached)
Sat Jul  5 21:00:24 2025 daemon.notice [2654]: <msg> [modem0] 3GPP packet service state changed (detached -> unknown)
Sat Jul  5 21:00:24 2025 daemon.info [2654]: <inf> [modem0] processing user request to set current modes to 'any' (preferred 'none')...
Sat Jul  5 21:00:24 2025 daemon.info [2654]: <inf> [modem0] current modes set to 'any' (preferred 'none')
Sat Jul  5 21:00:24 2025 daemon.notice netifd: LTE (5320): successfully set current modes in the modem
Sat Jul  5 21:00:24 2025 daemon.info [2654]: <inf> [modem0] processing user request to register modem...
Sat Jul  5 21:00:24 2025 daemon.notice [2654]: <msg> [modem0] 3GPP packet service state changed (unknown -> detached)
Sat Jul  5 21:00:24 2025 daemon.notice [2654]: <msg> [modem0] 3GPP packet service state changed (detached -> unknown)
Sat Jul  5 21:00:24 2025 daemon.info [2654]: <inf> [modem0] launching automatic network registration...
Sat Jul  5 21:00:25 2025 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) ee:b6:7a:03:b4:4d
Sat Jul  5 21:00:25 2025 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.1.180 ee:b6:7a:03:b4:4d
Sat Jul  5 21:00:25 2025 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) ee:b6:7a:03:b4:4d
Sat Jul  5 21:00:25 2025 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.1.180 ee:b6:7a:03:b4:4d
Sat Jul  5 21:00:25 2025 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) ee:b6:7a:03:b4:4d
Sat Jul  5 21:00:25 2025 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.1.180 ee:b6:7a:03:b4:4d
Sat Jul  5 21:00:25 2025 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.1.180 ee:b6:7a:03:b4:4d
Sat Jul  5 21:00:25 2025 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.1.180 ee:b6:7a:03:b4:4d Redmi-Note-12
Sat Jul  5 21:01:25 2025 user.notice podkop: 2025-07-05 21:01:25 ✅ DNS check passed
Sat Jul  5 21:01:25 2025 daemon.info podkop[3255]: [2025-07-05 21:01:25] ✅ DNS check passed
Sat Jul  5 21:01:27 2025 user.notice podkop: 2025-07-05 21:01:27 ✅ GitHub connection check passed
Sat Jul  5 21:01:27 2025 daemon.info podkop[3255]: [2025-07-05 21:01:27] ✅ GitHub connection check passed
Sat Jul  5 21:01:27 2025 user.notice podkop: 2025-07-05 21:01:27 📥 Downloading and processing lists...
Sat Jul  5 21:01:27 2025 daemon.info podkop[3255]: [2025-07-05 21:01:27] 📥 Downloading and processing lists...
Sat Jul  5 21:01:27 2025 user.notice podkop: 2025-07-05 21:01:27 Adding a srs list for main
Sat Jul  5 21:01:27 2025 daemon.err podkop[3255]: Downloading 'https://raw.githubusercontent.com/itdoginfo/allow-domains/main/Subnets/IPv4/meta.lst'
Sat Jul  5 21:01:27 2025 daemon.err podkop[3255]: Connecting to 185.199.109.133:443
Sat Jul  5 21:01:27 2025 daemon.err uhttpd[2523]: [info] luci: accepted login on /admin/network/network for root from 192.168.1.116
Sat Jul  5 21:01:27 2025 daemon.err podkop[3255]: Writing to '/tmp/podkop/meta.lst'
/tmp/podkop/meta.lst 100% |*******************************|   390   0:00:00 ETA
Sat Jul  5 21:01:27 2025 daemon.err podkop[3255]: Download completed (390 bytes)
Sat Jul  5 21:01:28 2025 user.notice podkop: 2025-07-05 21:01:28 ✅ Lists update completed successfully
Sat Jul  5 21:01:28 2025 daemon.info podkop[3255]: [2025-07-05 21:01:28] ✅ Lists update completed successfully
Sat Jul  5 21:01:29 2025 daemon.notice [2654]: <msg> [modem0] 3GPP registration state changed (idle -> registering)
Sat Jul  5 21:01:29 2025 daemon.info [2654]: <inf> [modem0] access technology changed (unknown -> lte)
Sat Jul  5 21:01:29 2025 daemon.notice [2654]: <msg> [modem0] 3GPP registration state changed (registering -> home)
Sat Jul  5 21:01:29 2025 daemon.info [2654]: <inf> [modem0] consolidated registration state: cs 'idle', ps 'idle', eps 'home', 5gs 'idle' --> 'home'
Sat Jul  5 21:01:29 2025 daemon.notice [2654]: <msg> [modem0] state changed (enabled -> registered)
Sat Jul  5 21:01:29 2025 daemon.notice [2654]: <msg> [modem0] 3GPP packet service state changed (unknown -> attached)
Sat Jul  5 21:01:29 2025 daemon.info [2654]: <inf> [modem0] currently registered in a 3GPP network
Sat Jul  5 21:01:29 2025 daemon.info [2654]: <inf> [modem0] modem registered
Sat Jul  5 21:01:29 2025 daemon.notice netifd: LTE (5320): successfully registered the modem
Sat Jul  5 21:01:29 2025 daemon.notice netifd: LTE (5320): starting connection with apn 'internet'...
Sat Jul  5 21:01:29 2025 daemon.info [2654]: <inf> [modem0] processing user request to connect modem...
Sat Jul  5 21:01:29 2025 daemon.info [2654]: <inf> [modem0]   apn: internet
Sat Jul  5 21:01:29 2025 daemon.info [2654]: <inf> [modem0]   ip type: ipv4
Sat Jul  5 21:01:29 2025 daemon.info [2654]: <inf> [modem0]   allowed auth: unknown
Sat Jul  5 21:01:29 2025 daemon.info [2654]: <inf> [modem0]   allow roaming: yes
Sat Jul  5 21:01:29 2025 daemon.notice [2654]: <msg> [modem0] simple connect started...
Sat Jul  5 21:01:29 2025 daemon.notice [2654]: <msg> [modem0] simple connect state (6/10): register
Sat Jul  5 21:01:29 2025 daemon.info [2654]: <inf> [modem0] already registered automatically in network '25099', automatic registration not launched...
Sat Jul  5 21:01:29 2025 daemon.notice [2654]: <msg> [modem0] simple connect state (7/10): wait to get packet service state attached
Sat Jul  5 21:01:29 2025 daemon.notice [2654]: <msg> [modem0] simple connect state (8/10): bearer
Sat Jul  5 21:01:29 2025 daemon.notice [2654]: <msg> [modem0] simple connect state (9/10): connect
Sat Jul  5 21:01:29 2025 daemon.notice [2654]: <msg> [modem0] state changed (registered -> connecting)
Sat Jul  5 21:01:30 2025 daemon.notice [2654]: <msg> [modem0] state changed (connecting -> connected)
Sat Jul  5 21:01:30 2025 daemon.notice [2654]: <msg> [modem0] simple connect state (10/10): all done
Sat Jul  5 21:01:30 2025 daemon.notice netifd: LTE (5320): successfully connected the modem
Sat Jul  5 21:01:30 2025 daemon.notice netifd: LTE (5320): signal refresh rate is not set
Sat Jul  5 21:01:30 2025 daemon.notice netifd: LTE (5320): network operator name: beeline
Sat Jul  5 21:01:30 2025 daemon.notice netifd: LTE (5320): network operator MCCMNC: 25099
Sat Jul  5 21:01:30 2025 daemon.notice netifd: LTE (5320): registration type: home
Sat Jul  5 21:01:30 2025 daemon.notice netifd: LTE (5320): access technology: lte
Sat Jul  5 21:01:30 2025 daemon.notice netifd: LTE (5320): signal quality: 29%
Sat Jul  5 21:01:30 2025 daemon.notice netifd: LTE (5320): IPv4 connection setup required in interface LTE: static
Sat Jul  5 21:01:30 2025 daemon.notice netifd: LTE (5320): adding IPv4 address 100.110.184.130, netmask 255.0.0.0
Sat Jul  5 21:01:30 2025 daemon.notice netifd: LTE (5320): adding default IPv4 route via 100.110.184.129
Sat Jul  5 21:01:30 2025 daemon.notice netifd: LTE (5320): adding primary DNS at 10.20.20.42
Sat Jul  5 21:01:30 2025 daemon.notice netifd: LTE (5320): adding secondary DNS at 194.186.191.1
Sat Jul  5 21:01:30 2025 daemon.notice netifd: Interface 'LTE' is now up
Sat Jul  5 21:01:30 2025 daemon.notice netifd: Network device 'wwan0' link is up
Sat Jul  5 21:01:30 2025 user.notice firewall: Reloading firewall due to ifup of LTE (wwan0)
Sat Jul  5 21:01:31 2025 daemon.warn odhcpd[2383]: No default route present, overriding ra_lifetime to 0!
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [238172493 10.0s] dns: exchange failed for privatemessages.roblox.com. IN A: context deadline exceeded
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [2399573794 9.99s] dns: exchange failed for apis.rbxcdn.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [1008583441 2.2s] dns: exchange failed for google.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [3906684420 5.79s] dns: exchange failed for www.msftconnecttest.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [1608415220 7.30s] dns: exchange failed for avatar.roblox.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [238172493 10.0s] dns: exchange failed for privatemessages.roblox.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [2196158962 7.30s] dns: exchange failed for catalog.roblox.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [3906684420 5.79s] dns: exchange failed for www.msftconnecttest.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [3906684420 5.79s] dns: exchange failed for www.msftconnecttest.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [544974295 9.99s] dns: exchange failed for accountsettings.roblox.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [2820587285 8.85s] dns: exchange failed for yandex.ru. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [1883894912 5.82s] dns: exchange failed for gvt1.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [4029139793 6.88s] dns: exchange failed for usermoderation.roblox.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [345816551 9.99s] dns: exchange failed for notifications.roblox.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [2820587285 8.85s] dns: exchange failed for yandex.ru. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [1008583441 2.2s] dns: exchange failed for google.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [1854031272 7.34s] dns: exchange failed for realtime-signalr.roblox.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [3906684420 5.79s] dns: exchange failed for www.msftconnecttest.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [345816551 9.99s] dns: exchange failed for notifications.roblox.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [1485172513 8.85s] dns: exchange failed for ad.mail.ru. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [1883894912 5.82s] dns: exchange failed for gvt1.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [3037132123 8.85s] dns: exchange failed for firebaselogging.googleapis.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [1485172513 8.85s] dns: exchange failed for ad.mail.ru. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [3906684420 5.79s] dns: exchange failed for www.msftconnecttest.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [3906684420 5.79s] dns: exchange failed for www.msftconnecttest.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [1194761271 9.99s] dns: exchange failed for economy.roblox.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [4029139793 6.88s] dns: exchange failed for usermoderation.roblox.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [1194761271 9.99s] dns: exchange failed for economy.roblox.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [3906684420 5.79s] dns: exchange failed for www.msftconnecttest.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [544974295 9.99s] dns: exchange failed for accountsettings.roblox.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [544974295 9.99s] dns: exchange failed for accountsettings.roblox.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [345816551 9.99s] dns: exchange failed for notifications.roblox.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [544974295 9.99s] dns: exchange failed for accountsettings.roblox.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [2196158962 7.30s] dns: exchange failed for catalog.roblox.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [345816551 9.99s] dns: exchange failed for notifications.roblox.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [2820587285 8.85s] dns: exchange failed for yandex.ru. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [1854031272 7.34s] dns: exchange failed for realtime-signalr.roblox.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [2399573794 9.99s] dns: exchange failed for apis.rbxcdn.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [1608415220 7.30s] dns: exchange failed for avatar.roblox.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [1883894912 5.82s] dns: exchange failed for gvt1.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [3065560359 361ms] dns: exchange failed for oene.rhward.net. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [3037132123 8.85s] dns: exchange failed for firebaselogging.googleapis.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [1485172513 8.85s] dns: exchange failed for ad.mail.ru. IN A: context canceled
Sat Jul  5 21:01:40 2025 daemon.err sing-box[5273]: ERROR[0019] [3037132123 8.85s] dns: exchange failed for firebaselogging.googleapis.com. IN A: context canceled
Sat Jul  5 21:01:40 2025 kern.alert kernel: [   42.445887] Unable to handle kernel paging request at virtual address ffffff7fc5ce4fff
Sat Jul  5 21:01:40 2025 kern.alert kernel: [   42.453818] Mem abort info:
Sat Jul  5 21:01:40 2025 kern.alert kernel: [   42.456600]   ESR = 0x0000000096000004
Sat Jul  5 21:01:40 2025 kern.alert kernel: [   42.460338]   EC = 0x25: DABT (current EL), IL = 32 bits
Sat Jul  5 21:01:40 2025 kern.alert kernel: [   42.465647]   SET = 0, FnV = 0
Sat Jul  5 21:01:40 2025 kern.alert kernel: [   42.468690]   EA = 0, S1PTW = 0
Sat Jul  5 21:01:40 2025 kern.alert kernel: [   42.471820]   FSC = 0x04: level 0 translation fault
Sat Jul  5 21:01:40 2025 kern.alert kernel: [   42.476692] Data abort info:
Sat Jul  5 21:01:40 2025 kern.alert kernel: [   42.479562]   ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000
Sat Jul  5 21:01:40 2025 kern.alert kernel: [   42.485040]   CM = 0, WnR = 0, TnD = 0, TagAccess = 0
Sat Jul  5 21:01:40 2025 kern.alert kernel: [   42.490081]   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
Sat Jul  5 21:01:40 2025 kern.alert kernel: [   42.495385] [ffffff7fc5ce4fff] address between user and kernel address ranges

> Впишите сюда текст цитаты`Текст «как есть» (без применения форматирования)`
36

Please use code tags (```, e.g. via <> button)

37

It seems that the modem successfully establishes a connection, but then a kernel panic occurs afterwards. Is the power supply voltage sufficient? For reference, I am using a PC-VP-BP143 AC adapter, as described here:

38

It still exhibits kernel panic using this card in pcie mode using the latest software packages.

39

Please try removing sing-box.

 -----------------------------------------------------
 OpenWrt 24.10.2, r28739-d9340319c6
 -----------------------------------------------------
root@bpi-r4:~# lspci -vvv | grep -A 50 "Wireless controller"
lspci: Unable to load libkmod resources: error -2
0003:01:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device 4d75 (rev 01)
        Subsystem: Device 1cf8:3500
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 115
        Region 0: Memory at 21800000 (64-bit, prefetchable) [size=32K]
        Region 2: Memory at 20800000 (64-bit, non-prefetchable) [size=8M]
        Region 4: Memory at 21000000 (64-bit, prefetchable) [size=8M]
        Capabilities: [80] Express (v2) Endpoint, IntMsgNum 0
                DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
                        ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 0W TEE-IO-
                DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+
                        RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
                        MaxPayload 256 bytes, MaxReadReq 256 bytes
                DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
                LnkCap: Port #1, Speed 8GT/s, Width x2, ASPM L0s L1, Exit Latency L0s <2us, L1 <8us
                        ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
                LnkCtl: ASPM Disabled; RCB 64 bytes, LnkDisable- CommClk+
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 8GT/s, Width x1 (downgraded)
                        TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
                DevCap2: Completion Timeout: Range ABCD, TimeoutDis+ NROPrPrP- LTR+
                         10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt+ EETLPPrefix-
                         EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
                         FRS- TPHComp- ExtTPHComp-
                         AtomicOpsCap: 32bit- 64bit- 128bitCAS-
                DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
                         AtomicOpsCtl: ReqEn-
                         IDOReq- IDOCompl- LTR+ EmergencyPowerReductionReq-
                         10BitTagReq- OBFF Disabled, EETLPPrefixBlk-
                LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- Retimer- 2Retimers- DRS-
                LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
                         Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
                         Compliance Preset/De-emphasis: -6dB de-emphasis, 0dB preshoot
                LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete+ EqualizationPhase1+
                         EqualizationPhase2+ EqualizationPhase3+ LinkEqualizationRequest-
                         Retimer- 2Retimers- CrosslinkRes: unsupported
        Capabilities: [d0] MSI-X: Enable+ Count=34 Masked-
                Vector table: BAR=0 offset=00004000
                PBA: BAR=0 offset=00000f80
        Capabilities: [e0] MSI: Enable- Count=1/32 Maskable+ 64bit+
                Address: 0000000000000000  Data: 0000
                Masking: 00000000  Pending: 00000000
        Capabilities: [f8] Power Management version 3
                Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
                Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [100 v1] Vendor Specific Information: ID=1556 Rev=1 Len=008 <?>
        Capabilities: [108 v1] Latency Tolerance Reporting
                Max snoop latency: 0ns
                Max no snoop latency: 0ns
root@bpi-r4:~#
40

upd. added mtk-feed build into folder

i build 24.10.3 with dtso overlay for disabling pcie on m2 slot

dtso + eeprom be14 patch and no more tweaks

maybe its useful for someone

its stable build with stock kernel (kmod’s install’s normally)

fw_setenv bootconf_extra 'mt7988a-bananapi-bpi-r4-disable-pcie2'

then reboot and cut power → now m2 pcie disabled and port in usb mode

2 Likes
41

thank you, ive been pulling my hair out over this issue and was just about to compile my own.

This should be included by standard in wrt

42

Uploaded openwrt-mtk-feed + atc + epm +3ginfo and some kmods for basic use

fw_setenv bootconf_extra ‘mt7988a-bananapi-bpi-r4-disable-pcie2’

same procedure to disable pcie mode for modem

43

Where is the source for this overlay? Do you only set status of pci2 to disabled?

1 Like
44

Yes, src - me =)

 /dts-v1/;
/plugin/;

/ {
    compatible = "bananapi,bpi-r4", "mediatek,mt7988";

    fragment@0 {
        target = <&pcie2>;
        __overlay__ {
            status = "disabled";
        };
    };
};
45

You could convert it like this (imho much more readable) and upstream it with description why this is useful

https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/

46

Thanks for the advice, but I have absolutely no experience with this. Could I ask you to do this, if it’s not too much trouble, thank you!

47

Should look like something like this

// SPDX-License-Identifier: (GPL-2.0 OR MIT)
/*
 * Copyright (C) 2023 MediaTek Inc.
 */

/dts-v1/;
/plugin/;

/ {
	compatible = "bananapi,bpi-r4", "mediatek,mt7988a";
};

&{/soc/pcie@11280000} {
	status = "disabled";
};

Put in the directory where mt7988a.dtsi is and add line in Makefile to let it compile like in my patch above

edit: added overlay to my repo

1 Like
48

Has anyone a compiled ready firmware, just to save time?

49
1 Like
50

Is there anyone already build with usb mode (fm-350-gl - HP version ) for the bpi-r4 2.5g version ?

1 Like
51

There’s a build shortly after this comment. [Banana BPI-R4] all related to MTK-SDK - #958 by darkeye - Community Builds, Projects & Packages - OpenWrt Forum

52

BPI-R4: PCIe resource conflict (Unaddressable device) and initialization failure with Fibocom FM350-GL (MT7988 / T700)

Description:

On Banana Pi BPI-R4 running OpenWrt (MediaTek Filogic 880 target, kernel 6.12), the Fibocom FM350-GL (MediaTek T700 5G modem, ID 14c3:4d75) fails to initialize properly when connected via PCIe.

While the device is detected by lspci, the kernel throws memory resource conflict errors during PCIe bridge initialization, preventing the driver from establishing communication.

Hardware & Environment:

  • Board: Banana Pi BPI-R4 (eMMC version)
  • Modem: Fibocom FM350-GL (MT7988/T700)
  • OS/Firmware: OpenWrt 25.12 (Kernel 6.12.94)

Kernel Logs (dmesg snippet):

Plaintext[ 8.065245] xhci-mtk 11200000.usb: supply vusb33 not found, using dummy regulator ... [ 20.354799] resource: Unaddressable device pcie@11280000 [mem 0x20200000-0x27ffffff] conflicts with [mem 0x21800000-0x21807fff] [ 20.366310] resource: Unaddressable device pcie@11280000 [mem 0x20200000-0x27ffffff] conflicts with [mem 0x20800000-0x20ffffff] [ 20.387189] mtk-pcie-gen3 11280000.pcie: msi#0x1 address_hi 0x0 address_lo 0x11280c00 data 1

lspci -nn Output:

Plaintext0003:00:00.0 PCI bridge [0604]: MEDIATEK Corp. MT7988 PCI Express Host Bridge [Filogic 880] [14c3:7988] (rev 01) 0003:01:00.0 Cellular controller/modem [0d40]: MEDIATEK Corp. T700 5G Modem [5G Solution 5000] [14c3:4d75] (rev 01)

Steps to Reproduce:

  1. Install Fibocom FM350-GL into the M.2 PCIe slot of BPI-R4.
  2. Boot OpenWrt.
  3. Check dmesg and lspci.

Expected Behavior:

The modem initializes successfully on the PCIe bus without memory region overlap/conflicts.

Actual Behavior:

Memory window collision occurs (resource: Unaddressable device ... conflicts with ...), and the modem remains unusable in PCIe mode.

53

The memory range mem 0x20200000–0x27fffff is pre-reserved by the system for PCIe MMIO. It appears this region has already been occupied by other components in the system, causing a conflict when PCIe attempts to allocate this memory.

  1. Please investigate the current system memory reservation status to identify which component is occupying mem 0x21800000–0x21807fff and mem 0x20800000–0x20ffffff.
  2. Simultaneously, please determine the size of MMIO memory the PCIe EP (Endpoint) currently requires, covering both I/O and Memory types.
54

Thanks for analyzing this. Here is the detailed breakdown of the system memory reservation and the Endpoint (EP) requirements based on /proc/iomem and lspci -v:

1. System Memory / proc/iomem Status: The ranges 20800000–20ffffff and 21800000–21807fff are not occupied by external system components. Instead, they are allocated inside the root bridge window 20200000–27ffffff (assigned to pcie@11280000) specifically for the modem endpoint (0003:01:00.0).

Here is the exact layout from /proc/iomem:

Plaintext20200000-27ffffff : pcie@11280000 20200000-20207fff : 0003:00:00.0 (PCI bridge) 20800000-20ffffff : 0003:01:00.0 (Modem non-prefetchable memory) 21800000-21807fff : 0003:01:00.0 (Modem prefetchable memory)

2. PCIe Endpoint (Fibocom FM350-GL / MT7988 T700) MMIO Requirements: According to lspci -v -s 0003:01:00.0, the modem requests the following memory resources:

  • BAR 0 (Prefetchable): size=32K (mapped at 21800000)
  • BAR 2 (Non-prefetchable): size=8M (mapped at 20800000)
  • BAR 4 (Prefetchable): size=8M (mapped at 21000000)

**3. Crucial Behavior Clue (Cold vs. Warm Initialization): It is very important to note that during cold initialization (the first power-on from a completely powered-off state), the modem registers successfully. The memory conflict and initialization failure occur specifically during warm initialization (reboots), suggesting an issue with how the mtk-pcie-gen3 driver or reset sequence handles state cleanup and re-initialization.

Summary: The total requested MMIO footprint by the endpoint is well within the 128MB host bridge window (20200000-27ffffff), yet the kernel throws “Unaddressable device… conflicts with…” during initialization. Could this be an issue with how the mtk-pcie-gen3 driver or the DTS sets up the window mapping/translation for this specific PCIe port?