Network connection dropping

tjh3nm48 · 13 June 2024 23:22

Just checking: you included the bracketed “[connection]” line, right? The whole file should look like this:

[connection]
wifi.powersave = 0

So I entered this into the file I created :
/etc/NetworkManager/conf.d/default-wifi-powersave-on.conf/wifi.powersave = 0

After entering the above, when I restarted the computer I no longer had a network connection on startup. I ran:
sudo systemctl restart NetworkManager
I received these error messages:
Job for NetworkManager.service faile because control

In Terminal I entered:

sudo systemctl restart NetworkManager

while I had a WiFi connection. I immediately lost the connection.

λ inxi -Naz
Network:
  Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter
    vendor: Hewlett-Packard driver: rtw_8821ce v: kernel modules: rtw88_8821ce
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 02:00.0
    chip-ID: 10ec:c821 class-ID: 0280

tjh3nm48 · 13 June 2024 23:24

I need to address this tomorrow. I have to attend to some family matters now.

BluishHumility · 13 June 2024 23:35

That’s fine, but when you do return please paste the actual terminal output into the thread.

Just describing the error message is not enough, because we can’t see what is happening.

This whole situation is kind of unclear. The Network Manager service file doesn’t just disappear, something else must be happening.

tjh3nm48 · 14 June 2024 19:46

“please paste the actual terminal output into the thread.”

I will try. Because I so frequently loose WiFi connection on my laptop, I have to copy/paste what I get and email it to myself. I use my desktop machine to communicate with you.

I will explore several different setups of /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf on my laptop and how they respond to NetworkManager;

FIRST - /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf/default-wifi-powersave-on
with
“/etc/NetworkManager/conf.d/default-wifi-powersave-on.conf/wifi.powersave = 0”
entered into the file
default-wifi-powersave-on

Reboot computer. WiFi connection is not made. Clicking on the NetworkManager icon yields a message “NetworkManager is not running”.

Terminal:

-joe@tjh in ~ took 60ms

sudo systemctl restart NetworkManager

[sudo] password for joe:

Job for NetworkManager.service failed because the control process exited with error code.

See “systemctl status NetworkManager.service” and “journalctl -xeu NetworkManager.service” for details.

This was the entire output of Terminal for the entry

SECOND - /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf/default-wifi-powersave-on
with
“wifi.powersave = 0” entered into the file
default-wifi-powersave-on

Reboot computer. WiFi connection is not made. Clicking on the NetworkManager icon yields a message “NetworkManager is not running”.

Terminal:

-joe@tjh in ~ took 60ms

sudo systemctl restart NetworkManager

[sudo] password for joe:

Job for NetworkManager.service failed because the control process exited with error code.

See “systemctl status NetworkManager.service” and “journalctl -xeu NetworkManager.service” for details.

This was the entire output of Terminal for the entry

THIRD - /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf/default-wifi-powersave-on
with
nothing entered into the file
default-wifi-powersave-on

Reboot computer. WiFi connection is made. For how long???

Terminal:

-joe@tjh in ~ took 60ms

sudo systemctl restart NetworkManager

[sudo] password for joe:

The Terminal jumped to an open prompt. I received a notice that the WiFi connection had been disconnected. I got a ball of doom and the connection reestablished.

This last scenario seems a bit different than yesterday when I usually lost connection within 4-10 minutes. I have another family engagement to attend tonight. I will leave the computer running to see if the connection remains intact.

BluishHumility · 14 June 2024 20:04

This is not right. The contents of the file should be like so:

Just those two lines, nothing else.

To be more specific, the path to the file should not be in the file. The second line should just say “wifi.powersave = 0”.

You are also missing the first line, which is the word “connection” inside of square brackets.

tjh3nm48:

sudo systemctl restart NetworkManager
[sudo] password for joe:

Job for NetworkManager.service failed because the control process exited with error code.

See “systemctl status NetworkManager.service” and “journalctl -xeu NetworkManager.service” for details.

Probably the service is failing because you created an invalid config. You can verify this by reviewing the logs as suggested in the error message. For example:

systemctl status NetworkManager.service

Again, this is not right because you are missing the first line that needs to be in the file:

The contents of the file should be exactly like that, with those two lines and nothing else.

tjh3nm48:

sudo systemctl restart NetworkManager
[sudo] password for joe:

Job for NetworkManager.service failed because the control process exited with error code.

See “systemctl status NetworkManager.service” and “journalctl -xeu NetworkManager.service” for details.

Restarting the service fails again because you have provided an invalid config.

Here, the connection succeeds because you are no longer providing an invalid config. However, you have not disabled the powersave feature of the radio because the config is empty.

The amount of information you added to the thread is much better this time. It is easier to see what is happening since you added the terminal output.

tbg · 15 June 2024 00:38

If after fixing your configuration errors you’re still experiencing disconnections, be sure to implement my suggestion from the post before on the thread that @BluishHumility linked:

tjh3nm48 · 15 June 2024 15:10

I have been working with the laptop this morning.

First, thank you for making clear that I needed to enter:
[connection]
wifi.powersave = 0
That is a simple. elegant soulution.

I had been thinking [connection] meant I should enter the computer address to the file. I made the change and I thought it worked. However, I am not sure. I have not lost connection on my home wifi now since I logged on over an hour ago. But, I went to a local coffee shop this morning and logged on to check my setup. Once again, I was kicked off after a few minutes.

[B]e sure to implement my suggestion from the post before on the thread that @BluishHumility linked:
Disable mac address randomization.
Then reboot your router and laptop.
How do I " Disable mac address randomization"?

I now note that although the NetworkManager shows I am connected, I am unable to connect with websites online. I just clicked on my network connection again and my connection showed disconnected. I don’t know how long I was actually not connected for the last hour and a half.

I ran the log scripts. Here is what I got:

While the Network is still functioning:

─joe@tjh in ~ took 30ms
╰─λ systemctl status NetworkManager
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; p>
Active: active (running) since Sat 2024-06-15 09:15:39 EDT; 1h 14min ago
Docs: man:NetworkManager(8)
Main PID: 543 (NetworkManager)
Tasks: 4 (limit: 8570)
Memory: 39.1M (peak: 41.1M)
CPU: 815ms
CGroup: /system.slice/NetworkManager.service
└─543 /usr/bin/NetworkManager --no-daemon

Notice: journal has been rotated since unit was started, output may be incomple>

╭─joe@tjh in ~
[] × journalctl -xeu NetworkManager
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
– No entries –

AFTER Disconnection

╭─joe@tjh in ~ took 19ms
╰─λ systemctl status NetworkManager
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; preset: disabled)
Active: active (running) since Sat 2024-06-15 09:15:39 EDT; 1h 30min ago
Docs: man:NetworkManager(8)
Main PID: 543 (NetworkManager)
Tasks: 4 (limit: 8570)
Memory: 39.2M (peak: 41.1M)
CPU: 12.537s
CGroup: /system.slice/NetworkManager.service
└─543 /usr/bin/NetworkManager --no-daemon

Jun 15 10:42:58 tjh-hplaptop NetworkManager[543]: [1718462578.6093] device (wlo1): set-hw-addr: res>
Jun 15 10:43:00 tjh-hplaptop NetworkManager[543]: [1718462580.8866] platform-linux: do-change-link[>
Jun 15 10:43:00 tjh-hplaptop NetworkManager[543]: [1718462580.8867] device (wlo1): state change: pr>
Jun 15 10:43:00 tjh-hplaptop NetworkManager[543]: [1718462580.8872] manager: NetworkManager state i>
Jun 15 10:43:00 tjh-hplaptop NetworkManager[543]: [1718462580.8875] device (wlo1): Activation: fail>
Jun 15 10:43:00 tjh-hplaptop NetworkManager[543]: [1718462580.8880] device (wlo1): supplicant inter>
Jun 15 10:43:00 tjh-hplaptop NetworkManager[543]: [1718462580.8880] device (p2p-dev-wlo1): supplica>
Jun 15 10:43:00 tjh-hplaptop NetworkManager[543]: [1718462580.8888] device (wlo1): state change: fa>
Jun 15 10:43:00 tjh-hplaptop NetworkManager[543]: [1718462580.8895] device (wlo1): set-hw-addr: set>
Jun 15 10:43:03 tjh-hplaptop NetworkManager[543]: [1718462583.1693] platform-linux: do-change-link[>
lines 1-21/21 (END)

╭─joe@tjh in ~ took 14ms
╰─λ journalctl -xeu NetworkManager
Jun 15 10:42:37 tjh-hplaptop NetworkManager[543]: [1718462557.8764] dhc>
Jun 15 10:42:37 tjh-hplaptop NetworkManager[543]: [1718462557.8770] man>
Jun 15 10:42:37 tjh-hplaptop NetworkManager[543]: [1718462557.8834] dev>
Jun 15 10:42:37 tjh-hplaptop NetworkManager[543]: [1718462557.8856] aud>
Jun 15 10:42:38 tjh-hplaptop NetworkManager[543]: [1718462558.0421] dev>
Jun 15 10:42:56 tjh-hplaptop NetworkManager[543]: [1718462576.3443] dev>
Jun 15 10:42:58 tjh-hplaptop NetworkManager[543]: [1718462578.6067] pla>
Jun 15 10:42:58 tjh-hplaptop NetworkManager[543]: [1718462578.6073] man>
Jun 15 10:42:58 tjh-hplaptop NetworkManager[543]: [1718462578.6077] dev>
Jun 15 10:42:58 tjh-hplaptop NetworkManager[543]: [1718462578.6082] dev>
Jun 15 10:42:58 tjh-hplaptop NetworkManager[543]: [1718462578.6082] dev>
Jun 15 10:42:58 tjh-hplaptop NetworkManager[543]: [1718462578.6087] dev>
Jun 15 10:42:58 tjh-hplaptop NetworkManager[543]: [1718462578.6088] man>
Jun 15 10:42:58 tjh-hplaptop NetworkManager[543]: [1718462578.6093] dev>
Jun 15 10:43:00 tjh-hplaptop NetworkManager[543]: [1718462580.8866] pla>
Jun 15 10:43:00 tjh-hplaptop NetworkManager[543]: [1718462580.8867] dev>
Jun 15 10:43:00 tjh-hplaptop NetworkManager[543]: [1718462580.8872] man>
Jun 15 10:43:00 tjh-hplaptop NetworkManager[543]: [1718462580.8875] dev>
Jun 15 10:43:00 tjh-hplaptop NetworkManager[543]: [1718462580.8880] dev>
Jun 15 10:43:00 tjh-hplaptop NetworkManager[543]: [1718462580.8880] dev>
Jun 15 10:43:00 tjh-hplaptop NetworkManager[543]: [1718462580.8888] dev>
Jun 15 10:43:00 tjh-hplaptop NetworkManager[543]: [1718462580.8895] dev>
Jun 15 10:43:03 tjh-hplaptop NetworkManager[543]: [1718462583.1693] pla>
lines 5-27/27 (END)

SGS · 15 June 2024 15:35

Again, please edit all your post for better reading.

The thread is solved since three days?
If, then

ONE issue per topic.

and if you post logs, check that you did not cut them on the right side

Jun 15 10:42:37 tjh-hplaptop NetworkManager[543]: [1718462557.8764] dhc>

For long logs, use PrivateBin, upper right on this forum side.

tbg · 15 June 2024 17:35

The phrase " Disable mac address randomization" is fairly easy to search for, as it is not easily confused with other search results.

We expect our users to perform their due diligence before they make demands on forum support resources. The minimum that is expected is that users at least perform a search before requesting assistance with something. A quick search should have easily turned up the answer. Aside from this, there is a GUI setting to disable mac address randomization and WiFi power saving included in Garuda’s utilities. Perhaps you are not quite ready for an Arch Linux based distro yet, if you are unable to perform the most rudimentary of searches.

Sorry to be so blunt, but frankly this thread is almost painful to read.

https://wiki.archlinux.org/title/NetworkManager#Configuring_MAC_address_randomization

tjh3nm48 · 15 June 2024 19:03

Did you get up on the wrong side of the bed this morning? You really are good at putting a bad taste in a user’s mouth. The other responders have been great.
I have happily used garuda linux for 3+ years without once seeking help. I purchased a new laptop to take on trips and encountered a network connection issue I could not get my head around. I had read glowing reviews of the responsiveness of the garuda forum, so I gave it a shot. I had no prior experience with the protocol and the insider ways of operating on the forum. I was feeling my way here.

Obviously you must be the type that looks down on and disparages ordinary users who are not as divinely advanced as you.

It looks like I need to look for another distribution.

SGS · 15 June 2024 21:41

If you’ve signed up and read here before, you probably know that we don’t look down on users who take the trouble to solve problems themselves.
However, we have zero tolerance for users thinking that we are their personal AI or search engine automaton.
We don’t spoon-feed, like in other forums, we try to guide users towards independence.
The OS is only as good as its administrator, and that is you, not Garuda Linux and not the forum.
If you can’t cope with simple things, you should seek professional help.
The Garuda team does everything on a voluntary basis, for the fun of it.

Maybe we should just close the forum for a while to minimize this sense of entitlement to 0?

Never stop a traveler, if you think Garuda Linux is too hard for you, take something else, good luck.

tbg · 16 June 2024 02:42

Not in the least.

Everyone starts with zero knowledge of how Linux works. Absolutely no one on the Garuda forum will give any user a hard time for not knowing how to troubleshoot their problem themselves.

What is likely to test a forum assistants patience very quickly is when a user repeatedly asks the assistants how perform every action that could be easily determined with a 5 second internet search. We are not your own unpaid personal internet search assistant. If the answer can be found with a 5 second internet search, why would we want/need to constantly reexplain something that is already well documented and easily found online. We expect our users to expend at least a bare minimum of time searching before requesting further information be provided by assistants.

Do you ask for assistance crossing the road if you are capable of doing it yourself?How would you feel if you were elderly and some physically capable young guy expected you to carry a heavy load for you? Show some initiative on our forum and people will bend over backwards to help you. If you come off as lazy or entitled by expecting others to do for you on our forum, then yes you will eventually find someone will call you on it.

That’s simply the way the world works. We provide free assistance to our users on the Garuda forum, we will not carry them when the task is easily accomplished by the user with a little effort on their part.

I’m sorry if I offended you, but be reasonable in your expectations from a completely free service provided by volunteers. There are limits to what you can reasonably expect for free.

nepti · 16 June 2024 19:15

Reinstall Garuda and check if the kernel driver and kernel modules for the WiFi card are loaded correctly.
If not, then install a different kernel and check if everything is loaded correctly.
If not, then try this driver:

paru -S rtl8821ce-dkms-git

Reboot. You have to blacklist the module rtw88_8821ce afterwards.

If you still have these issues, try this as a kernel parameter: pcie_aspm.policy=performance.

If none of that works for you, then check the wild_wild_web which Intel WiFi card works on Linux without problems, buy one for 20-25$ and replace the Realtek WiFi card with it.

Realtek and Broadcom are the worst on Linux. And nVidia btw…