MOFI5500-5GXeLTE-EM7411-DUAL Latest firmware deleted my 2nd modem

[scorchen]

Recently updated the firmware on my MOFI5500-5GXeLTE-EM7411-DUAL router. I have 2 sim cards in this device. 1 tmobile, 1 verizon. After updating to the latest firmware 4.9.5-5500-std I no longer have the Internal Modem #2 on the configuration pages.

A little SSH'ing around and it looks like the 2nd device is still detected on USB

[root@MOFI5500:/sys/bus/usb-serial/drivers/generic]#lsusb
Bus 002 Device 003: ID 1199:9090 Sierra Wireless, Inc.
Bus 002 Device 005: ID 1199:9091 Sierra Wireless, Inc.
Bus 002 Device 002: ID 05e3:0626 Genesys Logic, Inc.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Let me know how much of an idiot I am internet. Thanks in advance

[Didneywhorl]

Clear your caches, or use a new browser and make sure you use the incognito feature when loading the UI.

[scorchen]

I've cleared cache as well as tried an entirely different browser and I do not believe this is the issue. Still missing the config pages for the 2nd Modem. Is it possible the 2nd modem died somehow? It was working prior to the firmware update

[Didneywhorl]

Not if you can still see it on the USB bus. Are they both EM7411s?

[scorchen]

Yes, they are both EM7411 Sierra Wireless modems that come with the MOFI5500 Dual sim router. I'm wondering if their latest firmware has an issue with dual modems or something. Working with their support as well, but they are slow to respond. Can i copy pasta any command information that may help someone with a more informed eye?

Here's a command i saw someone else run to spit out their USB infos:

[root@MOFI5500:/root]#dmesg | grep -i tty
[ 0.000000] Kernel command line: console=ttyS0,115200
[ 0.736138] console [ttyS0] disabled
[ 0.739703] 1e000c00.uartlite: ttyS0 at MMIO 0x1e000c00 (irq = 33, base_baud = 3125000) is a 16550A
[ 0.748706] console [ttyS0] enabled
[ 17.348521] usb 2-1.4: Qualcomm USB modem converter now attached to ttyUSB0
[ 17.363562] usb 2-1.3: Qualcomm USB modem converter now attached to ttyUSB1
[ 17.378710] usb 2-1.3: Qualcomm USB modem converter now attached to ttyUSB2
[ 17.394216] usb 2-1.3: Qualcomm USB modem converter now attached to ttyUSB3
[ 82.114700] qcserial ttyUSB1: Qualcomm USB modem converter now disconnected from ttyUSB1
[ 82.128970] qcserial ttyUSB2: Qualcomm USB modem converter now disconnected from ttyUSB2
[ 82.143294] qcserial ttyUSB3: Qualcomm USB modem converter now disconnected from ttyUSB3
[ 99.007738] usb 2-1.3: Qualcomm USB modem converter now attached to ttyUSB1
[ 99.023479] usb 2-1.3: Qualcomm USB modem converter now attached to ttyUSB2
[ 99.039759] usb 2-1.3: Qualcomm USB modem converter now attached to ttyUSB3

As well as
[root@MOFI5500:/root]#dmesg | grep -i usb
[ 9.424187] usbcore: registered new interface driver usbfs
[ 9.429803] usbcore: registered new interface driver hub
[ 9.435231] usbcore: registered new device driver usb
[ 9.825875] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 9.842904] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 9.858228] uhci_hcd: USB Universal Host Controller Interface driver
[ 9.878092] xhci-mtk 1e1c0000.usb: xHCI Host Controller
[ 9.883382] xhci-mtk 1e1c0000.usb: new USB bus registered, assigned bus number 1
[ 9.894223] xhci-mtk 1e1c0000.usb: hcc params 0x01401198 hci version 0x96 quirks 0x00210010
[ 9.902685] xhci-mtk 1e1c0000.usb: irq 29, io mem 0x1e1c0000
[ 9.909446] hub 1-0:1.0: USB hub found
[ 9.917767] xhci-mtk 1e1c0000.usb: xHCI Host Controller
[ 9.923023] xhci-mtk 1e1c0000.usb: new USB bus registered, assigned bus number 2
[ 9.930571] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[ 9.939727] hub 2-0:1.0: USB hub found
[ 10.284269] usb 2-1: new SuperSpeed USB device number 2 using xhci-mtk
[ 10.308030] hub 2-1:1.0: USB hub found
[ 10.455101] usb 1-1: new high-speed USB device number 2 using xhci-mtk
[ 10.629575] hub 1-1:1.0: USB hub found
[ 11.511171] usb 2-1.4: new SuperSpeed USB device number 3 using xhci-mtk
[ 11.699286] usb 2-1.3: new SuperSpeed USB device number 4 using xhci-mtk
[ 11.717337] usb 2-1.3: config 1 has an invalid interface number: 12 but max is 4
[ 11.724748] usb 2-1.3: config 1 has an invalid interface number: 13 but max is 4
[ 11.732153] usb 2-1.3: config 1 has an invalid interface number: 13 but max is 4
[ 11.739560] usb 2-1.3: config 1 has no interface number 1
[ 11.744968] usb 2-1.3: config 1 has no interface number 4
[ 17.297464] usbcore: registered new interface driver usbserial
[ 17.303591] usbcore: registered new interface driver usbserial_generic
[ 17.310342] usbserial: USB Serial support registered for generic
[ 17.321165] usbcore: registered new interface driver qcserial
[ 17.327123] usbserial: USB Serial support registered for Qualcomm USB modem
[ 17.334389] usbserial: USB Serial support registered for Qualcomm USB modem
[ 17.341611] qcserial 2-1.4:1.0: Qualcomm USB modem converter detected
[ 17.348521] usb 2-1.4: Qualcomm USB modem converter now attached to ttyUSB0
[ 17.356306] qcserial 2-1.3:1.0: Qualcomm USB modem converter detected
[ 17.363562] usb 2-1.3: Qualcomm USB modem converter now attached to ttyUSB1
[ 17.371509] qcserial 2-1.3:1.2: Qualcomm USB modem converter detected
[ 17.378710] usb 2-1.3: Qualcomm USB modem converter now attached to ttyUSB2
[ 17.386777] qcserial 2-1.3:1.3: Qualcomm USB modem converter detected
[ 17.394216] usb 2-1.3: Qualcomm USB modem converter now attached to ttyUSB3
[ 17.403948] usbcore: registered new interface driver option
[ 17.409818] usbserial: USB Serial support registered for GSM modem (1-port)
[ 17.936554] usbcore: registered new interface driver cdc_wdm
[ 17.970102] usbcore: registered new interface driver ipheth
[ 18.081210] usbcore: registered new interface driver usb-storage
[ 18.092120] usbcore: registered new interface driver usblp
[ 18.184745] usbcore: registered new interface driver cdc_ether
[ 18.195333] usbcore: registered new interface driver cdc_ncm
[ 18.253142] usbcore: registered new interface driver qmi_wwan
[ 18.262268] usbcore: registered new interface driver rndis_host
[ 18.284452] cdc_mbim 2-1.3:1.12: cdc-wdm0: USB WDM device
[ 18.291727] cdc_mbim 2-1.3:1.12 module1: register 'cdc_mbim' at usb-1e1c0000.usb-1.3, CDC MBIM, ea:82:90:c3:45:ae
[ 18.302313] usbcore: registered new interface driver cdc_mbim
[ 82.108980] usb 2-1.3: USB disconnect, device number 4
[ 82.114700] qcserial ttyUSB1: Qualcomm USB modem converter now disconnected from ttyUSB1
[ 82.128970] qcserial ttyUSB2: Qualcomm USB modem converter now disconnected from ttyUSB2
[ 82.143294] qcserial ttyUSB3: Qualcomm USB modem converter now disconnected from ttyUSB3
[ 82.157245] cdc_mbim 2-1.3:1.12 module1: unregister 'cdc_mbim' usb-1e1c0000.usb-1.3, CDC MBIM
[ 98.946226] usb 2-1.3: new SuperSpeed USB device number 5 using xhci-mtk
[ 98.964109] usb 2-1.3: config 1 has an invalid interface number: 12 but max is 4
[ 98.971511] usb 2-1.3: config 1 has an invalid interface number: 13 but max is 4
[ 98.978905] usb 2-1.3: config 1 has an invalid interface number: 13 but max is 4
[ 98.986302] usb 2-1.3: config 1 has no interface number 1
[ 98.991700] usb 2-1.3: config 1 has no interface number 4
[ 99.000429] qcserial 2-1.3:1.0: Qualcomm USB modem converter detected
[ 99.007738] usb 2-1.3: Qualcomm USB modem converter now attached to ttyUSB1
[ 99.016267] qcserial 2-1.3:1.2: Qualcomm USB modem converter detected
[ 99.023479] usb 2-1.3: Qualcomm USB modem converter now attached to ttyUSB2
[ 99.032332] qcserial 2-1.3:1.3: Qualcomm USB modem converter detected
[ 99.039759] usb 2-1.3: Qualcomm USB modem converter now attached to ttyUSB3
[ 99.061316] cdc_mbim 2-1.3:1.12: cdc-wdm0: USB WDM device
[ 99.068836] cdc_mbim 2-1.3:1.12 module1: register 'cdc_mbim' at usb-1e1c0000.usb-1.3, CDC MBIM, ea:82:90:c3:45:ae

[Didneywhorl]

Bus 002 Device 003: ID 1199:9090 Sierra Wireless, Inc.
Bus 002 Device 005: ID 1199:9091 Sierra Wireless, Inc.

This one jumps out at me. The USB ID of each should be the same. 1199 is Sierra, but the PID of the EM7411 I don't think should be either 9090 or 9091

Can you send AT commands to the one you do show:
First send:

Code: Select all

AT!ENTERCND="A710"

then

Code: Select all

ati

and

Code: Select all

at!usbvid

and

Code: Select all

at!usbpid

Show the output from each command, except the first. The first should just respond with "OK"

[scorchen]

ati
Manufacturer: Sierra Wireless, Incorporated
Model: EM7411
Revision: SWI9X50C_01.14.13.00 883709 jenkins 2022/01/05 07:08:35
IMEI: ****** (EDITED FOR PRIVACY)
IMEI SV: 14
FSN: 8F1374212202B1
+GCAP: +CGSM


All the others just say OK

[Didneywhorl]

All the others just say OK

add a ? on the end and send again, sorry

[scorchen]

at!usbpid?
!USBPID:
APP : 9091
BOOT: 9090


at!usbvid?
!USBVID:
1199

[Didneywhorl]

in the SSH, run:

Code: Select all

ls /dev/*

[scorchen]

[root@MOFI5500:/root]#ls -alh /dev/*
crw------- 1 root root 10, 234 Dec 31 1969 /dev/btrfs-control
crw------- 1 root root 180, 176 Dec 11 22:40 /dev/cdc-wdm0
crw------- 1 root root 5, 1 Dec 31 1969 /dev/console
crw------- 1 root root 10, 63 Dec 31 1969 /dev/cpu_dma_latency
crw-rw-rw- 1 root root 1, 7 Dec 31 1969 /dev/full
crw------- 1 root root 10, 229 Dec 11 22:38 /dev/fuse
crw------- 1 root root 10, 183 Dec 31 1969 /dev/hwrng
crw------- 1 root root 89, 0 Dec 31 1969 /dev/i2c-0
crw------- 1 root root 1, 2 Dec 31 1969 /dev/kmem
crw------- 1 root root 1, 11 Dec 31 1969 /dev/kmsg
srw-rw-rw- 1 root root 0 Dec 11 22:38 /dev/log
crw------- 1 root root 1, 1 Dec 31 1969 /dev/mem
crw------- 1 root root 10, 60 Dec 31 1969 /dev/memory_bandwidth
lrwxrwxrwx 1 root root 12 Dec 11 22:38 /dev/modem1 -> /dev/ttyUSB3
crw------- 1 root root 90, 0 Dec 31 1969 /dev/mtd0
crw------- 1 root root 90, 1 Dec 31 1969 /dev/mtd0ro
crw------- 1 root root 90, 2 Dec 31 1969 /dev/mtd1
crw------- 1 root root 90, 3 Dec 31 1969 /dev/mtd1ro
crw------- 1 root root 90, 4 Dec 31 1969 /dev/mtd2
crw------- 1 root root 90, 5 Dec 31 1969 /dev/mtd2ro
crw------- 1 root root 90, 6 Dec 31 1969 /dev/mtd3
crw------- 1 root root 90, 7 Dec 31 1969 /dev/mtd3ro
crw------- 1 root root 90, 8 Dec 31 1969 /dev/mtd4
crw------- 1 root root 90, 9 Dec 31 1969 /dev/mtd4ro
crw------- 1 root root 90, 10 Dec 31 1969 /dev/mtd5
crw------- 1 root root 90, 11 Dec 31 1969 /dev/mtd5ro
crw------- 1 root root 90, 12 Dec 31 1969 /dev/mtd6
crw------- 1 root root 90, 13 Dec 31 1969 /dev/mtd6ro
crw------- 1 root root 90, 14 Dec 31 1969 /dev/mtd7
crw------- 1 root root 90, 15 Dec 31 1969 /dev/mtd7ro
brw------- 1 root root 31, 0 Dec 31 1969 /dev/mtdblock0
brw------- 1 root root 31, 1 Dec 31 1969 /dev/mtdblock1
brw------- 1 root root 31, 2 Dec 31 1969 /dev/mtdblock2
brw------- 1 root root 31, 3 Dec 31 1969 /dev/mtdblock3
brw------- 1 root root 31, 4 Dec 31 1969 /dev/mtdblock4
brw------- 1 root root 31, 5 Dec 31 1969 /dev/mtdblock5
brw------- 1 root root 31, 6 Dec 31 1969 /dev/mtdblock6
brw------- 1 root root 31, 7 Dec 31 1969 /dev/mtdblock7
crw------- 1 root root 10, 62 Dec 31 1969 /dev/network_latency
crw------- 1 root root 10, 61 Dec 31 1969 /dev/network_throughput
crw-rw-rw- 1 root root 1, 3 Dec 31 1969 /dev/null
crw------- 1 root root 252, 0 Dec 31 1969 /dev/otp
crw------- 1 root root 1, 4 Dec 31 1969 /dev/port
crw------- 1 root root 108, 0 Dec 11 22:38 /dev/ppp
crw-rw-rw- 1 root root 5, 2 Dec 12 11:00 /dev/ptmx
crw-rw-rw- 1 root root 1, 8 Dec 31 1969 /dev/random
lrwxrwxrwx 1 root root 8 Dec 31 1969 /dev/shm -> /tmp/shm
crw-rw-rw- 1 root root 5, 0 Dec 31 1969 /dev/tty
crw------- 1 root root 4, 64 Dec 31 1969 /dev/ttyS0
crw------- 1 root root 4, 65 Dec 31 1969 /dev/ttyS1
crw------- 1 root root 4, 66 Dec 31 1969 /dev/ttyS2
crw------- 1 root root 188, 0 Dec 12 10:20 /dev/ttyUSB0
crw------- 1 root root 188, 1 Dec 12 10:22 /dev/ttyUSB1
crw------- 1 root root 188, 2 Dec 12 10:22 /dev/ttyUSB2
crw------- 1 root root 188, 3 Dec 12 11:00 /dev/ttyUSB3
crw------- 1 root root 10, 59 Dec 31 1969 /dev/ubi_ctrl
crw-rw-rw- 1 root root 1, 9 Dec 31 1969 /dev/urandom
crw-rw-rw- 1 root root 1, 5 Dec 31 1969 /dev/zero

/dev/bus:
drwxr-xr-x 3 root root 60 Dec 31 1969 .
drwxr-xr-x 5 root root 1.2K Dec 11 22:40 ..
drwxr-xr-x 4 root root 80 Dec 31 1969 usb

/dev/net:
drwxr-xr-x 2 root root 60 Dec 11 22:38 .
drwxr-xr-x 5 root root 1.2K Dec 11 22:40 ..
crw------- 1 root root 10, 200 Dec 11 22:38 tun

/dev/pts:
drwxr-xr-x 2 root root 0 Dec 31 1969 .
drwxr-xr-x 5 root root 1.2K Dec 11 22:40 ..
crw--w--w- 1 root root 136, 0 Dec 12 11:00 0
crw--w--w- 1 root root 136, 1 Dec 12 10:46 1

[Didneywhorl]

crw------- 1 root root 180, 176 Dec 11 22:40 /dev/cdc-wdm0

Looks like it's only seeing one modem.

[JimHelms]

If the router was working fine and would recognize both modems "prior" to the upgrade, then the new firmware seems to be the contributing factor. And, while I am not very familiar with their firmware and/or update process:

1. "if" the new firmware is of a different kernel, and
2. "if" the firmware provides an option to save its current configuration during the upgrade(which you did), then

it is reasonably possible that a component of the old configuration is not compatible with the new firmware.

You should be able to download (backup) the current configuration. Then, if their firmware has in the menu the option to restore the firmware to default settings, I would try it. Then see if both modems are recognized.

If there is no option to reset to default, I would download and install a fresh image and not save settings (configurations).

If it still does not work as desired, it is possible there is glitch with the newest firmware. I would next try to reinstall the older version from anew (saving no settings). You can then upload your original configuration backup that worked on the older firmware.

Just my two cents worth.

[scorchen]

Thanks for the troubleshooting help all. I'm going to probably perform a full fresh flash and factory reset as well as module resets before messin with it further. UGHH this is what I get for fixing something that wasn't broke!

[scorchen]

Alright, I downloaded the latest firmware 4.9.5-5500-std and manually flashed without saving any configurations. Then i reset factory defaults and then reset modules just for good measure. System log never shows the IMEI of the 2nd module anywhere throughout. It's really making me think the USB port or the modem itself died. I would think the system would be displaying more information about it if not, but I really have no idea what happened. I might take the router down and pull the case off it just to see if anything looks broken. (This is installed inside a camper van so there are constant vibrations and temperature fluctuations. Some of my electronic equipment do not last as long in this context).

[JimHelms]

It may be worth removing the modems and placing each in a USB sled and use a PC to check each to make sure they are working. At that time you may want to update the modem firmware to the latest and configure the modem composition that MoFi uses (i.e., QMI, MBIM).

Unfortunately, there are times one must implement a process of elimination.

[scorchen]

That's a good idea! I will pursue that avenue and report back when I have a resolution. Thanks for the help!