You are not logged in.
Got a brand new shiny x63 from 51nb.com, very happy but for the WLAN connectivity issues. Random disconnects, definitely in the range, never have been an issue until now. Tried a different WLAN module and both iwd and the network manager (edit: separately). In order to regain connectivity need to manually restart iwd/NetworkManager service. Icewm as the front-end if you think that matters.
Something's definitely wrong, the very same connectivity issue is experienced on FreeBSD, only it's even harder to recover from (at least for me it is). At the beginning at times the WLAN module was not being detected at all, suddently the wlan interface would reappear after the restart. I've failed to troubleshoot that at the time, learned to live with it, doesn't happen any more actually.
I understand it is hard to troubleshoot the cause of such issues looking at a post like this but this is not entirely what I'm asking here, ofcourse any tips regarding troubleshooting and getting to the bottom of this much appreciated.
The real question is, since none of this seems to be an issue on other distro(s) from the Ubuntu family (tried both (K)Ubuntu), what could possibly be different between my simple Arch setup and the other distro? What could possibly be missing that would allow the other distro to recover gracefully on it's own but would require a manual intervention on Arch?
I'd love to be able to stick to Arch and the Arch-way-of-life, unfortunately struggling to solve the issue at the minute :| kind of a deal breaker.
Any help, suggestions, tips, pointers etc. very much appreciated, or if there's anything I could add I'd be more than happy to.
Last edited by muthuh (2021-12-28 09:14:53)
Offline
See: https://bbs.archlinux.org/viewtopic.php?id=57855
Iwd/networkmanager are not freely interchangeable. If you mix them you create a conflict that leads to issues not unlikely to what you're describing. Decide which of the two you want to use and disable and stop the other.
If that didn't help post a complete journal while having issues.
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
sudo journalctl -bOffline
I've switched to NM from iwd hoping it'd resolve the issue (*buntu use NM afaik). I definitely have only the one running at a time ;)
I'll keep you posted. I'll get the output when (not 'if', surely 'when') it happens again.
Meanwhile the following is the systemd services dump you suggested as part of the requested output:
avahi-daemon.service | multi-user.target.wants
avahi-daemon.socket | sockets.target.wants
dbus-org.freedesktop.Avahi.service | system
dbus-org.freedesktop.home1.service | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service | system
dhcpcd.service | multi-user.target.wants
dirmngr.socket | sockets.target.wants
getty@tty1.service | getty.target.wants
gpg-agent-browser.socket | sockets.target.wants
gpg-agent-extra.socket | sockets.target.wants
gpg-agent.socket | sockets.target.wants
gpg-agent-ssh.socket | sockets.target.wants
NetworkManager.service | multi-user.target.wants
NetworkManager-wait-online.service | network-online.target.wants
p11-kit-server.socket | sockets.target.wants
remote-fs.target | multi-user.target.wants
systemd-homed-activate.service | systemd-homed.service.wants
systemd-homed.service | multi-user.target.wants
systemd-timesyncd.service | sysinit.target.wants
systemd-userdbd.socket | sockets.target.wantLast edited by muthuh (2021-12-16 14:34:02)
Offline
dhcpcd.service | multi-user.target.wantsNot necessary with NM and definitely a conflict leading to these kinds of issues, disable that.
Offline
Stopped and disabled. Actually now that you pointed it out I think I remember specifically enabling it :|
Last edited by muthuh (2021-12-16 14:11:37)
Offline
I am pretty sure it's looking better already. No disconnects as of yet. Let me verify over the next few days but many thanks @V1del already.
Last edited by muthuh (2021-12-16 21:47:12)
Offline
No longer an issue since the dhcpcd service was disabled. Thanks for the suggestion and the fix @V1del
Offline