LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM
User Name
Password
Slackware - ARM This forum is for the discussion of Slackware ARM.

Notices


Reply
  Search this Thread
Old 02-09-2017, 04:18 AM   #16
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 7,854

Rep: Reputation: 760Reputation: 760Reputation: 760Reputation: 760Reputation: 760Reputation: 760Reputation: 760

Right, your wlan0 seems to be sitting there but not joining the network. The driver etc looks ok so far. You're down to wpa_supplicant, protocols, & dhcp.
1. Os the psk in wpa_supplicant.conf passed through wpa_passpgrase? You get an output to paste into wpa_supplicant.conf
Code:
bash-4.3$ wpa_passphrase My_ESSID My_Password
network={
	ssid="My_ESSID"
	#psk="My_Password"
	psk=116c4b8b7dc9419a4f2a7e12c80e721ccd7650942b17781f79e38fc9632e04fc
}
Try invoking wpa_supplicant by hand. Kill any wpa_supplicant & dhcpcd or dhclient processes, and of course stop networkmanager, which I find to be NetworkMismanager. Then run
Code:
wpa_supplicant -c/path/to/wpa_supplicant.conf -i wlan0 -Dwext >> some.log && dhcpcd wlan0 >>some.log
You can of course just use dhclient instead of dhcpcd if that's installed. some.log might be interesting. It stops errors going to /dev/null anyhow.
 
Old 02-09-2017, 10:01 AM   #17
slackist
Member
 
Registered: Feb 2004
Location: Phuket
Distribution: Slackware 14.1 and Slackware Arm
Posts: 478

Original Poster
Rep: Reputation: 41
Quote:
1. Os the psk in wpa_supplicant.conf passed through wpa_passpgrase? You get an output to paste into wpa_supplicant.conf
Yes, I snipped the full psk out just in case my neighbours grow a brain but it was generated by wpa_passphrase.

Quote:
Try invoking wpa_supplicant by hand. Kill any wpa_supplicant & dhcpcd or dhclient processes, and of course stop networkmanager, which I find to be NetworkMismanager. Then run
NetworkMismanager is not installed as I also find it to be a PITA, I did run the command you posted. As usual dhcpd overwrote my resolv.conf with useless cruft.

Code:
[root@darkmoon:log] # wpa_supplicant -c/etc/wpa_supplicant.conf -i wlan0 -Dwext >> /var/log/bk.log && dhcpcd wlan0 >> /var/log/bk.log
I was running a tail -f on the syslog:
Code:
Feb  9 22:22:05 darkmoon kernel: [95066.510646] brcmfmac: brcmf_cfg80211_escan: Connecting: status (3)
Feb  9 22:22:05 darkmoon kernel: [95066.510668] brcmfmac: brcmf_cfg80211_scan: scan error (-11)
Feb  9 22:22:17 darkmoon kernel: [95078.184872] brcmfmac: brcmf_cfg80211_escan: Connecting: status (3)
Feb  9 22:22:17 darkmoon kernel: [95078.184895] brcmfmac: brcmf_cfg80211_scan: scan error (-11)
Feb  9 22:22:29 darkmoon kernel: [95089.857325] brcmfmac: brcmf_cfg80211_escan: Connecting: status (3)
Feb  9 22:22:29 darkmoon kernel: [95089.857348] brcmfmac: brcmf_cfg80211_scan: scan error (-11)
And /var/log/messages:
Code:
Feb  9 22:22:05 darkmoon kernel: [95066.279479] brcmfmac: power management disabled
Feb  9 22:22:05 darkmoon kernel: [95066.279977] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb  9 22:24:31 darkmoon dhcpcd[23270]: wlan0: adding address fe80::9f6d:a6c9:2c45:3095
Feb  9 22:24:31 darkmoon dhcpcd[23270]: wlan0: waiting for carrier
Feb  9 22:24:31 darkmoon kernel: [95212.014419] brcmfmac: power management disabled
Feb  9 22:24:31 darkmoon kernel: [95212.017674] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb  9 22:25:01 darkmoon dhcpcd[23270]: dhcpcd exited
And the log file generated:

Code:
[root@darkmoon:log] #cat /var/log/bk.log
Successfully initialized wpa_supplicant
ioctl[SIOCSIWSCAN]: Resource temporarily unavailable
wlan0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
wlan0: Trying to associate with 18:a3:e8:23:67:10 (SSID='House1000' freq=2442 MHz)
ioctl[SIOCSIWFREQ]: Operation not supported
wlan0: Association request to the driver failed
wlan0: Authentication with 18:a3:e8:23:67:10 timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=18:a3:e8:23:67:10 reason=3 locally_generated=1
ioctl[SIOCSIWSCAN]: Resource temporarily unavailable
wlan0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
wlan0: Trying to associate with 18:a3:e8:23:67:10 (SSID='House1000' freq=2442 MHz)
ioctl[SIOCSIWFREQ]: Operation not supported
wlan0: Association request to the driver failed
wlan0: Authentication with 18:a3:e8:23:67:10 timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=18:a3:e8:23:67:10 reason=3 locally_generated=1
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="House1000" auth_failures=1 duration=10 reason=CONN_FAILED
ioctl[SIOCSIWSCAN]: Resource temporarily unavailable
wlan0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
wlan0: CTRL-EVENT-SSID-REENABLED id=0 ssid="House1000"
wlan0: Trying to associate with 18:a3:e8:23:67:10 (SSID='House1000' freq=2442 MHz)
ioctl[SIOCSIWFREQ]: Operation not supported
wlan0: Association request to the driver failed
wlan0: Authentication with 18:a3:e8:23:67:10 timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=18:a3:e8:23:67:10 reason=3 locally_generated=1
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="House1000" auth_failures=2 duration=23 reason=CONN_FAILED
ioctl[SIOCSIWSCAN]: Resource temporarily unavailable
wlan0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
wlan0: CTRL-EVENT-SSID-REENABLED id=0 ssid="House1000"
wlan0: Trying to associate with 18:a3:e8:23:67:10 (SSID='House1000' freq=2442 MHz)
ioctl[SIOCSIWFREQ]: Operation not supported
wlan0: Association request to the driver failed
wlan0: Authentication with 18:a3:e8:23:67:10 timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=18:a3:e8:23:67:10 reason=3 locally_generated=1
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="House1000" auth_failures=3 duration=46 reason=CONN_FAILED
ioctl[SIOCSIWSCAN]: Resource temporarily unavailable
wlan0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
wlan0: CTRL-EVENT-SSID-REENABLED id=0 ssid="House1000"
wlan0: Trying to associate with 18:a3:e8:23:67:10 (SSID='House1000' freq=2442 MHz)
ioctl[SIOCSIWFREQ]: Operation not supported
wlan0: Association request to the driver failed
wlan0: Authentication with 18:a3:e8:23:67:10 timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=18:a3:e8:23:67:10 reason=3 locally_generated=1
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="House1000" auth_failures=4 duration=77 reason=CONN_FAILED
ioctl[SIOCSIWSCAN]: Resource temporarily unavailable
wlan0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
wlan0: CTRL-EVENT-TERMINATING 
wlan0: adding address fe80::9f6d:a6c9:2c45:3095
wlan0: waiting for carrier
dhcpcd exited
 
Old 02-09-2017, 01:44 PM   #18
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 7,854

Rep: Reputation: 760Reputation: 760Reputation: 760Reputation: 760Reputation: 760Reputation: 760Reputation: 760
On that output, the software looks ok, and you have driver or firmware trouble. One thing to try is that there's another -D option for wpa_supplicant, e.g. nl802.11. That's easy.

The messier bit is getting a driver & firmware your system agrees with, especially as you're Arm based & not x86. I think there's a big endian/little endian thing going on between those 2.

If that doesn't sort it, and you get drivers that work for others & not you, we might end up calling the hardware dud. Ebay has usb wifi modules that plug into usb & provide wifi. I think you need the usbnet kernel module. I got one for the RasPi 1 I had, and it worked like a dream.
 
1 members found this post helpful.
Old 02-09-2017, 03:40 PM   #19
justwantin
Member
 
Registered: Aug 2003
Location: Melbourne, Australia
Distribution: Slackware, Slackwarearm
Posts: 679

Rep: Reputation: 69
@ slackist,
Sorry, been busy, I note that your system sets up wlan0 and that you have setup your essid, After that have you run ifconfig wlan0 up and then iwlist wlan0 scan? If you did and get a list of networks including your own then may I suggest that you forget about wpa supplicant et.al. and try using wicd. Wicd does not require you to have wpa supplicant configured, nor does network manager for that matter, but I find wicd easier to use. Just be sure that you have removed any entries you may have made in /etc/rc.d/rc.inet1.conf or wicd will not work. I never bothered with wpa supplicant so I'm not sure what you should do with that but probably it too would need any configs to be removed.
 
1 members found this post helpful.
Old 02-09-2017, 07:47 PM   #20
slackist
Member
 
Registered: Feb 2004
Location: Phuket
Distribution: Slackware 14.1 and Slackware Arm
Posts: 478

Original Poster
Rep: Reputation: 41
Quote:
Originally Posted by business_kid View Post
On that output, the software looks ok, and you have driver or firmware trouble. One thing to try is that there's another -D option for wpa_supplicant, e.g. nl802.11. That's easy.

The messier bit is getting a driver & firmware your system agrees with, especially as you're Arm based & not x86. I think there's a big endian/little endian thing going on between those 2.

If that doesn't sort it, and you get drivers that work for others & not you, we might end up calling the hardware dud. Ebay has usb wifi modules that plug into usb & provide wifi. I think you need the usbnet kernel module. I got one for the RasPi 1 I had, and it worked like a dream.
I've tried the -Dnl80211 switch (the output is in the last bit of post #15) and as mentioned upthread I have an old WiFi dongle that works fine (when it's plugged in or removed the system loads and unloads a driver as reported by lsmod and /var/log/messages and wpa_supplicant works with it as wlan1) but it's so big that it effectively takes up 2 of the 4 USB ports, I know I could stick it into a USB hub but I've already got cables all over my desk plus it is slow being so old, hence the efforts to get the onboard WiFi working!

Quote:
Originally Posted by justwantin View Post
@ slackist,
Sorry, been busy, I note that your system sets up wlan0 and that you have setup your essid, After that have you run ifconfig wlan0 up and then iwlist wlan0 scan? If you did and get a list of networks including your own then may I suggest that you forget about wpa supplicant et.al. and try using wicd. Wicd does not require you to have wpa supplicant configured, nor does network manager for that matter, but I find wicd easier to use. Just be sure that you have removed any entries you may have made in /etc/rc.d/rc.inet1.conf or wicd will not work. I never bothered with wpa supplicant so I'm not sure what you should do with that but probably it too would need any configs to be removed.
I’ve tried wicd via wicd-curses and the Xfce4 panel applet several times with all the rc.inet1.conf references commented out and wpa_supplicant.conf renamed but it rolls around trying to connect and then gives up with a 'not connected' message to my AP.

Last edited by slackist; 02-09-2017 at 07:49 PM. Reason: I type like a muppet on crack.
 
Old 02-09-2017, 08:54 PM   #21
justwantin
Member
 
Registered: Aug 2003
Location: Melbourne, Australia
Distribution: Slackware, Slackwarearm
Posts: 679

Rep: Reputation: 69
This may be a wicd configuration problem.

That happened to me on an install to a bananapro. I had first gotten the pro up and running with a wired connection to my lan. When I then tried to configure to wireless with configs known to be correct it just rolled around. It turned out that wireless was turned off in wicd. I was able to connect once I turned it on. I was in an x session via ssh when I did it and don't remember exactly how now. Here's a link that might give you some ideas http://www.linuxquestions.org/questi...ff-4175475544/ I remember at the time I found some other references to this problem and solution so have a look.

Last edited by justwantin; 02-09-2017 at 08:54 PM. Reason: tyop
 
1 members found this post helpful.
Old 02-10-2017, 02:02 AM   #22
SCerovec
Senior Member
 
Registered: Oct 2006
Location: Cp6uja
Distribution: Slackware on x86 and arm
Posts: 1,069
Blog Entries: 2

Rep: Reputation: 126Reputation: 126
May I chime in some?
tcpdump can rely some of the 802 frame headers
Also aircrack-ng might help a bit
If not, alone the RTFMing of the respective chapters of said apps might shed a light of the culprits?

IIRC the problem is the immature driver/firmware of the wifi MAC, so reading the module source might help even

But before anything:
/sbin/modinfo <module of ours>
Would yield a clue?
 
Old 02-13-2017, 05:39 AM   #23
yustin
LQ Newbie
 
Registered: Dec 2012
Distribution: Slackware
Posts: 5

Rep: Reputation: Disabled
maybe this solves your problem ....

https://debianforum.de/forum/viewtop...142749#p935640

# /etc/modprobe.d/regdomain.conf
options cfg80211 ieee80211_regdom=[your_country_code]

have phun
 
Old 02-13-2017, 02:13 PM   #24
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 7,854

Rep: Reputation: 760Reputation: 760Reputation: 760Reputation: 760Reputation: 760Reputation: 760Reputation: 760
I'm not confident that will sort it as his wifi is puking on normal setup instructions. At the risk of repeating myself from post #20
Quote:
On that output, the software looks ok, and you have driver or firmware trouble.
 
Old 02-14-2017, 04:38 AM   #25
SCerovec
Senior Member
 
Registered: Oct 2006
Location: Cp6uja
Distribution: Slackware on x86 and arm
Posts: 1,069
Blog Entries: 2

Rep: Reputation: 126Reputation: 126
Reminds me of the days of ACX100 and how it got from a patch to mainline

My bet: kernel side (=not ready yet).

Remedy: try upgrade kernel until it works?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Sound issues with slack 10.2 and onboard sound chip ricardo_ok Slackware 10 08-21-2006 12:38 PM
Onboard sound chip problem after kernel upgrade coralsaw Debian 4 06-15-2006 02:25 AM
Getting sound in slackware 9.1 with a ess 1868 onboard chip! HELP! toolfan Slackware - Installation 6 05-19-2004 06:21 PM
Need to Know Whether my Onboard Graphics Chip is an Intel i810 Huddlebum Linux - General 4 04-04-2004 10:14 AM
Audio driver for Gigabyte GA8IK1100's onboard sound chip? TMMO Linux - Newbie 1 08-10-2003 04:59 PM


All times are GMT -5. The time now is 08:28 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration