You are not logged in.

#1 2018-11-17 22:47:43

aSystemOverload
Member
Registered: 2017-09-14
Posts: 9

Network Connectivity Fails to Start On Boot

I've acquired a new Lenovo IdeaPad 320S, Intel Quad Core i5.

I set to install Arch, using notes I've used on previous machines many times and updated each time.  I've had issues getting WiFi to work before, but always had a RJ45 wired connection to fall back to, where I'd set up a netctl profile, enable it, and issue

sudo dhclient

. It always worked fine, even after boot.

I did the same here, but it would not work.  Now I've manage to get it working, reliably, but not after each reboot, without

ip link set interface X down

,

wifi-menu -o.

How can I get the wifi to work on boot.  My progress/attempts are below.  I've tried to get as ,much info, following the main Network Config Arch Wiki and the Wireless Wiki.  They get me UP, but I can't seem to get WiFi working on boot.  Let me know if there's anything else I can provide to complete the picture.

pacman -S iproute2 wpa_supplicant

Get name of Wireless Interface

iw dev 
Interface wlp2s0
ifindex 2
       wdev 0x1
       addr 64:6e:69:f8:71:b3
       ssid WiFiConnection_5Ghz
       type managed
       channel 36 (5180 MHz), width: 80 MHz, center1: 5210 MHz
       txpower 17.00 dBm
Check Interface
iw dev wlp2s0 link
Connected to 50:68:0a:62:c2:7f (on wlp2s0)
       SSID: WiFiConnection_5Ghz
       freq: 5180
       RX: 4633413 bytes (23965 packets)
       TX: 141005 bytes (1203 packets)
       signal: -53 dBm
       tx bitrate: 6.0 MBit/s

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

Check Driver Status

lspci -k
02:00.0 
Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31)
Subsystem: Lenovo QCA9377 802.11ac Wireless Network Adapter
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci

Check Kernel Messages for Firmware being Loaded

dmesg | grep firmware
ath10k_pci 0000:02:00.0: firmware ver WLAN.TF.2.1-00021-QCARMSWP-1 api 6 features wowlan,ignore-otp crc32 42e41877

Check Module for Relevant Output

dmesg | grep ath10k_pci
[    2.807021] ath10k_pci 0000:02:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[    3.065955] ath10k_pci 0000:02:00.0: qca9377 hw1.1 target 0x05020001 chip_id 0x003821ff sub 17aa:0901
[    3.065961] ath10k_pci 0000:02:00.0: kconfig debug 1 debugfs 1 tracing 1 dfs 0 testmode 0
[    3.067459] ath10k_pci 0000:02:00.0: firmware ver WLAN.TF.2.1-00021-QCARMSWP-1 api 6 features wowlan,ignore-otp crc32 42e41877
[    3.131294] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 8aedfa4a
[    3.725280] ath10k_pci 0000:02:00.0: Unknown eventid: 118809
[    3.728336] ath10k_pci 0000:02:00.0: Unknown eventid: 90118
[    3.728782] ath10k_pci 0000:02:00.0: htt-ver 3.56 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[    3.745662] ath10k_pci 0000:02:00.0 wlp2s0: renamed from wlan0
[    4.577968] ath10k_pci 0000:02:00.0: Unknown eventid: 118809
[    4.580806] ath10k_pci 0000:02:00.0: Unknown eventid: 90118
[ 3320.153473] ath10k_pci 0000:02:00.0: Unknown eventid: 118809
[ 3320.156320] ath10k_pci 0000:02:00.0: Unknown eventid: 90118
[ 3499.756858] ath10k_pci 0000:02:00.0: Unknown eventid: 118809
[ 3499.759770] ath10k_pci 0000:02:00.0: Unknown eventid: 90118
[ 3535.970234] ath10k_pci 0000:02:00.0: Unknown eventid: 118809
[ 3535.973148] ath10k_pci 0000:02:00.0: Unknown eventid: 90118

Bring interface up

ip link set wlp2s0 up

Check Interface/Connection

ip link show wlp2s0
2: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
   link/ether 64:6e:69:f8:71:b3 brd ff:ff:ff:ff:ff:ff

Check for Access Points

iw dev wlp2s0 scan | less

Find Specific Wireless Connection

iw dev wlp2s0 scan | WiFiConnection

Disable Power Saving on Interface

iw dev wlp2s0 set power_save off

Connect to WiFiConnection

wifi-menu -o

Successfully connects, creates profile in /etc/netctl, sometimes requires following line first:

ip link set wlp2s0 down

Edit Profile

nano /etc/netctl/wlp2s0-WiFiConnection_5Ghz
Description='Automatically generated profile by wifi-menu'
Interface=wlp2s0
Connection=wireless
Security=wpa
ESSID=WiFiConnection_5Ghz
IP=dhcp
DHCPClient=dhclient
DHCPReleaseOnStop=no
IP6=dhcp
DHCP6Client=dhclient
Key=\”<seemingly random characters>

Check state of connection

sudo netctl status wlp2s0-WiFiConnection_5Ghz
● netctl@wlp2s0\x2dWiFiConnection_5Ghz.service - Automatically generated profile by wifi-menu
  Loaded: loaded (/usr/lib/systemd/system/netctl@.service; enabled; vendor preset: disabled)
 Drop-In: /etc/systemd/system/netctl@wlp2s0\x2dCypherAlign_5Ghz.service.d
          └─profile.conf
  Active: active (running) since Sat 2018-11-17 20:44:21 GMT; 57min ago
    Docs: man:netctl.profile(5)
Main PID: 1259 (network)
   Tasks: 5 (limit: 4915)
  Memory: 8.4M
  CGroup: /system.slice/system-netctl.slice/netctl@wlp2s0\x2dCypherAlign_5Ghz.service
          ├─1259 /bin/bash /usr/lib/netctl/network start wlp2s0-CypherAlign_5Ghz
          ├─1271 wpa_supplicant -q -B -P /run/wpa_supplicant-wlp2s0.pid -i wlp2s0 -D nl80211,wext -c/run/netctl/wpa_supplicant-wlp2s0.conf
          ├─1436 dhclient -4 -q -e TIMEOUT=30 -pf /run/dhclient-wlp2s0-4.pid wlp2s0
          ├─1472 dhclient -6 -q -e TIMEOUT=30 -pf /run/dhclient-wlp2s0-6.pid wlp2s0
          └─1473 dhclient -6 -q -e TIMEOUT=30 -pf /run/dhclient-wlp2s0-6.pid wlp2s0

Nov 17 21:22:02 lt002 dhclient[1473]: XMT: Solicit on wlp2s0, interval 129590ms.
Nov 17 21:24:12 lt002 dhclient[1473]: XMT: Solicit on wlp2s0, interval 130840ms.
Nov 17 21:26:23 lt002 dhclient[1473]: XMT: Solicit on wlp2s0, interval 121920ms.
Nov 17 21:28:25 lt002 dhclient[1473]: XMT: Solicit on wlp2s0, interval 121750ms.
Nov 17 21:30:27 lt002 dhclient[1473]: XMT: Solicit on wlp2s0, interval 129620ms.
Nov 17 21:32:36 lt002 dhclient[1473]: XMT: Solicit on wlp2s0, interval 112950ms.
Nov 17 21:34:30 lt002 dhclient[1473]: XMT: Solicit on wlp2s0, interval 131500ms.
Nov 17 21:36:41 lt002 dhclient[1473]: XMT: Solicit on wlp2s0, interval 123130ms.
Nov 17 21:38:44 lt002 dhclient[1473]: XMT: Solicit on wlp2s0, interval 109200ms.
Nov 17 21:40:34 lt002 dhclient[1473]: XMT: Solicit on wlp2s0, interval 129520ms.

Enable Connection

sudo netctl enable wlp2s0-WiFiConnection_5Ghz               
The profile ‘wlp2s0-WiFiConnection_5Ghz’ is already enabled

Connection is stable, lets reboot to check status afterwards…
After Reboot

ping google.co.uk
Temporary failure in name resolution
ping 8.8.8.8
connect: network is unreachable

Offline

#2 2018-11-18 00:37:12

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: Network Connectivity Fails to Start On Boot

Please paste the output of `systemctl list-unit-files -state=enabled`.


Not an Installation issue, moving to NC...


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#3 2018-11-18 12:40:28

aSystemOverload
Member
Registered: 2017-09-14
Posts: 9

Re: Network Connectivity Fails to Start On Boot

Hi Jason,

systemctl list-unit-files --state=enabled
acpid.service enabled
autovt@.service enabled
getty@.service enabled
sshd.service enabled
remote-fs.target enabled

Offline

#4 2018-11-18 12:46:19

loqs
Member
Registered: 2014-03-06
Posts: 19,106

Re: Network Connectivity Fails to Start On Boot

netctl@.service is not in the list.  What is the status of wlp2s0-WiFiConnection_5Ghz now?

Offline

#5 2018-11-18 13:31:18

aSystemOverload
Member
Registered: 2017-09-14
Posts: 9

Re: Network Connectivity Fails to Start On Boot

I've now also tried

systemctl --type=service

, showing

netctl-auto@wlp2s0.service    loaded active running

, but at the time it was FAILED, FAILED. 
There was also an enabled entry for the netctl profile, which is FAILED/FAILED on boot, but if I bring the interface down, then do

wifi-menu -o

it works.  I disable the netctl profile, leaving just the netctl-auto.

I then (five min ago) came across a StackExchange https://unix.stackexchange.com/question … atic#83108 which mentioned ensuring wpa_actiond is installed, which I've not seen mention anywhere.
I've installed wpa_actiond and rebooted and hey presto, it works on reboot.  Even within KDE.

Offline

Board footer

Powered by FluxBB