# mangOH yellow wifi not working **URL:** \ **Category:** mangOH Yellow\ **Created:** [November 13, 2019, 2:54pm UTC](https://mangoh.discourse.group/t/mangoh-yellow-wifi-not-working/3059 "2019-11-13T14:54:13Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![Elmo](https://avatars.discourse-cdn.com/v4/letter/e/e480ec/32.png) [@Elmo](https://mangoh.discourse.group/u/Elmo)\ **Post date:** [November 13, 2019, 2:54pm UTC](https://mangoh.discourse.group/t/mangoh-yellow-wifi-not-working/3059/1 "2019-11-13T14:54:13Z")
Hi, how can I get mangOH yellow builtin wifi to work? When wifiService is running and I “wifi client start”, it responds me with this: ERROR: le\_wifiClient\_Start returns ERROR. When I set all the necessary settings and try “wifi ap start”, i get back: ERROR:le\_wifiAp\_Start returns -1. Thanks in advance -Elmo ---
**Author:** ![tomalex](https://avatars.discourse-cdn.com/v4/letter/t/71e660/32.png) [@tomalex](https://mangoh.discourse.group/u/tomalex)\ **Post date:** [November 13, 2019, 7:53pm UTC](https://mangoh.discourse.group/t/mangoh-yellow-wifi-not-working/3059/2 "2019-11-13T19:53:16Z")
Hi Elmo, What exactly did you do before your have started the wifi service and client? Did you do some system changes? Like installing a new Mangoh Build? Or using the swiflash command? We also had some problems with Yellow Wifi last week after installing the Mangoh Build without Octave. Here is the ticket: > [@Mangoh Yellow Wifi app only iPV6](https://mangoh.discourse.group/t/mangoh-yellow-wifi-app-only-ipv6/2996/14): > > There were no external devices connected, and I used a high power USB. I have just talked with my colleague an he ended up with the same issue after installing a Mangoh Build without Octave. I think it has something to do with mixing up something on the filesystem. Swiflash -r does not work (only with WP77 release 11 but no difference) I will send you the new logs in PM. Thanks a lot, tom Due to time constrainst we ended up implementing the POC with FX30 and IOT wifi card but would be good to clear this issue. Please share us the log messages (logread cmd) when you start the wifi client. If you have the same problem you should see an error message like “‘/legato/systems/current/modules/brcmfmac.ko’: File exists”” . Best, tom ---
**Author:** ![Elmo](https://avatars.discourse-cdn.com/v4/letter/e/e480ec/32.png) [@Elmo](https://mangoh.discourse.group/u/Elmo)\ **Post date:** [November 13, 2019, 8:51pm UTC](https://mangoh.discourse.group/t/mangoh-yellow-wifi-not-working/3059/3 "2019-11-13T20:51:39Z")
Thanks for the answer, here is my logread of wifi client start command: Nov 13 22:30:13 swi-mdm9x28-wp user.warn Legato: -WRN- | supervisor[4236]/supervisor T=main | proc.c GetWatchdogAction() 362 | wifi@0 watchdogAction ‘’ in proc section Nov 13 22:30:13 swi-mdm9x28-wp user.info Legato: INFO | supervisor[4236]/supervisor T=main | app.c app\_Start() 3469 | Starting app ‘wifi’ Nov 13 22:30:13 swi-mdm9x28-wp user.info Legato: INFO | supervisor[4236]/supervisor T=main | app.c CreateFileLink() 2083 | Skipping file link ‘/legato/systems/current/apps/wifi/read-only/lib/libComponent\_wifi.so’ to '/legato/systems/current/appsWriteable/wifi/lib/libComponen Nov 13 22:30:13 swi-mdm9x28-wp user.info Legato: INFO | supervisor[4236]/supervisor T=main | app.c CreateFileLink() 2083 | Skipping file link ‘/legato/systems/current/apps/wifi/read-only/bin/wifi’ to ‘/legato/systems/current/appsWriteable/wifi/bin/wifi’: Already exists Nov 13 22:30:13 swi-mdm9x28-wp user.info Legato: INFO | supervisor[4236]/supervisor T=main | proc.c proc\_Start() 1403 | Starting process ‘wifi@0’ with pid 13543 Nov 13 22:30:13 swi-mdm9x28-wp user.info Legato: INFO | supervisor[4236]/supervisor T=main | supervisor.c SigChildHandler() 899 | Reaping unconfigured child process 13539. Nov 13 22:30:13 swi-mdm9x28-wp user.info Legato: INFO | supervisor[13543]/supervisor T=main | proc.c proc\_Start() 1363 | Execing ‘bin/wifi’ Nov 13 22:30:13 swi-mdm9x28-wp user.info Legato: INFO | supervisor[13543]/supervisor T=main | resourceLimits.c SetRLimitValue() 301 | Setting resource limit maxCoreDumpFileBytes to value 8192. Nov 13 22:30:13 swi-mdm9x28-wp user.info Legato: INFO | supervisor[13543]/supervisor T=main | resourceLimits.c SetRLimitValue() 301 | Setting resource limit maxFileBytes to value 90112. Nov 13 22:30:13 swi-mdm9x28-wp user.info Legato: INFO | supervisor[13543]/supervisor T=main | resourceLimits.c SetRLimitValue() 301 | Setting resource limit maxLockedMemoryBytes to value 8192. Nov 13 22:30:13 swi-mdm9x28-wp user.info Legato: INFO | supervisor[13543]/supervisor T=main | resourceLimits.c SetRLimitValue() 301 | Setting resource limit maxFileDescriptors to value 256. Nov 13 22:30:13 swi-mdm9x28-wp user.info Legato: INFO | supervisor[13543]/supervisor T=main | resourceLimits.c SetRLimitValue() 301 | Setting resource limit maxMQueueBytes to value 512. Nov 13 22:30:13 swi-mdm9x28-wp user.info Legato: INFO | supervisor[13543]/supervisor T=main | resourceLimits.c SetRLimitValue() 301 | Setting resource limit maxThreads to value 20. Nov 13 22:30:13 swi-mdm9x28-wp user.info Legato: INFO | supervisor[13543]/supervisor T=main | resourceLimits.c SetRLimitValue() 301 | Setting resource limit maxQueuedSignals to value 100. Nov 13 22:30:13 swi-mdm9x28-wp user.debug Legato: DBUG | wifiService[4405]/framework T=main | unixSocket.c ExtractFileDescriptor() 34 | Received fd (14). Nov 13 22:30:13 swi-mdm9x28-wp user.debug Legato: DBUG | wifiService[4405]/framework T=main | unixSocket.c ExtractFileDescriptor() 34 | Received fd (15). Nov 13 22:30:13 swi-mdm9x28-wp user.info Legato: INFO | wifiService[4405] | WIFI\_START Nov 13 22:30:14 swi-mdm9x28-wp user.err kernel: [21645.182350] 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 Nov 13 22:30:14 swi-mdm9x28-wp user.err kernel: [21645.197480] 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 Nov 13 22:30:14 swi-mdm9x28-wp user.err kernel: [21645.213303] 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 Nov 13 22:30:14 swi-mdm9x28-wp user.err kernel: [21645.228852] 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 Nov 13 22:30:14 swi-mdm9x28-wp user.err kernel: [21645.244587] 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 Nov 13 22:30:14 swi-mdm9x28-wp user.info Legato: INFO | wifiService[4405] | mangOH red board Nov 13 22:30:14 swi-mdm9x28-wp user.err kernel: [21645.260295] 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 Nov 13 22:30:14 swi-mdm9x28-wp user.debug kernel: [21645.276993] gpio\_map\_name\_to\_num: find GPIO 76 Nov 13 22:30:14 swi-mdm9x28-wp user.debug kernel: [21645.278075] gpio\_map\_name\_to\_num: find GPIO 38 Nov 13 22:30:14 swi-mdm9x28-wp user.info kernel: [21645.315050] cfg80211: Calling CRDA to update world regulatory domain Nov 13 22:30:14 swi-mdm9x28-wp user.info kernel: [21645.315172] cfg80211: World regulatory domain updated: Nov 13 22:30:14 swi-mdm9x28-wp user.info kernel: [21645.315184] cfg80211: DFS Master region: unset Nov 13 22:30:14 swi-mdm9x28-wp user.info kernel: [21645.315193] cfg80211: (start\_freq - end\_freq @ bandwidth), (max\_antenna\_gain, max\_eirp), (dfs\_cac\_time) Nov 13 22:30:14 swi-mdm9x28-wp user.info kernel: [21645.315206] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) Nov 13 22:30:14 swi-mdm9x28-wp user.info kernel: [21645.315217] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) Nov 13 22:30:14 swi-mdm9x28-wp user.info kernel: [21645.315228] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) Nov 13 22:30:14 swi-mdm9x28-wp user.info kernel: [21645.315238] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) Nov 13 22:30:14 swi-mdm9x28-wp user.info kernel: [21645.315249] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) Nov 13 22:30:14 swi-mdm9x28-wp user.info kernel: [21645.315260] cfg80211: (5490000 KHz - 5710000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) Nov 13 22:30:14 swi-mdm9x28-wp user.info kernel: [21645.315270] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) Nov 13 22:30:14 swi-mdm9x28-wp user.info kernel: [21645.315281] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) Nov 13 22:30:20 swi-mdm9x28-wp user.info Legato: INFO | wifiService[4405] | Failed to start TI wifi, interface does not exist. Nov 13 22:30:20 swi-mdm9x28-wp user.err kernel: [21650.745889] 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 Nov 13 22:30:20 swi-mdm9x28-wp user.err kernel: [21650.760749] 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 Nov 13 22:30:20 swi-mdm9x28-wp user.err kernel: [21650.787465] 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 Nov 13 22:30:20 swi-mdm9x28-wp user.err kernel: [21650.802667] 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 Nov 13 22:30:20 swi-mdm9x28-wp user.err kernel: [21650.818373] 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 Nov 13 22:30:20 swi-mdm9x28-wp user.info Legato: INFO | wifiService[4405] | mangOH red board Nov 13 22:30:20 swi-mdm9x28-wp user.err kernel: [21650.834056] 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 Nov 13 22:30:20 swi-mdm9x28-wp user.err Legato: =ERR= | wifiService[4405]/daemon T=main | pa\_wifi\_client.c pa\_wifiClient\_Start() 519 | WiFi card is not inserted Nov 13 22:30:20 swi-mdm9x28-wp user.warn Legato: -WRN- | wifiService[4405]/daemon T=main | le\_wifiClient.c le\_wifiClient\_Start() 821 | Unable to start WIFI client; return code: -1 Nov 13 22:30:20 swi-mdm9x28-wp user.info Legato: INFO | supervisor[4236]/supervisor T=main | proc.c proc\_SigChildHandler() 2079 | Process ‘wifi@0’ (PID: 13543) has exited with exit code 1. Nov 13 22:30:20 swi-mdm9x28-wp user.debug kernel: [21650.860945] gpio\_map\_name\_to\_num: find GPIO 76 Nov 13 22:30:20 swi-mdm9x28-wp user.debug kernel: [21650.861527] gpio\_map\_name\_to\_num: find GPIO 38 Nov 13 22:30:20 swi-mdm9x28-wp user.debug Legato: DBUG | wifiService[4405]/framework T=main | le\_wifiClient\_server.c CleanupClientData() 163 | Client 0x7f56c268 is closed !!! Nov 13 22:30:20 swi-mdm9x28-wp user.debug Legato: DBUG | wifiService[4405]/framework T=main | le\_wifiClient\_server.c CleanupClientData() 184 | Found session ref 0x7f56c388; does not match Nov 13 22:30:20 swi-mdm9x28-wp user.debug Legato: DBUG | wifiService[4405]/framework T=main | le\_wifiAp\_server.c CleanupClientData() 163 | Client 0x7f56c2f8 is closed !!! Nov 13 22:30:20 swi-mdm9x28-wp user.warn Legato: -WRN- | supervisor[4236]/supervisor T=main | app.c app\_SigChildHandler() 4064 | Process ‘wifi@0’ in app ‘wifi’ faulted: Ignored. Nov 13 22:30:20 swi-mdm9x28-wp user.info Legato: INFO | supervisor[4236]/supervisor T=main | app.c app\_StopComplete() 4751 | app ‘wifi’ has stopped. Nov 13 22:30:20 swi-mdm9x28-wp user.info Legato: INFO | supervisor[4236]/supervisor T=main | apps.c DeactivateAppContainer() 374 | Application ‘wifi’ has stopped. Seems like it’s not the same problem as you had. I might have messed up this unit trying to fix the problem, but i managed to test wifi with a brand new yellow also. Same errors there. -Elmo ---
**Author:** ![tomalex](https://avatars.discourse-cdn.com/v4/letter/t/71e660/32.png) [@tomalex](https://mangoh.discourse.group/u/tomalex)\ **Post date:** [November 13, 2019, 9:24pm UTC](https://mangoh.discourse.group/t/mangoh-yellow-wifi-not-working/3059/4 "2019-11-13T21:24:35Z")
Yes it seems to be a different problem. I don’t know what changes you have made before It seems to be that it is trying to enable the TI wifi which can be found for example on the IOT card. I presume you are not using a wifi IOT card as Mangoh Yellow should have a fully working on-board Cypress wifi chip, so it is not your goal. Could you install the offical Mangoh Yellow spk ([https://mangoh.io/mangoh-yellow-resources-software](https://mangoh.io/mangoh-yellow-resources-software)) and see if it starts the right wifi script. (BTW. Have you not changed something in the /etc/network/interfaces or some other files ? I think the Cypress wifi should be connected to wlan1 and TI chip to wlan0 but I am not sure) ---
**Author:** ![asyal](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/asyal/32/78_2.png) [@asyal](https://mangoh.discourse.group/u/asyal)\ **Post date:** [November 13, 2019, 9:45pm UTC](https://mangoh.discourse.group/t/mangoh-yellow-wifi-not-working/3059/5 "2019-11-13T21:45:49Z")
> [@Elmo](#): > > mangOH red board Did you update your firmware or is it standard yellow software? If yellow, I dont understand why you see mangohred on your log messages. ---
**Author:** ![Elmo](https://avatars.discourse-cdn.com/v4/letter/e/e480ec/32.png) [@Elmo](https://mangoh.discourse.group/u/Elmo)\ **Post date:** [November 14, 2019, 6:08am UTC](https://mangoh.discourse.group/t/mangoh-yellow-wifi-not-working/3059/6 "2019-11-14T06:08:38Z")
Thanks a lot, I will try to install yellow spk. I’m still afraid it won’t fix the problem as this has been the problem from the beginning. I haven’t touched interfaces as far as I remember. If I install yellow spk, will the interface file reset? -Elmo ---
**Author:** ![Elmo](https://avatars.discourse-cdn.com/v4/letter/e/e480ec/32.png) [@Elmo](https://mangoh.discourse.group/u/Elmo)\ **Post date:** [November 14, 2019, 6:13am UTC](https://mangoh.discourse.group/t/mangoh-yellow-wifi-not-working/3059/7 "2019-11-14T06:13:22Z")
With this unit, I have updated the firmware. But when I first got this, I tried right away ”ifup wlan0” and I remember wondering why it said ”mangOH red board”. I thought it used some same drivers or something for the wifi. I will test another unit with the firmware it came with when I have time, but the wifi has not been working on that one either. -Elmo ---
**Author:** ![asyal](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/asyal/32/78_2.png) [@asyal](https://mangoh.discourse.group/u/asyal)\ **Post date:** [November 14, 2019, 3:44pm UTC](https://mangoh.discourse.group/t/mangoh-yellow-wifi-not-working/3059/8 "2019-11-14T15:44:32Z")
There is no reason to see mangoh red in log file. Anyways, we will have a new spk and leaf packages available by tomorrow that should allow wifi to work with published commands ---
**Author:** ![Elmo](https://avatars.discourse-cdn.com/v4/letter/e/e480ec/32.png) [@Elmo](https://mangoh.discourse.group/u/Elmo)\ **Post date:** [November 14, 2019, 4:37pm UTC](https://mangoh.discourse.group/t/mangoh-yellow-wifi-not-working/3059/9 "2019-11-14T16:37:07Z")
Hi, thanks for advices. i got it working by installing spk-file tom suggested. Everything’s fine now. Still when you try ”ifup wlan0” you get back some mangOH red-stuff, idk why is that. -Elmo ---
**Author:** ![asyal](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/asyal/32/78_2.png) [@asyal](https://mangoh.discourse.group/u/asyal)\ **Post date:** [November 14, 2019, 5:05pm UTC](https://mangoh.discourse.group/t/mangoh-yellow-wifi-not-working/3059/10 "2019-11-14T17:05:13Z")
Can you point to the package? ---
**Author:** ![dfrey](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/dfrey/32/303_2.png) [@dfrey](https://mangoh.discourse.group/u/dfrey)\ **Post date:** [November 14, 2019, 9:11pm UTC](https://mangoh.discourse.group/t/mangoh-yellow-wifi-not-working/3059/11 "2019-11-14T21:11:36Z")
`ifup` and `ifdown` use the `/etc/network/interfaces` file. There is some junk in that file pertaining to the TI WiFi IoT card. Please use `ifconfig` or use the `wifi` command provided by legato. ---
**Author:** ![asyal](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/asyal/32/78_2.png) [@asyal](https://mangoh.discourse.group/u/asyal)\ **Post date:** [November 15, 2019, 7:46pm UTC](https://mangoh.discourse.group/t/mangoh-yellow-wifi-not-working/3059/12 "2019-11-15T19:46:32Z")
We have the spk available with the fix. Please try it and let us know. ---
**Author:** ![Elmo](https://avatars.discourse-cdn.com/v4/letter/e/e480ec/32.png) [@Elmo](https://mangoh.discourse.group/u/Elmo)\ **Post date:** [November 18, 2019, 2:27pm UTC](https://mangoh.discourse.group/t/mangoh-yellow-wifi-not-working/3059/13 "2019-11-18T14:27:11Z")
Works like a charm. Thanks for the help. -Elmo