GL-E750V2 Mudi V2 internal modem keeps unplugging itself

Hello,

I recently bought from the official web store the GL-E750V2 Mudi V2 Portable 4G LTE Router. It has been updated to the latest firmware version 4.0 (type 0317 release 2, and compile time 2024-06-07 7:46:06(UTC+08:00)).

It's been more than 10 days since I set up this router with a 4G SIM card to connect to the Internet. The connection is usually fine with fast 4G speeds which I share as two WiFi networks for my other devices.

However, over the past 10 days, the internal cellular 4G modem keeps unplugging itself up to several times each day. When this happens, the main admin dashboard of this router says "No Modem device found. Plug in your USB modem to start"! Every time I have to manually reboot the router, and the modem suddenly starts working again.

I have attached a screenshot above of the admin page saying "no modem device found", and the latest logs which show that the internal modem unplugged itself. For example, the system logs show that:

"Interface modem_1_1_2 (wwan0) is offline".

This is very frustrating because it interrupts my workflow, including in the middle of mission-critical online meetings.

Can you please advise on how to fix this issue, or if the there is a problem with the hardware itself?

Thank you!

System logs: logread 2024-08-20.tar (121.5 KB)

P.S. I used SSH to log into the router to get detailed version numbers. Here they are:
OpenWrt 22.03.4, r20123-38ccc47687
cat /etc/glversion output: 4.3.17

Have you turned off 5G wifi?

1 Like

@ywp No, 5G WiFi is on on this router.

Is the module EM060K?

1 Like

@ywp Yes, I believe it is. This is the exact product description in my original order confirmation:

Mudi V2 Portable 4G LTE Router | Travel WiFi | (GL-E750V2) × 1
EM060K-G 4G Global / US+EU+UK+AU plug

Are 5Gwifi and 2g wifi on normally?
Do you normally connect to 2g or 5g?

1 Like

@ywp:

Are 5Gwifi and 2g wifi on normally?

Yes.

Do you normally connect to 2g or 5g?

My devices use both networks.

Can you turn off 2g wifi and just try 5G?

1 Like

@ywp: I can try temporarily, but several of my devices only use the 2G WiFi network. I will do that now.

How long do I need to keep the 2G network off? How might this be related to the internal cellular modem unplugging itself?

About an hour
It looks like the 2g device caused the usb port to automatically hang, resulting in a power outage

1 Like

Hi @ywp thanks for your help. I turned off the 2G WiFi network, and here's what happened:

Within 10 minutes of 2G off and only 5G WiFi on, the modem unplugged itself again!

I had to completely reboot the router again.

I'm attaching the latest logs which show the internal modem becoming unplugged again. Look for everything that happens starting Wed Aug 21 11:23:56 which was when I turned off 2G.

logread 2024-08-21.tar (121.5 KB)

I see some errors with Permission denied, Failed to remove, Invalid argument, failed to read device, not supported. Lots of usb 1-1-port1: cannot reset (err = -71). There are also mentions of the GSM modem disconnecting like:

...
[74592.859849] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
...
[74592.875917] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
...
daemon.notice netifd: Network device 'wwan0' link is down

Any other ideas?

Do you have anything on your USB port?
Are you using an original charger?

1 Like

@ywp:

Do you have anything on your USB port?

Yes, there is a Raspberry Pi Zero 2 W (power input: 5V DC 2.5A) connected. This is the same one I used with my old GL-E750C6 router that this GL-E750V2 replaces.

Are you using an original charger?

Yes, my GL-E750V2 is using an original charger.

sorry
My English is not very good
I want to confirm, is it connected to the usb port of E750V2?

1 Like

@ywp: Thanks!

I want to confirm, is it connected to the usb port of E750V2?

YES, the Raspberry Pi Zero 2 W is connected to the USB port of the E750V2. I was just saying that, in the past, this Raspberry Pi Zero 2 W was also connected to an E750V1. Does that make sense?

Can remove it
And then test it again?
thank you

1 Like

Hello @ywp: Thanks for the suggestion. I can confirm that I:

  1. Unplugged the Raspberry Pi Zero 2 W. There is nothing connected on the USB port of the E750V2.
  2. 2G WiFi is off, only 5G WiFi is on.
  3. I'm using the official charger.

Sadly, the same problem happened again! The internal modem disconnected itself and I get the same message on the web interface dashboard saying: "No Modem device found. Plug in your USB modem to start."

I managed to copy and paste the error messages from the log (see below). However, even the web interface became unresponsive, so I didn't get a chance to export the full log before rebooting the router.

This is a very frustrating problem. Is there anyway to fix it? Or should I return this router for a refund? There are only about 10 days left for me to return it, so I need to know now.

Thanks!

Thu Aug 22 10:27:58 2024 kern.err kernel: [82290.332111] usb 1-1-port1: cannot reset (err = -71)
Thu Aug 22 10:27:58 2024 kern.err kernel: [82290.366114] usb 1-1-port1: cannot reset (err = -71)
Thu Aug 22 10:27:58 2024 kern.err kernel: [82290.400103] usb 1-1-port1: cannot reset (err = -71)
Thu Aug 22 10:27:58 2024 kern.err kernel: [82290.434625] usb 1-1-port1: cannot reset (err = -71)
Thu Aug 22 10:27:58 2024 kern.err kernel: [82290.471110] usb 1-1-port1: cannot reset (err = -71)
Thu Aug 22 10:27:58 2024 kern.err kernel: [82290.471130] usb 1-1-port1: Cannot enable. Maybe the USB cable is bad?
Thu Aug 22 10:27:58 2024 kern.err kernel: [82290.505096] usb 1-1-port1: cannot disable (err = -71)
Thu Aug 22 10:27:58 2024 kern.err kernel: [82290.539096] usb 1-1-port1: cannot reset (err = -71)
Thu Aug 22 10:27:58 2024 kern.err kernel: [82290.576113] usb 1-1-port1: cannot reset (err = -71)
Thu Aug 22 10:27:58 2024 kern.err kernel: [82290.610153] usb 1-1-port1: cannot reset (err = -71)
Thu Aug 22 10:27:58 2024 kern.err kernel: [82290.644102] usb 1-1-port1: cannot reset (err = -71)
Thu Aug 22 10:27:58 2024 kern.err kernel: [82290.678103] usb 1-1-port1: cannot reset (err = -71)
Thu Aug 22 10:27:58 2024 kern.err kernel: [82290.678123] usb 1-1-port1: Cannot enable. Maybe the USB cable is bad?
Thu Aug 22 10:27:58 2024 kern.err kernel: [82290.712104] usb 1-1-port1: cannot disable (err = -71)
Thu Aug 22 10:27:58 2024 kern.err kernel: [82290.745106] usb 1-1-port1: cannot reset (err = -71)
Thu Aug 22 10:27:58 2024 kern.err kernel: [82290.779104] usb 1-1-port1: cannot reset (err = -71)
Thu Aug 22 10:27:58 2024 kern.err kernel: [82290.819092] usb 1-1-port1: cannot reset (err = -71)
Thu Aug 22 10:27:58 2024 kern.err kernel: [82290.854113] usb 1-1-port1: cannot reset (err = -71)
Thu Aug 22 10:27:58 2024 kern.err kernel: [82290.889100] usb 1-1-port1: cannot reset (err = -71)
Thu Aug 22 10:27:58 2024 kern.err kernel: [82290.889120] usb 1-1-port1: Cannot enable. Maybe the USB cable is bad?
Thu Aug 22 10:27:58 2024 kern.err kernel: [82290.923086] usb 1-1-port1: cannot disable (err = -71)
Thu Aug 22 10:27:59 2024 kern.err kernel: [82290.956108] usb 1-1-port1: cannot reset (err = -71)
Thu Aug 22 10:27:59 2024 kern.err kernel: [82290.990109] usb 1-1-port1: cannot reset (err = -71)
Thu Aug 22 10:27:59 2024 kern.err kernel: [82291.025100] usb 1-1-port1: cannot reset (err = -71)
Thu Aug 22 10:27:59 2024 kern.err kernel: [82291.058108] usb 1-1-port1: cannot reset (err = -71)
Thu Aug 22 10:27:59 2024 kern.err kernel: [82291.093109] usb 1-1-port1: cannot reset (err = -71)
Thu Aug 22 10:27:59 2024 kern.err kernel: [82291.093129] usb 1-1-port1: Cannot enable. Maybe the USB cable is bad?
Thu Aug 22 10:27:59 2024 kern.err kernel: [82291.127111] usb 1-1-port1: cannot disable (err = -71)
Thu Aug 22 10:27:59 2024 kern.err kernel: [82291.163100] usb 1-1-port1: cannot disable (err = -71)
Thu Aug 22 10:27:59 2024 kern.err kernel: [82291.197111] hub 1-1:1.0: hub_ext_port_status failed (err = -71)
Thu Aug 22 10:28:10 2024 kern.warn kernel: [82302.829650] ------------[ cut here ]------------
Thu Aug 22 10:28:10 2024 kern.warn kernel: [82302.829708] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:467 dev_watchdog+0x26c/0x274
Thu Aug 22 10:28:10 2024 kern.info kernel: [82302.829715] NETDEV WATCHDOG: wwan0 (qmi_wwan): transmit queue 0 timed out
Thu Aug 22 10:28:10 2024 kern.warn kernel: [82302.829719] Modules linked in: shortcut_fe_cm ath9k ath9k_common pppoe ppp_async option ath9k_hw ath10k_pci ath10k_core ath usb_wwan rndis_host qmi_wwan pppox ppp_generic nft_fib_inet nf_flow_table_ipv6 nf_flow_table_ipv4 nf_flow_table_inet mac80211 ipt_REJECT huawei_cdc_ncm cfg80211 cdc_ncm cdc_ether xt_time xt_tcpudp xt_tcpmss xt_string xt_statistic xt_state xt_recent xt_quota xt_pkttype xt_owner xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_cgroup xt_bpf xt_addrtype xt_TPROXY xt_TCPMSS xt_REDIRECT xt_MASQUERADE xt_LOG xt_HL xt_DSCP xt_CT xt_CLASSIFY wireguard usbserial usbnet ts_kmp ts_fsm ts_bm slhc nft_reject_ipv6 nft_reject_ipv4 nft_reject_inet nft_reject nft_redir nft_quota nft_objref nft_numgen nft_nat nft_masq nft_log nft_limit nft_hash nft_flow_offload nft_fib_ipv6 nft_fib_ipv4 nft_fib nft_ct nft_counter nft_compat nft_chain_nat nf_tproxy_ipv6 nf_tproxy_ipv4 nf_tables
Thu Aug 22 10:28:10 2024 kern.warn kernel: [82302.830099]  nf_reject_ipv4 nf_log_ipv6 nf_log_ipv4 nf_log_common nf_flow_table nf_conntrack_netlink nf_conncount libcrc32c iptable_raw iptable_nat iptable_mangle iptable_filter ipt_ECN ipheth ip_tables crc_ccitt compat cdc_wdm cdc_acm br_netfilter arptable_filter arpt_mangle arp_tables fuse sch_tbf sch_ingress sch_htb sch_hfsc em_u32 cls_u32 cls_route cls_matchall cls_fw cls_flow cls_basic act_skbedit act_mirred act_gact xt_set ip_set_list_set ip_set_hash_netportnet ip_set_hash_netport ip_set_hash_netnet ip_set_hash_netiface ip_set_hash_net ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ipmac ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink ip6table_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6t_NPT ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 ifb ip6_udp_tunnel udp_tunnel udp_diag tcp_diag raw_diag inet_diag tun vfat fat ntfs nls_utf8
Thu Aug 22 10:28:10 2024 kern.warn kernel: [82302.830417]  nls_iso8859_1 nls_cp437 shortcut_fe_ipv6 shortcut_fe sha256_generic libsha256 seqiv jitterentropy_rng drbg hmac cmac mtdoops usb_storage uhci_hcd ohci_platform ohci_hcd fsl_mph_dr_of ehci_platform ehci_fsl sd_mod scsi_mod ehci_hcd gpio_button_hotplug gl_sdk4_tertf ext4 mbcache jbd2 exfat phy_ar7100_usb usbcore nls_base usb_common mii crc32c_generic gl_sdk4_hw_info
Thu Aug 22 10:28:10 2024 kern.warn kernel: [82302.830569] CPU: 0 PID: 0 Comm: swapper Not tainted 5.10.176 #0
Thu Aug 22 10:28:10 2024 kern.warn kernel: [82302.830576] Stack : 80870000 8076ebd8 00000000 00000000 80c09dd4 809b0000 80800000 8073cd58
Thu Aug 22 10:28:10 2024 kern.warn kernel: [82302.830613]         807fa288 807f9e47 809b32d0 00000000 00000000 00000001 80c09d88 38c63493
Thu Aug 22 10:28:10 2024 kern.warn kernel: [82302.830649]         00000000 00000000 8073cd58 80c09c28 ffffefff 00000000 00000000 ffffffea
Thu Aug 22 10:28:10 2024 kern.warn kernel: [82302.830684]         0000017d 80c09c34 0000017d 807ffb48 00000000 00000009 80c09e68 805367e0
Thu Aug 22 10:28:10 2024 kern.warn kernel: [82302.830720]         00000009 00000000 007d2071 80869cf4 00000003 00000038 00000000 809b0000
Thu Aug 22 10:28:10 2024 kern.warn kernel: [82302.830755]         ...
Thu Aug 22 10:28:10 2024 kern.warn kernel: [82302.830766] Call Trace:
Thu Aug 22 10:28:10 2024 kern.warn kernel: [82302.830796] [<80066ea4>] show_stack+0x30/0x100
Thu Aug 22 10:28:10 2024 kern.warn kernel: [82302.830815] [<80085b54>] __warn+0xb0/0x11c
Thu Aug 22 10:28:10 2024 kern.warn kernel: [82302.830827] [<80085c4c>] warn_slowpath_fmt+0x8c/0xac
Thu Aug 22 10:28:10 2024 kern.warn kernel: [82302.830844] [<805367e0>] dev_watchdog+0x26c/0x274
Thu Aug 22 10:28:10 2024 kern.warn kernel: [82302.830873] [<800d09a4>] call_timer_fn.constprop.0+0x1c/0x8c
Thu Aug 22 10:28:10 2024 kern.warn kernel: [82302.830886] [<800d0ce0>] run_timer_softirq+0x2cc/0x364
Thu Aug 22 10:28:10 2024 kern.warn kernel: [82302.830918] [<8069f770>] __do_softirq+0x118/0x2ec
Thu Aug 22 10:28:10 2024 kern.warn kernel: [82302.830939] [<8039dd50>] plat_irq_dispatch+0x94/0xc8
Thu Aug 22 10:28:10 2024 kern.warn kernel: [82302.830954] [<800625d8>] handle_int+0x138/0x144
Thu Aug 22 10:28:10 2024 kern.warn kernel: [82302.830965] [<80062460>] __r4k_wait+0x20/0x40
Thu Aug 22 10:28:10 2024 kern.warn kernel: [82302.830972]
Thu Aug 22 10:28:10 2024 kern.warn kernel: [82302.830979] ---[ end trace 062b719ee8f8b513 ]---
Thu Aug 22 10:28:38 2024 user.notice mwan3[27759]: Execute ifdown event on interface modem_1_1_2 (wwan0)
Thu Aug 22 10:28:41 2024 user.notice firewall: Reloading firewall due to ifdown of modem_1_1_2 (wwan0)
Thu Aug 22 10:28:44 2024 user.info mwan3track[7574]: Detect ifdown event on interface modem_1_1_2 (wwan0)
Thu Aug 22 10:28:50 2024 user.notice mwan3track[7574]: Interface modem_1_1_2 (wwan0) is offline
Thu Aug 22 10:28:52 2024 daemon.err glc: (common.c:1280) SMS set failed
Thu Aug 22 10:31:33 2024 daemon.err glc: (common.c:1280) SMS set failed

Thank you for the test
I'm trying to solve this problem
Can you wait a few days?
You don't have to worry about not being able to return it, if it's out of time, I can contact our after-sales team

1 Like

OK, yes, I can wait a few days.

Thank you so much for confirming! In the meantime please let me know if there's something else I can do to test or troubleshoot.

yes.....
of course.....
Please omit this line