[BUG] modem_ctrl.sh: vendor_get_disabled_features not found & PCI conflict on AW1000

[keyofworl]

Describe the Issue
Module: Quectel RG500Q-EA (PCIe)
Platform: Arcadyan AW1000 (IPQ807x)
Distribution: NoobWrt (Kernel 6.6.119)
ISP: Airtel (Sri Lanka) - 5G NSA

Problem: Cell locking fails when both the LTE Anchor and the NR cell share the same PCI (e.g., PCI 429). The system log shows a fatal script error in modem_ctrl.sh at line 190. Even though the modem is Qualcomm-based, it triggers a missing vendor function call which crashes the script logic.

Steps to Reproduce
Navigate to Modem -> Cell Locking in the NoobWrt WebUI.
Input a PCI value that is identical for both LTE and NR layers (e.g., 429).
Enter the EARFCN (1725) and ARFCN (628896) for Airtel 5G.
Click Apply Settings.
Observe the 5G attachment failure and check logread.

Expected Behavior
The modem should successfully lock to the specified PCI/ARFCN combination even if the PCI values are identical across layers, maintaining a stable 5G NSA connection.

Log Information

模组配置 (Module Configuration)

uci show qmodem (Privacy Masked)

qmodem.main=main
qmodem.main.enable_dial='1'
qmodem.main.try_preset_usb='1'
qmodem.main.try_preset_pcie='1'
qmodem.main.enable_pcie_scan='1'
qmodem.main.modem_count='1'
qmodem.pcie0=modem-slot
qmodem.pcie0.slot='0000:01:00.0'
qmodem.pcie0.type='pcie'
qmodem.4_1=modem-device
qmodem.4_1.name='rg500q-ea'
qmodem.4_1.manufacturer='quectel'
qmodem.4_1.platform='qualcomm'
qmodem.4_1.at_port='/dev/ttyUSB3'

系统日志 (System Logs)

daemon.err uhttpd[6366]: /usr/share/qmodem/modem_ctrl.sh: line 190: vendor_get_disabled_features: not found
daemon.err uhttpd[6366]: sh: 1: unknown operand
daemon.err uhttpd[6366]: awk: cmd. line:1: Unexpected token
daemon.err odhcp6c[12506]: Failed to send SOLICIT message (Network unreachable)

PCIe设备信息 (PCIe Devices)

lspci

0000:00:00.0 PCI bridge: Qualcomm Device 0108 (rev 01)
0000:01:00.0 Unassigned class [ff00]: Quectel Wireless Solutions Co., Ltd. RG500Q-EA LTE-A (PCIe Mode)

Additional Context (Script Analysis) I manually inspected /usr/share/qmodem/modem_ctrl.sh and found the following at line 190:

"get_disabled_features")
    json_add_array disabled_features
    vendor_get_disabled_features  # <--- Fails here (Line 190)
    get_modem_disabled_features
    get_global_disabled_features
    json_close_array
    ;;

The function vendor_get_disabled_features is undefined in the environment, causing the modem control script to crash during cell locking operations on this hardware.

[FUjr]

Which version do you use ? qmodem or qmodem-next
Try run lock cell command below manually to get further debug info
/usr/share/qmodem/modem_ctrl.sh set_neighborcell 4_1 '{"rat":1,"pci":"113","arfcn":"627264","band":"","scs":0}'
RAT: 1 for nr , 2 for lte
BAND: leave blank if lte and add prefix "50" to actual band like 5041
SCS: "0") scs="15" ;;
"1") scs="30" ;;
"2") scs="60" ;;
"3") scs="120" ;;
"4") scs="240" ;;

[FUjr]

And NR-NSA Or CA cell lock haven't support yet. If your module support this feature, you can refer to modem at manual and send at command manually.

[keyofworl]

GitHub Issue Body: Module: Quectel RG500Q-EA (PCIe) Platform: Arcadyan AW1000 (IPQ807x) Distribution: NoobWrt (Kernel 6.6.119) QModem Version: 3.0.0-r1 ISP: Airtel (Sri Lanka) - 5G NSA Problem: Cell locking fails when both LTE Anchor and NR cell share the same PCI (429). The script crashes at line 190, and manual AT commands return CME errors. Steps to Reproduce Navigate to Modem -> Cell Locking in WebUI. Input PCI 429 for both LTE (EARFCN 1725) and NR (ARFCN 628896). Click Apply Settings. Observe the script error in logread and the connection failure. Technical Analysis Script Bug: In /usr/share/qmodem/modem_ctrl.sh at line 190, the function vendor_get_disabled_features is called but is undefined in this environment, causing the script to terminate prematurely. CME ERROR 902: The modem rejects the parameters sent by the script, possibly due to the identical PCI conflict or incorrect band indexing for Qualcomm modules. CME ERROR 904: The common/4g locking command is not recognized by this specific RG500Q-EA firmware. Expected Behavior The script should handle Qualcomm-specific cell locking without calling missing vendor functions and should successfully apply locks even when LTE/NR share the same PCI.

…

On Thu, Mar 19, 2026, 9:15 AM Fu Jianrong ***@***.***> wrote: *FUjr* left a comment (FUjr/QModem#192) <#192 (comment)> And NR-NSA Or CA cell lock haven't support yet. If your module support this feature, you can refer to modem at manual and send at command manually. — Reply to this email directly, view it on GitHub <#192 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BB5MM2QDNEFKGQH53UIVY7T4RNUMJAVCNFSM6AAAAACWXNL542VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAOBXGU4DSMJXGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[keyofworl]

Module: Quectel RG500Q-EA Firmware: RG500QEAAAR13A01M4G The Issue: > Even with a 5G Smartphone IMEI (Pixel 7a), manually locking the cell to a known 5G tower results in no internet access or fallback to LTE only. Technical Details: Auto Mode: Modem connects to PCI 291 (B3). Internet works but speed is limited to ~800 Mbps. Manual Lock Attempt: I executed AT+QNWLOCK="common/4g",1,1725,429. Result: The modem successfully shows PCI 429 in AT+QENG="servingcell", but NR_Status becomes "NONE" or "SEARCHING", and no data flows. Comparison: My Poco F5 connects to the same PCI 429 (B3+B1+n78) and reaches 1.2 Gbps without any issues. Request: > Why does the RG500Q-EA fail to trigger the 5G NSA (n78) addition when the LTE anchor is manually locked to PCI 429? Is there a specific sequence or additional AT command needed to keep the NR carrier active during a manual lock?

…

On Thu, Mar 19, 2026, 9:24 AM Key of World ***@***.***> wrote: GitHub Issue Body: Module: Quectel RG500Q-EA (PCIe) Platform: Arcadyan AW1000 (IPQ807x) Distribution: NoobWrt (Kernel 6.6.119) QModem Version: 3.0.0-r1 ISP: Airtel (Sri Lanka) - 5G NSA Problem: Cell locking fails when both LTE Anchor and NR cell share the same PCI (429). The script crashes at line 190, and manual AT commands return CME errors. Steps to Reproduce Navigate to Modem -> Cell Locking in WebUI. Input PCI 429 for both LTE (EARFCN 1725) and NR (ARFCN 628896). Click Apply Settings. Observe the script error in logread and the connection failure. Technical Analysis Script Bug: In /usr/share/qmodem/modem_ctrl.sh at line 190, the function vendor_get_disabled_features is called but is undefined in this environment, causing the script to terminate prematurely. CME ERROR 902: The modem rejects the parameters sent by the script, possibly due to the identical PCI conflict or incorrect band indexing for Qualcomm modules. CME ERROR 904: The common/4g locking command is not recognized by this specific RG500Q-EA firmware. Expected Behavior The script should handle Qualcomm-specific cell locking without calling missing vendor functions and should successfully apply locks even when LTE/NR share the same PCI. On Thu, Mar 19, 2026, 9:15 AM Fu Jianrong ***@***.***> wrote: > *FUjr* left a comment (FUjr/QModem#192) > <#192 (comment)> > > And NR-NSA Or CA cell lock haven't support yet. If your module support > this feature, you can refer to modem at manual and send at command manually. > > — > Reply to this email directly, view it on GitHub > <#192 (comment)>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/BB5MM2QDNEFKGQH53UIVY7T4RNUMJAVCNFSM6AAAAACWXNL542VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAOBXGU4DSMJXGQ> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >