Arch Linux

vorzek

Guest

Wifi connection randomly dropping.

Hello, i'm having trouble with (mostly) random wifi drops. They always happen when trying to play CS2,  it almost always drops when i initially start the game, after that it may work properly, or it may drop again after a few minutes.
Besides while playing CS, my connection rarely drops, but it does still happen.

I'm using Network Manager with iwd as backend, i only manually changed to that because thats what the guides i found online suggested to fix the wifi drop problem, it's better than how it was before, it used to drop constantly, every 5 minutes it would kick me out of the game. (i think i had wpa before i used iwd, i stopped, disabled and masked wpa)

Here is the journalctf log with CS2 open (from when it drops all the way until the connection is restored):

> aug 09 23:13:12 vorzek-linux kernel: wlan0: Connection to AP 24:4b:fe:c2:56:74 lost
> 
> aug 09 23:13:12 vorzek-linux iwd[16450]: Received Deauthentication event, reason: 4, from_ap: false
> 
> aug 09 23:13:12 vorzek-linux iwd[16450]: event: disconnect-info, reason: 4
> 
> aug 09 23:13:12 vorzek-linux iwd[16450]: event: state, old: connected, new: disconnected
> 
> aug 09 23:13:12 vorzek-linux iwd[16450]: event: state, old: disconnected, new: autoconnect_quick
> 
> aug 09 23:13:12 vorzek-linux NetworkManager[22576]: <info> [1723234392.5621] device (wlan0): new IWD device state is disconnected
> 
> aug 09 23:13:12 vorzek-linux NetworkManager[22576]: <info> [1723234392.5622] device (wlan0): state change: activated -> failed (reason 'supplicant-disconnect', sys-iface-state: 'managed')
> 
> aug 09 23:13:12 vorzek-linux NetworkManager[22576]: <info> [1723234392.5623] manager: NetworkManager state is now DISCONNECTED
> 
> aug 09 23:13:12 vorzek-linux NetworkManager[22576]: <warn> [1723234392.5625] device (wlan0): Activation: failed for connection 'ASUS_5G'
> 
> aug 09 23:13:12 vorzek-linux NetworkManager[22576]: <info> [1723234392.5628] device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
> 
> aug 09 23:13:12 vorzek-linux NetworkManager[22576]: <info> [1723234392.5629] dhcp4 (wlan0): canceled DHCP transaction
> 
> aug 09 23:13:12 vorzek-linux NetworkManager[22576]: <info> [1723234392.5629] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
> 
> aug 09 23:13:12 vorzek-linux NetworkManager[22576]: <info> [1723234392.5629] dhcp4 (wlan0): state changed no lease
> 
> aug 09 23:13:12 vorzek-linux avahi-daemon[664]: Withdrawing address record for 192.168.50.153 on wlan0.
> 
> aug 09 23:13:12 vorzek-linux avahi-daemon[664]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.50.153.
> 
> aug 09 23:13:12 vorzek-linux avahi-daemon[664]: Interface wlan0.IPv4 no longer relevant for mDNS.
> 
> aug 09 23:13:12 vorzek-linux systemd[1]: Starting Network Manager Script Dispatcher Service...
> 
> aug 09 23:13:12 vorzek-linux systemd[1]: Started Network Manager Script Dispatcher Service.
> 
> aug 09 23:13:12 vorzek-linux iwd[16450]: event: connect-info, ssid: ASUS_5G, bss: 24:4b:fe:c2:56:74, signal: -65, load: 20/255
> 
> aug 09 23:13:12 vorzek-linux iwd[16450]: event: state, old: autoconnect_quick, new: connecting (auto)
> 
> aug 09 23:13:12 vorzek-linux NetworkManager[22576]: <info> [1723234392.6751] device (wlan0): new IWD device state is connecting
> 
> aug 09 23:13:12 vorzek-linux NetworkManager[22576]: <info> [1723234392.6754] device (wlan0): Activation: starting connection 'ASUS_5G' (9b3f1958-7d39-4b8c-817f-2388169c04cc)
> 
> aug 09 23:13:12 vorzek-linux NetworkManager[22576]: <info> [1723234392.6755] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
> 
> aug 09 23:13:12 vorzek-linux NetworkManager[22576]: <info> [1723234392.6756] manager: NetworkManager state is now CONNECTING
> 
> aug 09 23:13:12 vorzek-linux NetworkManager[22576]: <info> [1723234392.6758] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
> 
> aug 09 23:13:12 vorzek-linux kernel: wlan0: authenticate with 24:4b:fe:c2:56:74
> 
> aug 09 23:13:12 vorzek-linux kernel: wlan0: send auth to 24:4b:fe:c2:56:74 (try 1/3)
> 
> aug 09 23:13:12 vorzek-linux kernel: wlan0: send auth to 24:4b:fe:c2:56:74 (try 2/3)
> 
> aug 09 23:13:12 vorzek-linux kernel: wlan0: send auth to 24:4b:fe:c2:56:74 (try 3/3)
> 
> aug 09 23:13:12 vorzek-linux kernel: wlan0: authenticated
> 
> aug 09 23:13:12 vorzek-linux kernel: wlan0: associate with 24:4b:fe:c2:56:74 (try 1/3)
> 
> aug 09 23:13:12 vorzek-linux kernel: wlan0: RX AssocResp from 24:4b:fe:c2:56:74 (capab=0x1011 status=0 aid=20)
> 
> aug 09 23:13:13 vorzek-linux kernel: wlan0: associated
> 
> aug 09 23:13:13 vorzek-linux iwd[16450]: event: state, old: connecting (auto), new: connected
> 
> aug 09 23:13:13 vorzek-linux NetworkManager[22576]: <info> [1723234393.0253] device (wlan0): new IWD device state is connected
> 
> aug 09 23:13:13 vorzek-linux NetworkManager[22576]: <info> [1723234393.0254] device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
> 
> aug 09 23:13:13 vorzek-linux NetworkManager[22576]: <info> [1723234393.0303] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
> 
> aug 09 23:13:13 vorzek-linux NetworkManager[22576]: <info> [1723234393.1683] dhcp4 (wlan0): state changed new lease, address=192.168.50.153, acd pending
> 
> aug 09 23:13:13 vorzek-linux NetworkManager[22576]: <info> [1723234393.3711] dhcp4 (wlan0): state changed new lease, address=192.168.50.153
> 
> aug 09 23:13:13 vorzek-linux NetworkManager[22576]: <info> [1723234393.3713] policy: set 'ASUS_5G' (wlan0) as default for IPv4 routing and DNS
> 
> aug 09 23:13:13 vorzek-linux avahi-daemon[664]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.50.153.
> 
> aug 09 23:13:13 vorzek-linux avahi-daemon[664]: New relevant interface wlan0.IPv4 for mDNS.
> 
> aug 09 23:13:13 vorzek-linux avahi-daemon[664]: Registering new address record for 192.168.50.153 on wlan0.IPv4.
> 
> aug 09 23:13:13 vorzek-linux NetworkManager[22576]: <info> [1723234393.3770] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
> 
> aug 09 23:13:13 vorzek-linux NetworkManager[22576]: <info> [1723234393.3777] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
> 
> aug 09 23:13:13 vorzek-linux NetworkManager[22576]: <info> [1723234393.3778] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
> 
> aug 09 23:13:13 vorzek-linux NetworkManager[22576]: <info> [1723234393.3780] manager: NetworkManager state is now CONNECTED_SITE
> 
> aug 09 23:13:13 vorzek-linux NetworkManager[22576]: <info> [1723234393.3781] device (wlan0): Activation: successful, device activated.

and my iwconfig:

> lo        no wireless extensions.
> 
> enp9s0    no wireless extensions.
> 
> enp11s0   no wireless extensions.
> 
> eth0      no wireless extensions.
> 
> wlan0     IEEE 802.11  ESSID:"ASUS_5G"  
>           Mode:Managed  Frequency:5.26 GHz  Access Point: 24:4B:FE:C2:56:74   
>           Bit Rate=1.225 Gb/s   Tx-Power=22 dBm   
>           Retry short limit:7   RTS thr:off   Fragment thr:off
>           Power Management:on
>           Link Quality=48/70  Signal level=-62 dBm  
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:42   Missed beacon:0

Here is the journal log with just some firefox browsing/watching yt. (probably the same thing as before, figured i'd post it here anyway)
heres the log:

> aug 10 00:16:20 vorzek-linux kernel: wlan0: Connection to AP 24:4b:fe:c2:56:74 lost
> aug 10 00:16:20 vorzek-linux iwd[16450]: Received Deauthentication event, reason: 4, from_ap: false
> aug 10 00:16:20 vorzek-linux iwd[16450]: event: disconnect-info, reason: 4
> aug 10 00:16:20 vorzek-linux iwd[16450]: event: state, old: connected, new: disconnected
> aug 10 00:16:20 vorzek-linux iwd[16450]: event: state, old: disconnected, new: autoconnect_quick
> aug 10 00:16:20 vorzek-linux NetworkManager[22576]: <info>  [1723238180.4218] device (wlan0): new IWD device state is disconnected
> aug 10 00:16:20 vorzek-linux NetworkManager[22576]: <info>  [1723238180.4219] device (wlan0): state change: activated -> failed (reason 'supplicant-disconnect', sys-iface-state: 'managed')
> aug 10 00:16:20 vorzek-linux NetworkManager[22576]: <info>  [1723238180.4221] manager: NetworkManager state is now DISCONNECTED
> aug 10 00:16:20 vorzek-linux NetworkManager[22576]: <warn>  [1723238180.4222] device (wlan0): Activation: failed for connection 'ASUS_5G'
> aug 10 00:16:20 vorzek-linux NetworkManager[22576]: <info>  [1723238180.4226] device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
> aug 10 00:16:20 vorzek-linux NetworkManager[22576]: <info>  [1723238180.4226] dhcp4 (wlan0): canceled DHCP transaction
> aug 10 00:16:20 vorzek-linux NetworkManager[22576]: <info>  [1723238180.4227] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
> aug 10 00:16:20 vorzek-linux NetworkManager[22576]: <info>  [1723238180.4227] dhcp4 (wlan0): state changed no lease
> aug 10 00:16:20 vorzek-linux systemd[1]: Starting Network Manager Script Dispatcher Service...
> aug 10 00:16:20 vorzek-linux avahi-daemon[664]: Withdrawing address record for 192.168.50.153 on wlan0.
> aug 10 00:16:20 vorzek-linux avahi-daemon[664]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.50.153.
> aug 10 00:16:20 vorzek-linux avahi-daemon[664]: Interface wlan0.IPv4 no longer relevant for mDNS.
> aug 10 00:16:20 vorzek-linux systemd[1]: Started Network Manager Script Dispatcher Service.
> aug 10 00:16:20 vorzek-linux iwd[16450]: event: state, old: autoconnect_quick, new: autoconnect_full
> aug 10 00:16:24 vorzek-linux iwd[16450]: invalid HE capabilities for 48:a9:8a:e3:92:06
> aug 10 00:16:24 vorzek-linux iwd[16450]: invalid HE capabilities for 4a:a9:8a:e3:92:06
> aug 10 00:16:24 vorzek-linux iwd[16450]: invalid HE capabilities for 24:91:bb:72:ce:a0
> aug 10 00:16:24 vorzek-linux iwd[16450]: event: connect-info, ssid: ASUS_5G, bss: 24:4b:fe:c2:56:74, signal: -66, load: 2/255
> aug 10 00:16:24 vorzek-linux iwd[16450]: event: state, old: autoconnect_full, new: connecting (auto)
> aug 10 00:16:24 vorzek-linux kernel: wlan0: authenticate with 24:4b:fe:c2:56:74
> aug 10 00:16:24 vorzek-linux NetworkManager[22576]: <info>  [1723238184.0558] device (wlan0): new IWD device state is connecting
> aug 10 00:16:24 vorzek-linux NetworkManager[22576]: <info>  [1723238184.0561] device (wlan0): Activation: starting connection 'ASUS_5G' (9b3f1958-7d39-4b8c-817f-2388169c04cc)
> aug 10 00:16:24 vorzek-linux NetworkManager[22576]: <info>  [1723238184.0563] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
> aug 10 00:16:24 vorzek-linux NetworkManager[22576]: <info>  [1723238184.0565] manager: NetworkManager state is now CONNECTING
> aug 10 00:16:24 vorzek-linux NetworkManager[22576]: <info>  [1723238184.0566] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
> aug 10 00:16:24 vorzek-linux kernel: wlan0: send auth to 24:4b:fe:c2:56:74 (try 1/3)
> aug 10 00:16:24 vorzek-linux kernel: wlan0: authenticated
> aug 10 00:16:24 vorzek-linux kernel: wlan0: associate with 24:4b:fe:c2:56:74 (try 1/3)
> aug 10 00:16:24 vorzek-linux kernel: wlan0: RX AssocResp from 24:4b:fe:c2:56:74 (capab=0x1011 status=0 aid=9)
> aug 10 00:16:24 vorzek-linux kernel: wlan0: associated
> aug 10 00:16:24 vorzek-linux iwd[16450]: event: state, old: connecting (auto), new: connected
> aug 10 00:16:24 vorzek-linux NetworkManager[22576]: <info>  [1723238184.1517] device (wlan0): new IWD device state is connected
> aug 10 00:16:24 vorzek-linux NetworkManager[22576]: <info>  [1723238184.1518] device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
> aug 10 00:16:24 vorzek-linux NetworkManager[22576]: <info>  [1723238184.1523] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
> aug 10 00:16:24 vorzek-linux NetworkManager[22576]: <info>  [1723238184.1854] dhcp4 (wlan0): state changed new lease, address=192.168.50.153, acd pending
> aug 10 00:16:24 vorzek-linux NetworkManager[22576]: <info>  [1723238184.3440] dhcp4 (wlan0): state changed new lease, address=192.168.50.153
> aug 10 00:16:24 vorzek-linux NetworkManager[22576]: <info>  [1723238184.3442] policy: set 'ASUS_5G' (wlan0) as default for IPv4 routing and DNS
> aug 10 00:16:24 vorzek-linux avahi-daemon[664]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.50.153.
> aug 10 00:16:24 vorzek-linux avahi-daemon[664]: New relevant interface wlan0.IPv4 for mDNS.
> aug 10 00:16:24 vorzek-linux avahi-daemon[664]: Registering new address record for 192.168.50.153 on wlan0.IPv4.
> aug 10 00:16:24 vorzek-linux NetworkManager[22576]: <info>  [1723238184.3491] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
> aug 10 00:16:24 vorzek-linux NetworkManager[22576]: <info>  [1723238184.3498] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
> aug 10 00:16:24 vorzek-linux NetworkManager[22576]: <info>  [1723238184.3499] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
> aug 10 00:16:24 vorzek-linux NetworkManager[22576]: <info>  [1723238184.3501] manager: NetworkManager state is now CONNECTED_SITE
> aug 10 00:16:24 vorzek-linux NetworkManager[22576]: <info>  [1723238184.3502] device (wlan0): Activation: successful, device activated.

If anything else is needed please let me know.
I've been trying to fix this problem for hours.

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 74,330

Re: Wifi connection randomly dropping.

I'm using Network Manager with iwd as backend, i only manually changed to that because thats what the guides i found online suggested to fix the wifi drop problem

The iwd PID is smaller than the NM PID, suggesting you're not using iwd as backend but concurrently (likewise does "disabled …  wpa")
https://wiki.archlinux.org/title/Networ … Fi_backend

Then please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

and if the issue remains please post your complete system journal for a boot covering such connection losses:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

for the current one.

Reason 4 is "Disassociated due to inactivity"

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

vorzek

Guest

Re: Wifi connection randomly dropping.

I did follow the instructions from that link, unless i did something wrong. I made sure to edit wifi_backend conf

[~]>> sudo cat /etc/NetworkManager/conf.d/wifi_backend.conf
[device]
wifi.backend=iwd

Here is the output: (the wifi-power-off thing is a service i made that turns of power saving for the wifi card)

avahi-daemon.service                     | multi-user.target.wants
avahi-daemon.socket                      | sockets.target.wants
cups.path                                | multi-user.target.wants
cups.service                             | multi-user.target.wants
cups.service                             | printer.target.wants
cups.socket                              | sockets.target.wants
dbus-org.freedesktop.Avahi.service       | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service   | system
default.target                           | system
display-manager.service                  | system
fstrim.timer                             | timers.target.wants
getty@tty1.service                       | getty.target.wants
gnome-keyring-daemon.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
pipewire-pulse.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
power-profiles-daemon.service            | graphical.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-timesyncd.service                | sysinit.target.wants
systemd-userdbd.socket                   | sockets.target.wants
wifi-power-off.service                   | multi-user.target.wants
wireplumber.service                      | pipewire.service.wants
xdg-user-dirs-update.service             | default.target.wants

And here is the log: http://0x0.st/XWPb.txt

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 74,330

Re: Wifi connection randomly dropping.

What is

wifi-power-off.service                   | multi-user.target.wants

aug 10 01:06:15 vorzek-linux NetworkManager[668]: <info>  [1723241175.2542] manager: NetworkManager state is now CONNECTED_GLOBAL
aug 10 01:06:19 vorzek-linux systemd-logind[673]: New session 3 of user vorzek.
aug 10 01:08:11 vorzek-linux NetworkManager[668]: <info>  [1723241291.3958] manager: NetworkManager state is now DISCONNECTED
aug 10 01:08:12 vorzek-linux NetworkManager[668]: <info>  [1723241292.0629] manager: NetworkManager state is now CONNECTED_GLOBAL

You get globally connected, login, disconnect and reconnect immediately from your session.
There's no further indication of any network failure but the journal also only continues for ~90s and is about 4½ minutes total - are you suggesting there has been a perceived conneciton loss during that time?
Reason 4 could be the result of the NIC powering down and not up (in time)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

vorzek

Guest

Re: Wifi connection randomly dropping.

wifi-power-off.service is just a service i made that runs

 sudo iwconfig wlan0 power off 

, which turns off power saving for the wifi card, it's something i saw suggested online to fix my problems. Although i seem to have messed up the service so it hasn't been correctly running for the log below, meaning power saving was turned on. I'll have to test it again later.

But, if i recall correctly, earlier today i manually turned off power saving for the wifi card, and i still had the connection drop happen. Plus i don't see how power saving could make it so my connection drops more often while playing CS, than while watching a yt video for example.

As for the journal, i had my pc turned off, i then turned it on, waited for the error to happen then got the log from my last reply.
Here is a longer version, since my pc has been running for a while now: http://0x0.st/XWPy.txt

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 74,330

Re: Wifi connection randomly dropping.

https://wiki.archlinux.org/title/Power_ … interfaces

aug 10 01:23:44 vorzek-linux NetworkManager[657]: <info>  [1723242224.7218] manager: NetworkManager state is now CONNECTED_GLOBAL
aug 10 01:23:45 vorzek-linux iwd[723]: invalid HE capabilities for 24:91:bb:72:ce:9c
…
aug 10 01:23:48 vorzek-linux systemd-timesyncd[650]: Contacted time server 44.32.28.18:123 (2.arch.pool.ntp.org).
aug 10 01:23:48 vorzek-linux systemd-timesyncd[650]: Initial clock synchronization to Sat 2024-08-10 01:23:48.941029 EEST.
…
aug 10 01:24:00 vorzek-linux kernel: wlan0: Connection to AP 24:4b:fe:c2:56:74 lost
aug 10 01:24:01 vorzek-linux iwd[723]: Received Deauthentication event, reason: 4, from_ap: false
aug 10 01:24:01 vorzek-linux iwd[723]: event: disconnect-info, reason: 4
aug 10 01:24:01 vorzek-linux iwd[723]: event: state, old: connected, new: disconnected
aug 10 01:24:01 vorzek-linux iwd[723]: event: state, old: disconnected, new: autoconnect_quick
aug 10 01:24:01 vorzek-linux NetworkManager[657]: <info>  [1723242241.0684] device (wlan0): new IWD device state is disconnected
aug 10 01:24:01 vorzek-linux NetworkManager[657]: <info>  [1723242241.0685] device (wlan0): state change: activated -> failed (reason 'supplicant-disconnect', sys-iface-state: 'managed')
aug 10 01:24:01 vorzek-linux NetworkManager[657]: <info>  [1723242241.0687] manager: NetworkManager state is now DISCONNECTED
aug 10 01:24:01 vorzek-linux NetworkManager[657]: <warn>  [1723242241.0689] device (wlan0): Activation: failed for connection 'ASUS_5G'
…
aug 10 01:24:01 vorzek-linux kernel: wlan0: authenticate with 24:4b:fe:c2:56:74
aug 10 01:24:01 vorzek-linux kernel: wlan0: send auth to 24:4b:fe:c2:56:74 (try 1/3)
aug 10 01:24:01 vorzek-linux kernel: wlan0: authenticated
aug 10 01:24:01 vorzek-linux kernel: wlan0: associate with 24:4b:fe:c2:56:74 (try 1/3)
aug 10 01:24:01 vorzek-linux kernel: wlan0: associate with 24:4b:fe:c2:56:74 (try 2/3)
aug 10 01:24:01 vorzek-linux kernel: wlan0: associate with 24:4b:fe:c2:56:74 (try 3/3)
aug 10 01:24:01 vorzek-linux kernel: wlan0: RX AssocResp from 24:4b:fe:c2:56:74 (capab=0x1011 status=0 aid=19)
aug 10 01:24:01 vorzek-linux kernel: wlan0: associated
aug 10 01:24:02 vorzek-linux kernel: iwlwifi 0000:05:00.0: Unhandled alg: 0x707
aug 10 01:24:02 vorzek-linux iwd[723]: event: state, old: connecting (auto), new: connected

Do you have another AP available for testing (eg. your phone in hotspot mode)?

Edit: you can also try "iwlwifi.disable_11ax=1", https://wiki.archlinux.org/title/Kernel_parameters

Last edited by seth (2024-08-09 23:43:40)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

vorzek

Guest

Re: Wifi connection randomly dropping.

I’ll try my phone hotspot tomorrow.

Is network manager with iwd as backend even the way to go? should i try another alternative?

Would there be any way i could delete every network related package on my system (network manager, iwd, wpa and whatever else) and just do a clean install with only the things i need?

Can’t help but think i got some info mixed up and messed a config file since i followed a lot of different guides and forum posts trying to fix my problem.

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 74,330

Re: Wifi connection randomly dropping.

Is network manager with iwd as backend even the way to go? should i try another alternative?

NM still defaults to wpa_supplicant but there's nothing fundamentally wrong w/ using iwd as backend - whether you want to use NM itfp. is a matter of personal preference.

This doesn't look like an issue w/ the network configuration at large and

messed a config file

many of those changes would by default preserved anywy.

Sanity check

aug 10 01:06:09 vorzek-linux ntfs-3g[616]: Mounted /dev/sda1 (Read-Write, label "Games", NTFS 3.1)

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc