You are not logged in.
I uninstalled Reaper along with a few plugins due to a glitch; thought I'd give it a fresh install after clearing it out. I may have done something foolish, however, because at first it wouldn't allow me to remove it - and so I used "-Runsdd" to force the process. The only package listed in its deletion was Reaper itself and none other. Nothing appeared to be wrong, but upon rebooting, wlan0 does not detect or connect to WiFi.
Intel 6 AX201 is the chip.
This is the list of packages I uninstalled:
surge-xt
reaper
reapack
cardinal
amsynth
I upgraded and reinstalled everything, including linux, linux-headers, base-devel. I also installed broadcom-wl in case it somehow was uninstalled (assuming I had it beforehand). I've searched around online as much as I could but couldn't find anything that worked. Also claims it to be "unmanaged".
I am typing this on the PC using my phone as a tether. Nmtui and nmcli register and show it as a working connection.
Output of "nmcli":
lo: connected (externally) to lo
"lo"
loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
inet4 127.0.0.1/8
inet6 ::1/128
wlan0: unmanaged
"Intel 6 AX201"
wifi (iwlwifi), F4:4E:E3:A5:CA:EE, plugin missing, hw, mtu 1500
Output of "sudo systemctl status NetworkManager.service":
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; preset: disabled)
Active: active (running) since Thu 2025-04-24 19:53:55 EDT; 18min ago
Invocation: 70596393e30f42e0b7f5adedab3d81b0
Docs: man:NetworkManager(8)
Main PID: 2425 (NetworkManager)
Tasks: 4 (limit: 18733)
Memory: 3.1M (peak: 4.1M)
CPU: 73ms
CGroup: /system.slice/NetworkManager.service
└─2425 /usr/bin/NetworkManager --no-daemon
Apr 24 19:54:38 Tinderbox NetworkManager[2425]: <info> [1745538878.2319] dhcp4 (enp0s20f0u3): state changed new lease, address=192.168.245.210
Apr 24 19:54:38 Tinderbox NetworkManager[2425]: <info> [1745538878.2348] policy: set 'Wired connection 1' (enp0s20f0u3) as default for IPv4 routing and DNS
Apr 24 19:54:38 Tinderbox NetworkManager[2425]: <info> [1745538878.2383] device (enp0s20f0u3): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Apr 24 19:54:38 Tinderbox NetworkManager[2425]: <info> [1745538878.2392] device (enp0s20f0u3): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Apr 24 19:54:38 Tinderbox NetworkManager[2425]: <info> [1745538878.2393] device (enp0s20f0u3): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Apr 24 19:54:38 Tinderbox NetworkManager[2425]: <info> [1745538878.2394] manager: NetworkManager state is now CONNECTED_SITE
Apr 24 19:54:38 Tinderbox NetworkManager[2425]: <info> [1745538878.2395] device (enp0s20f0u3): Activation: successful, device activated.
Apr 24 19:54:38 Tinderbox NetworkManager[2425]: <warn> [1745538878.2513] dispatcher: (8) /etc/NetworkManager/dispatcher.d/doh-client failed (failed): Script '/etc/NetworkManager/dispatcher.d/doh-client' exited with status 3
Apr 24 19:54:38 Tinderbox NetworkManager[2425]: <warn> [1745538878.2513] dispatcher: (8) /etc/NetworkManager/dispatcher.d/doh-server failed (failed): Script '/etc/NetworkManager/dispatcher.d/doh-server' exited with status 3
Apr 24 19:54:39 Tinderbox NetworkManager[2425]: <info> [1745538879.1244] manager: NetworkManager state is now CONNECTED_GLOBAL
Any suggestions or help will be greatly appreciated: I'd really rather not have to reinstall Arch if avoidable. Thanks in advance.
ouch his jaw
Offline
Why installing a Broadcom driver when your WiFi adapter is Intel? Makes no sense.
Do
less /var/log/pacman.log
and look for
[ALPM] removed reaper
with the appropriate date and time.
Start checking which packages were actually removed and installed.
Offline
Why installing a Broadcom driver when your WiFi adapter is Intel? Makes no sense.
Do
less /var/log/pacman.log
and look for
[ALPM] removed reaper
with the appropriate date and time.
Start checking which packages were actually removed and installed.
1. It was a shot in the dark: just tried it because it wouldn't cause any damage
and could potentially fix the issue.
2. Did that, and nothing except what I uninstalled was uninstalled. My guess is that I interrupted
Reaper while it was connected to network-related protocols/drivers. Thusly, when it was forcefully
removed, something corrupted. Could've been writing or something when I cut it off. Not sure.
Other people seem to have had similar issues where Reaper messed with their internet. There doesn't
seem to be an explanation as far as I saw.
3. I reinstalled Arch and everything works fine now. I'm a bit confused on whether I should
mark this thread as "solved" or not, however; perhaps I shouldn't until someone chimes
in with a solution or explanation? Would it be rude to ping a moderator?
ouch his jaw
Offline