# Wifi not coming up, with rmnet enabled **URL:** \ **Category:** mangOH Red\ **Created:** [October 7, 2020, 2:23pm UTC](https://mangoh.discourse.group/t/wifi-not-coming-up-with-rmnet-enabled/5370 "2020-10-07T14:23:48Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![tejaswisj](https://avatars.discourse-cdn.com/v4/letter/t/ee7513/32.png) [@tejaswisj](https://mangoh.discourse.group/u/tejaswisj)\ **Post date:** [October 7, 2020, 2:23pm UTC](https://mangoh.discourse.group/t/wifi-not-coming-up-with-rmnet-enabled/5370/1 "2020-10-07T14:23:48Z")
Hi, My setup has MangoH red board + talon mirage module with rmnet enabled. Able to make a call with the setup. When trying to enabled wifi getting error. the rmnet\_config\_notify\_cb is unregistering the wlan0 as per the logs. Any idea whats happening here. Console logs : root@swi-mdm9x28:~# wifi client start [58.899749] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:2 cur:0 tx) bc(rx:1 tx:1) mode:FIFO slv\_addr:0x70 MSTR\_STS:0x0d1300c8 OPER:0x00000010 [58.917872] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:2 cur:0 tx) bc(rx:1 tx:1) mode:FIFO slv\_addr:0x70 MSTR\_STS:0x011363c8 OPER:0x00000010 [58.934524] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:2 cur:0 tx) bc(rx:1 tx:1) mode:FIFO slv\_addr:0x70 MSTR\_STS:0x0d1300c8 OPER:0x00000010 [64.584390] wlcore: ERROR firmware boot failed despite 3 retries [64.589709] [RMNET:HI] rmnet\_config\_notify\_cb(): Kernel is trying to unregister wlan0 [64.651405] [RMNET:HI] rmnet\_config\_notify\_cb(): Kernel is trying to unregister wlan0 ERROR: le\_wifiClient\_Start returns ERROR. Logread : Oct 7 11:55:25 swi-mdm9x28 user.warn Legato: -WRN- | posDaemon[690]/le\_pa\_gnss T=unknown | pa\_gnss\_qmi.c PositionHandler() 1340 | Bad position indication Oct 7 11:55:25 swi-mdm9x28 user.warn kernel: [33.874339] PSM: Modem oprt mode - 6 Oct 7 11:55:26 swi-mdm9x28 user.warn kernel: [34.599609] PSM: Modem oprt mode - 0 Oct 7 11:55:27 swi-mdm9x28 user.info Legato: INFO | modemDaemon[687]/le\_pa T=main | pa\_mrc\_qmi.c pa\_mrc\_GetNetworkRegState() 2062 | called Oct 7 11:55:29 swi-mdm9x28 daemon.warn dnsmasq-dhcp[1212]: DHCP packet received on ecm0 which has no address Oct 7 11:55:42 swi-mdm9x28 authpriv.notice login[1247]: ROOT LOGIN on ‘/dev/ttyHSL1’ Oct 7 11:55:44 swi-mdm9x28 daemon.warn dnsmasq-dhcp[1212]: DHCP packet received on ecm0 which has no address Oct 7 11:55:49 swi-mdm9x28 user.debug Legato: DBUG | wifiService[694]/framework T=main | LE\_FILENAME ExtractFileDescriptor() 34 | Received fd (11). Oct 7 11:55:49 swi-mdm9x28 user.debug Legato: DBUG | wifiService[694]/framework T=main | LE\_FILENAME ExtractFileDescriptor() 34 | Received fd (12). Oct 7 11:55:49 swi-mdm9x28 user.debug Legato: DBUG | wifiService[694]/framework T=main | LE\_FILENAME le\_mem\_ForceAlloc() 841 | Memory pool ‘framework.DestructorObjs’ overflowed. Expanded to 2 blocks. Oct 7 11:55:49 swi-mdm9x28 user.debug Legato: DBUG | wifiService[694]/framework T=WifiClientPaThread | LE\_FILENAME PThreadStartRoutine() 362 | Set nice level to 0. Oct 7 11:55:49 swi-mdm9x28 user.debug Legato: DBUG | wifiService[694]/framework T=WifiClientPaThread | LE\_FILENAME le\_mem\_ForceAlloc() 841 | Memory pool ‘framework.DestructorObjs’ overflowed. Expanded to 3 blocks. Oct 7 11:55:49 swi-mdm9x28 user.info Legato: INFO | wifiService[694]/daemon T=WifiClientPaThread | pa\_wifi\_client\_ti.c WifiClientPaThreadMain() 240 | Started! Oct 7 11:55:49 swi-mdm9x28 user.info Legato: INFO | wifiService[694] | WIFI\_START Oct 7 11:55:49 swi-mdm9x28 user.info Legato: INFO | wifiService[694]/daemon T=WifiClientPaThread | pa\_wifi\_client\_ti.c WifiClientPaThreadMain() 257 | PARSING:WIFI\_SET\_EVENT : len:15 Oct 7 11:55:49 swi-mdm9x28 user.info kernel: [57.954740] cfg80211: Calling CRDA to update world regulatory domain Oct 7 11:55:49 swi-mdm9x28 user.info kernel: [57.954869] cfg80211: World regulatory domain updated: Oct 7 11:55:49 swi-mdm9x28 user.info kernel: [57.954880] cfg80211: DFS Master region: unset Oct 7 11:55:49 swi-mdm9x28 user.info kernel: [57.954889] cfg80211: (start\_freq - end\_freq @ bandwidth), (max\_antenna\_gain, max\_eirp), (dfs\_cac\_time) Oct 7 11:55:49 swi-mdm9x28 user.info kernel: [57.954901] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) Oct 7 11:55:49 swi-mdm9x28 user.info kernel: [57.954911] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) Oct 7 11:55:49 swi-mdm9x28 user.info kernel: [57.954922] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) Oct 7 11:55:49 swi-mdm9x28 user.info kernel: [57.954932] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) Oct 7 11:55:49 swi-mdm9x28 user.info kernel: [57.954943] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) Oct 7 11:55:49 swi-mdm9x28 user.info kernel: [57.954954] cfg80211: (5490000 KHz - 5710000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) Oct 7 11:55:49 swi-mdm9x28 user.info kernel: [57.954965] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) Oct 7 11:55:49 swi-mdm9x28 user.info kernel: [57.954976] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) Oct 7 11:55:50 swi-mdm9x28 user.err kernel: [58.899749] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:2 cur:0 tx) bc(rx:1 tx:1) mode:FIFO slv\_addr:0x70 MSTR\_STS:0x0d1300c8 OPER:0x00000010 Oct 7 11:55:50 swi-mdm9x28 user.err kernel: [58.917872] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:2 cur:0 tx) bc(rx:1 tx:1) mode:FIFO slv\_addr:0x70 MSTR\_STS:0x011363c8 OPER:0x00000010 Oct 7 11:55:50 swi-mdm9x28 user.info Legato: INFO | wifiService[694] | mangOH red board Oct 7 11:55:50 swi-mdm9x28 user.err kernel: [58.934524] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:2 cur:0 tx) bc(rx:1 tx:1) mode:FIFO slv\_addr:0x70 MSTR\_STS:0x0d1300c8 OPER:0x00000010 Oct 7 11:55:50 swi-mdm9x28 user.debug kernel: [58.951982] gpio\_sync\_ri: RI owner is Modem Oct 7 11:55:50 swi-mdm9x28 user.debug kernel: [58.952023] gpio\_map\_name\_to\_num: find GPIO 76 Oct 7 11:55:50 swi-mdm9x28 user.debug kernel: [58.952037] export\_store: Export GPIO: 76 Oct 7 11:55:50 swi-mdm9x28 user.debug kernel: [58.952078] gpio\_sync\_ri: RI owner is Modem Oct 7 11:55:50 swi-mdm9x28 user.debug kernel: [58.952098] gpiod\_export: sierra–find GPIO,chipdev = -822253552,chipngpio = 80,chipbase = 0 Oct 7 11:55:50 swi-mdm9x28 user.debug kernel: [58.953769] gpio\_sync\_ri: RI owner is Modem Oct 7 11:55:50 swi-mdm9x28 user.debug kernel: [58.953803] gpio\_map\_name\_to\_num: find GPIO 38 Oct 7 11:55:50 swi-mdm9x28 user.debug kernel: [58.953817] export\_store: Export GPIO: 38 Oct 7 11:55:50 swi-mdm9x28 user.debug kernel: [58.953851] gpio\_sync\_ri: RI owner is Modem Oct 7 11:55:50 swi-mdm9x28 user.debug kernel: [58.953869] gpiod\_export: sierra–find GPIO,chipdev = -822253552,chipngpio = 80,chipbase = 0 Oct 7 11:55:50 swi-mdm9x28 user.debug kernel: [58.983681] gpio\_sync\_ri: RI owner is Modem Oct 7 11:55:50 swi-mdm9x28 user.debug kernel: [58.983716] gpio\_map\_name\_to\_num: find GPIO 58 Oct 7 11:55:50 swi-mdm9x28 user.debug kernel: [58.983729] export\_store: Export GPIO: 58 Oct 7 11:55:50 swi-mdm9x28 user.debug kernel: [58.983762] gpio\_sync\_ri: RI owner is Modem Oct 7 11:55:50 swi-mdm9x28 user.debug kernel: [58.983779] gpiod\_export: sierra–find GPIO,chipdev = -822253552,chipngpio = 80,chipbase = 0 Oct 7 11:55:50 swi-mdm9x28 user.warn kernel: [58.985691] sdhci\_msm 7864900.sdhci: card claims to support voltages below defined range Oct 7 11:55:50 swi-mdm9x28 user.warn kernel: [59.031787] mmc0: queuing unknown CIS tuple 0x91 (3 bytes) Oct 7 11:55:50 swi-mdm9x28 user.info kernel: [59.033967] mmc0: new high speed SDIO card at address 0001 Oct 7 11:55:51 swi-mdm9x28 user.warn kernel: [59.158695] modprobe (1654) used greatest stack depth: 4884 bytes left Oct 7 11:55:51 swi-mdm9x28 user.info kernel: [59.774835] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11) Oct 7 11:55:51 swi-mdm9x28 user.info Legato: INFO | wifiService[694]/daemon T=WifiClientPaThread | pa\_wifi\_client\_ti.c WifiClientPaThreadMain() 257 | PARSING:phy #0: renamed to phy0 : len:24 Oct 7 11:55:51 swi-mdm9x28 user.info kernel: [59.871614] wlcore: loaded Oct 7 11:55:56 swi-mdm9x28 user.err kernel: [64.584390] wlcore: ERROR firmware boot failed despite 3 retries Oct 7 11:55:56 swi-mdm9x28 user.err kernel: [64.589709] [RMNET:HI] rmnet\_config\_notify\_cb(): Kernel is trying to unregister wlan0 Oct 7 11:55:56 swi-mdm9x28 user.err Legato: =ERR= | wifiService[694] | ifconfig: SIOCSIFFLAGS: No medium found Oct 7 11:55:56 swi-mdm9x28 user.info Legato: INFO | wifiService[694] | Failed to start TI wifi Oct 7 11:55:56 swi-mdm9x28 user.err Legato: =ERR= | wifiService[694]/daemon T=main | pa\_wifi\_client\_ti.c pa\_wifiClient\_Start() 349 | WiFi Client Command Failed: (23296)wlan0 WIFI\_START Oct 7 11:55:56 swi-mdm9x28 user.err kernel: [64.651405] [RMNET:HI] rmnet\_config\_notify\_cb(): Kernel is trying to unregister wlan0 Oct 7 11:55:56 swi-mdm9x28 user.info kernel: [64.751969] mmc0: card 0001 removed Oct 7 11:55:56 swi-mdm9x28 user.info Legato: INFO | supervisor[657]/supervisor T=main | supervisor.c SigChildHandler() 781 | Reaping unconfigured child process 1627. Oct 7 11:55:56 swi-mdm9x28 user.err Legato: =ERR= | wifiService[694]/daemon T=WifiClientPaThread | pa\_wifi\_client\_ti.c ThreadDestructor() 189 | Unable to kill the WIFI events script Oct 7 11:55:56 swi-mdm9x28 user.err Legato: =ERR= | wifiService[694]/daemon T=main | le\_wifiClient.c le\_wifiClient\_Start() 607 | Unable to start WIFI client. Err: -6 Oct 7 11:55:56 swi-mdm9x28 user.debug Legato: DBUG | wifiService[694]/daemon T=main | le\_wifiClient.c CloseSessionEventHandler() 452 | sessionRef 0x7f57cd8c GetFirstSessionRef (nil) Oct 7 11:55:56 swi-mdm9x28 user.debug Legato: DBUG | wifiService[694]/framework T=main | le\_wifiClient\_server.c CleanupClientData() 148 | Client 0x7f57cd8c is closed !!! Oct 7 11:55:56 swi-mdm9x28 user.debug Legato: DBUG | wifiService[694]/framework T=main | le\_wifiAp\_server.c CleanupClientData() 148 | Client 0x7f57ccfc is closed !!! Oct 7 11:56:03 swi-mdm9x28 user.info Legato: INFO | supervisor[657]/supervisor T=main | supervisor.c HandleRebootExpiry() 524 | Expired reboot timer root@swi-mdm9x28:~# ---
**Author:** ![jyijyi](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jyijyi/32/997_2.png) [@jyijyi](https://mangoh.discourse.group/u/jyijyi)\ **Post date:** [October 7, 2020, 2:26pm UTC](https://mangoh.discourse.group/t/wifi-not-coming-up-with-rmnet-enabled/5370/2 "2020-10-07T14:26:28Z")
do you mean problem only happens when rmnet is enabled? I don’t see problem with the following command: cm data connect & (wait until IP address obtained in rmnet) wifi client start ---
**Author:** ![tejaswisj](https://avatars.discourse-cdn.com/v4/letter/t/ee7513/32.png) [@tejaswisj](https://mangoh.discourse.group/u/tejaswisj)\ **Post date:** [October 7, 2020, 6:04pm UTC](https://mangoh.discourse.group/t/wifi-not-coming-up-with-rmnet-enabled/5370/3 "2020-10-07T18:04:21Z")
Yes, only when the cellular is enabled this issue happens. Else wifi works fine. As per the logs the firmware boot failed, and then SIOCSIFFLAGS: No medium found. Can you help me understand what is the issue here. Logs: Oct 7 11:55:56 swi-mdm9x28 user.err kernel: [64.584390] wlcore: ERROR firmware boot failed despite 3 retries Oct 7 11:55:56 swi-mdm9x28 user.err kernel: [64.589709] [RMNET:HI] rmnet\_config\_notify\_cb(): Kernel is trying to unregister wlan0 Oct 7 11:55:56 swi-mdm9x28 user.err Legato: =ERR= | wifiService[694] | ifconfig: SIOCSIFFLAGS: No medium found Oct 7 11:55:56 swi-mdm9x28 user.info Legato: INFO | wifiService[694] | Failed to start TI wifi ---
**Author:** ![jyijyi](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jyijyi/32/997_2.png) [@jyijyi](https://mangoh.discourse.group/u/jyijyi)\ **Post date:** [October 8, 2020, 1:22am UTC](https://mangoh.discourse.group/t/wifi-not-coming-up-with-rmnet-enabled/5370/4 "2020-10-08T01:22:32Z")
I don’t see problem with WP76 FW R13: root@swi-mdm9x28-wp:~# legato version 19.02.0\_4cb954265427b8c2c668a010ff5be274 root@swi-mdm9x28-wp:~# root@swi-mdm9x28-wp:~# cm info Device: WP7607-1 IMEI: 359780080500170 IMEISV: 6 FSN: [77.518959] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv\_addr:0x3a MSTR\_STS:0x0c1300c8 OPER:0x00000090 V2842570321010 Firmware Version: SWI9X07Y\_02.28.0[77.538586] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv\_addr:0x3a MSTR\_STS:0x0c1300c8 OPER:0x00000090 3.05 000000 jenkins 2019/07/08 11:04:16 Bootloader Version: SWI9X07Y\_02.28.03.05 000000 jenkins 2019/07/08 11:04:16 MCU Version: 002.011 PRI Part Number (PN): 9908645 PRI Revision: 001.001 Carrier PRI Name: GENERIC Carrier PRI Revision: 002.073\_000 SKU: 1104186 Last Reset Cause: Reset, User Requested Resets Count: Expected: 111 Unexpected: 0 root@swi-mdm9x28-wp:~# root@swi-mdm9x28-wp:~# cm data connect & root@swi-mdm9x28-wp:~# root@swi-mdm9x28-wp:~# Setting up profile 1 Connecting … ok Checking if device ‘rmnet\_data0’ is up … ok Routing inet … ok mv: can’t remove ‘/etc/resolv.conf’: Device or resource busy Updating /etc/resolv.conf … ok Updating /etc/resolv.conf … ok Testing connection … root@swi-mdm9x28-wp:~# root@swi-mdm9x28-wp:~# cm data Index: 1 APN: hkcsl PDP Type: IPV4V6 Connected: yes Interface: rmnet\_data0 Family[IPv4]: inet IP[IPv4]: 10.165.52.210 Gateway[IPv4]: 10.165.52.209 Dns1[IPv4]: 10.144.148.129 Dns2[IPv4]: 10.144.148.5 root@swi-mdm9x28-wp:~# root@swi-mdm9x28-wp:~# ping [www.google.com](http://www.google.com) PING [www.google.com](http://www.google.com) (172.217.24.196): 56 data bytes 64 bytes from 172.217.24.196: seq=0 ttl=117 time=27.860 ms 64 bytes from 172.217.24.196: seq=1 ttl=117 time=38.277 ms ^C — [www.google.com](http://www.google.com) ping statistics — 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max = 27.860/33.068/38.277 ms root@swi-mdm9x28-wp:~# wifi client start [104.363892] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:2 cur:0 tx) bc(rx:1 tx:1) mode:FIFO slv\_addr:0x70 MSTR\_STS:0x0d1300c8 OPER:0x00000010 [104.379295] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:2 cur:0 tx) bc(rx:1 tx:1) mode:FIFO slv\_addr:0x70 MSTR\_STS:0x0d1300c8 OPER:0x00000010 [104.395195] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:2 cur:0 tx) bc(rx:1 tx:1) mode:FIFO slv\_addr:0x70 MSTR\_STS:0x0d1300c8 OPER:0x00000010 [104.411746] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:2 cur:0 tx) bc(rx:1 tx:1) mode:FIFO slv\_addr:0x70 MSTR\_STS:0x0d1300c8 OPER:0x00000010 [104.427038] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:2 cur:0 tx) bc(rx:1 tx:1) mode:FIFO slv\_addr:0x70 MSTR\_STS:0x0d1300c8 OPER:0x00000010 [104.442676] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:2 cur:0 tx) bc(rx:1 tx:1) mode:FIFO slv\_addr:0x70 MSTR\_STS:0x0d1300c8 OPER:0x00000010 successfully called start. root@swi-mdm9x28-wp:~# root@swi-mdm9x28-wp:~# ifconfig bridge0 Link encap:Ethernet HWaddr FA:CF:97:AA:94:A1 inet addr:192.168.225.1 Bcast:192.168.225.255 Mask:255.255.255.0 inet6 addr: fe80::f8cf:97ff:fea7:919e/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:1 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:76 (76.0 B) ecm0 Link encap:Ethernet HWaddr 86:63:6E:45:02:1C inet6 addr: fe80::8463:6eff:fe45:21c/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:191 errors:0 dropped:4 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:28560 (27.8 KiB) TX bytes:468 (468.0 B) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) rmnet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 UP RUNNING MTU:2000 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:16 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:972 (972.0 B) TX bytes:1162 (1.1 KiB) rmnet\_data0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:10.165.52.210 Mask:255.255.255.252 inet6 addr: fe80::3ce7:dc:76d1:2e91/64 Scope:Link UP RUNNING MTU:1500 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:16 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:908 (908.0 B) TX bytes:1162 (1.1 KiB) wlan0 Link encap:Ethernet HWaddr D0:B5:C2:F1:F5:5B UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) ---
**Author:** ![tejaswisj](https://avatars.discourse-cdn.com/v4/letter/t/ee7513/32.png) [@tejaswisj](https://mangoh.discourse.group/u/tejaswisj)\ **Post date:** [October 14, 2020, 12:45pm UTC](https://mangoh.discourse.group/t/wifi-not-coming-up-with-rmnet-enabled/5370/5 "2020-10-14T12:45:25Z")
we tried on existing board which was flashed with FW13 and it dint work. We got another MangoH red board, dint flash bcoz we faced dhcp not cmg up issues when flashed. When i try wifi scan on that i get only one AP , even if there are 2 more available. Below are the console logs and logread. Is there any issue faced like this ? root@swi-mdm9x28:~# wifi client start [144.574458] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:2 cur:0 tx) bc(rx:1 tx:1) mode:FIFO slv\_addr:0x70 [144.591628] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:2 cur:0 tx) bc(rx:1 tx:1) mode:FIFO slv\_addr:0x70 [144.607456] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:2 cur:0 tx) bc(rx:1 tx:1) mode:FIFO slv\_addr:0x70 successfully called start. root@swi-mdm9x28:~# wifi client scan starting scan. Found: SSID: “TP-Link\_49F5” BSSID: “” Strength:-37 Ref:0x10000001 root@swi-mdm9x28:~# cm info Device: WP7608 IMEI: 352913090102888 IMEISV: 4 FSN: XG814285460710 Firmware Version: SWI9X07Y\_02.14.04.00 000000 jenkins 2018/[195.359005] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its 0 02/14 20:19:41 Bootloader Version: SWI9X07Y\_02.14.04.00 000000 jenkins 2018/02/14 20:19:41 MCU Version: 002.007 PRI Part Number (PN): 9907762 PRI Revision: 001.002 Carrier PRI Name: GENERIC Carrier PRI Revision: 002.025\_000 SKU: 1103788 Last Reset Cause: Unknown Resets Count: Expected: 3 Unexpected: 2 [log.txt](https://mangoh.discourse.group/uploads/short-url/MiWka14B7bhxtzMyv5zXWL7q0A.txt) (40.5 KB) ---
**Author:** ![jyijyi](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jyijyi/32/997_2.png) [@jyijyi](https://mangoh.discourse.group/u/jyijyi)\ **Post date:** [October 14, 2020, 1:39pm UTC](https://mangoh.discourse.group/t/wifi-not-coming-up-with-rmnet-enabled/5370/6 "2020-10-14T13:39:11Z")
At least this one is working. Probably the signal is too weak ---
**Author:** ![tejaswisj](https://avatars.discourse-cdn.com/v4/letter/t/ee7513/32.png) [@tejaswisj](https://mangoh.discourse.group/u/tejaswisj)\ **Post date:** [October 14, 2020, 4:40pm UTC](https://mangoh.discourse.group/t/wifi-not-coming-up-with-rmnet-enabled/5370/7 "2020-10-14T16:40:02Z")
Very interestingly, when i do a parallel test of scan, on the new one i get only one AP, while on the other i get 2 / 3 more. Images are different. Will there be any SW changes which is causing this ? ---
**Author:** ![jyijyi](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jyijyi/32/997_2.png) [@jyijyi](https://mangoh.discourse.group/u/jyijyi)\ **Post date:** [October 14, 2020, 11:10pm UTC](https://mangoh.discourse.group/t/wifi-not-coming-up-with-rmnet-enabled/5370/8 "2020-10-14T23:10:14Z")
Not sure if same fw in the wifi chipset. Are you using same WIFI IOT card for your testing? ---
**Author:** ![tejaswisj](https://avatars.discourse-cdn.com/v4/letter/t/ee7513/32.png) [@tejaswisj](https://mangoh.discourse.group/u/tejaswisj)\ **Post date:** [October 15, 2020, 2:25am UTC](https://mangoh.discourse.group/t/wifi-not-coming-up-with-rmnet-enabled/5370/9 "2020-10-15T02:25:20Z")
Yes, using the Talon Mirage module. ---
**Author:** ![jyijyi](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jyijyi/32/997_2.png) [@jyijyi](https://mangoh.discourse.group/u/jyijyi)\ **Post date:** [October 15, 2020, 2:32am UTC](https://mangoh.discourse.group/t/wifi-not-coming-up-with-rmnet-enabled/5370/10 "2020-10-15T02:32:25Z")
is it same card for the two testings? BTW, you can check the WIFI FW by dmesg: * * * [73361.133427] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11) [73361.244136] wlcore: loaded [73376.281456] wlcore: PHY firmware version: Rev 8.2.0.0.212 [73376.334918] wlcore: firmware booted (Rev 8.9.0.0.17) * * * ---
**Author:** ![tejaswisj](https://avatars.discourse-cdn.com/v4/letter/t/ee7513/32.png) [@tejaswisj](https://mangoh.discourse.group/u/tejaswisj)\ **Post date:** [October 15, 2020, 8:15am UTC](https://mangoh.discourse.group/t/wifi-not-coming-up-with-rmnet-enabled/5370/11 "2020-10-15T08:15:52Z")
yes i am using the same card. ---
**Author:** ![jyijyi](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jyijyi/32/997_2.png) [@jyijyi](https://mangoh.discourse.group/u/jyijyi)\ **Post date:** [October 15, 2020, 8:24am UTC](https://mangoh.discourse.group/t/wifi-not-coming-up-with-rmnet-enabled/5370/12 "2020-10-15T08:24:24Z")
As you say " Images are different" for the test, then probably this makes the difference. ---
**Author:** ![tejaswisj](https://avatars.discourse-cdn.com/v4/letter/t/ee7513/32.png) [@tejaswisj](https://mangoh.discourse.group/u/tejaswisj)\ **Post date:** [October 15, 2020, 8:37am UTC](https://mangoh.discourse.group/t/wifi-not-coming-up-with-rmnet-enabled/5370/13 "2020-10-15T08:37:12Z")
Ok if the mangoH red board Image makes a difference, i find only FW13/12 working for me. But if i reflash the MangoH red board, the dhcp is having issue. How to fix all these. Is there a way to fix the dhcp issue on the MangoH red board after flashing ? ---
**Author:** ![jyijyi](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jyijyi/32/997_2.png) [@jyijyi](https://mangoh.discourse.group/u/jyijyi)\ **Post date:** [October 15, 2020, 8:46am UTC](https://mangoh.discourse.group/t/wifi-not-coming-up-with-rmnet-enabled/5370/14 "2020-10-15T08:46:15Z")
what do you mean by “DHCP is having issue”? you can manually setup host IP so that you can ping 192.168.2.2 from the host to module USB ECM. ---
**Author:** ![tejaswisj](https://avatars.discourse-cdn.com/v4/letter/t/ee7513/32.png) [@tejaswisj](https://mangoh.discourse.group/u/tejaswisj)\ **Post date:** [October 15, 2020, 10:29am UTC](https://mangoh.discourse.group/t/wifi-not-coming-up-with-rmnet-enabled/5370/15 "2020-10-15T10:29:05Z")
When the board boots up, the ecm0 is assigned IP automatically. If the IP is manually assigned, the dhcp fails to run and my other device which is trying to use the ecm0 IP is having issues . ---
**Author:** ![jyijyi](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jyijyi/32/997_2.png) [@jyijyi](https://mangoh.discourse.group/u/jyijyi)\ **Post date:** [October 15, 2020, 10:30am UTC](https://mangoh.discourse.group/t/wifi-not-coming-up-with-rmnet-enabled/5370/16 "2020-10-15T10:30:45Z")
you can set your “other device” to have static IP address: e.g. sudo ifconfig usb0 192.168.2.3 ---
**Author:** ![tejaswisj](https://avatars.discourse-cdn.com/v4/letter/t/ee7513/32.png) [@tejaswisj](https://mangoh.discourse.group/u/tejaswisj)\ **Post date:** [October 15, 2020, 11:35am UTC](https://mangoh.discourse.group/t/wifi-not-coming-up-with-rmnet-enabled/5370/17 "2020-10-15T11:35:17Z")
Yes that is already been set. So if the dhcp does not come up or failed at the WP end, the other devices which is running android also will not assign IP. This will lead to other issues on the Android device. ---
**Author:** ![jyijyi](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jyijyi/32/997_2.png) [@jyijyi](https://mangoh.discourse.group/u/jyijyi)\ **Post date:** [October 15, 2020, 11:52am UTC](https://mangoh.discourse.group/t/wifi-not-coming-up-with-rmnet-enabled/5370/18 "2020-10-15T11:52:12Z")
Why don’t you set static IP on your android device? ---
**Author:** ![tejaswisj](https://avatars.discourse-cdn.com/v4/letter/t/ee7513/32.png) [@tejaswisj](https://mangoh.discourse.group/u/tejaswisj)\ **Post date:** [October 16, 2020, 7:48am UTC](https://mangoh.discourse.group/t/wifi-not-coming-up-with-rmnet-enabled/5370/19 "2020-10-16T07:48:16Z")
yes, we are doing that only. Static IP on usb0 port. But on reboot of WP, if ecm0 is not assigned automatically, the android device will not function properly since dhcp does not come up at WP, ---
**Author:** ![jyijyi](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jyijyi/32/997_2.png) [@jyijyi](https://mangoh.discourse.group/u/jyijyi)\ **Post date:** [October 16, 2020, 8:02am UTC](https://mangoh.discourse.group/t/wifi-not-coming-up-with-rmnet-enabled/5370/20 "2020-10-16T08:02:54Z")
I don’t see problem to have the DHCP on USB ECM port: [8864798.502432] usb 3-6: Product: Sierra Wireless WP7607-1 [8864798.502438] usb 3-6: Manufacturer: Sierra Wireless, Incorporated [8864798.502444] usb 3-6: SerialNumber: V284257032101004 [8864798.509630] GobiSerial 3-6:1.0: GobiSerial converter detected [8864798.510011] usb 3-6: GobiSerial converter now attached to ttyUSB0 [8864798.510739] GobiSerial 3-6:1.2: GobiSerial converter detected [8864798.510986] usb 3-6: GobiSerial converter now attached to ttyUSB1 [8864798.512679] GobiSerial 3-6:1.3: GobiSerial converter detected [8864798.512988] usb 3-6: GobiSerial converter now attached to ttyUSB2 [8864798.513801] QMAP Disabled [8864798.515434] GobiNet 3-6:1.8 eth1: register ‘GobiNet’ at usb-0000:00:14.0-6, GobiNet Ethernet Device, 5e:e4:09:45:f5:59 [8864798.515814] USB Speed : USB 2.0 [8864798.520669] cdc\_ether 3-6:1.19 usb0: register ‘cdc\_ether’ at usb-0000:00:14.0-6, CDC Ethernet Device, 22:c7:9a:99:c2:99 [8864818.495453] creating qcqmi0 [8864818.495738] RawIP mode owner@CNHKG-EX-001367:~/Yocto/WP76/R13.3/yocto$ ifconfig usb0 usb0 Link encap:Ethernet HWaddr 22:c7:9a:99:c2:99 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) owner@CNHKG-EX-001367:~/Yocto/WP76/R13.3/yocto$ sudo dhclient usb0 [sudo] password for owner: owner@CNHKG-EX-001367:~/Yocto/WP76/R13.3/yocto$ ifconfig usb0 usb0 Link encap:Ethernet HWaddr 22:c7:9a:99:c2:99 inet addr:192.168.2.3 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::20c7:9aff:fe99:c299/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:15 errors:0 dropped:0 overruns:0 frame:0 TX packets:27 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1632 (1.6 KB) TX bytes:7109 (7.1 KB) owner@CNHKG-EX-001367:~/Yocto/WP76/R13.3/yocto$ ping 192.168.2.2 PING 192.168.2.2 (192.168.2.2) 56(84) bytes of data. 64 bytes from 192.168.2.2: icmp\_seq=1 ttl=64 time=2.29 ms 64 bytes from 192.168.2.2: icmp\_seq=2 ttl=64 time=2.16 ms