1. Home
  2. Qualcomm Flight RB5 5G Drone
  3. wwan0 carrier lost

wwan0 carrier lost

  • N

    Hi

    we are trying to set up the 5G quectel modem, we tried with different mobile networks and different SIM cards.
    We are getting a disconnection from the mobile network approximately every minute, sometimes a bit more.

    Looking into the journalctl we can see the following pattern every few seconds: carrier lost and the modem connects again
    We are thinking if the config-wwan0.sh could be the reason... but any other ideas are appreciated

    Feb 09 16:23:31 robot133 config-wwan0.sh[17365]: Configuring wwan0 LTE interface netmask...
Feb 09 16:23:31 robot133 config-wwan0.sh[17365]: Setting default gateway...
Feb 09 16:23:31 robot133 config-wwan0.sh[17365]: Error: Nexthop has invalid gateway.
Feb 09 16:23:31 robot133 config-wwan0.sh[17365]: Setting wwan0 MTU size...
Feb 09 16:23:31 robot133 systemd[1]: Started modallink-relink.service.
Feb 09 16:23:32 robot133 kernel: cnss: Firmware does not support non-DRV suspend, reject
Feb 09 16:23:36 robot133 kernel: [dp_rx_][0xad5f82b4a][16:23:36.060254] wlan: [1775:I:QDF] DHCP RX: SA:          (null) DA:          (null) msdu_id:0 status: drop
Feb 09 16:23:36 robot133 kernel: [dp_rx_][0xad70673b7][16:23:36.982805] wlan: [1775:I:QDF] DHCP RX: SA:          (null) DA:          (null) msdu_id:0 status: drop
Feb 09 16:23:38 robot133 kernel: cnss: Firmware does not support non-DRV suspend, reject
Feb 09 16:23:38 robot133 kernel: cnss: Firmware does not support non-DRV suspend, reject
Feb 09 16:23:39 robot133 kernel: cnss: Firmware does not support non-DRV suspend, reject
Feb 09 16:23:40 robot133 kernel: [soft_i][0xadaa2d5d4][16:23:40.137985] wlan: [0:I:QDF] DHCP-R TX: SA:00:03:7f:12:c1:11 DA:cc:2d:e0:a5:6e:47 msdu_id:302 status: succ
Feb 09 16:23:40 robot133 kernel: [dp_rx_][0xadaa47700][16:23:40.143547] wlan: [1775:I:QDF] DHCP-A RX: SA:cc:2d:e0:a5:6e:47 DA:00:03:7f:12:c1:11
Feb 09 16:23:40 robot133 kernel: cnss: Firmware does not support non-DRV suspend, reject
Feb 09 16:23:42 robot133 dhcpcd[1678]: wwan0: carrier lost
Feb 09 16:23:42 robot133 systemd[1]: Stopping modallink-relink.service...
Feb 09 16:23:42 robot133 systemd[1]: Stopped modallink-relink.service.
Feb 09 16:23:42 robot133 systemd[1]: Stopping Modem Initialization...
Feb 09 16:23:42 robot133 kernel: cnss: Firmware does not support non-DRV suspend, reject
Feb 09 16:23:42 robot133 dhcpcd[1678]: wwan0: carrier acquired
Feb 09 16:23:42 robot133 dhcpcd[1678]: wwan0: IAID f6:16:a2:03
Feb 09 16:23:42 robot133 dhcpcd[1678]: wwan0: waiting for 3rd party to configure IP address
Feb 09 16:23:42 robot133 dhcpcd[1678]: wwan0: carrier lost
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:22:32:649] Quectel_QConnectManager_Linux_V1.6.0.24
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:22:32:652] Find /sys/bus/usb/devices/2-1.1 idVendor=0x2c7c idProduct=0x800, bus=0x002, dev=0x003
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:22:32:652] Auto find qmichannel = /dev/cdc-wdm0
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:22:32:653] Auto find usbnet_adapter = wwan0
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:22:32:653] netcard driver = qmi_wwan, driver version = 22-Aug-2005
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:22:32:653] Modem works in QMI mode
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:22:32:677] cdc_wdm_fd = 7
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:22:32:755] Get clientWDS = 2
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:22:32:787] Get clientDMS = 1
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:22:32:823] Get clientNAS = 4
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:22:32:851] Get clientUIM = 1
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:22:32:886] Get clientWDA = 1
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:22:32:916] requestBaseBandVersion RM502QAEAAR11A02M4G
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:22:33:043] requestGetSIMStatus SIMStatus: SIM_READY
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:22:33:043] requestSetProfile[1] movistar.es///0
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:22:33:107] requestGetProfile[1] movistar.es///0
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:22:33:139] requestRegistrationState2 MCC: 214, MNC: 7, PS: Attached, DataCap: 5G_NSA
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:22:33:171] requestQueryDataCall IPv4ConnectionStatus: DISCONNECTED
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:22:33:171] ifconfig wwan0 0.0.0.0
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:22:33:178] ifconfig wwan0 down
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:22:33:235] requestSetupDataCall WdsConnectionIPv4Handle: 0x1d607ec0
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:22:33:363] ifconfig wwan0 up
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:22:33:370] busybox udhcpc -f -n -q -t 5 -i wwan0
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:23:42:649] requestDeactivateDefaultPDP WdsConnectionIPv4Handle
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:23:42:674] ifconfig wwan0 0.0.0.0
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:23:42:686] ifconfig wwan0 down
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:23:42:867] QmiWwanThread exit
Feb 09 16:23:42 robot133 voxl-modem-start.sh[17042]: [02-09_16:23:42:867] qmi_main exit
Feb 09 16:23:42 robot133 systemd[1]: Stopped Modem Initialization.
Feb 09 16:23:42 robot133 systemd[1]: Starting Modem Initialization...
Feb 09 16:23:43 robot133 kernel: cnss: Firmware does not support non-DRV suspend, reject
Feb 09 16:23:43 robot133 kernel: [dp_rx_][0xadec340c5][16:23:43.743835] wlan: [1775:I:QDF] DHCP RX: SA:          (null) DA:          (null) msdu_id:0 status: drop
Feb 09 16:23:44 robot133 systemd-journald[539]: Forwarding to syslog missed 154619 messages.
Feb 09 16:23:44 robot133 systemd[1]: Started Modem Initialization.
Feb 09 16:23:44 robot133 systemd[1]: Starting modallink-relink.service...
Feb 09 16:23:45 robot133 voxl-modem-start.sh[17458]: qrb5165 based hardware detected...
Feb 09 16:23:45 robot133 voxl-modem-start.sh[17458]: \Setting mode preference to LTE / 5G
Feb 09 16:23:45 robot133 voxl-modem-start.sh[17458]: AT+QNWPREFCFG="mode_pref",LTE:NR5G
Feb 09 16:23:45 robot133 voxl-modem-start.sh[17458]: OK
Feb 09 16:23:45 robot133 kernel: cnss: Firmware does not support non-DRV suspend, reject
Feb 09 16:23:46 robot133 voxl-modem-start.sh[17458]: Initalizing cellular connection...
Feb 09 16:23:46 robot133 dhcpcd[1678]: wwan0: carrier acquired
Feb 09 16:23:46 robot133 dhcpcd[1678]: wwan0: IAID f6:16:a2:03
Feb 09 16:23:46 robot133 dhcpcd[1678]: wwan0: waiting for 3rd party to configure IP address
Feb 09 16:23:46 robot133 dhcpcd[1678]: wwan0: carrier lost
Feb 09 16:23:46 robot133 dhcpcd[1678]: wwan0: carrier acquired
Feb 09 16:23:46 robot133 voxl-modem-start.sh[17458]: udhcpc: started, v1.27.2
Feb 09 16:23:46 robot133 dhcpcd[1678]: wwan0: IAID f6:16:a2:03
Feb 09 16:23:46 robot133 dhcpcd[1678]: wwan0: waiting for 3rd party to configure IP address
Feb 09 16:23:46 robot133 voxl-modem-start.sh[17458]: Too few arguments.
Feb 09 16:23:46 robot133 voxl-modem-start.sh[17458]: Too few arguments.
Feb 09 16:23:46 robot133 udhcpc[17558]: wwan0: deconfigured
Feb 09 16:23:46 robot133 voxl-modem-start.sh[17458]: udhcpc: sending discover
Feb 09 16:23:46 robot133 voxl-modem-start.sh[17458]: udhcpc: sending select for 95.126.100.218
Feb 09 16:23:46 robot133 voxl-modem-start.sh[17458]: udhcpc: lease of 95.126.100.218 obtained, lease time 7200
Feb 09 16:23:47 robot133 voxl-modem-start.sh[17458]: Too few arguments.
Feb 09 16:23:47 robot133 voxl-modem-start.sh[17458]: Too few arguments.
Feb 09 16:23:47 robot133 udhcpc[17614]: wwan0: bound: IP=95.126.100.218/255.255.255.252 router=95.126.100.217 domain="" dns="80.58.61.250 80.58.61.254" lease=7200
Feb 09 16:23:47 robot133 kernel: [dp_rx_][0xae2dc6869][16:23:47.324895] wlan: [1775:I:QDF] DHCP-IN RX: SA:0c:9a:3c:a2:57:6a DA:ff:ff:ff:ff:ff:ff
Feb 09 16:23:47 robot133 dhcpcd[1678]: wwan0: soliciting an IPv6 router
Feb 09 16:23:47 robot133 kernel: cnss: Firmware does not support non-DRV suspend, reject
Feb 09 16:23:50 robot133 systemd[1]: robot.service: State 'stop-final-sigterm' timed out. Killing.
Feb 09 16:23:50 robot133 systemd[1]: robot.service: Killing process 13198 (docker) with signal SIGKILL.
Feb 09 16:23:50 robot133 systemd[1]: robot.service: Failed with result 'timeout'.
Feb 09 16:23:50 robot133 systemd[1]: Stopped Robot bringup for the universe app manager and multimaster.
Feb 09 16:23:51 robot133 systemd-journald[539]: Suppressed 2833335 messages from start_cnss_daemon.service
    0
  • tom
    Dev Team

    @nacho I'm seeing references to modallink-relink, that shouldn't be used in your configuration. I would run through voxl-configure-modem again and make sure you answer "no" to "Are you attempting to connect to ModalLink?".

    Or you can disable it with systemctl disable modallink-relink and a reboot.

    1
  • tom
    Dev Team

    config-wwan0 shouldn't be used either

    0
  • N

    Hi @tom !
    Thank you for your response, the issue was solved by deactivating this service.

    Thank you so much

    0
Log in to reply