Network connectivity issues

My Ethernet and Wi-Fi were working perfectly fine yesterday, but suddenly after powering the laptop off yesterday and booting up again later in the day, the network connections both just fail to connect, the hardware is clearly detected, but when attempting to connect, instantly (milliseconds), I see it goes back to an ‘off’ state.
Also I see the notification popup regularly telling me that the network connection failed.

I do manage to connect via a USB Ethernet connection, but only if I’ve disconnected it and reconnected it when I’m on the desktop, so I assume that some way of restating the network hardware after arriving on the desktop may be the answer? (for the time being).

Can you post the output of these 2 commands, so that we have more information from your system:

ip addr
inxi -Fxxa

Also you can take a look in this posts:

Sorry, my bad.

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: enp60s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 8c:04:ba:98:a8:b7 brd ff:ff:ff:ff:ff:ff
4: wlp61s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether da:f8:f2:82:bf:0c brd ff:ff:ff:ff:ff:ff permaddr 38:00:25:ac:d2:8a
7: enp0s20f0u4u1i5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 8c:ae:4c:ec:08:ad brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.78/24 brd 192.168.1.255 scope global dynamic noprefixroute enp0s20f0u4u1i5
       valid_lft 82805sec preferred_lft 82805sec
    inet6 2a00:23c5:7c97:ec00:c973:b7c5:171a:ae1c/64 scope global dynamic noprefixroute 
       valid_lft 315359980sec preferred_lft 315359980sec
    inet6 fdaa:bbcc:ddee:0:6601:b9b8:983f:2435/64 scope global noprefixroute 
       valid_lft forever preferred_lft forever
    inet6 fe80::2973:bcaa:35e0:a3eb/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
8: ipv6leakintrf0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether 96:b7:83:62:f0:70 brd ff:ff:ff:ff:ff:ff
    inet6 fdeb:446c:912d:8da::/64 scope global noprefixroute 
       valid_lft forever preferred_lft forever
    inet6 fe80::9125:248e:a375:1d09/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
9: proton0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 500
    link/none 
    inet 10.38.0.14/16 brd 10.38.255.255 scope global noprefixroute proton0
       valid_lft forever preferred_lft forever
    inet6 fe80::2433:d74d:ea1d:f598/64 scope link stable-privacy 
       valid_lft forever preferred_lft forever

inxi -Fxxa

Network:
  Device-1: Realtek vendor: Dell driver: r8169 v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 3c:00.0 chip-ID: 10ec:2502
    class-ID: 0200
  IF: enp60s0 state: down mac: 8c:04:ba:98:a8:b7
  Device-2: Intel Wi-Fi 6 AX200 vendor: Rivet Networks Killer™
    driver: iwlwifi v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
    bus-ID: 3d:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlp61s0 state: down mac: da:f8:f2:82:bf:0c
  IF-ID-1: enp0s20f0u4u1i5 state: up speed: 1000 Mbps duplex: half
    mac: 8c:ae:4c:ec:08:ad
  IF-ID-2: ipv6leakintrf0 state: unknown speed: N/A duplex: N/A
    mac: 96:b7:83:62:f0:70
  IF-ID-3: proton0 state: unknown speed: 10 Mbps duplex: full mac: N/A

Fixed

I can’t confirm that this is a permanent fix, but it has temporarily enabled my network hardware to be usable again in this Manjaro installation.

I’ll leave this here in case it helps anybody else.

Enter the following command in the terminal to restart your NetworkManager service:

systemctl restart NetworkManager.service

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.