Internet (WiFi and Ethernet) constantly cutting out frequently

I’ve switched to EndeavorOS from Ubuntu and have been loving it so far. Ever since switching to EndeavorOS I have been having severe internet problems. Every 10-30 seconds my internet connection seems to get choppy, before dropping completely. This is annoyingly frequent and makes Discord practically unusable as I have to listen to the reconnection noises and my friends’ audio getting chopped up constantly. I switch to my phone and everything’s fine, which is more supporting evidence that this is isolated to the EndeavorOS upgrade. The problems occur both on ethernet or Wi-Fi.

I am certain this is not a duplicate as the root of the forums which got a solution seem irrelevant, such as with USB ethernet adapters, which I am not using.

I don’t know how to find relevant internet driver and device information, so please let me know what I need to do next. All I could find is using the command lspci, which has this relevant line:

03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 15)

Here’s the full output:

Output

00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 07)
00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630]
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 07)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10)
00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10)
00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
00:14.3 Network controller: Intel Corporation Cannon Lake PCH CNVi WiFi (rev 10)
00:14.5 SD Host controller: Intel Corporation Device a375 (rev 10)
00:15.0 Serial bus controller: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #0 (rev 10)
00:15.1 Serial bus controller: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #1 (rev 10)
00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10)
00:17.0 SATA controller: Intel Corporation Cannon Lake Mobile PCH SATA AHCI Controller (rev 10)
00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #9 (rev f0)
00:1d.6 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #15 (rev f0)
00:1f.0 ISA bridge: Intel Corporation HM470 Chipset LPC/eSPI Controller (rev 10)
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
00:1f.5 Serial bus controller: Intel Corporation Cannon Lake PCH SPI Controller (rev 10)
01:00.0 VGA compatible controller: NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] (rev a1)
01:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio Controller (rev a1)
01:00.2 USB controller: NVIDIA Corporation TU106 USB 3.1 Host Controller (rev a1)
01:00.3 Serial bus controller: NVIDIA Corporation TU106 USB Type-C UCSI Controller (rev a1)
02:00.0 Non-Volatile memory controller: Kingston Technology Company, Inc. A1000/U-SNS8154P3 x2 NVMe SSD (rev 01)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 15)

Any help appreciated, thank you very much for anyone who takes the time to reply

Welcome @Roadhog360! :wave: :sunglasses: :enos_flag:

There’s a couple of things I’d like to clarify if I may.

When you’re connected via LAN cable, have you got WiFi on your system disabled? If not, do this and see if the problem persists. Otherwise, it’s possible it’s specifically a WiFi issue that’s still persisting even when a LAN cable is attached.

With respect to your mobile not having an issue, presumably your mobile is using the same WiFi network during this test?

I technically didn’t have Wi-Fi disabled, but at the time I installed EndeavorOS I never connected to Wi-Fi yet, so it wasn’t connecting to my network via Wi-Fi automatically if that’s what would interrupt the ethernet. Wi-Fi was not disabled, but there was no way for it to connect to networks at the time. I only even tried Wi-Fi to see if that was also affected.

Yes, every device uses the same network, and since installing EndeavorOS the choppy issues appeared exclusively within it.

1 Like

Thanks @Roadhog360, that is clarifying :+1:

What stands out as unusual then, is that it is affecting both LAN, and WiFi. To me, that would make a driver issue less likely, unless both WiFi and LAN drivers just happen to be exhibiting exactly the same issue.

The next question I have in mind, is can this be isolated to a particular piece of software? Whilst you’re noticing this in Discord, could it be Discord itself, or something else that’s running (a game for example), that’s actually responsible for the issue?

Are you able to replicate the issue, with Discord closed and anything other significant software you might have been running also closed?

It’s hard to tell. While Discord was open I’d notice page loading stopping would be exactly in sync with voice cutting out. However since it’s effectively random it is really hard to tell if the issue happens without Discord since I have no audio cue as a reference point, since I don’t know how else I’d do that without just frantically loading pages until it happens. I’d want something that constantly connects to the internet that’d be apparent right away when it fails, which is exactly why the problem is so inhibiting in a voice chat. For further clarification I am using the client modification of Discord, Vesktop.

Hmm, so perhaps a means of testing.

Perhaps in a terminal, while using Discord and such, running this in the background.
ping 1.1.1.1 | while read result; do echo "[$(date)] $result";done

That’ll ping Cloudflare’s public DNS (a reliable ping test) continuously. That’s piped to a date function to add meaningful timestamps.

If you experience a dropout, note the time and go check on this process and see if it also started timing out.

Will let you know. Sometimes when I do tests to issues, they’ll decide to do this until I stop any means of recording the issue:


So if my response takes a while, blame my bloody luck

2 Likes

I guess you could also try running that same test during regular use too, as a way of monitoring connectivity.

That could be a helpful way of collecting comparative data. For example, if it never timed out while not using Discord vs recorded timeouts while using Discord.

Yep. “Now I am not doing it…” Of course, I’ll pack up and try again tomorrow.

1 Like

Welcome! :smile:

Please show the output of

inxi -Nza

to get some more network info.

Looks like your ethernet hw is from realtek, have you installed package r8168 or not?

Edit: these links have lots of info:

perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
        LANGUAGE = "",
        LC_ALL = (unset),
        LC_ADDRESS = "en_US.UTF-8",
        LC_NAME = "en_US.UTF-8",
        LC_MONETARY = "en_US.UTF-8",
        LC_PAPER = "en_US.UTF-8",
        LC_IDENTIFICATION = "en_US.UTF-8",
        LC_TELEPHONE = "en_US.UTF-8",
        LC_MEASUREMENT = "en_US.UTF-8",
        LC_TIME = "en_GB.UTF-8",
        LC_NUMERIC = "en_US.UTF-8",
        LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
Network:
  Device-1: Intel Cannon Lake PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3 chip-ID: 8086:a370 class-ID: 0280
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: 3000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200

Ah yes, I remember something about package r8168 when I was booting live, but that option did not come back after I installed EndeavorOS on my PC. I remember now it recommended to install a different network driver if I had issues. Ok! I will install it now and see if that helps.

Here is the output of attempting to install that with yay -S
-Syyu also fails, here’s the output of that

Finally got it to happen while this command was running. What happens is the pinging simply stops, it seems like the ms doesn’t go up or anything, the lines just stop printing for a bit.

I got it to install by trying r8168-dkms instead. However, the problem persists. Maybe I need to uninstall the old driver? Not sure how, and it seems like r8169 is not a target for the AUR.

r8169 is a driver in kernel. To use r8169, remove any r8168 package and reboot (r8168 blacklists r8169).
Then check the driver:

lsmod | grep r816

but looks like you already have r8169 in use.

Did you look at the links?

I will try this when I arrive at home. I searched both pages for the r816 drivers until I found a mention of it and then installed the AUR package for r8168. I thought you wanted me to install r8169? Am I supposed to be using r8169 or r8168? I thought your last message told me to use r8168 and now this message tells me to use r8169? I’m a little confused. I had installed r8168 in response to your previous message.

On some systems r8168 works better than r8169, I meant you might try the other too, and you seem to have done that. But that didn’t help, I see.

As the problem is with both networks, maybe the router settings (or VPN if you use it?) are the culprit?

r8168                 692224  0

Looks like r8168 is in use. I don’t use a VPN and my router settings have basically never been changed. It was working in Ubuntu so it’s probably not the router settings but some internet drivers instead.

So it would seem the wider system is halting momentarily, not just the network / Internet.

If you can reliably trigger the issue, you might consider having top running where you can see it, and see what processes are consuming resources when it happens.

$ top

I don’t think the entire system is halting as other applications continue to run, and nothing seems to freeze. It hasn’t happened today but I will run top when it happens again. I’m not sure if it’s anything to do with specific programs open. It sometimes happens when I have next to nothing open, but won’t happen with a handful of fairly hungry apps open.