This will be quite a long post, so I will structure it in the following "chapters"
1) Overview of what the problem is
2) OS, hardware data, system log when trying to connect, type of router
3) Things I have already attempted in order to fix the problem (that obviously did not work)
1) Overview
I have bought a new router after the previous one broke - a dual band 5Ghz+ 2.4Ghz router, set up both connections with different SSID's - the 2.4Ghz connection has the same SSID as the previous WiFi I had before I replaced the router. There aren't many differences between the configuration of the 5Ghz connection and the 2.4Ghz connection, so you can imagine my surprise when Network Manager can connect to the 5Ghz just fine without any issues or troubleshooting but absolutely refuses to connect to the 2.4Ghz connection - which is a huge problem, as I have a laptop and I want to be able to move throughout my house and still be connected - and the 5Ghz network simply does not go through walls. Network manager has absolutely no issues connecting to any other WiFi except the 2.4Ghz network I've mentioned. I'll give a list of the general configuration of both networks on point 2.
I had thought that maybe the issue was that Network Manager somehow twists up the old network I had with the same SSID and the new one - apparently that wasn't the issue as I tried any conceivable way of removing the data network manager had stored up until that point that I could find, which did not fix the issue - list of what I've done to remove the data on point 3.
I dual boot Windows 10 and Manjaro, and the 2.4Ghz network works just fine on Windows 10 which makes me believe that the issue isn't the network chip not being somehow compatible with the router or something among those lines. And also, if the chip wasn't compatible, why would I be able to connect to the 5Ghz network, which is from the same router, but not the 2.4 one? So hardware issues are ruled out for me at the moment.
Long story short - Network Manager simply refuses to connect to this particular network I'm talking about, while having no issues with all the other networks I've connected to.
2) OS, hardware, logs, router and configuration
OS + hardware
Logs when trying to connect to the network
Type of router + network configuration
Router: D-link DIR-842
2.4Ghz network:
Security mode WPA/WPA2Personal
Mixed 802.11g/n
WiFi channel Auto
Channel width 20Hz
5Ghz network (for comparison):
Security mode WPA/WPA2Personal
Mixed 802.11 a/n/ac
Wifi Channel Auto
Channel width auto 20/40/80Mhz
Both DHCP.
3) What I've already attempted
a) Listed all the files from /etc/NetworkManager/system-connections and then deleted the file with the SSID name of the network that’s causing the issues.
b) Went further and deleted all of the files in /etc/NetworkManager/system-connections/
c) after reattempting to connect and seeing that it doesn't work, I used nmcli to delete the connection instead, still didn't work.
d) After that, tried to delete all the data from Network Manager and reinstalling it, in an attempt to restore it to factory settings in hope that it would help.
Ran these commands (after using killall on network manager):
This should have been enough - I've completely removed network manager, removed the data it stored, reinstalled it from the package that pacman saved, restarted - it still did not fix the issue.
e) Used a Live USB Manjaro installer just to check if it would connect there - it still refused to connect. Which means that it's probably an issue from Network Manager itself.
f) Only other thing that I've found is cases when netctl would conflict with network manager and cause these issues - never had netctl installed, checked to see if it was there anyway - it is not.
I've probably given way more data and written way more than it was necessary - but I'm growing a little desperate from not being able to fix this issue at all and I'm throwing whatever in hopes that someone might actually know what is going on.
1) Overview of what the problem is
2) OS, hardware data, system log when trying to connect, type of router
3) Things I have already attempted in order to fix the problem (that obviously did not work)
1) Overview
I have bought a new router after the previous one broke - a dual band 5Ghz+ 2.4Ghz router, set up both connections with different SSID's - the 2.4Ghz connection has the same SSID as the previous WiFi I had before I replaced the router. There aren't many differences between the configuration of the 5Ghz connection and the 2.4Ghz connection, so you can imagine my surprise when Network Manager can connect to the 5Ghz just fine without any issues or troubleshooting but absolutely refuses to connect to the 2.4Ghz connection - which is a huge problem, as I have a laptop and I want to be able to move throughout my house and still be connected - and the 5Ghz network simply does not go through walls. Network manager has absolutely no issues connecting to any other WiFi except the 2.4Ghz network I've mentioned. I'll give a list of the general configuration of both networks on point 2.
I had thought that maybe the issue was that Network Manager somehow twists up the old network I had with the same SSID and the new one - apparently that wasn't the issue as I tried any conceivable way of removing the data network manager had stored up until that point that I could find, which did not fix the issue - list of what I've done to remove the data on point 3.
I dual boot Windows 10 and Manjaro, and the 2.4Ghz network works just fine on Windows 10 which makes me believe that the issue isn't the network chip not being somehow compatible with the router or something among those lines. And also, if the chip wasn't compatible, why would I be able to connect to the 5Ghz network, which is from the same router, but not the 2.4 one? So hardware issues are ruled out for me at the moment.
Long story short - Network Manager simply refuses to connect to this particular network I'm talking about, while having no issues with all the other networks I've connected to.
2) OS, hardware, logs, router and configuration
OS + hardware
Code:
System:
Kernel: 5.8.18-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.8-x86_64
root=UUID=49267eb0-b637-4c0d-8186-3b4f1567a55b rw quiet apparmor=1
security=apparmor resume=UUID=77cc4b1c-18f1-4758-9ca5-2c7558bd6e1e
udev.log_priority=3
Desktop: KDE Plasma 5.20.3 tk: Qt 5.15.1 wm: kwin_x11 dm: SDDM
Distro: Manjaro Linux
Machine:
Type: Convertible System: ASUSTeK product: ZenBook UX463FL_UX463FL v: 1.0
serial: <filter>
Mobo: ASUSTeK model: UX463FL v: 1.0 serial: <filter>
UEFI: American Megatrends v: UX463FL.304 date: 12/17/2019
Battery:
ID-1: BAT0 charge: 29.5 Wh condition: 45.9/50.0 Wh (92%) volts: 11.9/11.9
model: ASUSTeK ASUS Battery type: Li-ion serial: N/A status: Discharging
cycles: 55
Device-1: hid-0018:04F3:29B9.0001-battery model: ELAN9008:00 04F3:29B9
serial: N/A charge: N/A status: N/A
CPU:
Info: Quad Core model: Intel Core i7-10510U bits: 64 type: MT MCP
arch: Kaby Lake family: 6 model-id: 8E (142) stepping: C (12) microcode: DE
L2 cache: 8192 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 36812
Speed: 800 MHz min/max: 400/4900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800
4: 800 5: 800 6: 800 7: 800 8: 800
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling
Type: srbds mitigation: TSX disabled
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel UHD Graphics vendor: ASUSTeK driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:9b41
Device-2: NVIDIA GP108BM [GeForce MX250] vendor: ASUSTeK driver: nvidia
v: 450.80.02 alternate: nouveau,nvidia_drm bus ID: 02:00.0
chip ID: 10de:1d52
Device-3: IMC Networks USB2.0 HD IR UVC WebCam type: USB driver: uvcvideo
bus ID: 1-5:4 chip ID: 13d3:56cb serial: <filter>
Display: x11 server: X.Org 1.20.9 compositor: kwin_x11
driver: modesetting,nvidia unloaded: intel,nouveau alternate: fbdev,nv,vesa
display ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 507x285mm (20.0x11.2")
s-diag: 582mm (22.9")
Monitor-1: eDP-1 res: 1920x1080 hz: 60 dpi: 158 size: 309x174mm (12.2x6.9")
diag: 355mm (14")
OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.2.2
direct render: Yes
Audio:
Device-1: Intel vendor: ASUSTeK driver: snd_hda_intel v: kernel
alternate: snd_soc_skl,snd_sof_pci bus ID: 00:1f.3 chip ID: 8086:02c8
Sound Server: ALSA v: k5.8.18-1-MANJARO
Network:
Device-1: Intel Wireless-AC 9462 driver: iwlwifi v: kernel port: 4000
bus ID: 00:14.3 chip ID: 8086:02f0
IF: wlo1 state: up mac: <filter>
Drives:
Local Storage: total: 953.87 GiB used: 15.02 GiB (1.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB1T0HALR-00000
size: 953.87 GiB block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 serial: <filter> rev: EXA7301Q scheme: GPT
Partition:
ID-1: / raw size: 200.00 GiB size: 195.86 GiB (97.93%)
used: 14.38 GiB (7.3%) fs: ext4 dev: /dev/nvme0n1p6
ID-2: /home raw size: 150.00 GiB size: 146.64 GiB (97.76%)
used: 654.0 MiB (0.4%) fs: ext4 dev: /dev/nvme0n1p5
Swap:
Kernel: swappiness: 60 (default) cache pressure: 100 (default)
ID-1: swap-1 type: partition size: 8.00 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/nvme0n1p7
Sensors:
System Temperatures: cpu: 40.0 C mobo: N/A
Fan Speeds (RPM): cpu: 0
Info:
Processes: 226 Uptime: 8m Memory: 15.42 GiB used: 1.65 GiB (10.7%)
Init: systemd v: 246 Compilers: gcc: 10.2.0 clang: 11.0.0 Packages: 1277
pacman: 1271 lib: 366 flatpak: 6 Shell: Bash v: 5.0.18 running in: yakuake
inxi: 3.1.08
Logs when trying to connect to the network
Code:
2 2/11/2020 12:41 wpa_supplicant wlo1: Trying to associate with 40:9b:cd:a5:0e:b4 (SSID='007' freq=2432 MHz)
22/11/2020 12:41 NetworkManager <info> [1606041702.2397] device (wlo1): supplicant interface state: authenticating -> associating
22/11/2020 12:41 NetworkManager <info> [1606041702.2397] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating
22/11/2020 12:41 kernel wlo1: authenticated
22/11/2020 12:41 kernel wlo1: associate with 40:9b:cd:a5:0e:b4 (try 1/3)
22/11/2020 12:41 kernel wlo1: associate with 40:9b:cd:a5:0e:b4 (try 2/3)
22/11/2020 12:41 kernel wlo1: associate with 40:9b:cd:a5:0e:b4 (try 3/3)
22/11/2020 12:41 kernel wlo1: association with 40:9b:cd:a5:0e:b4 timed out
22/11/2020 12:41 wpa_supplicant wlo1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="007" auth_failures=1 duration=10 reason=CONN_FAILED
22/11/2020 12:41 NetworkManager <info> [1606041702.5824] device (wlo1): supplicant interface state: associating -> disconnected
22/11/2020 12:41 NetworkManager <info> [1606041702.5825] device (p2p-dev-wlo1): supplicant management interface state: associating -> disconnected
22/11/2020 12:41 NetworkManager <info> [1606041712.5834] device (wlo1): supplicant interface state: disconnected -> scanning
22/11/2020 12:41 NetworkManager <info> [1606041712.5835] device (p2p-dev-wlo1): supplicant management interface state: disconnected -> scanning
22/11/2020 12:41 wpa_supplicant wlo1: CTRL-EVENT-SSID-REENABLED id=0 ssid="007"
22/11/2020 12:41 wpa_supplicant wlo1: SME: Trying to authenticate with 40:9b:cd:a5:0e:b4 (SSID='007' freq=2432 MHz)
22/11/2020 12:41 kernel wlo1: authenticate with 40:9b:cd:a5:0e:b4
22/11/2020 12:41 kernel wlo1: send auth to 40:9b:cd:a5:0e:b4 (try 1/3)
22/11/2020 12:41 NetworkManager <info> [1606041713.5980] device (wlo1): supplicant interface state: scanning -> authenticating
22/11/2020 12:41 NetworkManager <info> [1606041713.5981] device (p2p-dev-wlo1): supplicant management interface state: scanning -> authenticating
22/11/2020 12:41 wpa_supplicant wlo1: Trying to associate with 40:9b:cd:a5:0e:b4 (SSID='007' freq=2432 MHz)
22/11/2020 12:41 NetworkManager <info> [1606041713.6606] device (wlo1): supplicant interface state: authenticating -> associating
22/11/2020 12:41 NetworkManager <info> [1606041713.6607] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating
22/11/2020 12:41 kernel wlo1: authenticated
22/11/2020 12:41 kernel wlo1: associate with 40:9b:cd:a5:0e:b4 (try 1/3)
22/11/2020 12:41 kernel wlo1: associate with 40:9b:cd:a5:0e:b4 (try 2/3)
22/11/2020 12:41 kernel wlo1: associate with 40:9b:cd:a5:0e:b4 (try 3/3)
22/11/2020 12:41 kernel wlo1: association with 40:9b:cd:a5:0e:b4 timed out
22/11/2020 12:41 wpa_supplicant wlo1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="007" auth_failures=2 duration=20 reason=CONN_FAILED
22/11/2020 12:41 NetworkManager <info> [1606041714.0253] device (wlo1): supplicant interface state: associating -> disconnected
22/11/2020 12:41 NetworkManager <info> [1606041714.0254] device (p2p-dev-wlo1): supplicant management interface state: associating -> disconnected
22/11/2020 12:42 NetworkManager <info> [1606041724.0273] device (wlo1): supplicant interface state: disconnected -> scanning
22/11/2020 12:42 NetworkManager <info> [1606041724.0274] device (p2p-dev-wlo1): supplicant management interface state: disconnected -> scanning
22/11/2020 12:42 NetworkManager <warn> [1606041727.0387] device (wlo1): Activation: (wifi) association took too long
22/11/2020 12:42 NetworkManager <info> [1606041727.0388] device (wlo1): state change: config -> failed (reason 'no-secrets', sys-iface-state: 'managed')
22/11/2020 12:42 NetworkManager <info> [1606041727.0398] manager: NetworkManager state is now DISCONNECTED
22/11/2020 12:42 NetworkManager <info> [1606041727.0431] device (wlo1): set-hw-addr: set MAC address to 82:02:29:D7:5E:56 (scanning)
22/11/2020 12:42 NetworkManager <warn> [1606041727.0474] device (wlo1): Activation: failed for connection '007'
22/11/2020 12:42 NetworkManager <info> [1606041727.0484] device (wlo1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
22/11/2020 12:42 kded5 "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/NetworkManager/ActiveConnection/9"
22/11/2020 12:42 kdeconnectd "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/NetworkManager/ActiveConnection/9"
22/11/2020 12:42 NetworkManager <info> [1606041727.0906] device (wlo1): supplicant interface state: scanning -> disconnected
22/11/2020 12:42 NetworkManager <info> [1606041727.0907] device (p2p-dev-wlo1): supplicant management interface state: scanning -> disconnected
22/11/2020 12:42 NetworkManager <info> [1606041727.0953] device (wlo1): supplicant interface state: disconnected -> inactive
22/11/2020 12:42 NetworkManager <info> [1606041727.0954] device (p2p-dev-wlo1): supplicant management interface state: disconnected -> inactive
Type of router + network configuration
Router: D-link DIR-842
2.4Ghz network:
Security mode WPA/WPA2Personal
Mixed 802.11g/n
WiFi channel Auto
Channel width 20Hz
5Ghz network (for comparison):
Security mode WPA/WPA2Personal
Mixed 802.11 a/n/ac
Wifi Channel Auto
Channel width auto 20/40/80Mhz
Both DHCP.
3) What I've already attempted
a) Listed all the files from /etc/NetworkManager/system-connections and then deleted the file with the SSID name of the network that’s causing the issues.
b) Went further and deleted all of the files in /etc/NetworkManager/system-connections/
c) after reattempting to connect and seeing that it doesn't work, I used nmcli to delete the connection instead, still didn't work.
d) After that, tried to delete all the data from Network Manager and reinstalling it, in an attempt to restore it to factory settings in hope that it would help.
Ran these commands (after using killall on network manager):
sudo pacman -Rnsdd networkmanager
sudo rm -rf /etc/NetworkManager/*
sudo pacman -U /var/cache/pacman/pkg/networkmanager-1.26.4-1-x86_64.pkg.tar.zst
This should have been enough - I've completely removed network manager, removed the data it stored, reinstalled it from the package that pacman saved, restarted - it still did not fix the issue.
e) Used a Live USB Manjaro installer just to check if it would connect there - it still refused to connect. Which means that it's probably an issue from Network Manager itself.
f) Only other thing that I've found is cases when netctl would conflict with network manager and cause these issues - never had netctl installed, checked to see if it was there anyway - it is not.
I've probably given way more data and written way more than it was necessary - but I'm growing a little desperate from not being able to fix this issue at all and I'm throwing whatever in hopes that someone might actually know what is going on.
Last edited: