[SOLVED] Wi-fi not working - wlp3s0 (ath9k) is always DOWN

jookuma · 2017-02-18 16:34:45

I installed this week for the first time Arch using a ethernet cable, but I can't use the wi-fi.

I've found a few threads related to this but all of them are kernel/updates bugs that have already been updated or the solution didn't work for me :(.

Here is some of the terminal outputs:

lscpi -k

03:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01)
	Subsystem: Lenovo Device 4026
	Kernel driver in use: ath9k
	Kernel modules: ath9k

ip link

3: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000
    link/ether 3e:51:ab:7d:c5:1c brd ff:ff:ff:ff:ff:ff

It stays the same if a use

sudo ip link set wlp3s0 up

I've tried using NetworkManager and the gnome3 interface but it keeps asking me the passwork just like if I'm writing it wrong.

I also used wpa_supplicant but it didn't work, I'm not sure if I was doing something wrong or it wasn't working because the interface is not up.

Last edited by jookuma (2017-02-19 00:02:24)

Starfish · 2017-02-18 17:19:55

jookuma wrote:

It stays the same if a use
sudo ip link set wlp3s0 up

That's because it is already up, as you can see between the brackets:

 ... <NO-CARRIER,BROADCAST,MULTICAST,UP> ...

jookuma wrote:

I've tried using NetworkManager and the gnome3 interface but it keeps asking me the passwork just like if I'm writing it wrong.

Please be more specific. If you try to connect via shell, do you get an error message? If yes, post it.

Does

iw dev wlp3s0 scan | grep -i ssid

show your network?

Right after trying to connect, what does

journalctl -e

look like?

PS.: Be careful not to use multiple network managers at once, but stick to one. They usually interfere with each other. If you can't remember all the stuff you've enabled, check 'systemctl list-units'.

Last edited by Starfish (2017-02-18 17:21:29)

jookuma · 2017-02-18 21:01:19

Starfish wrote:

Please be more specific. If you try to connect via shell, do you get an error message? If yes, post it.

When I try to connect via shell it doesn't appear any error, it just keep asking my password and it never connects, most to of the time it asks for my password again immediately after I enter the password.

Starfish wrote:

Does
iw dev wlp3s0 scan | grep -i ssid
show your network?

It shows all the networks available, it doesn't show mine because it's a hidden network, when I was using my last distro I could see it with aircrack-ng.
I know it's just a illusion of security to hide your network, but I'm not at my house.

Starfish wrote:

Right after trying to connect, what does
journalctl -e
look like?

Right after I try to connect via shell this shows:

fev 18 15:39:04 jo-arch gnome-shell[620]: Ignoring excess values in shadow definition
fev 18 15:39:04 jo-arch gnome-shell[620]: Ignoring excess values in shadow definition
fev 18 15:39:04 jo-arch NetworkManager[270]: <info>  [1487450344.8739] device (wlp3s0): supplicant interface state: disconnected -> inactive
fev 18 15:39:10 jo-arch NetworkManager[270]: <info>  [1487450350.7396] device (wlp3s0): state change: need-auth -> prepare (reason 'none') [60 40 0]
fev 18 15:39:10 jo-arch NetworkManager[270]: <info>  [1487450350.7405] device (wlp3s0): state change: prepare -> config (reason 'none') [40 50 0]
fev 18 15:39:10 jo-arch NetworkManager[270]: <info>  [1487450350.7408] device (wlp3s0): Activation: (wifi) connection 'NetworkName' has security, and s
fev 18 15:39:10 jo-arch NetworkManager[270]: <info>  [1487450350.7408] Config: added 'ssid' value 'NetworkName'
fev 18 15:39:10 jo-arch NetworkManager[270]: <info>  [1487450350.7408] Config: added 'scan_ssid' value '1'
fev 18 15:39:10 jo-arch NetworkManager[270]: <info>  [1487450350.7408] Config: added 'key_mgmt' value 'WPA-PSK'
fev 18 15:39:10 jo-arch NetworkManager[270]: <info>  [1487450350.7408] Config: added 'psk' value '<hidden>'
fev 18 15:39:10 jo-arch NetworkManager[270]: <info>  [1487450350.7437] sup-iface[0x17d0220,wlp3s0]: config: set interface ap_scan to 1
fev 18 15:39:10 jo-arch NetworkManager[270]: <info>  [1487450350.7607] device (wlp3s0): supplicant interface state: inactive -> scanning
fev 18 15:39:11 jo-arch wpa_supplicant[368]: wlp3s0: SME: Trying to authenticate with 00:7f:28:06:e6:1e (SSID='NetworkName' freq=2462 MHz)
fev 18 15:39:11 jo-arch kernel: wlp3s0: authenticate with 00:7f:28:06:e6:1e
fev 18 15:39:11 jo-arch kernel: wlp3s0: send auth to 00:7f:28:06:e6:1e (try 1/3)
fev 18 15:39:11 jo-arch NetworkManager[270]: <info>  [1487450351.7465] device (wlp3s0): supplicant interface state: scanning -> authenticating
fev 18 15:39:11 jo-arch kernel: wlp3s0: authenticated
fev 18 15:39:11 jo-arch wpa_supplicant[368]: wlp3s0: Trying to associate with 00:7f:28:06:e6:1e (SSID='NetworkName' freq=2462 MHz)
fev 18 15:39:11 jo-arch NetworkManager[270]: <info>  [1487450351.7534] device (wlp3s0): supplicant interface state: authenticating -> associating
fev 18 15:39:11 jo-arch kernel: wlp3s0: associate with 00:7f:28:06:e6:1e (try 1/3)
fev 18 15:39:11 jo-arch wpa_supplicant[368]: wlp3s0: Associated with 00:7f:28:06:e6:1e
fev 18 15:39:11 jo-arch wpa_supplicant[368]: wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
fev 18 15:39:11 jo-arch kernel: wlp3s0: RX AssocResp from 00:7f:28:06:e6:1e (capab=0x431 status=0 aid=6)
fev 18 15:39:11 jo-arch kernel: wlp3s0: associated
fev 18 15:39:11 jo-arch kernel: wlp3s0: deauthenticating from 00:7f:28:06:e6:1e by local choice (Reason: 3=DEAUTH_LEAVING)
fev 18 15:39:11 jo-arch NetworkManager[270]: <info>  [1487450351.7605] device (wlp3s0): supplicant interface state: associating -> associated
fev 18 15:39:11 jo-arch wpa_supplicant[368]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=00:7f:28:06:e6:1e reason=3 locally_generated=1
fev 18 15:39:11 jo-arch wpa_supplicant[368]: wlp3s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="NetworkName" auth_failures=1 duration=10 reason=CONN_FAIL
fev 18 15:39:11 jo-arch NetworkManager[270]: <warn>  [1487450351.7640] sup-iface[0x17d0220,wlp3s0]: connection disconnected (reason -3)
fev 18 15:39:11 jo-arch NetworkManager[270]: <info>  [1487450351.7685] device (wlp3s0): supplicant interface state: associated -> disconnected
fev 18 15:39:11 jo-arch NetworkManager[270]: <info>  [1487450351.8699] device (wlp3s0): supplicant interface state: disconnected -> scanning

Do you think that the wpa_supplicant is interfering with the NetworkManager? Should I remove the wpa_supplicant?

Last edited by jookuma (2017-02-18 21:09:58)

Starfish · 2017-02-18 21:21:27

jookuma wrote:

Do you think that the wpa_supplicant is interfering with the NetworkManager? Should I remove the wpa_supplicant?

Yes and yes. That's what I already told you in my last post.

Arch Linux

#1 2017-02-18 16:34:45

[SOLVED] Wi-fi not working - wlp3s0 (ath9k) is always DOWN

#2 2017-02-18 17:19:55

Re: [SOLVED] Wi-fi not working - wlp3s0 (ath9k) is always DOWN

#3 2017-02-18 21:01:19

Re: [SOLVED] Wi-fi not working - wlp3s0 (ath9k) is always DOWN

#4 2017-02-18 21:21:27

Re: [SOLVED] Wi-fi not working - wlp3s0 (ath9k) is always DOWN

Board footer