You are not logged in.
I have several headless machines on X86_64 and ARM which have been afflicted by the same failure for about a month now.
I ran pacman -Syu, rebooted, and now the WiFi does not pull an IPv4 anymore. I was waiting for this to be repaired, but it doesn't seem that the responsible party wants to fix this.
I can't find any diagnostically useful data to post. All 5 systems (2x AMD_64, 3x ARM) have the exact same problem. Yet, there are no errors. It claims to be working fine when it is not.
I find it hard to believe that a problem so severe that it's cross platform and completely breaks WiFi would go unnoticed...
I tried a fresh install and it has the same problem. WiFi unusable due to DHCP failing to pull IPv4. It claims to successfully bring the adapter up, but it has only a link scope IPv6.
So, something was altered around the end of August that completely broke WiFi and it has yet to be fixed.
Wired Ethernet "just works." But, running wires all over the place to all these computers isn't an option...
I use netctl because the networkd/wpa_supplicant documentation is incomplete nonsense.
Offline
There's little in your post that can be used to help you: https://bbs.archlinux.org/viewtopic.php?id=57855
Post a journal, information about your chipset, which services are actually enabled etc.. post in
[code]code[/code]
tags
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
sudo journalctl -b
FWIW what's quite plausible here is that you have multiple instances of dhcpcd running (was always an issue and a unsupported misconfiguration, got effectively problematic due to a restructuring of how dhcpcd works in the 9.0 release of it, )
Last edited by V1del (2020-11-01 14:56:14)
Offline