What do you mean by it did not work? If you could not switch the kernel how do you know the new updated kernel is the problem? Also if you meant that changing the kernel did not fix your slow internet problem, wouldn’t that mean it’s not a problem with the kernel?
Whenever I have a slow internet problem I follow this process. I check other web browsers to see if it is a problem with my browser. Then I check other devices on the same network to see if it is a network problem. If I find it is a problem with my computer I will try switching kernel, I will download the speedtest.net CLI tool and test the internet speed outside a browser. That is just my process I use to find my internet problems which normally works for me. Hope this helps.
I meant switching to 5.8 and 5.7 did not resolve the slow internet issue.
My assumption is that the kernel/driver update is the cause, as that was the only change that I can think off. Now reverting to the other installed ones did not resolve it, I am going to try 5.4 and see if that makes a difference.
My other devices using the same wifi connection work well. It is only the manjaro box which has the issues.
The slow internet issue is intermittent, when I restart the machine or reconnect to the wifi the internet works normally for some 5-10 minutes and then again starts crawling. Sometimes the internet will become very slow, sometimes it will just stop working. At times restarting resolves it, at times it doesnt do anything. sorry for the vague answer.
ping also starts failing so its not just a browser issue.
this is my ip a output
$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether e8:6a:64:bb:93:98 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether a6:3a:01:d0:df:0e brd ff:ff:ff:ff:ff:ff permaddr d4:3b:04:d4:a8:f0
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:a7:56:4f:2a brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
5: br-fa46bcd05aa7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:43:6c:8b:df brd ff:ff:ff:ff:ff:ff
inet 172.22.0.1/16 brd 172.22.255.255 scope global br-fa46bcd05aa7
valid_lft forever preferred_lft forever
inet6 fe80::42:43ff:fe6c:8bdf/64 scope link noprefixroute
valid_lft forever preferred_lft forever
7: vethf498503@if6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-fa46bcd05aa7 state UP group default
link/ether 76:36:4f:28:84:a3 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet6 fe80::7436:4fff:fe28:84a3/64 scope link
valid_lft forever preferred_lft forever
9: vethc2f0c96@if8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-fa46bcd05aa7 state UP group default
link/ether f6:dc:a1:97:56:d8 brd ff:ff:ff:ff:ff:ff link-netnsid 1
inet6 fe80::f4dc:a1ff:fe97:56d8/64 scope link
valid_lft forever preferred_lft forever
I am not sure is some of the above interfaces should be removed etc
below is the output from ping when it had become very slow -
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
I did some research and I think that you are exceeding a system parameter at /proc/sys/net/core/wmem_max . You can change it with the following command.
Make sure you are logged in as root with sudo su or su
Then run, # echo 83886080 > /proc/sys/net/core/wmem_max
I think you are right about it being a problem with updated drivers if this parameter was changed.
I changed my connection:
IPv4 settings - Method: Automatic (DHCP) addresses only
IPv6 settings - Method: Automatic, addresses only
and my Youtube now loads faster than before. Of course, the first run loads slower but when you search or reload it loads faster compared to the default settings.