You are not logged in.
Hello guys, I'm using a company laptop and I installed Arch linux + i3-gaps.
I'm using NetworkManager as my network manager.
I can connect to the wifi interface smoothly, but it random disconnects after a while and I can't bring the interface back up.
Even running `sudo ip link set <interface> up`returns an input/output error.
The driver is ath10k_pci.
Can you guys help me? (I didn't post any outcomes because I'm not sure what to post, please feel free to ask me for more information.
Last edited by IceS2 (2018-04-27 18:10:04)
Offline
Please paste the output of:
systemctl list-unit-files --state=enabled
Moving to NC...
Offline
If it's another issue I'm thinking of, posting a
dmesg
might be helpful as well.
Online
```
$ systemctl list-unit-files --state=enabled
UNIT FILE STATE
autovt@.service enabled
bluetooth.service enabled
dbus-fi.w1.wpa_supplicant1.service enabled
dbus-org.bluez.service enabled
dbus-org.freedesktop.NetworkManager.service enabled
dbus-org.freedesktop.nm-dispatcher.service enabled
display-manager.service enabled
getty@.service enabled
lightdm.service enabled
NetworkManager-dispatcher.service enabled
NetworkManager.service enabled
ntpd.service enabled
wpa_supplicant.service enabled
remote-fs.target enabled
14 unit files listed.
```
I'll post dmesg as soon as the wifi goes down again!
PS. How do I tag code? ><
Last edited by IceS2 (2018-04-25 17:06:11)
Offline
Disable the wpa_supplicant.service, you should not have conflicting network management utilities running at the same time.
Look at the bbcode link under every post editor for information on how to use certain tags.
Online
V1del, I've done that and network manager stopped working. When getting wpa_supplicant back up it started to work again. Doesn't NetworkManager use wpa_supplicant???
Offline
You''ve done what exactly?
NM invokes wpa_supplicant, but you should not have wpa_supplicant services *enabled* next to NM.
Online
I've disabled wpa_supplicant and the wifi became unavailable
Edit: Nvm, tried it again and now it seems to work after restarting the PC again. For now it's solved. I'll just wait for a few hours to see if that fixed the issue and If it did, I'll mark the post as solved! Thanks guys!
Last edited by IceS2 (2018-04-27 15:57:27)
Offline