Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
There's no need to hire - this is a forum. You just need a little familiarity with this stuff. I found it a nightmare when I started. Here's a few commands to check.
<sudo iwconfig -a> lists all network devices. Presuming yours is wlan0
<sudo iwlist wlan0 scan |grep -C3 Quality> Should show you all local wifi points like this with channel numbers and quality
I gather you're on some version of slackware? There's a DHCP_KEEPRESOLV setting in /etc/rc.d/rc.inet1.conf which you need to uncomment and set to yes. That will stop dhcpcd overwriting resolv.conf. Look for it with grep -n, which gives you a line number. Also, the easiest way to start the wifi is
Ok. your card can see the wifi. Looks exactly like mine. That seems to clear that wifi.
If you can switch off encryption, you should be able to connect with
I'm not able to disable the encryption. For a little more context, this is a remote solar powered Raspberry Pi connected with a USB LTE stick. I'm able to SSH into the Raspberry Pi via this connection.
I'm trying to connect to a GoPro AP to download images, which was working for months. The GoPro turns on, enables WiFi, takes an image, then goes to sleep every hour. Suddenly I'm not able to connect to it's WiFi. In this context, I can't change anything about the AP physically or software wise.
It could be a problem with the GoPro, but based on my Pi I can see that it still comes on and enables wifi every hour - which lead me to believe that this is still a Raspberry Pi issue. If you would like to SSH into the Pi and take a look you are welcome. The purpose of my system is not working so anything will help.
I don't see how I can ssh in if you haven't got internet.
Ok. Let's presume the card is working, dhcp is working, and get down to wpa_supplicant. Humour me and copy your wpa -supplicant.conf into /etc, as that's the usual location in my Slackware anyhow. Then start wpa_supplicant. Here's what I used, and what I got.
Code:
root@RoseViolet:~# wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf
Successfully initialized wpa_supplicant
wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlan0: SME: Trying to authenticate with 34:81:c4:e0:4b:88 (SSID='MY_ESSID' freq=2437 MHz)
wlan0: Trying to associate with 34:81:c4:e0:4b:88 (SSID='MY_ESSID' freq=2437 MHz)
wlan0: Associated with 34:81:c4:e0:4b:88
wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=IE
wlan0: WPA: Key negotiation completed with 34:81:c4:e0:4b:88 [PTK=CCMP GTK=TKIP]
wlan0: CTRL-EVENT-CONNECTED - Connection to 34:81:c4:e0:4b:88 completed [id=0 id_str=]
And the Network looks like this
Code:
bash-4.3$ iwconfig wlan0
wlan0 IEEE 802.11 ESSID:"MY_ESSID"
Mode:Managed Frequency:2.437 GHz Access Point: 34:81:C4:E0:4B:88
Bit Rate=135 Mb/s Tx-Power=15 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=62/70 Signal level=-48 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:17 Missed beacon:0
Now I would have to start dhcpcd to get myself an IP & route. If wpa_supplicant fails, reinstall that, retry, and add '-d' to the command shown. Paste the output to pastebin, and we'll have to grok it for clues. What's your kernel? Distro, or home built?
Successfully initialized wpa_supplicant
wlan0: Trying to associate with d6:d9:19:9a:00:5a (SSID='DiscoPro' freq=2412 MHz)
wlan0: CTRL-EVENT-ASSOC-REJECT status_code=16
wlan0: Trying to associate with d6:d9:19:9a:00:5a (SSID='DiscoPro' freq=2412 MHz)
wlan0: CTRL-EVENT-ASSOC-REJECT status_code=16
wlan0: Trying to associate with d6:d9:19:9a:00:5a (SSID='DiscoPro' freq=2412 MHz)
wlan0: CTRL-EVENT-ASSOC-REJECT status_code=16
wlan0: Trying to associate with d6:d9:19:9a:00:5a (SSID='DiscoPro' freq=2412 MHz)
wlan0: CTRL-EVENT-ASSOC-REJECT status_code=16
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="DiscoPro" auth_failures=1 duration=10 reason=CONN_FAILED
wpa_supplicant v2.3
Linux version 4.9.64-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #1053 SMP Tue Nov 21 14:56:27 GMT 2017
If everything's correct, and wpa has been reinstalled, you've one last option, which is to check it's loading firmware and that the firmware is good. Also the manufacturer's site for downloads. Errors of that sort are SSID/PSK, firmware, reception, or occasionally hardware.I've asked about all of them, but haven't always been answered. Check for a driver bug also. I would next suggest a usb wifi from ebay which can stay under the 100mA. The one I got had some weirdo realtek chip but I was able to compile a driver for the early ras-pi I had. You mightn't get that with 802.11n, but you can make the choices. If you have the wpa config, the wpa package, or anything else wrong, of course, it won't work.
There are Atheros USB WiFi dongles out there - buy, compile the (mainline) kernel module (if not already present) and off You go.
They do cost a bit more than the realtek ones, but it pays off later, in the setup.
Just thinking, if you don't like this and have another box on hand, you can set up a wifi & dhcp server on that, and try logging in with your raspi. You may even go to setting up wpa_supplicant in server mode and completely duplicate your own setup. That way,you'll be able to fool around and gradually narrow things down. If you keep coming up against wpa_supplicant, and have reinstalled it, it could be hardware. But you eliminate everything else first. It's unusual for hardware to fail that way; Not impossible, but unusual.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.