10-08-2020, 01:40 PM
(This post was last modified: 10-08-2020, 03:19 PM by TheOldPresbyope.
Edit Reason: typo in expanded note about line breaks
)
@McFly
MoodeOS uses the underlying Raspberry Pi OS WiFi subsystem with no modification so CallMeMike's suggestion that you try with plain Raspberry Pi OS is a good one.
I'm a little dubious there's a problem with your onboard WiFi transceiver but certainly trying an external adapter would be a check.
Alternatively, if you are confident using the Linux command line you can try this on your ethernet-connected moOde player:
1. log into the moOde command line using either the built-in Web SSH Terminal or ssh from another computer.
2. kill the running wpa_supplicant processes:
3. start the wpa_supplicant process from the command line [ETA: both here and in step 5---depending on which monitor, orientation, and browser, this line may be folded into two with a line break between the '-' and the 'c'. This is not real.]
4. examine the scrolling output
5. kill the running wpa_supplicant process with a ^C.
Here's what I get with the correct SSID/PW credentials for my access point (I have edited out the real SSID and MAC address):
The key phrase is "Connection to xxxxxxx completed".
Here's what I get for a correct SSID and incorrect PW (I killed the process after several interations):
The key phrases are obvious.
Don't forget to reboot when you're done just for good measure.
Good luck.
Regards,
Kent
MoodeOS uses the underlying Raspberry Pi OS WiFi subsystem with no modification so CallMeMike's suggestion that you try with plain Raspberry Pi OS is a good one.
I'm a little dubious there's a problem with your onboard WiFi transceiver but certainly trying an external adapter would be a check.
Alternatively, if you are confident using the Linux command line you can try this on your ethernet-connected moOde player:
1. log into the moOde command line using either the built-in Web SSH Terminal or ssh from another computer.
2. kill the running wpa_supplicant processes:
Code:
sudo killall wpa_supplicant
3. start the wpa_supplicant process from the command line [ETA: both here and in step 5---depending on which monitor, orientation, and browser, this line may be folded into two with a line break between the '-' and the 'c'. This is not real.]
Code:
sudo wpa_supplicant -Dnl80211,wext -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf
4. examine the scrolling output
5. kill the running wpa_supplicant process with a ^C.
Here's what I get with the correct SSID/PW credentials for my access point (I have edited out the real SSID and MAC address):
Code:
pi@moode:~ $ sudo wpa_supplicant -Dnl80211,wext -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf
Successfully initialized wpa_supplicant
wlan0: Trying to associate with SSID 'MyAP'
wlan0: CTRL-EVENT-ASSOC-REJECT bssid=00:00:00:00:00:00 status_code=16
wlan0: Trying to associate with SSID 'MyAP'
wlan0: Associated with 48:5d:36:xx:xx:xx
wlan0: CTRL-EVENT-CONNECTED - Connection to 48:5d:36:xx:xx:xx completed [id=0 id_str=]
wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US
The key phrase is "Connection to xxxxxxx completed".
Here's what I get for a correct SSID and incorrect PW (I killed the process after several interations):
Code:
pi@moode:~ $ sudo wpa_supplicant -Dnl80211,wext -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf
Successfully initialized wpa_supplicant
wlan0: Trying to associate with SSID 'MyAP'
wlan0: CTRL-EVENT-ASSOC-REJECT bssid=48:5d:36:xx:xx:xx status_code=16
wlan0: Trying to associate with SSID 'MyAP'
wlan0: CTRL-EVENT-ASSOC-REJECT bssid=48:5d:36:xx:xx:xx status_code=16
wlan0: Trying to associate with SSID 'MyAP'
wlan0: CTRL-EVENT-ASSOC-REJECT bssid=48:5d:36:xx:xx:xx status_code=16
wlan0: Trying to associate with SSID 'MyAP'
wlan0: CTRL-EVENT-ASSOC-REJECT bssid=48:5d:36:xx:xx:xx status_code=16
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="MyAP" auth_failures=1 duration=10 reason=CONN_FAILED
wlan0: CTRL-EVENT-SSID-REENABLED id=0 ssid="Phyllis"
wlan0: Trying to associate with SSID 'MyAP'
wlan0: CTRL-EVENT-ASSOC-REJECT bssid=48:5d:36:xx:xx:xx status_code=16
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="MyAP" auth_failures=2 duration=23 reason=CONN_FAILED
qwlan0: CTRL-EVENT-SSID-REENABLED id=0 ssid="MyAP"
wlan0: Trying to associate with SSID 'MyAP'
^C
The key phrases are obvious.
Don't forget to reboot when you're done just for good measure.
Good luck.
Regards,
Kent