LTE modem Quectel EP06-E does not work after recent upgrades

Hi, Quectel EP06-E LTE does not work after recent upgrades, see /var/log/messages, thank you for help in advance!

May 1 05:27:30 turris odhcpd[5780]: Failed to send to ff02::1%guest_turris@br-guest-turris (Address not available)
May 1 05:27:32 turris pppd[3428]: pppd 2.4.9 started by root, uid 0
May 1 05:27:33 turris chat[3432]: abort on (BUSY)
May 1 05:27:33 turris chat[3432]: abort on (NO CARRIER)
May 1 05:27:33 turris chat[3432]: abort on (ERROR)
May 1 05:27:33 turris chat[3432]: report (CONNECT)
May 1 05:27:33 turris chat[3432]: timeout set to 10 seconds
May 1 05:27:33 turris chat[3432]: send (AT&F^M)
May 1 05:27:33 turris chat[3432]: expect (OK)
May 1 05:27:33 turris chat[3432]: AT&F^M^M
May 1 05:27:33 turris chat[3432]: OK
May 1 05:27:33 turris chat[3432]: ā€“ got it
May 1 05:27:33 turris chat[3432]: send (ATE1^M)
May 1 05:27:33 turris chat[3432]: expect (OK)
May 1 05:27:33 turris chat[3432]: ^M
May 1 05:27:33 turris chat[3432]: ATE1^M^M
May 1 05:27:33 turris chat[3432]: OK
May 1 05:27:33 turris chat[3432]: ā€“ got it
May 1 05:27:33 turris chat[3432]: send (AT+CGDCONT=1,ā€œIPā€,ā€œinternetā€^M)
May 1 05:27:34 turris chat[3432]: timeout set to 30 seconds
May 1 05:27:34 turris chat[3432]: expect (OK)
May 1 05:27:34 turris chat[3432]: ^M
May 1 05:27:34 turris chat[3432]: AT+CGDCONT=1,ā€œIPā€,ā€œinternetā€^M^M
May 1 05:27:34 turris chat[3432]: OK
May 1 05:27:34 turris chat[3432]: ā€“ got it
May 1 05:27:34 turris chat[3432]: send (ATD991#^M)
May 1 05:27:34 turris chat[3432]: expect (CONNECT)
May 1 05:27:34 turris chat[3432]: ^M
May 1 05:27:34 turris chat[3432]: ATD
99
**1#^M^M
May 1 05:27:34 turris chat[3432]: CONNECT
May 1 05:27:34 turris chat[3432]: ā€“ got it
May 1 05:27:34 turris chat[3432]: send ( ^M)
May 1 05:27:34 turris pppd[3428]: Serial connection established.
May 1 07:27:34 turris kernel: [ 1071.770590] 3g-lte: renamed from ppp0
May 1 05:27:34 turris pppd[3428]: Renamed interface ppp0 to 3g-lte
May 1 05:27:34 turris pppd[3428]: Using interface 3g-lte
May 1 05:27:34 turris pppd[3428]: Connect: 3g-lte ā†” /dev/ttyUSB2
May 1 05:27:34 turris ModemManager[3438]: hotplug: event reported: action=add, name=ppp0, subsystem=net
May 1 05:27:34 turris [8582]: [ppp0] invalid sysfs path read for net/ppp0
May 1 05:27:34 turris [8582]: [base-manager] couldnā€™t handle kernel event: device net/ppp0 not found
May 1 05:27:34 turris ModemManager[3438]: hotplug: parent device sysfspath not found
May 1 05:27:34 turris ModemManager[3479]: hotplug: event reported: action=move, name=3g-lte, subsystem=net
May 1 05:27:34 turris [8582]: [base-manager] couldnā€™t handle kernel event: Invalid ā€˜actionā€™ parameter given: ā€˜moveā€™ (expected ā€˜addā€™ or ā€˜removeā€™)
May 1 05:27:35 turris pppd[3428]: Modem hangup
May 1 05:27:35 turris pppd[3428]: Connection terminated.
May 1 05:27:35 turris ModemManager[3495]: hotplug: event reported: action=remove, name=3g-lte, subsystem=net
May 1 05:27:36 turris pppd[3428]: Exit.
May 1 05:27:36 turris netifd: Interface ā€˜lteā€™ is now down
May 1 05:27:36 turris netifd: Interface ā€˜lteā€™ is setting up now
May 1 05:27:37 turris odhcpd[5780]: Failed to send to ff02::1%guest_turris@br-guest-turris (Address not available)

This is possibly the same reason.

1 Like

Hi, solved by scnapps to go to older snapschots from March and back to 7.0.0, to disable guest_turris network interface and there was obviously issue at o2 cz with sim card. So no errors in log now and lte works also on 7.0.0. Probably more factors together. Thank you!

2 Likes

Hi, I have also strange issue w. Quectel EP06-E LTE modem on my freshly flashed Turris Omnia (TOS7 latest medkit from 02-Apr-2024 02:54). According to the hard inspection of my Omnia seems that modem have some issues w. registration to the home mobile provider (which is O2 CZ operator id: 23002) which leads to missing bearer and network interface wwan0 remains down. Registration to the operator jumping randomly since restart between all available mobile networks (in roaming - if not home):

root@turris:~# mmcli -m 0 --3gpp-scan
  ---------------------
  3GPP scan | networks: 23003 - Vodafone (lte, available)
            |           23001 - TMO CZ (lte, available)
            |           23002 - O2.CZ (lte, current)

this seems on the first view OK, but 3GPP registration remains always in idle - no bearer, no APN, network interface is down even if I tried to force registration manually:

root@turris:~# mmcli -m 0 --3gpp-register-home
error: couldn't register the modem: 'Timeout was reached'

Here is full modem state according to ModemManager:

root@turris:~# mmcli -L
    /org/freedesktop/ModemManager1/Modem/0 [Quectel] EP06-E
root@turris:~# mmcli -m 0
  -----------------------------------
  General  |                    path: /org/freedesktop/ModemManager1/Modem/0
           |               device id: c3360cb2ae6b29dea92310283f22e67a5396203c
  -----------------------------------
  Hardware |            manufacturer: Quectel
           |                   model: EP06-E
           |       firmware revision: EP06ELAR03A08M4G
           |          carrier config: ROW_Generic_3GPP
           | carrier config revision: 06010821
           |            h/w revision: 20000
           |               supported: gsm-umts, lte
           |                 current: gsm-umts, lte
           |            equipment id: 868186041277243
  -----------------------------------
  System   |                  device: /sys/devices/platform/soc/soc:internal-regs/f1058000.usb/usb1/1-1
           |                 drivers: qmi_wwan, option1
           |                  plugin: quectel
           |            primary port: cdc-wdm0
           |                   ports: cdc-wdm0 (qmi), ttyUSB0 (qcdm), ttyUSB1 (gps), 
           |                          ttyUSB2 (at), ttyUSB3 (at), wwan0 (net)
  -----------------------------------
  Status   |                    lock: sim-pin2
           |          unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), sim-puk2 (10)
           |                   state: enabled
           |             power state: on
           |          signal quality: 71% (cached)
  -----------------------------------
  Modes    |               supported: allowed: 3g; preferred: none
           |                          allowed: 4g; preferred: none
           |                          allowed: 3g, 4g; preferred: 4g
           |                          allowed: 3g, 4g; preferred: 3g
           |                 current: allowed: 2g, 3g, 4g; preferred: 4g
  -----------------------------------
  Bands    |               supported: utran-1, utran-3, utran-5, utran-8, eutran-1, eutran-3, 
           |                          eutran-5, eutran-7, eutran-8, eutran-20, eutran-28, eutran-32, 
           |                          eutran-38, eutran-40, eutran-41
           |                 current: utran-1, utran-3, utran-5, utran-8, eutran-1, eutran-3, 
           |                          eutran-5, eutran-7, eutran-8, eutran-20, eutran-28, eutran-32, 
           |                          eutran-38, eutran-40, eutran-41
  -----------------------------------
  IP       |               supported: ipv4, ipv6, ipv4v6
  -----------------------------------
  3GPP     |                    imei: 868186041277243
           |           enabled locks: fixed-dialing
           |             operator id: 23002
           |            registration: idle
  -----------------------------------
  3GPP EPS |    ue mode of operation: csps-2
           |  initial bearer ip type: ipv4v6
  -----------------------------------
  SIM      |        primary sim path: /org/freedesktop/ModemManager1/SIM/0

Suspicious is communication w. SIM slot in my Omnia, I see strange things in the ModemManger log:

ay 27 07:21:28 turris [6876]: [/dev/cdc-wdm0] Registered 'voice' (version 2.1) client with ID '3'
May 27 07:21:28 turris ModemManager[6851]: hotplug: modem not detected at sysfs path
May 27 07:21:30 turris [6876]: <warn>  [modem0] couldn't query SIM slots: QMI protocol error (94): 'NotSupported'
May 27 07:21:30 turris [6876]: <warn>  [modem0/sim0] couldn't load list of emergency numbers: Failed to parse CRSM query result '+CRSM: 148,8,""'
May 27 07:21:31 turris [6876]: <warn>  [modem0] couldn't load list of own numbers: Couldn't get MSISDN: QMI protocol error (16): 'NotProvisioned'
May 27 07:21:31 turris [6876]: <info>  [modem0] state changed (unknown -> disabled)
May 27 07:21:33 turris ModemManager[6851]: hotplug: modem exported successfully at /sys/devices/platform/soc/soc:internal-regs/f1058000.usb/usb1/1-1
May 27 07:21:33 turris ModemManager[6851]: hotplug: setting interface 'gsm' as available
May 27 07:21:33 turris [6876]: <info>  [modem0] simple connect started...
May 27 07:21:33 turris [6876]: <info>  [modem0] simple connect state (3/8): enable
May 27 07:21:33 turris [6876]: <info>  [modem0] state changed (disabled -> enabling)
May 27 07:21:34 turris [6876]: <info>  [modem0] power state updated: on
May 27 07:21:34 turris [6876]: <info>  [modem0] 3GPP registration state changed (unknown -> idle)
May 27 07:21:35 turris [6876]: <info>  [modem0] simple connect state (4/8): wait to get fully enabled
May 27 07:21:35 turris [6876]: <info>  [modem0] state changed (enabling -> enabled)
May 27 07:21:35 turris [6876]: <info>  [modem0] simple connect state (5/8): register

Without NetworkManager is it the same - here you can see the roaming registration to the T-mobile network:

root@turris:~# uqmi -d /dev/cdc-wdm0 --get-plmn
{
        "mode": "automatic"
}
root@turris:~# uqmi -d /dev/cdc-wdm0 --get-serving-system
{
        "registration": "searching",
        "plmn_mcc": 230,
        "plmn_mnc": 1,
        "plmn_description": "",
        "roaming": true
root@turris:~# uqmi -d /dev/cdc-wdm0 --network-scan
{
        "network_info": [
                {
                        "mcc": 230,
                        "mnc": 2,
                        "description": "O2.CZ",
                        "status": [
                                "available",
                                "home",
                                "not_forbidden",
                                "preferred"
                        ]
                },
                {
                        "mcc": 230,
                        "mnc": 1,
                        "description": "TMO CZ",
                        "status": [
                                "current_serving",
                                "roaming",
                                "not_forbidden",
                                "not_preferred"
                        ]
                },
                {
                        "mcc": 230,
                        "mnc": 3,
                        "description": "Vodafone",
                        "status": [
                                "available",
                                "roaming",
                                "not_forbidden",
                                "not_preferred"
                        ]
                }
        ],
        "radio_access_technology": [
                {
                        "mcc": 230,
                        "mnc": 2,
                        "radio": "lte"
                },
                {
                        "mcc": 230,
                        "mnc": 1,
                        "radio": "lte"
                },
                {
                        "mcc": 230,
                        "mnc": 3,
                        "radio": "lte"
                }
        ]
}
 root@turris:~# uqmi -d /dev/cdc-wdm0 --uim-get-sim-state
{
        "pin1_status": "disabled",
        "pin1_verify_tries": 3,
        "pin1_unlock_tries": 10,
        "pin2_status": "not_verified",
        "pin2_verify_tries": 3,
        "pin2_unlock_tries": 10
}

SIM is present in the slot, PIN request has been disabled and mobile data works OK in my mobile phone. Iā€™m using the default configuration of the modem device interface gsm w. modemmanger (MM) but the same results I got if I stop MM and tried to force registartion by uqmi. There are very old firmware in my modem card (firmware revision: EP06ELAR03A08M4G) do you have the latest one? Omnia fw. has been also updated:

root@turris:~# /usr/bin/omnia-mcutool --firmware-version
Bootloader version:  b5a8a24e007eb72be16aeb3fff6f03ec647023e4
Application version: 67eddc9540526d0a9d9660f7a7867af9a28a68d6
MCU type: STM32
Board firmware type: stm32-rev23-user-regulator
Features: 0x1f6e
  EXT_CMDS
  WDT_PING
  LED_STATE_EXT
  LED_GAMMA_CORRECTION
  NEW_INT_API
  FLASHING
  NEW_MESSAGE_API
  BRIGHTNESS_INT
  POWEROFF_WAKEUP
  CAN_OLD_MESSAGE_API
Application firmware length: 21400 Bytes
Application firmware checksum: 0xfeeb0f31

There is no other hardware in my Omnia (even WiFI) only on USB is modem device ID 2c7c:0306 Quectel EP06-E
Do you have any idea? Thanks.

When comparing Turris OS 6.5.2 with 7.0,0, I found that the ModemManager package in 7.0 actually uses an older ModemManager version (7.0.0 has version 1.18.6 whereas 6.5.2 had 1.18.12). I filed a bug report for this:

Itā€™s hard to tell if that really is related to the issues youā€™re experiencing. But it might be worth to try the newer version which is already part of the 7.0.1 RC You can find it here. I make no guaranties, but since the differences between 7.0.0 and 7.0.1 are minor, it should be possible to install the package from the downloaded ipk file (even without switching to the testing branch and upgrading to TO 7.0.1).

Similar issue for me. See here.
Where do you find the ModemManager log? Complete path, please.

I spent a lot of time (almost 40hrs.) with this issue and Iā€™m pretty pissed. But finally I solved it!!! It worked exceptionally only when I left my Omnia Box openned - it mean there was a ā€˜state: Connectedā€™ in the Status field of the:
mmcli -m 0
And what helped? There was mistakenly connected middle antena connector of the mini-pci Quectel EP06-E card since Turris Omnia 4G manufacturing. The middle connector should remain unplugged, use only both on the sides one. Even of this issue, signal detection did not shows any issues, maybe because the right connector left properly connected, and mobile operators always accepted connection, but only in the enabled state (like in your case), but never falls to connected one (with one exception, when I left openned a metal cover).

and question regarding to ModemManager log:
logread | grep -i modem
Seems that there are some issues in the quality control during Omnia-4G manufacturing, hope that helps you too.

3 Likes

Indeed it helped.
Youā€™re a hero!! Thanks for pointing me in this direction :slight_smile:

The middle connector is for GPS, for the Quectel EP06 you will need an
active GPS antenna (magnetic) for getting the real tim from a sattelite if
you want to build a Startum0 (inside) or Straum1 (your network) NTP server.

Hi,

unfortunately strange behavior continues in my case. I am not able to get modem to online state except I switch off / on the router (my opinion is to restart sim card - power off the card). After connection modem disconnects after few minutes. It seems O2 CZ disconnects me. Even router restart does not help also as following commands:

ifdown lte
echo -e ā€œAT+CFUN=1,1ā€ > /dev/ttyUSB2
ifup lte

I use lte as a backup only for wan connection together with mwan3.

content of /var/log/messages log:

un 2 09:45:03 turris mwan3track[5225]: Check (ping) failed for target ā€œ8.8.4.4ā€ on interface lte (3g-lte). Current score: 15
Jun 2 09:46:20 turris pppd[20193]: LCP terminated by peer
Jun 2 09:46:20 turris pppd[20193]: Connect time 18.0 minutes.
Jun 2 09:46:20 turris pppd[20193]: Sent 6480 bytes, received 5964 bytes.
Jun 2 09:46:20 turris netifd: Network device ā€˜3g-lteā€™ link is down
Jun 2 09:46:20 turris netifd: Interface ā€˜lteā€™ has lost the connection
Jun 2 09:46:20 turris pppd[20193]: Modem hangup
Jun 2 09:46:20 turris pppd[20193]: Connection terminated.
Jun 2 09:46:21 turris ModemManager[381]: hotplug: event reported: action=remove, name=3g-lte, subsystem=net
Jun 2 09:46:21 turris mwan3-hotplug[372]: Execute ifdown event on interface lte (unknown)
Jun 2 09:46:21 turris mwan3track[5225]: Detect ifdown event on interface lte (3g-lte)
Jun 2 09:46:21 turris mwan3track[5225]: Interface lte (3g-lte) is offline
Jun 2 09:46:21 turris mwan3-hotplug[469]: Execute disconnected event on interface lte (3g-lte)
Jun 2 09:46:21 turris pppd[20193]: Exit.
Jun 2 09:46:22 turris netifd: Interface ā€˜lteā€™ is now down
Jun 2 09:46:22 turris netifd: Interface ā€˜lteā€™ is setting up now
Jun 2 09:47:03 turris netifd: lte (822): ppp: warning: Sleeping for ā€˜10ā€™ seconds
Jun 2 09:47:13 turris pppd[1205]: pppd 2.4.9 started by root, uid 0
Jun 2 09:47:14 turris chat[1208]: abort on (BUSY)
Jun 2 09:47:14 turris chat[1208]: abort on (NO CARRIER)
Jun 2 09:47:14 turris chat[1208]: abort on (ERROR)
Jun 2 09:47:14 turris chat[1208]: report (CONNECT)
Jun 2 09:47:14 turris chat[1208]: timeout set to 10 seconds
Jun 2 09:47:14 turris chat[1208]: send (AT&F^M)
Jun 2 09:47:14 turris chat[1208]: expect (OK)
Jun 2 09:47:14 turris chat[1208]: AT&F^M^M
Jun 2 09:47:14 turris chat[1208]: OK
Jun 2 09:47:14 turris chat[1208]: ā€“ got it
Jun 2 09:47:14 turris chat[1208]: send (ATE1^M)
Jun 2 09:47:14 turris chat[1208]: expect (OK)
Jun 2 09:47:14 turris chat[1208]: ^M
Jun 2 09:47:14 turris chat[1208]: ATE1^M^M
Jun 2 09:47:14 turris chat[1208]: OK
Jun 2 09:47:14 turris chat[1208]: ā€“ got it
Jun 2 09:47:14 turris chat[1208]: send (AT+CGDCONT=1,ā€œIPā€,ā€œinternetā€^M)
Jun 2 09:47:15 turris chat[1208]: timeout set to 30 seconds
Jun 2 09:47:15 turris chat[1208]: expect (OK)
Jun 2 09:47:15 turris chat[1208]: ^M
Jun 2 09:47:15 turris chat[1208]: AT+CGDCONT=1,ā€œIPā€,ā€œinternetā€^M^M
Jun 2 09:47:15 turris chat[1208]: OK
Jun 2 09:47:15 turris chat[1208]: ā€“ got it
Jun 2 09:47:15 turris chat[1208]: send (ATD991#^M)
Jun 2 09:47:15 turris chat[1208]: expect (CONNECT)
Jun 2 09:47:15 turris chat[1208]: ^M
Jun 2 09:47:15 turris chat[1208]: ATD
99
**1#^M^M
Jun 2 09:47:15 turris chat[1208]: CONNECT
Jun 2 09:47:15 turris chat[1208]: ā€“ got it
Jun 2 09:47:15 turris chat[1208]: send ( ^M)
Jun 2 09:47:15 turris pppd[1205]: Serial connection established.
Jun 2 11:47:15 turris kernel: [ 1220.755032] 3g-lte: renamed from ppp0
Jun 2 09:47:15 turris pppd[1205]: Renamed interface ppp0 to 3g-lte
Jun 2 09:47:15 turris pppd[1205]: Using interface 3g-lte
Jun 2 09:47:15 turris pppd[1205]: Connect: 3g-lte ā†” /dev/ttyUSB2
Jun 2 09:47:15 turris ModemManager[1212]: hotplug: event reported: action=add, name=ppp0, subsystem=net
Jun 2 09:47:15 turris [8491]: [ppp0] invalid sysfs path read for net/ppp0
Jun 2 09:47:15 turris [8491]: [base-manager] couldnā€™t handle kernel event: device net/ppp0 not found
Jun 2 09:47:15 turris ModemManager[1212]: hotplug: parent device sysfspath not found
Jun 2 09:47:15 turris ModemManager[1257]: hotplug: event reported: action=move, name=3g-lte, subsystem=net
Jun 2 09:47:15 turris [8491]: [base-manager] couldnā€™t handle kernel event: Invalid ā€˜actionā€™ parameter given: ā€˜moveā€™ (expected ā€˜addā€™ or ā€˜removeā€™)
Jun 2 09:47:16 turris pppd[1205]: Modem hangup
Jun 2 09:47:16 turris pppd[1205]: Connection terminated.
Jun 2 09:47:16 turris ModemManager[1271]: hotplug: event reported: action=remove, name=3g-lte, subsystem=net
Jun 2 09:47:17 turris pppd[1205]: Exit.
Jun 2 09:47:17 turris netifd: Interface ā€˜lteā€™ is now down

Any ideas please?

Why donā€™t you try to set up the connection as QMI cellular?
See LTE připojenĆ­ pomocĆ­ protokolu QMI [Turris wiki]

Hi, thank you for the advice. Even if I setup QMI LTE connection works only cca 10 minutes, then lte interface goes offline and I did not find way, how to make it functional apart router power off / on :-(.