You are not logged in.

Pages: 1

#1 2019-02-26 21:48:02

xavib
Member
Registered: 2019-01-19
Posts: 10

[SOLVED] Wifi connectivity issue

Hi,

I have seen various topics on a close or identical issue but none seems to solve mine.

I recently installed my first Archlinux laptop but I have WIFI connectivity issues.
(When I plug an ethernet cable it connects instantly)

I use iwctl with crda and dhcpcd installed.

Despite being connected on startup:

$ iw wlp1s0 link
Connected to XXXXXX (on wlp1s0)
	SSID: XXXXXX
	freq: 2412
	RX: 685754 bytes (2368 packets)
	TX: 48420 bytes (395 packets)
	signal: -76 dBm
	tx bitrate: 39.0 MBit/s MCS 4

	bss flags:	short-slot-time
	dtim period:	1
	beacon int:	100

Every ping command during ~5 minutes respond with "network unreachable"
After what it is connected to the internet.

Hardware and driver:

$ lspci -k
01:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)
	Subsystem: Foxconn International, Inc. Unex DHXA-225
	Kernel driver in use: ath9k
	Kernel modules: ath9k
$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 30:f9:ed:c8:14:33 brd ff:ff:ff:ff:ff:ff
3: wlp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state DORMANT group default qlen 1000
    link/ether 86:f2:e4:d6:c2:44 brd ff:ff:ff:ff:ff:ff
$ systemctl list-unit-files  --state=ate=enabled
UNIT FILE                              STATE  
autovt@.service                        enabled
dbus-org.freedesktop.timesync1.service enabled
dhcpcd.service                         enabled
display-manager.service                enabled
getty@.service                         enabled
iwd.service                            enabled
lightdm.service                        enabled
systemd-timesyncd.service              enabled
tlp-sleep.service                      enabled
tlp.service                            enabled
remote-fs.target                       enabled
$ dmesg | grep ath     
[    5.710317] systemd[1]: /usr/lib/systemd/system/auditd.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/auditd.pid \xe2\x86\x92 /run/auditd.pid; please update the unit file accordingly.
[   13.463528] ath: phy0: ASPM enabled: 0x42
[   13.463531] ath: EEPROM regdomain: 0x65
[   13.463531] ath: EEPROM indicates we should expect a direct regpair map
[   13.463533] ath: Country alpha2 being used: 00
[   13.463534] ath: Regpair used: 0x65
[   13.777853] ath9k 0000:01:00.0 wlp1s0: renamed from wlan0
[   15.033534] usbcore: registered new interface driver ath3k
[   19.826371] ath: EEPROM regdomain: 0x80fa
[   19.826372] ath: EEPROM indicates we should expect a country code
[   19.826374] ath: doing EEPROM country->regdmn map search
[   19.826375] ath: country maps to regdmn code: 0x37
[   19.826376] ath: Country alpha2 being used: FR
[   19.826377] ath: Regpair used: 0x37
[   19.826379] ath: regdomain 0x80fa dynamically updated by country element
$ cat /etc/resolv.conf
# Generated by resolvconf
domain home
nameserver 192.168.1.1

Hopefully, someone will be able to help me ! smile

Xavier

Last edited by xavib (2019-03-02 14:42:15)

Offline

#2 2019-02-26 21:59:18

loqs
Member
Registered: 2014-03-06
Posts: 17,321

Re: [SOLVED] Wifi connectivity issue

wlp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state DORMANT group default qlen 1000

Is the NO-CARRIER present when you can ping an internet address?

Offline

#3 2019-02-26 22:10:20

xavib
Member
Registered: 2019-01-19
Posts: 10

Re: [SOLVED] Wifi connectivity issue

Nope !

$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 30:f9:ed:c8:14:33 brd ff:ff:ff:ff:ff:ff
3: wlp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether da:b6:27:ad:34:af brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.81/24 brd 192.168.1.255 scope global noprefixroute wlp1s0
       valid_lft forever preferred_lft forever
    inet6 fde4:fb5d:9b93:3500:bad8:6371:6f2:e016/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 7151sec preferred_lft 3551sec
    inet6 fe80::6aed:ebcb:803e:d033/64 scope link 
       valid_lft forever preferred_lft forever

Offline

#4 2019-02-26 22:41:49

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,732
Website

Re: [SOLVED] Wifi connectivity issue

Please post the output of

journalctl -u iwd

Does wpa_supplicant provide a stable connection?

Have you seen https://wiki.archlinux.org/index.php/Wi … tion#ath9k?

Are you infected with Wetiko?

Offline

#5 2019-02-27 12:55:30

unixman
Member
Registered: 2015-03-12
Posts: 64

Re: [SOLVED] Wifi connectivity issue

xavib wrote:

Hi,
...
nameserver 192.168.1.1
Xavier

Try with a bit more normal nameserver eg 8.8.8.8

Ping to your nameserver immediately after it been connected to see what happened.

Offline

#6 2019-03-01 20:25:13

xavib
Member
Registered: 2019-01-19
Posts: 10

Re: [SOLVED] Wifi connectivity issue

Hi,

Sorry for the late reply !

Head_on_a_Stick wrote:

Please post the output of

journalctl -u iwd
Mar 01 21:15:14 archlinux-xavier iwd[654]: Wireless daemon version 0.13
Mar 01 21:15:14 archlinux-xavier iwd[654]: Skipping optional configuration file /etc/iwd/main.conf
Mar 01 21:15:12 archlinux-xavier systemd[1]: Starting Wireless service...
Mar 01 21:15:14 archlinux-xavier systemd[1]: Started Wireless service.
Mar 01 21:15:15 archlinux-xavier iwd[654]: Wiphy: 0, Name: phy0
Mar 01 21:15:15 archlinux-xavier iwd[654]:         Bands: 2.4 GHz
Mar 01 21:15:15 archlinux-xavier iwd[654]:         Ciphers: CCMP TKIP BIP
Mar 01 21:15:15 archlinux-xavier iwd[654]:         Supported iftypes: ad-hoc station ap
Mar 01 21:15:15 archlinux-xavier iwd[654]: No ControlPortOverNL80211 setting, defaulting to True
Mar 01 21:15:16 archlinux-xavier iwd[654]: hardware_rekey not supported
Mar 01 21:15:17 archlinux-xavier iwd[654]: Received Deauthentication event, reason: 3, from_ap: false

Does wpa_supplicant provide a stable connection?

Shoud I completly uninstall iwd to try wpa_supplicant ?

It does not work sad

Offline

#7 2019-03-01 21:00:56

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,732
Website

Re: [SOLVED] Wifi connectivity issue

xavib wrote:
Mar 01 21:15:14 archlinux-xavier iwd[654]: Wireless daemon version 0.13

That's an old version, does updating your system improve matters?

You are supposed to only post issues with fully updated systems, see https://bbs.archlinux.org/viewtopic.php?id=130309

xavib wrote:
Mar 01 21:15:17 archlinux-xavier iwd[654]: Received Deauthentication event, reason: 3, from_ap: false

https://www.cisco.com/assets/sol/sb/WAP … odes2.html

I'm not entirely sure what that means though... hmm

xavib wrote:

Does wpa_supplicant provide a stable connection?

Shoud I completly uninstall iwd to try wpa_supplicant ?

No, just disable iwd and enable wpa_supplicant@wlp1s0 instead (or activate the hook provided by dhcpcd).

EDIT: you also need a configuration file for wpa_supplicant, see the wiki for details.

xavib wrote:

What does not work? There are several suggestions in that link

Last edited by Head_on_a_Stick (2019-03-01 21:02:11)

Are you infected with Wetiko?

Offline

#8 2019-03-02 10:42:58

xavib
Member
Registered: 2019-01-19
Posts: 10

Re: [SOLVED] Wifi connectivity issue

Head_on_a_Stick wrote:
xavib wrote:
Mar 01 21:15:14 archlinux-xavier iwd[654]: Wireless daemon version 0.13

That's an old version, does updating your system improve matters?

No, it does not.

Head_on_a_Stick wrote:
xavib wrote:

What does not work? There are several suggestions in that link

Adding options ath9k nohwcrypt=1 in /etc/modprobe.d/ath9k.conf does not work.

Head_on_a_Stick wrote:
xavib wrote:

Does wpa_supplicant provide a stable connection?

Shoud I completly uninstall iwd to try wpa_supplicant ?

No, just disable iwd and enable wpa_supplicant@wlp1s0 instead (or activate the hook provided by dhcpcd).

EDIT: you also need a configuration file for wpa_supplicant, see the wiki for details.

$ journalctl -u wpa_supplicant
Mar 02 11:23:47 archlinux-xavier systemd[1]: Starting WPA supplicant...
Mar 02 11:23:47 archlinux-xavier wpa_supplicant[868]: Successfully initialized wpa_supplicant
Mar 02 11:23:47 archlinux-xavier systemd[1]: Started WPA supplicant.
Mar 02 11:23:47 archlinux-xavier wpa_supplicant[868]: wlp1s0: CTRL-EVENT-SCAN-FAILED ret=-16
Mar 02 11:30:50 archlinux-xavier wpa_supplicant[868]: wlp1s0: No network configuration found for the current AP
Mar 02 11:30:51 archlinux-xavier wpa_supplicant[868]: wlp1s0: CTRL-EVENT-DISCONNECTED bssid=e4:fb:5d:9b:93:3c reason=3 locally_generated=1
Mar 02 11:30:51 archlinux-xavier wpa_supplicant[868]: wlp1s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Mar 02 11:30:51 archlinux-xavier wpa_supplicant[868]: wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=FR
Mar 02 11:30:51 archlinux-xavier wpa_supplicant[868]: wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Mar 02 11:30:51 archlinux-xavier wpa_supplicant[868]: wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=FR
Mar 02 11:33:17 archlinux-xavier wpa_supplicant[868]: wlp1s0: No network configuration found for the current AP
Mar 02 11:33:17 archlinux-xavier wpa_supplicant[868]: wlp1s0: CTRL-EVENT-DISCONNECTED bssid=e4:fb:5d:9b:93:3c reason=3 locally_generated=1
Mar 02 11:33:17 archlinux-xavier wpa_supplicant[868]: wlp1s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Mar 02 11:33:17 archlinux-xavier wpa_supplicant[868]: wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=FR
Mar 02 11:33:17 archlinux-xavier wpa_supplicant[868]: wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Mar 02 11:33:17 archlinux-xavier wpa_supplicant[868]: wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=FR
Mar 02 11:33:17 archlinux-xavier wpa_supplicant[868]: wlp1s0: CTRL-EVENT-SCAN-FAILED ret=-16
$ journalctl -u dhcpcd
Mar 02 11:23:42 archlinux-xavier systemd[1]: Starting dhcpcd on all interfaces...
Mar 02 11:23:42 archlinux-xavier dhcpcd[651]: dev: loaded udev
Mar 02 11:23:42 archlinux-xavier dhcpcd[651]: forked to background, child pid 654
Mar 02 11:23:44 archlinux-xavier systemd[1]: Started dhcpcd on all interfaces.
Mar 02 11:23:44 archlinux-xavier dhcpcd[654]: enp3s0: waiting for carrier
Mar 02 11:23:44 archlinux-xavier dhcpcd[654]: wlp1s0: waiting for carrier
Mar 02 11:23:44 archlinux-xavier dhcpcd[654]: wlp1s0: carrier acquired
Mar 02 11:23:44 archlinux-xavier dhcpcd[654]: DUID 00:04:76:1b:9b:60:23:f2:11:e2:82:d1:30:f9:ed:c8:14:33
Mar 02 11:23:44 archlinux-xavier dhcpcd[654]: wlp1s0: IAID 31:c6:85:29
Mar 02 11:23:44 archlinux-xavier dhcpcd[654]: wlp1s0: adding address fe80::33:3e7a:d615:fa81
Mar 02 11:23:44 archlinux-xavier dhcpcd[654]: wlp1s0: carrier lost
Mar 02 11:23:44 archlinux-xavier dhcpcd[654]: wlp1s0: deleting address fe80::33:3e7a:d615:fa81
Mar 02 11:23:44 archlinux-xavier dhcpcd[654]: enp3s0: carrier acquired
Mar 02 11:23:44 archlinux-xavier dhcpcd[654]: enp3s0: IAID ed:c8:14:33
Mar 02 11:23:44 archlinux-xavier dhcpcd[654]: enp3s0: adding address fe80::c003:4ad6:a86a:3cc1
Mar 02 11:23:44 archlinux-xavier dhcpcd[654]: enp3s0: soliciting an IPv6 router
Mar 02 11:23:44 archlinux-xavier dhcpcd[654]: enp3s0: carrier lost
Mar 02 11:23:44 archlinux-xavier dhcpcd[654]: enp3s0: deleting address fe80::c003:4ad6:a86a:3cc1
Mar 02 11:23:45 archlinux-xavier dhcpcd[654]: wlp1s0: carrier acquired
Mar 02 11:23:45 archlinux-xavier dhcpcd[654]: wlp1s0: IAID 31:c6:85:29
Mar 02 11:23:45 archlinux-xavier dhcpcd[654]: wlp1s0: adding address fe80::e5b3:211b:4593:f52
Mar 02 11:23:45 archlinux-xavier dhcpcd[654]: wlp1s0: rebinding lease of 192.168.1.66
Mar 02 11:23:46 archlinux-xavier dhcpcd[654]: wlp1s0: soliciting an IPv6 router
Mar 02 11:23:46 archlinux-xavier dhcpcd[654]: wlp1s0: Router Advertisement from fe80::1
Mar 02 11:23:46 archlinux-xavier dhcpcd[654]: wlp1s0: adding address fde4:fb5d:9b93:3500:8bd4:fdd6:d7e8:8c6d/64
Mar 02 11:23:46 archlinux-xavier dhcpcd[654]: wlp1s0: adding route to fde4:fb5d:9b93:3500::/64
Mar 02 11:23:46 archlinux-xavier dhcpcd[654]: wlp1s0: soliciting a DHCPv6 lease
Mar 02 11:23:47 archlinux-xavier dhcpcd[654]: wlp1s0: deleted route to fde4:fb5d:9b93:3500::/64
Mar 02 11:23:47 archlinux-xavier dhcpcd[654]: wlp1s0: pid 0 deleted address fde4:fb5d:9b93:3500:8bd4:fdd6:d7e8:8c6d/64
Mar 02 11:23:47 archlinux-xavier dhcpcd[654]: wlp1s0: carrier lost
Mar 02 11:23:47 archlinux-xavier dhcpcd[654]: wlp1s0: adding route to fde4:fb5d:9b93:3500::/64
Mar 02 11:23:47 archlinux-xavier dhcpcd[654]: wlp1s0: deleting route to fde4:fb5d:9b93:3500::/64
Mar 02 11:23:47 archlinux-xavier dhcpcd[654]: wlp1s0: new hardware address: ca:86:ad:49:2f:9c
Mar 02 11:29:31 archlinux-xavier dhcpcd[654]: wlp1s0: new hardware address: 36:2d:f7:23:a2:7a
$ cat /etc/wpa_supplicant/wpa_supplicant-wlp1s0.conf 
ctrl_interface=/run/wpa_supplicant
update_config=1
ap_scan=1

network={
	ssid="XXXX"
	psk="XXXX"
}
$ cat /etc/wpa_supplicant/wpa_supplicant.conf        
ctrl_interface=/run/wpa_supplicant
update_config=1
ap_scan=1
$ ln -s /usr/share/dhcpcd/hooks/10-wpa_supplicant /usr/lib/dhcpcd/dhcpcd-hooks/

Not working...

This is driving me crazy ! big_smile

Offline

#9 2019-03-02 11:11:34

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,732
Website

Re: [SOLVED] Wifi connectivity issue

xavib wrote:

Adding options ath9k nohwcrypt=1 in /etc/modprobe.d/ath9k.conf does not work.

Check if it is being applied:

cat /sys/module/ath9k/parameters/nohwcrypt

The module may have a slightly different name, use `lsmod|grep ath9k` to check.

Perhaps also try the ps_enable=0 option to disable power saving for the card.

Did you try the backports-patched AUR package?

You can delete /etc/wpa_supplicant/wpa_supplicant.conf, the dhcpcd hook checks for wpa_supplicant-"$interface".conf so you only need the interface specific file.

Are you infected with Wetiko?

Offline

#10 2019-03-02 12:55:30

seth
Member
Registered: 2012-09-03
Posts: 51,017

Re: [SOLVED] Wifi connectivity issue

Please post a complete journal. The first carrier status messages from dhcpcd appear before wpa_supplicant is started. You most likely have iwd still enabled and running.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#11 2019-03-02 13:08:24

xavib
Member
Registered: 2019-01-19
Posts: 10

Re: [SOLVED] Wifi connectivity issue

It is applied:

$ cat /sys/module/ath9k/parameters/ps_enable
0
Head_on_a_Stick wrote:

Did you try the backports-patched AUR package?

Isn't it supposed to only be for older kernel version ?
Mine is 4.20.13

Offline

#12 2019-03-02 13:24:29

xavib
Member
Registered: 2019-01-19
Posts: 10

Re: [SOLVED] Wifi connectivity issue

seth wrote:

Please post a complete journal. The first carrier status messages from dhcpcd appear before wpa_supplicant is started. You most likely have iwd still enabled and running.

https://drive.google.com/file/d/18kx2m2 … sp=sharing

Offline

#13 2019-03-02 14:15:40

seth
Member
Registered: 2012-09-03
Posts: 51,017

Re: [SOLVED] Wifi connectivity issue

Mar 02 14:15:56 archlinux-xavier dhcpcd[660]: wlp1s0: waiting for carrier
Mar 02 14:15:56 archlinux-xavier NetworkManager[657]: <info>  [1551532556.7078] wifi-nl80211: (wlp1s0): using nl80211 for WiFi device control

Why is networkmanager enabled, running?
It's in a race w/ dhcpcd …

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#14 2019-03-02 14:20:43

xavib
Member
Registered: 2019-01-19
Posts: 10

Re: [SOLVED] Wifi connectivity issue

tlp service was starting networkmanager...
Everything works now...

Sorry and thanks !

Offline

#15 2019-03-02 14:24:04

seth
Member
Registered: 2012-09-03
Posts: 51,017

Re: [SOLVED] Wifi connectivity issue

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#16 2019-04-01 09:00:55

anarki@buttereblume
Member
Registered: 2015-12-29
Posts: 50

Re: [SOLVED] Wifi connectivity issue

Using plain iwd without any overlaying manager for about six months now I rarely experience the same behaviour:

Apr 01 10:35:14 butterblume iwd[3395]: Wireless daemon version 0.14
Apr 01 10:35:14 butterblume iwd[3395]: Skipping optional configuration file /etc/iwd/main.conf
Apr 01 10:35:14 butterblume systemd[1]: Started Wireless service.
Apr 01 10:35:14 butterblume iwd[3395]: Wiphy: 0, Name: phy0
Apr 01 10:35:14 butterblume iwd[3395]:         Bands: 2.4 GHz 5 GHz
Apr 01 10:35:14 butterblume iwd[3395]:         Ciphers: CCMP TKIP
Apr 01 10:35:14 butterblume iwd[3395]:         Supported iftypes: ad-hoc station ap
Apr 01 10:35:14 butterblume iwd[3395]: No ControlPortOverNL80211 setting, defaulting to True
Apr 01 10:45:45 butterblume iwd[3395]: Received Deauthentication event, reason: 6, from_ap: true

After deauth, I can only bring back the connection by 

iwctl adapter phy0 set-property Powered off
iwctl adapter phy0 set-property Powered on

or be restarting

systemctl restart iwd.service

It's not annoying, since it happens not more than twice a week. I have to state, though:

  • it does not happen when I switch to wpa_supplicant + NetworkManager (or I do not take notice of)

  • iwd does not renew the authentification by itself in this case and by reconnecting manually, it asks for the networks passphrase and then fails to connect

  • I have not tried iwd+NetworkManager yet (the latter might be able to do the reconnect for me)

The reason for me to stick with iwd is the plain and easy command line interface and the reasonable autocompletion. From my point of view as a user, its a beautiful piece of software.

Last edited by anarki@buttereblume (2019-04-01 09:04:25)

Offline

Pages: 1

Board footer

Powered by FluxBB