I just installed EndeavourOS/Gnome, when I’m playing minecraft (the only game i play) the ping goes way up to 1000+, very unplayable. I’ve tried reinstalled the OS, but the issue still happens. please help, i dont know how to fix this.
Welcome to the community @rexx 
High ping can have many causes, most of them outside of your PC. For the purpose of a baseline and a reason to believe it’s the PC, has this same system recently experienced better pings? What were you running prior to EndeavourOS, and what was the ping then?
Is that Noodle (Gorillaz) in your avatar?
Before i was running windows, then fully switch to Endeavour because no other distros would install for some reason, but my ping was usually from 70-100 which is not bad.
What network adapter are you running?
inxi -Nxx --za
If you’re using WiFi, do you have the option of cabling in instead, even if just for temporary testing purposes?
Does any other internet activity feel slow? What’s the output of pinging Cloudflare’s usually very responsive DNS server:
ping -c 5 1.1.1.1
other internet activity doesn’t seem slow to me, and i do not have option or access to cabling.
for inxi
Device-1: Realtek RTL8852BE PCIe 802.11ax Wireless Network [1T1R]
vendor: Hewlett-Packard driver: rtw89_8852be v: kernel pcie: speed: 2.5 GT/s
lanes: 1 port: 3000 bus-ID: 01:00.0 chip-ID: 10ec:b85b
and for the ping
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=49 time=23.5 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=49 time=28.0 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=49 time=61.5 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=49 time=82.8 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=49 time=106 ms
--- 1.1.1.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 23.488/60.261/105.552/31.468 ms
1 Like
sry idk how to make the embedded thing
All good. For future reference, you do it like this:
```
Some text
goes in here
```
alr tysm
1 Like
That ping is highly variable, with a 4-5x fluctuation. I suspect that’s unusual.
It is suggested here that your particular adapter may be prone to a connection stability issue (particularly on HP and Lenovo devices). The advice is to disable Active State Power Management (ASPM).
You do that by creating and adding options to /etc/modprobe.d/70-rtw89.conf. This command will achieve what the Wiki suggets:
sudo echo “options rtw89_pci disable_aspm_l1=y disable_aspm_l1ss” > /etc/modprobe.d/70-rtw89.conf
Restart and see how you go?
Edit: Command was no good…
1 Like
the output after the command was bash: /etc/modprobe.d/70-rtw89.conf: Permission denied , is that good or bad?
1 Like
Sorry my bad. I tested in a different folder. I’ll revise and repost.
There may be a more elegant way, but this does the job:
echo "options rtw89_pci disable_aspm_l1=y disable_aspm_l1ss" > ~/70-rtw89.conf && sudo mv ~/70-rtw89.conf /etc/modprobe.d/
Alternatively, you can edit that file directly and manually add the line 
sudo nano /etc/modprobe.d/70-rtw89.conf
And insert (CTRL+O to save, CTRL+X to exit):
options rtw89_pci disable_aspm_l1=y disable_aspm_l1ss
1 Like
i used echo "options rtw89_pci disable_aspm_l1=y disable_aspm_l1ss" > ~/70-rtw89.conf && sudo mv ~/70-rtw89.conf /etc/modprobe.d/ my ping doesn’t go to 1000 but its still around 500
Can you try running this test again, so we can see something of a comparison (a bit longer this time):
ping -c 10 1.1.1.1
well it seems a bit worse 
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=4 ttl=49 time=27.7 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=49 time=2054 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=49 time=1041 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=49 time=23.6 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=49 time=124 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=49 time=46.0 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=49 time=65.4 ms
64 bytes from 1.1.1.1: icmp_seq=9 ttl=49 time=88.1 ms
64 bytes from 1.1.1.1: icmp_seq=10 ttl=49 time=110 ms
--- 1.1.1.1 ping statistics ---
10 packets transmitted, 9 received, 10% packet loss, time 9041ms
rtt min/avg/max/mdev = 23.581/397.814/2054.450/660.266 ms, pipe 3
1 Like
It does indeed. Can you test this again next to the WiFi access point, to rule out signal strength as an issue? Make sure you’re plugged into power for all these tests.
i was right next to the wifi box with this one
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=49 time=122 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=49 time=42.3 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=49 time=63.5 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=49 time=85.8 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=49 time=109 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=49 time=467 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=49 time=36.5 ms
64 bytes from 1.1.1.1: icmp_seq=9 ttl=49 time=25.4 ms
64 bytes from 1.1.1.1: icmp_seq=10 ttl=49 time=115 ms
--- 1.1.1.1 ping statistics ---
10 packets transmitted, 9 received, 10% packet loss, time 9019ms
rtt min/avg/max/mdev = 25.397/118.496/467.060/127.756 ms
1 Like
That seems telling. So perhaps a signal quality issue. Just checking, has the access point and/or your typical laptop location changed since Windows?
no the place has not changed
In your usual spot, perhaps run this command and share the output. It’ll also report your signal strength. First you’ll need to install iw if it’s not already on your system:
sudo pacman -S iw
Edit: Then run this command, to get details about your WiFi connection. Replace wlan0 with your WiFi interface:
iw dev wlan0 station dump