I'm experiencing a severe and worsening Wi-Fi issue on my HP EliteBook 8460p. Running Zorin OS(dual-boot with Windows 10 IoT LTSC, also have an encrypted Parrot OS on external SSD). The problem is specifically with Zorin.
The Problem:
Every single time I log into Zorin, Wi-Fi fails to connect for up to 10 minutes.
I receive repeated "Activation of network connection failed" notifications. Eventually, it connects, but the delay is unbearable and is getting worse over time.
Key Observations:
Wi-Fi works fine on Windows 10 and Parrot OS on the same hardware.
The issue happens on every boot/login to Zorin.
The Wi-Fi card is detected and associates with the router, but DHCP IP configuration fails repeatedly.
*Relevant Logs (journalctl -u NetworkManager ):
dhcp4 (wlo1): activation: beginning transaction (timeout in 45 seconds)
device (wlo1): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Activation: failed for connection 'TP-Link_AP_5246_5GEXT'
This cycle repeats every 45 seconds for ~10 minutes before finally succeeding.
*What I've Tried (No Success):
Disabled IPv6 via nmcli
Increased DHCP timeout to 180 seconds
Disabled Wi-Fi power management (wifi.powersave = 2 )
Attempted to disable driver power save (options iwlwifi power_save=0 )
Verified drivers are loaded (iwlwifi module active)
*Note: All changes have been reverted to default to ensure a clean test.
Questions:
Has anyone with an Intel 6205 on an HP EliteBook 8460p experienced this specific DHCP timeout loop?
Could this be a conflict with my router's DHCP lease settings or 5GHz extension feature?
Are there any kernel parameters or iwlwifi module options I should try?
Would downgrading to an older kernel (e.g., 5.15 LTS) help, or is this a known regression?
Any insights or suggestions would be greatly appreciated. This is making Zorin nearly unusable for daily work.
Hm, I have the same wifi card in my Dell Latitude E6430 but don't have that problem in Zorin 17 Lite or Zorin 18 live session (have used the kernels 5.15, 6.8, 6.14, 6.17) . I'll take a look if I find out something about the Elitebook.
Since association works but DHCP times out, I’d test one thing that removes the DHCP part: set a temporary manual IPv4 on that Wi-Fi profile (same subnet/gateway/DNS as Windows gets). If manual IP works immediately, the card/driver is probably OK and the problem is between NetworkManager’s DHCP client and the extender/AP. Also try the 2.4 GHz SSID or the main router SSID once; older Centrino cards can be picky with 5 GHz extenders even when they eventually connect.
No secure or fastboots.
No typo. Not built in. yes, older corporate "fleet" refurbish steez.
Wifi is ready to go right after boot in Parrot OS. Win 10 can be a bit longer.
But Zorin is the "it don't boot right, so let me just go into Parrot" OS (these days).
Which exacerbates the problem. As it is like Zorin forgets the longer I am away.
But if I boot in and out 6 or 7 times; the wait goes down.
It has an ethernet port. But I am not really setup to use it.
I rent a tiny house in the Swedish countryside. The landlord has the main router in the big house.
I have a wifi radio extender jammy. But no cord long enough atm.
I appreciate all the advice folks.
I tried the suggestions. So the next boot sequence will let me know what's up.
I am not hip to changing kernels. So I will try to avoid this if possible.
Windows is my 20+ year music studio. Parrot OS is security, educational, etc.
But I consider Zorin home. And would like to iron out all the kinks of my daily driver.
Have a great week everyone.
Hi, Zorin 18 is based on Ubuntu 24.04 so I used this in my search criteria together with your issue and the extender details.
Brave A.I. search result via Mojeek gives:
" The DHCP timeout loop on Ubuntu 24.04 when connecting to TP-Link extenders is primarily caused by AppArmor blocking the default systemd-networkd DHCP client via the /etc/apparmor.d/sbin.dhclient profile.
To resolve this, you must switch NetworkManager to use the isc-dhcp-client and configure AppArmor to allow its execution.
Install the DHCP client :
sudo apt install isc-dhcp-client
Configure NetworkManager : Edit /etc/NetworkManager/NetworkManager.conf and add the following line under the [main] section:
[main]
dhcp=dhclient
Adjust AppArmor : Install AppArmor utilities and set the profile to "complain" mode:
If the issue persists, ensure your TP-Link extender is not using TKIP encryption, as this can cause connection failures; use WPA2/WPA3 (CCMP) instead. Additionally, check if a conflicting configuration file /etc/NetworkManager/conf.d/dhcp-client.conf exists from a previous upgrade and remove it if necessary.
Thank you. I will look into this.
Brave's A.I. assistant typlically causes more harm than good.
But every now and then, it gets close enough that you can close the gap and figure things out.
Blessings and Respect to you.
