[SOLVED] network connection fails after installing Arch linux.
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
network connection fails after installing Arch linux.
For the installation of Arch I used wifi-menu to establish the connection and make the install, and did the following to check network access details.
Code:
lspci -k|tail -4
01:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01)
Subsystem: Foxconn International, Inc. AR9462 Wireless Network Adapter
Kernel driver in use: ath9k
Kernel modules: ath9k, wl
ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
link/ether c0:38:96:7b:4b:13 brd ff:ff:ff:ff:ff:ff
dmesg|grep firmware
[ 0.298113] Spectre V2 : Enabling Restricted Speculation for firmware calls
dmesg|grep wlan0
[ 84.445744] wlan0: authenticate with ac:a3:1e:e4:a1:92
[ 84.467729] wlan0: send auth to ac:a3:1e:e4:a1:92 (try 1/3)
[ 84.468873] wlan0: authenticated
[ 84.471025] wlan0: associate with ac:a3:1e:e4:a1:92 (try 1/3)
[ 84.473690] wlan0: RX AssocResp from ac:a3:1e:e4:a1:92 (capab=0x1 status=0 aid=10)
[ 84.473850] wlan0: associated
[ 84.474515] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 84.551866] audit: type=1130 audit(1576011116.456:30): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=netctl@wlan0\x2dCity\x20of\x20Eugene\x2dFree\x20Public\x20WiFi comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
After installation I rebooted and failed to connect to the internet with wifi-menu, getting these results instead.
Code:
ping: www.google.com: Temporary failure in name resolution
lspci -k|tail -4
01:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01)
Subsystem: Foxconn International, Inc. AR9462 Wireless Network Adapter
Kernel driver in use: ath9k
Kernel modules: ath9k
ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
link/ether c0:38:96:7b:4b:13 brd ff:ff:ff:ff:ff:ff
dmesg|grep firmware
[ 5.276751] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
ip link set wlp1s0 up
ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
link/ether c0:38:96:7b:4b:13 brd ff:ff:ff:ff:ff:ff
dmesg|grep firmware
[ 5.276751] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
dmesg|grep firmware
[ 5.623139] ath9k 0000:01:00.0 wlp1s0: renamed from wlan0
dmesg|grep wlp1s0
[ 241.764977] wlp1s0: authenticate with ac:a3:1e:e4:a1:92
[ 241.775194] wlp1s0: send auth to ac:a3:1e:e4:a1:92 (try 1/3)
[ 241.776256] wlp1s0: authenticated
[ 241.777644] wlp1s0: associate with ac:a3:1e:e4:a1:92 (try 1/3)
[ 241.778999] wlp1s0: RX AssocResp from ac:a3:1e:e4:a1:92 (capab=0x1 status=0 aid=4)
[ 241.779160] wlp1s0: associated
[ 241.779745] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
[ 241.813454] audit: type=1130 audit(1576018783.420:29): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=netctl@wlp1s0\x2dCity\x20of\x20Eugene\x2dFree\x20Public\x20WiFi comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 241.818154] wlp1s0: deauthenticating from ac:a3:1e:e4:a1:92 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 242.032750] audit: type=1131 audit(1576018783.640:30): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=netctl@wlp1s0\x2dCity\x20of\x20Eugene\x2dFree\x20Public\x20WiFi comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
I do not understand why these results should be different, it's the same machine (acer c720), the same means of connection (wifi-menu), and the same network being connected to, or not. Regardless, if I have interpreted these results and the 'Wireless configuration' wiki correctly, what I need to do now is manually install the ath9k driver firmware from wherever it was stored on my system when pacstrap installed linux-firmware.
The wiki has an early section titled 'installing firmware' but nowhere explicitly states how that should be done, and pacman seems to care only for .tar.xz.
Code:
pacman -U /usr/lib/modules/5.4.2-arch1-1/kernel/drivers/net/wireless/ath/ath9k/ath9k.ko.xz
loading packages...
error: could not open file /usr/lib/modules/5.4.2-arch1-1/kernel/drivers/net/wireless/ath/ath9k/ath9k.ko.xz: Unrecognized archive format
error: '/usr/lib/modules/5.4.2-arch1-1/kernel/drivers/net/wireless/ath/ath9k/ath9k.ko.xz': cannot open package file
I had a similar problem. In my case I have an Intel card that is theoretically proprietary. For that reason Arch does not install it, although it uses it during installation. I'm not sure of the situation with your card but you might investigate along those lines. My solution was to use ethernet immediately after installation, bring the net up manually since no network manager is installed automatically, then install a network manager with pacman and play with it until it worked. Threats with a four pound hammer seemed to help, too. I can't be a whole lot of help with your specific situation. Luckily I am within 100 feet of my router and have a 100 foot ethernet cable so ethernet was a temporary option. If you can plug in ethernet I think it will configure automatically and then you can get the stuff you need off the net. As I remember I actually installed network manager and it seemed to be able to take care of everything. I don't remember the exact things I had to do, but if that doesn't help I'll try to go back and remember/rediscover.
I had a similar problem. In my case I have an Intel card that is theoretically proprietary. For that reason Arch does not install it, although it uses it during installation. I'm not sure of the situation with your card but you might investigate along those lines. My solution was to use ethernet immediately after installation, bring the net up manually since no network manager is installed automatically, then install a network manager with pacman and play with it until it worked. Threats with a four pound hammer seemed to help, too. I can't be a whole lot of help with your specific situation. Luckily I am within 100 feet of my router and have a 100 foot ethernet cable so ethernet was a temporary option. If you can plug in ethernet I think it will configure automatically and then you can get the stuff you need off the net. As I remember I actually installed network manager and it seemed to be able to take care of everything. I don't remember the exact things I had to do, but if that doesn't help I'll try to go back and remember/rediscover.
Thanks for response but I have no ethernet, only wifi connection.
Did you complete the network configuration in the install guide, more specifically, the part where you set the systemd service to start at boot? Assuming the network worked during install.
I don't see any indication in your first post that this is driver- or firmware-related.
Have you checked the logs for such indications?
Also check rfkill.
The way it looks now, the interface just isn't configured correctly - not the device.
PS: it's normal that it changes from wlan0 to wnlps00123 or some such after installation.
Did you complete the network configuration in the install guide, more specifically, the part where you set the systemd service to start at boot? Assuming the network worked during install.
Originally I made the install, rebooted and made a number of systemd modifications, as to lid closure, power switch press and
Code:
systemctl start netctl-auto@wlp1s0.service
so I could immediately download additional software. This was when I discovered the lack of internet. I then did
Code:
systemctl enable netctl-auto@wlp1s0.service
and rebooted. No luck. I also tried running dhcpcd, though I thought that was only for wired interfaces, and that worked, one time and I downloaded and installed extra software.
The next time I booted wifi would not work again, so I decided to do a fresh install, but if I encountered the same problem to connect by hand instead of by netctl. Which is where I'm at now.
Did you investigate ondoho's suggestion that perhaps the adapter device name changes from what it is during the install to another name after reboot? The times I have used Arch have all been with wired connections and I have never had an issue, except when I forgot to enable dhcpds@adapter.service...
I don't see any indication in your first post that this is driver- or firmware-related.
Have you checked the logs for such indications?
Also check rfkill.
The way it looks now, the interface just isn't configured correctly - not the device.
PS: it's normal that it changes from wlan0 to wnlps00123 or some such after installation.
Here are logs. I understand what they say. I have no clue what they mean in terms of fixing the problem. re Rfkill list, that was OK is included in 1st post. I apologize for delay in replying, where I can try to connect, I cannot use another computer to send data.
wlan0 becoming wlp1s0 does not bother me.
Code:
~ $ sudo netctl status wlp1s0
● netctl@wlp1s0.service - Networking for netctl profile wlp1s0
Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static; vendor pr>
Active: inactive (dead)
Docs: man:netctl.profile(5)
~ $ sudo iw dev wlp1s0 set type ibss
~ $ sudo iw dev wlp1s0 connect City\ of\ Eugene-Free\ Public\ Wifi
command failed: Network is down (-100)
~ $ sudo ip link set wlp1s0 up
~ $ sudo ip link show wlp1s0
2: wlp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
link/ether c0:38:96:7b:4b:13 brd ff:ff:ff:ff:ff:ff
~ $ sudo iw dev wlp1s0 connect City\ of\ Eugene-Free\ Public\ Wifi
command failed: Operation not supported (-95)
~ $ dmesg | grep wlp1s0
[ 5.712060] ath9k 0000:01:00.0 wlp1s0: renamed from wlan0
[ 21.753606] wlp1s0: authenticate with ac:a3:1e:e4:a1:92
[ 21.777410] wlp1s0: send auth to ac:a3:1e:e4:a1:92 (try 1/3)
[ 21.779287] wlp1s0: authenticated
[ 21.785473] wlp1s0: associate with ac:a3:1e:e4:a1:92 (try 1/3)
[ 21.787588] wlp1s0: RX AssocResp from ac:a3:1e:e4:a1:92 (capab=0x1 status=0 aid=10)
[ 21.787691] wlp1s0: associated
[ 21.788366] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
[ 22.009192] audit: type=1130 audit(1576280055.602:40): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=netctl@wlp1s0\x2dCity\x20of\x20Eugene\x2dFree\x20Public\x20WiFi comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 22.019412] wlp1s0: deauthenticating from ac:a3:1e:e4:a1:92 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 22.246802] audit: type=1131 audit(1576280055.839:43): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=netctl@wlp1s0\x2dCity\x20of\x20Eugene\x2dFree\x20Public\x20WiFi comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
~ $
~ $ sudo journalctl -xe|grep wlp1s0 >> ~/profile.txt
Dec 13 15:33:59 a kernel: ath9k 0000:01:00.0 wlp1s0: renamed from wlan0
Dec 13 15:34:11 a systemd[1]: Starting Networking for netctl profile wlp1s0-City of Eugene-Free Public WiFi...
-- Subject: A start job for unit netctl@wlp1s0\x2dCity\x20of\x20Eugene\x2dFree\x20Public\x20WiFi.service has begun execution
-- A start job for unit netctl@wlp1s0\x2dCity\x20of\x20Eugene\x2dFree\x20Public\x20WiFi.service has begun execution.
Dec 13 15:34:11 a network[553]: Starting network profile 'wlp1s0-City of Eugene-Free Public WiFi'...
Dec 13 15:34:15 a kernel: wlp1s0: authenticate with ac:a3:1e:e4:a1:92
Dec 13 15:34:15 a kernel: wlp1s0: send auth to ac:a3:1e:e4:a1:92 (try 1/3)
Dec 13 15:34:15 a kernel: wlp1s0: authenticated
Dec 13 15:34:15 a kernel: wlp1s0: associate with ac:a3:1e:e4:a1:92 (try 1/3)
Dec 13 15:34:15 a kernel: wlp1s0: RX AssocResp from ac:a3:1e:e4:a1:92 (capab=0x1 status=0 aid=10)
Dec 13 15:34:15 a kernel: wlp1s0: associated
Dec 13 15:34:15 a kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
Dec 13 15:34:15 a systemd[1]: Started Networking for netctl profile wlp1s0-City of Eugene-Free Public WiFi.
-- Subject: A start job for unit netctl@wlp1s0\x2dCity\x20of\x20Eugene\x2dFree\x20Public\x20WiFi.service has finished successfully
-- A start job for unit netctl@wlp1s0\x2dCity\x20of\x20Eugene\x2dFree\x20Public\x20WiFi.service has finished successfully.
Dec 13 15:34:15 a kernel: audit: type=1130 audit(1576280055.602:40): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=netctl@wlp1s0\x2dCity\x20of\x20Eugene\x2dFree\x20Public\x20WiFi comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 13 15:34:15 a audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=netctl@wlp1s0\x2dCity\x20of\x20Eugene\x2dFree\x20Public\x20WiFi comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 13 15:34:15 a kernel: wlp1s0: deauthenticating from ac:a3:1e:e4:a1:92 by local choice (Reason: 3=DEAUTH_LEAVING)
Dec 13 15:34:15 a network[553]: Failed to bring the network up for profile 'wlp1s0-City of Eugene-Free Public WiFi'
Dec 13 15:34:15 a audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=netctl@wlp1s0\x2dCity\x20of\x20Eugene\x2dFree\x20Public\x20WiFi comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Dec 13 15:34:15 a kernel: audit: type=1131 audit(1576280055.839:43): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=netctl@wlp1s0\x2dCity\x20of\x20Eugene\x2dFree\x20Public\x20WiFi comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Dec 13 15:34:15 a systemd[1]: netctl@wlp1s0\x2dCity\x20of\x20Eugene\x2dFree\x20Public\x20WiFi.service: Main process exited, code=exited, status=1/FAILURE
-- An ExecStart= process belonging to unit netctl@wlp1s0\x2dCity\x20of\x20Eugene\x2dFree\x20Public\x20WiFi.service has exited.
Dec 13 15:34:15 a systemd[1]: netctl@wlp1s0\x2dCity\x20of\x20Eugene\x2dFree\x20Public\x20WiFi.service: Failed with result 'exit-code'.
-- The unit netctl@wlp1s0\x2dCity\x20of\x20Eugene\x2dFree\x20Public\x20WiFi.service has entered the 'failed' state with result 'exit-code'.
Dec 13 15:37:06 a sudo[839]: q : TTY=pts/0 ; PWD=/home/q ; USER=root ; COMMAND=/usr/bin/netctl status wlp1s0
Dec 13 15:42:56 a sudo[1167]: q : TTY=pts/0 ; PWD=/home/q ; USER=root ; COMMAND=/usr/bin/iw dev wlp1s0 set type ibss
Dec 13 15:45:57 a sudo[1176]: q : TTY=pts/0 ; PWD=/home/q ; USER=root ; COMMAND=/usr/bin/iw dev wlp1s0 connect City of Eugene-Free Public Wifi
Dec 13 15:47:03 a sudo[1181]: q : TTY=pts/0 ; PWD=/home/q ; USER=root ; COMMAND=/usr/bin/ip link set wlp1s0 up
Dec 13 15:47:19 a sudo[1184]: q : TTY=pts/0 ; PWD=/home/q ; USER=root ; COMMAND=/usr/bin/ip link show wlp1s0
Dec 13 15:47:29 a sudo[1186]: q : TTY=pts/0 ; PWD=/home/q ; USER=root ; COMMAND=/usr/bin/iw dev wlp1s0 connect City of Eugene-Free Public Wifi
Did you investigate ondoho's suggestion that perhaps the adapter device name changes from what it is during the install to another name after reboot? The times I have used Arch have all been with wired connections and I have never had an issue, except when I forgot to enable dhcpds@adapter.service...
Yes, I'm used to the name change after install, I'm using the new interface name.
I also tried running dhcpcd, though I thought that was only for wired interfaces, and that worked, one time and I downloaded and installed extra software.
The next time I booted wifi would not work again
This should give you some indicators about what's wrong.
BTW, is your SSID City\ of\ Eugene-Free\ Public\ Wifi indicativer of a Public Wifi? That might cause problems.
This should give you some indicators about what's wrong.
BTW, is your SSID City\ of\ Eugene-Free\ Public\ Wifi indicativer of a Public Wifi? That might cause problems.
Right, dhcpcd, but not really; the real problem is my aversion to systemd, and the fact that more and more of Arch is being controlled by it. I ran dhcpcd, it fixed the connection problem that one time only, this time I started and enabled it with systemctl, so it persists after rebooting. Thank you very much for your help, problem solved.
Right, dhcpcd, but not really; the real problem is my aversion to systemd, and the fact that more and more of Arch is being controlled by it. I ran dhcpcd, it fixed the connection problem that one time only, this time I started and enabled it with systemctl, so it persists after rebooting. Thank you very much for your help, problem solved.
That is exactly what I was describing in my first post: ensuring that dhcpcd@<device>.service was enabled during the install with systemctl.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
