I've got OpenWrt running fine so far, the only issue is the modem, which is a Qualcomm modem (same as in the v4). It's being detected as QMI device and AT commands work as well. I'm already using @mrhaav modified uqmi which made it possible to have at least some response from it. But it doesn't register with the network, I've only got it this far with various configurations:
yeah the antennas are connected. The modem did work on stock, I've also tested two sim cards from different providers, no real change. I've added the setting to keep it searching (also yes, I changed the interface name to wan), but it's unable to find anything (or register?).
Tue Sep 5 17:02:44 2023 daemon.notice netifd: wan (1789): Waiting for modem to initiate
Tue Sep 5 17:02:46 2023 daemon.notice netifd: wan (1789): PINcode disabled
Tue Sep 5 17:02:46 2023 daemon.notice netifd: wan (1789): Data format set to raw-ip
Tue Sep 5 17:02:46 2023 daemon.notice netifd: wan (1789): Default profile: 1
Tue Sep 5 17:02:47 2023 daemon.notice netifd: wan (1789): not_registered on
Tue Sep 5 17:02:49 2023 daemon.notice netifd: wan (1789): not_registered on
Tue Sep 5 17:02:51 2023 daemon.notice netifd: wan (1789): not_registered on
Tue Sep 5 17:02:53 2023 daemon.notice netifd: wan (1789): not_registered on
Tue Sep 5 17:02:56 2023 daemon.notice netifd: wan (1789): not_registered on
Tue Sep 5 17:02:59 2023 daemon.notice netifd: wan (1789): not_registered on
Tue Sep 5 17:03:02 2023 daemon.notice netifd: wan (1789): not_registered on
Tue Sep 5 17:03:06 2023 daemon.notice netifd: wan (1789): not_registered on
Tue Sep 5 17:03:12 2023 daemon.notice netifd: wan (1789): not_registered on
Tue Sep 5 17:03:18 2023 daemon.notice netifd: wan (1789): not_registered on
Tue Sep 5 17:03:25 2023 daemon.notice netifd: wan (1789): not_registered on
Tue Sep 5 17:03:32 2023 daemon.notice netifd: wan (1789): not_registered on
Tue Sep 5 17:03:43 2023 daemon.notice netifd: wan (1789): not_registered on
Tue Sep 5 17:03:54 2023 daemon.notice netifd: wan (1789): not_registered on
Tue Sep 5 17:04:06 2023 daemon.notice netifd: wan (1789): not_registered on
Tue Sep 5 17:04:20 2023 daemon.notice netifd: wan (1789): not_registered on
Tue Sep 5 17:04:38 2023 daemon.notice netifd: wan (1789): not_registered on
Tue Sep 5 17:04:57 2023 daemon.notice netifd: wan (1789): not_registered on
Tue Sep 5 17:05:17 2023 daemon.notice netifd: wan (1789): not_registered on
Tue Sep 5 17:05:38 2023 daemon.notice netifd: wan (1789): not_registered on
Hm, I can't actually do that, picocom hangs when I try to enter the command. When I re-open picocom it hangs for a few seconds then greets me with "+CME ERROR: operation not allowed". Some logs and information about the device:
cat /sys/kernel/debug/usb/devices:
(Had to add the device ID manually so I can use the ttys)
at+cops=?
Terminating...
Skipping tty reset...
Thanks for using picocom
root@OpenWrt:~# picocom /dev/ttyUSB2
picocom v3.1
port is : /dev/ttyUSB2
flowcontrol : none
baudrate is : 9600
parity is : none
databits are : 8
stopbits are : 1
escape is : C-a
local echo is : no
noinit is : no
noreset is : no
hangup is : no
nolock is : no
send_cmd is : sz -vv
receive_cmd is : rz -vv -E
imap is :
omap is :
emap is : crcrlf,delbs,
logfile is : none
initstring : none
exit_after is : not set
exit is : no
Type [C-a] [C-h] to see available commands
Terminal ready
+CME ERROR: operation not allowed
ati
Manufacturer: QUALCOMM INCORPORATED
Model: 4108
Revision: MPSS.JO.2.0.2.c1.7-00034-9607_GENNS_PACK-1.280100.1 1 [Apr 20 2020 00:00:00]
SVN: 01
IMEI: - snip -
+GCAP: +CGSM
OK
option driver incorrectly bound to the ADB interface, hence the offset with tty numbers. But you figured that out.
Please try AT+COPS=?, you may need to wait for a response.