Wifi carte Atheros

Hello,
I've recently posted my problem here :
https://forum.slackware-fr.eu.org/vi...8&p=1077#p1077

it's in french , my native language, but if someone could help I can try to translate.
Thank you .

I have the same device.

Network controller: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01)

With my -current install, I see the same modules.

lsmod | grep ath ath9k 106496 0 ath9k_common 16384 1 ath9k ath9k_hw 442368 2 ath9k,ath9k_common ath 24576 3 ath9k_hw,ath9k,ath9k_common mac80211 606208 1 ath9k cfg80211 548864 4 mac80211,ath9k,ath,ath9k_common

I do not use /etc/rc.d/rc.inet1.conf to handle my device, but I do note the double quote character at the end of WPAPSK= in the information in your original post.

My /etc/wpa_supplicant.conf

ctrl_interface=/var/run/wpa_supplicant
# By default, only root (group 0) may use wpa_cli
ctrl_interface_group=root
eapol_version=1
ap_scan=1
fast_reauth=1
#country=US
# WPA2 protected network, supply your own ESSID and WPAPSK here:
network={
  scan_ssid=0
#  ssid="your_essid_here"
#old  ssid="OPTUSA4680E8"
# RSN is WPA2 protocol
  proto=RSN
  key_mgmt=WPA-PSK
  pairwise=CCMP TKIP
  group=CCMP TKIP
#  psk=your_64_char_psk_here
#old  psk=a895812ddbd2c70ece741f4c2765da52e7da966829b91450fc731d4f63d83a68
#  or psk="<my_password>" as quoted string 
#old  psk="PFSLYHUMQTHHSQH47982"
  priority=10
}

I note that I do not have WPA in the proto= line.

To use wpa_supplicant, I run, as root, this script.

#!/bin/sh

# Script to start wireless networking

# Stop NetworkManager daemon
/etc/rc.d/rc.networkmanager stop
# kill any existing wpa_supplicant processes
pkill wpa_supplicant
#  Unblock any blocked wireless
rfkill unblock wlan
# Bring up the wlan0 interface - Not necessary, just use wpa_supplicant
#ip link set wlan0 up
# Start wpa_supplicant
wpa_supplicant -B -c/etc/wpa_supplicant.conf -iwlan0
# Get IP address
dhcpcd wlan0
# Run firewall script
/etc/rc.d/rc.firewall_wlan0

hello Allend,
First thank's for your answer. Then, you mean that with you configuration your wifi is working I imagine .
You say you don't use rc.inet.1.conf to manage your device, so what does your rc.inet1.conf looks like ?
And then, is it possible to handle the device with rc.inet1.conf instead your script ? ( just to simply manage as indicate Alien in his wiki

I have the device in a netbook where I manage network devices (wired, wireless and USB modem) using Network Manager.
As I use Network Manager, the /etc/rc.d/rc.inet1.conf does not contain any entries.
It should be possible to handle the device using rc.inet1.conf. The reason for posting the script was to show commands that directly handle the device, so you can find your problem, which I suspect is in authentication.

I uncommented the lines talking about wifi in rc.inet1.conf ; started your script, and here is the answer :

./TestWifi
Stopping NetworkManager: stopped
Bogus unblock argument 'wlan1'.
Successfully initialized wpa_supplicant
Could not read interface wlan0 flags: No such device
nl80211: Driver does not support authentication/association or connect commands
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Could not read interface wlan0 flags: No such device
wlan0: Failed to initialize driver interface
wlan1: adding address fe80::f164:ca22:2e79:fca4
wlan1: waiting for carrier
timed out
dhcpcd exited
./TestWifi: line 18: /etc/rc.d/rc.firewall_wlan1: No such file or directory


I don't understand why it's talked about wlan0 , when I asked ifconfig I get :

wlan1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether c2:53:7d:a9:68:43 txqueuelen 1000 (Ethernet)

!!!!??????

and here is the answer of syslog :

<warn> [1557319487.6084] device (wlan1): Activation: (wifi) asking for new secrets
May 8 14:44:54 Slack NetworkManager[1834]: <warn> [1557319494.8119] sup-iface[0xd3da90,wlan1]: connection disconnected (reason 15)
May 8 14:45:12 Slack NetworkManager[1834]: <warn> [1557319512.0188] sup-iface[0xd3da90,wlan1]: connection disconnected (reason 15)
May 8 14:45:12 Slack NetworkManager[1834]: <warn> [1557319512.6033] device (wlan1): Activation: (wifi) association took too long
May 8 14:45:12 Slack NetworkManager[1834]: <warn> [1557319512.6049] device (wlan1): Activation: failed for connection 'freeMEUNIER'
May 8 14:50:59 Slack dhcpcd[2091]: exited: interface not found or invalid
May 8 14:53:53 Slack dhcpcd[1845]: script_runreason: /usr/libexec/nm-dhcp-helper: WEXITSTATUS 1
May 8 14:53:53 Slack dhcpcd[1845]: script_runreason: /usr/libexec/nm-dhcp-helper: WEXITSTATUS 1
May 8 14:54:28 Slack dhcpcd[2145]: timed out


????????????????????

It seems that your device is appearing as wlan1.
Please post the output of '/sbin/ip l' and 'cat /etc/udev/rules.d/70-persistent-net.rules'.

Here is cat /etc......

# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:22:15:d9:91:e7", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x1814:0x0301 (rt61pci)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1a:70:ac:ae:a0", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
bash-4.3# sbin/ip | cat /etc/udev/rules.d/70-persistent-net.rules
bash: sbin/ip: No such file or directory

# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:22:15:d9:91:e7", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x1814:0x0301 (rt61pci)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1a:70:ac:ae:a0", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"


and for /sbin/ip it seems something is missing in the command, that's all I get :

/sbin/ip
Usage: ip [ OPTIONS ] OBJECT { COMMAND | help }
ip [ -force ] -batch filename
where OBJECT := { link | address | addrlabel | route | rule | neighbor | ntable |
tunnel | tuntap | maddress | mroute | mrule | monitor | xfrm |
netns | l2tp | fou | tcp_metrics | token | netconf }
OPTIONS := { -V[ersion] | -s[tatistics] | -d[etails] | -r[esolve] |
-h[uman-readable] | -iec |
-f[amily] { inet | inet6 | ipx | dnet | mpls | bridge | link } |
-4 | -6 | -I | -D | -B | -0 |
-l[oops] { maximum-addr-flush-attempts } | -br[ief] |
-o[neline] | -t[imestamp] | -ts[hort] | -b[atch] [filename] |
-rc[vbuf] [size] | -n[etns] name | -a[ll] |Â*-c[olor]}

PCI device 0x1814:0x0301

That is a Ralink device, different to the Qualcomm Atheros AR9285 Wireless Network Adapter

and for /sbin/ip it seems something is missing in the command

Yes, the " l"
I suggest that you delete the /etc/udev/rules.d/70-persistent-net.rules file and reboot. It will be regenerated on reboot.

Ok I do it again :

/sbin/ip l 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether 00:26:9e:7b:52:6e brd ff:ff:ff:ff:ff:ff 3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000 link/ether 3a:f3:da:86:7d:40 brd ff:ff:ff:ff:ff:ff

and
c

at /etc/udev/rules.d/70-persistent-net.rules # PCI device 0x10ec:0x8168 (r8169) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:26:9e:7b:52:6e", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" # PCI device 0x168c:0x002b (ath9k) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="0c:60:76:50:3e:a4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"

Better ?

# PCI device 0x168c:0x002b (ath9k) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="0c:60:76:50:3e:a4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"

I think it is better. Your device is now recognised as wlan0.

3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000 link/ether 3a:f3:da:86:7d:40 brd ff:ff:ff:ff:ff:ff

The device shows as DOWN.
You will need to update your /etc/rc.d/rc.inet1.conf from IFNAME[4]="wlan1" to IFNAME[4]="wlan0".

Well, well, well , it's much better, but not yet perfect ; no wifi for the while.

Here is cat /var/log/syslog :

NetworkManager[1332]: <warn> [1557393365.0391] device (wlan0): Activation: (wifi) asking for new secrets May 9 11:16:05 Slack NetworkManager[1332]: <warn> [1557393365.1196] sup-iface[0x1f4b290,wlan0]: connection disconnected (reason -3) May 9 11:16:15 Slack NetworkManager[1332]: <warn> [1557393375.0819] sup-iface[0x1f4b290,wlan0]: connection disconnected (reason -3) May 9 11:16:29 Slack named[1367]: checkhints: b.root-servers.net/A (199.9.14.201) missing from hints May 9 11:16:29 Slack named[1367]: checkhints: b.root-servers.net/A (192.228.79.201) extra record in hints May 9 11:16:29 Slack named[1367]: checkhints: b.root-servers.net/AAAA (2001:500:200::b) missing from hints May 9 11:16:29 Slack named[1367]: checkhints: b.root-servers.net/AAAA (2001:500:84::b) extra record in hints May 9 11:16:29 Slack named[1367]: checkhints: h.root-servers.net/A (198.97.190.53) missing from hints May 9 11:16:29 Slack named[1367]: checkhints: h.root-servers.net/A (128.63.2.53) extra record in hints May 9 11:16:29 Slack named[1367]: checkhints: h.root-servers.net/AAAA (2001:500:1::53) missing from hints May 9 11:16:29 Slack named[1367]: checkhints: h.root-servers.net/AAAA (2001:500:1::803f:235) extra record in hints May 9 11:16:29 Slack named[1367]: checkhints: l.root-servers.net/AAAA (2001:500:9f::42) missing from hints May 9 11:16:29 Slack named[1367]: checkhints: l.root-servers.net/AAAA (2001:500:3::42) extra record in hints May 9 11:16:30 Slack NetworkManager[1332]: <warn> [1557393390.0342] device (wlan0): Activation: (wifi) association took too long May 9 11:16:30 Slack NetworkManager[1332]: <warn> [1557393390.0385] device (wlan0): Activation: (wifi) asking for new secrets May 9 11:16:30 Slack NetworkManager[1332]: <warn> [1557393390.1278] sup-iface[0x1f4b290,wlan0]: connection disconnected (reason -3) May 9 11:16:40 Slack NetworkManager[1332]: <warn> [1557393400.1312] sup-iface[0x1f4b290,wlan0]: connection disconnected (reason -3) May 9 11:16:55 Slack NetworkManager[1332]: <warn> [1557393415.0352] device (wlan0): Activation: (wifi) association took too long May 9 11:16:55 Slack NetworkManager[1332]: <warn> [1557393415.0366] device (wlan0): Activation: failed for connection 'freeMEUNIER'

because of rc.inet1.conf ?

IFNAME[4]="wlan0" IPADDR[4]="" NETMASK[4]="" USE_DHCP[4]="yes" #DHCP_HOSTNAME[4]="" #DHCP_KEEPRESOLV[4]="yes" #DHCP_KEEPNTP[4]="yes" #DHCP_KEEPGW[4]="yes" #DHCP_IPADDR[4]="" WLAN_ESSID[4]=freeMEUNIER WLAN_MODE[4]=Managed WLAN_RATE[4]="54M auto" WLAN_CHANNEL[4]="auto" WLAN_KEY[4]="s:Glasgow5052!" ##WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set WPAPSK=461039ade0bbef5735f5c9aff84fb4510146ccc0541585fe76c84bdf7790b14f WLAN_WPA[4]="wpa_supplicant" WLAN_WPADRIVER[4]="wext"

I feel a little bit confused beetwin all this configurations (WPA, WEP, etc....) though I try to just do like the wiki of Alien

Anyway, already thank you for the help .

NetworkManager[1332]: <warn> [1557393365.0391] device (wlan0): Activation: (wifi) asking for new secrets

You are using Network Manager, which people usually find to be easier to configure.
You seem to have missed this note on the wiki page you linked.

If you want to use NetworkManager, you will have to remove any network interface configuration information from /etc/rc.d/rc.inet1.conf in order to prevent a struggle for power between Network Manager and Slackware's rc.inet1 script.

When changing to use Network Manager, follow the official advice. The relevant paragraph is reproduced here.

I think i 'm gone make a little rest for my neurons ; at the moment I'm said to be wifi connected, but as I am a little bit suspicious, I'm gone wait and let things settle for a while and see what happens at the next reboot.
Thank's for all; I'll be back to tell you .