WiFi doesn't start

Hope this helps.

More info:

Looks like something is wrong with(or processing of) wpa_supplicant.conf file

Content of my wpa_supplicant.conf:

root@reach[/etc/wpa_supplicant]# ls
entropy.bin udhcpd-p2p.conf wpa_supplicant.conf
p2p_supplicant.conf wpa_cli-actions.sh

root@reach[/etc/wpa_supplicant]# cat wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
config_methods=virtual_push_button virtual_display push_button keypad
update_config=1
fast_reauth=1
device_name=Edison
manufacturer=Intel
model_name=Edison

network={
ssid="SiminnHeima"
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
eap=TTLS PEAP TLS
psk=“MY_PSK”
}
root@reach[/etc/wpa_supplicant]#

rfkill list returns:

root@reach[~]# rfkill list
2: bcm43xx Bluetooth: bluetooth
Soft blocked: no
Hard blocked: no
3: hci0: bluetooth
Soft blocked: no
Hard blocked: no
4: phy1: wlan
Soft blocked: no
Hard blocked: no
5: brcmfmac-wifi: wlan
Soft blocked: no
Hard blocked: no

journalctl -u reach_setup --no-pager returns

root@reach[~]# journalctl -u reach_setup --no-pager
– Logs begin at Sat 2000-01-01 00:00:10 UTC, end at Mon 2017-01-30 17:40:23 UTC. –
Jan 30 17:31:15 reach systemd[1]: Starting Emlid Reach setup…
Jan 30 17:31:15 reach systemd[1]: Started Emlid Reach setup.
Jan 30 17:31:19 reach reach_setup[258]: u-blox:true,mpu:true,ltc:false,stc:false,lora:false
Jan 30 17:31:19 reach reach_setup[258]: Reach
Jan 30 17:31:24 reach reach_setup[258]: Network mode: master
Jan 30 17:31:29 reach reach_setup[258]: --2017-01-30 17:31:29-- https://files.emlid.com/reach/dev-repo/edison/Packages.gz
Jan 30 17:31:30 reach reach_setup[258]: Resolving files.emlid.com… failed: Temporary failure in name resolution.
Jan 30 17:31:30 reach reach_setup[258]: wget: unable to resolve host address 'files.emlid.com
Jan 30 17:31:30 reach reach_setup[258]: --2017-01-30 17:31:30-- https://files.emlid.com/reach/dev-repo/core2-32/Packages.gz
Jan 30 17:31:30 reach reach_setup[258]: Resolving files.emlid.com… failed: Temporary failure in name resolution.
Jan 30 17:31:30 reach reach_setup[258]: wget: unable to resolve host address 'files.emlid.com
Jan 30 17:31:31 reach reach_setup[258]: --2017-01-30 17:31:31-- https://files.emlid.com/reach/dev-repo/all/Packages.gz
Jan 30 17:31:31 reach reach_setup[258]: Resolving files.emlid.com… failed: Temporary failure in name resolution.
Jan 30 17:31:31 reach reach_setup[258]: wget: unable to resolve host address 'files.emlid.com
Jan 30 17:31:31 reach reach_setup[258]: (335) wsgi starting up on http://0.0.0.0:80
Jan 30 17:32:09 reach reach_setup[258]: (335) accepted (‘192.168.42.20’, 48588)
Jan 30 17:32:09 reach reach_setup[258]: (335) accepted (‘192.168.42.20’, 48590)
Jan 30 17:32:09 reach reach_setup[258]: (335) accepted (‘192.168.42.20’, 48592)
Jan 30 17:32:09 reach reach_setup[258]: (335) accepted (‘192.168.42.20’, 48594)
Jan 30 17:32:10 reach reach_setup[258]: (335) accepted (‘192.168.42.20’, 48596)
Jan 30 17:32:10 reach reach_setup[258]: (335) accepted (‘192.168.42.20’, 48598)

journalctl -u wpa_supplicant --no-pager returns

root@reach[~]# journalctl -u wpa_supplicant --no-pager
– Logs begin at Sat 2000-01-01 00:00:10 UTC, end at Mon 2017-01-30 17:41:26 UTC. –
Jan 30 17:31:20 reach systemd[1]: Starting WPA supplicant service…
Jan 30 17:31:21 reach wpa_supplicant[290]: Successfully initialized wpa_supplicant
Jan 30 17:31:21 reach wpa_supplicant[290]: Long line in configuration file truncated
Jan 30 17:31:21 reach wpa_supplicant[290]: Line 11: unknown global field ‘ssid=“SiminnHeima”’.
Jan 30 17:31:21 reach wpa_supplicant[290]: Line 11: Invalid configuration line ‘ssid=“SiminnHeima”’.
Jan 30 17:31:21 reach wpa_supplicant[290]: Line 12: unknown global field ‘proto=RSN’.
Jan 30 17:31:21 reach wpa_supplicant[290]: Line 12: Invalid configuration line ‘proto=RSN’.
Jan 30 17:31:21 reach wpa_supplicant[290]: Line 13: unknown global field ‘key_mgmt=WPA-PSK’.
Jan 30 17:31:21 reach wpa_supplicant[290]: Line 13: Invalid configuration line ‘key_mgmt=WPA-PSK’.
Jan 30 17:31:21 reach wpa_supplicant[290]: Line 14: unknown global field ‘pairwise=CCMP TKIP’.
Jan 30 17:31:21 reach wpa_supplicant[290]: Line 14: Invalid configuration line ‘pairwise=CCMP TKIP’.
Jan 30 17:31:21 reach wpa_supplicant[290]: Line 15: unknown global field ‘group=CCMP TKIP’.
Jan 30 17:31:21 reach wpa_supplicant[290]: Line 15: Invalid configuration line ‘group=CCMP TKIP’.
Jan 30 17:31:21 reach wpa_supplicant[290]: Line 16: unknown global field ‘eap=TTLS PEAP TLS’.
Jan 30 17:31:21 reach wpa_supplicant[290]: Line 16: Invalid configuration line ‘eap=TTLS PEAP TLS’.
Jan 30 17:31:21 reach wpa_supplicant[290]: Line 17: unknown global field ‘psk=“MY_PSK”’.
Jan 30 17:31:21 reach wpa_supplicant[290]: Line 17: Invalid configuration line ‘psk=“MY_PSK”’.
Jan 30 17:31:21 reach wpa_supplicant[290]: Line 18: unknown global field ‘}’.
Jan 30 17:31:21 reach wpa_supplicant[290]: Line 18: Invalid configuration line ‘}’.
Jan 30 17:31:21 reach wpa_supplicant[290]: Failed to read or parse configuration ‘/etc/wpa_supplicant/wpa_supplicant.conf’.
Jan 30 17:31:21 reach systemd[1]: wpa_supplicant.service: main process exited, code=exited, status=255/n/a
Jan 30 17:31:21 reach systemd[1]: Failed to start WPA supplicant service.
Jan 30 17:31:21 reach systemd[1]: Unit wpa_supplicant.service entered failed state.
Jan 30 17:31:21 reach systemd[1]: Stopped WPA supplicant service.

Problem solved for both Reach modules.
Now running ReachView 2.9.1 (was 2.9.0).
Problem was corrupt wpa_supplicant.conf file and only shows in editor(nano).
When cat(ed) looks ok but in nano editor you see problem.

How can a .conf get corrupted ? I mean since both device had the same issue.
Its a question in general, feel free to answer anybody how can

This topic was automatically closed 100 days after the last reply. New replies are no longer allowed.