Wifi stops working suddenly [RESOLVED]

aminepro · 2026-08-16 21:08:53

This happened many times before, I always fixed it by rebooting my system.
Today I was really upset to fix it
so when it happens I do

ip link

to find wlan0 is Down .
I tried

ip link set wlan0 up

RTNETLINK answers: Device or resource busy (this is the first time I get this error, it usually goes silent without doing what I wanted).
I stopped iwd until I restart the module iwlwifi using modeprob but I still get

modprobe: FATAL: Module iwlwifi is in use.

I rebooted before trying to create a new interface using iw which I learnt for this moment long ago, desperate.

I need help trace where the problem comes from; I didn't want to share my entire journal so I used --since option , here's the journal https://paste.c-net.org/LawrencePaint

for this thing here

 python[1351]: /usr/bin/python: Error while finding module specification for 'wallshift.app' (ModuleNotFoundError: No module name>
Aug 16 22:15:41 koko systemd[656]: wallshift-rotate.service: Main process exited, code=exited, status=1/FAILURE
Aug 16 22:15:41 koko systemd[656]: wallshift-rotate.service: Failed with result 'exit-code'.
Aug 16 22:15:41 koko systemd[656]: Failed to start WallShift rotation.
Aug 16 22:15:55 koko systemd[1]: systemd-timedated.service: Deactivated successfully.

I really don't know what it is.
and for the xdg-desktop-portal stuff they have never worked I never needed to fix them (many things don't work and I don't need them) I actually just did

sudo pacman -R flatpak shutter xdg-desktop-portal-hyprland lutris foundry

I'll look to fixing any other stuff so the culprit will become crystal clear next time.

Last edited by aminepro (2026-08-18 21:17:05)

aminepro · 2026-08-16 21:33:41

in this session I got a quick wifi cut and returned after probably a second when I tried to use it, here's the journal https://paste.c-net.org/SpleenJustify
So I think it might be a kernel problem.
This is crazy

ip link #here there's no wlan0 only lo and wlan1
iw phy phy0 interface add wlan0 type managed
sudo iw phy phy0 interface add wlan0 type managed # ph0 doesn't exist either
iw phy
iw phy |less
iw phy phy1 interface add wlan0 type managed
iw phy phy1 interface add wlan0 type managed
sudo iw phy phy1 interface add wlan0 type managed
ip link
ip link set wlan0 up 
sudo ip link set wlan0 up # I get this error again "RTNETLINK answers: Operation not permitted"

this happens with wlan2 too, so anything I add, does that only mean that my wifi card don't support these operations or it's related to the op (problem).

Last edited by aminepro (2026-08-16 22:12:14)

aminepro · 2026-08-16 22:31:47

it happened again now with wlan3 and ph0 can't do ip link set wlan3 up and even when I get a new wlanx the set up goes without errors without doing anything.
I rebooted my system and upgraded the system, I suspect that these problems arise because of outdated system I'll add something if it happens again, another journal https://paste.c-net.org/DrivingBarrier .

aminepro · 2026-08-16 23:20:43

As expected, it hasn't been fixed, it just turns worse, I don't know why, really I opened this thread just because it happens sometimes, now it happens every time after a short period after reboot so I write this in that period seems like a virus cause this is crazy

ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

sudo modprobe -r iwlwifi
modprobe: FATAL: Module iwlwifi is in use.

journal : https://paste.c-net.org/LeavinDescend

WorMzy · 2026-08-17 00:05:43

Please stop bumping your thread needlessly. This isn't a live chat. If you are the last person to post in a thread, and you have something to add, use the edit function to amend your last post.

seth · 2026-08-17 07:10:41

Aug 17 01:04:17 koko sudo[6767]:    amine : TTY=pts/0 ; PWD=/home/amine ; USER=root ; COMMAND=/usr/bin/iw phy phy0 interface add wlan2 type managed

What's that's gonna be?
Please dump a journal after losing the wifi for the first time on a fresh reboot - w/o any flailings to "fix" it.

sudo journalctl -b > ~/mostmewifi.txt

Then upload that when you've network again.

cat ~/mostmewifi.txt | nc termbin.com 9999

Also check rfkill

In general please *never* use -x (spam) or -r ( top-posting; you didn't - just a preemptive request ) w/ journalctl

aminepro · 2026-08-17 19:39:57

Finally happened again frankly while the only site I'm on this site.
journal https://termbin.com/f9o3b
another one when it happened while trying to post the former: https://termbin.com/lhlf7
this is a summary of my trials that didn't work, though the very first one that gave me hope worked (it's inconsistent)
https://termbin.com/yqtjw

what I know till now (maybe the only thing you want to look is the journal):
it happens mostly at the evening
primarily when in archlinux.org
and that it is not consistent and recovers after a reboot

Last edited by aminepro (2026-08-17 20:05:03)

seth · 2026-08-17 20:38:22

You want to address xdg-desktop-portal-gtk and wallshift
Also

Aug 17 10:58:50 koko pipewire-pulse[1166]: pw.conf: 0x558ed879b930: error loading config '/etc/pipewire/pipewire-pulse.conf.d/10-adjustQuirkRules.conf': Invalid argument
Aug 17 10:58:50 koko pipewire-pulse[1166]: mod.rt: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown

But after ~10h

Aug 17 20:48:40 koko kernel: iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
Aug 17 20:48:40 koko kernel: iwlwifi 0000:00:14.3: Failed to send recovery cmd blob was invalid 1
Aug 17 20:48:40 koko kernel: iwlwifi 0000:00:14.3: restart completed
Aug 17 20:48:40 koko iwd[534]: Received Deauthentication event, reason: 1, from_ap: false
Aug 17 20:48:40 koko iwd[534]: event: disconnect-info, reason: 1
Aug 17 20:48:40 koko iwd[534]: WARNING: src/resolve.c:resolve_systemd_revert() condition !systemd_state.is_ready failed
Aug 17 20:48:40 koko iwd[534]: event: state, old: connected, new: disconnected
Aug 17 20:48:40 koko iwd[534]: event: state, old: disconnected, new: autoconnect_quick
Aug 17 20:48:40 koko iwd[534]: event: connect-info, ssid: modified, bss: modified, signal: -61, load: 0/255
Aug 17 20:48:40 koko iwd[534]: event: state, old: autoconnect_quick, new: connecting (auto)
Aug 17 20:48:40 koko kernel: wlan0: authenticate with modified (local address=64:49:7d:4f:17:35)
Aug 17 20:48:40 koko kernel: wlan0: send auth to modified (try 1/3)
Aug 17 20:48:40 koko kernel: wlan0: authenticated
Aug 17 20:48:40 koko kernel: wlan0: associate with modified (try 1/3)
Aug 17 20:48:40 koko kernel: wlan0: RX AssocResp from modified (capab=0x1511 status=0 aid=4)
Aug 17 20:48:40 koko kernel: wlan0: associated
Aug 17 20:48:40 koko kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by modified
Aug 17 20:48:40 koko iwd[534]: event: state, old: connecting (auto), new: connecting (netconfig)
Aug 17 20:48:42 koko iwd[534]: WARNING: src/resolve.c:resolve_systemd_set_dns() condition !systemd_state.is_ready failed
Aug 17 20:48:42 koko iwd[534]: event: state, old: connecting (netconfig), new: connected
Aug 17 20:50:01 koko kernel: iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
Aug 17 20:50:01 koko kernel: iwlwifi 0000:00:14.3: Start IWL Error Log Dump:

the firmware crashes pretty much out of nowhere and never recovers.

Aug 17 10:56:57 archlinux kernel:  nvme0n1: p1 p2 p3 p4 p5 p6
Aug 17 10:56:57 archlinux kernel:  sda: sda1 sda2 sda3

What is on the other partitions? Are you dual booting windows?
=> 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

aminepro · 2026-08-17 21:21:08

and never recovers? what does that actually mean?

the firmware crashes pretty much out of nowhere and never recovers.
Aug 17 10:56:57 archlinux kernel: nvme0n1: p1 p2 p3 p4 p5 p6
Aug 17 10:56:57 archlinux kernel: sda: sda1 sda2 sda3
What is on the other partitions? Are you dual booting windows?
=> 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

I'm not dual booting windows

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    0 476.9G  0 disk
├─sda1        8:1    0   117M  0 part /boot
├─sda2        8:2    0    40G  0 part /
└─sda3        8:3    0 436.8G  0 part /home
zram0       253:0    0   3.7G  0 disk [SWAP]
nvme0n1     259:0    0 476.9G  0 disk
├─nvme0n1p1 259:1    0   276M  0 part
├─nvme0n1p2 259:2    0 224.7G  0 part
├─nvme0n1p3 259:3    0    16M  0 part
├─nvme0n1p4 259:4    0   150G  0 part
├─nvme0n1p5 259:5    0    16G  0 part [SWAP]
└─nvme0n1p6 259:6    0    86G  0 part /home/amine/zbackup

the nvmen1p1 is the efi partition for booting windows I boot arch using sda1
I'll go to that windows later to check.

It seems that I did this a long time ago and forgot about it

cat /etc/pipewire/pipewire-pulse.conf.d/10-adjustQuirkRules.conf
#try something here

For wallshift
that was a service that I added on an other system and when I moved the .config to the current in .config/systemd/user/ there were services defined

I disabled fast start on windows
I noticed that the problem happened inside windows too but was recovered in short time

While writing this it happened again and I rebooted here's the log, https://termbin.com/z1s3
Never mind this last line I had two installation of Windows (not mine) that I forgot to disable fast startup on it.

Last edited by aminepro (2026-08-18 21:16:42)

seth · 2026-08-17 21:25:09

I'm not dual booting windows … nvmen1p1 is the efi partition for booting windows

If you're using windows and linux on the same motherboard you *are* dual booting windows, the involved drives are completely irrelevant for that condition.
=> 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Edit: to point out that radio is the primary victim of that condition.

Last edited by seth (2026-08-17 21:26:32)

aminepro · 2026-08-18 21:14:18

I think you solved it seth, there was no problem with wifi today, and the journal logs are clean from any iwlwifi errors.
That was really dual booting with Windows problem.
I was underrating https://wiki.archlinux.org/title/Dual_boot_with_Windows , never though all kinds of problems may arise from dual booting

Thanks seth

Arch Linux

#1 2026-08-16 21:08:53

Wifi stops working suddenly [RESOLVED]

#2 2026-08-16 21:33:41

Re: Wifi stops working suddenly [RESOLVED]

#3 2026-08-16 22:31:47

Re: Wifi stops working suddenly [RESOLVED]

#4 2026-08-16 23:20:43

Re: Wifi stops working suddenly [RESOLVED]

#5 2026-08-17 00:05:43

Re: Wifi stops working suddenly [RESOLVED]

#6 2026-08-17 07:10:41

Re: Wifi stops working suddenly [RESOLVED]

#7 2026-08-17 19:39:57

Re: Wifi stops working suddenly [RESOLVED]

#8 2026-08-17 20:38:22

Re: Wifi stops working suddenly [RESOLVED]

#9 2026-08-17 21:21:08

Re: Wifi stops working suddenly [RESOLVED]

#10 2026-08-17 21:25:09

Re: Wifi stops working suddenly [RESOLVED]

#11 2026-08-18 21:14:18

Re: Wifi stops working suddenly [RESOLVED]

Board footer