Arch Linux

Belgi

Member

Registered: 2013-06-23

Posts: 12

WiFI extremely slow in Arch

I have a new install of Arch after deciding to give it a go after 6 or 7 years on Gentoo.

The only problem I am experiencing is extremely slow internet. 1.58Mbps vs 31Mbps previously in Gentoo.

Google seems to indicate a lot of people have similar issues with Arch, but having followed the Wiki to the letter and not finding any solutions on Google I am stuck at where to start.

iw dev

phy#0
	Interface wlp0s29u1u5
		ifindex 3
		wdev 0x1
		addr c4:3d:c7:ca:85:02
		type managed
		channel 1 (2412 MHz), width: 20 MHz, center1: 2412 MHz

Please let me know what logs to upload, any assistance appreciated. I will continue to search myself.

Belgi

Member

Registered: 2013-06-23

Posts: 12

Re: WiFI extremely slow in Arch

ping -c 3 google.com

PING google.com (173.194.34.167) 56(84) bytes of data.
64 bytes from lhr14s22-in-f7.1e100.net (173.194.34.167): icmp_seq=1 ttl=52 time=14.4 ms
64 bytes from lhr14s22-in-f7.1e100.net (173.194.34.167): icmp_seq=2 ttl=52 time=12.5 ms
64 bytes from lhr14s22-in-f7.1e100.net (173.194.34.167): icmp_seq=3 ttl=52 time=20.0 ms

--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 12.511/15.676/20.060/3.200 ms

thesystematic

Member

Registered: 2013-02-08

Posts: 44

Re: WiFI extremely slow in Arch

what card/usb dongle do you have? have you installed the drivers for it (if required)?

can you post results of

lspci | grep -i net

or

lsusb

depending if card/usb

Belgi

Member

Registered: 2013-06-23

Posts: 12

Re: WiFI extremely slow in Arch

Hello,

I'm using a Netgear N150 USB dongle.

lsusb

Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 006 Device 002: ID 1058:1042 Western Digital Technologies, Inc. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 003: ID 045e:00f6 Microsoft Corp. Comfort Optical Mouse 1000
Bus 004 Device 004: ID 045e:00dd Microsoft Corp. Comfort Curve Keyboard 2000 V1.0
Bus 004 Device 005: ID 0846:9030 NetGear, Inc. WNA1100 Wireless-N 150 [Atheros AR9271]
Bus 004 Device 007: ID 0b05:179c ASUSTek Computer, Inc. 

Thanks

Hector

Member

Registered: 2012-09-18

Posts: 16

Re: WiFI extremely slow in Arch

Check out this.
Download package crda and wireless-regdb next edit /etc/conf.d/wireless-regdom and uncomment redom for your country.After this reboot. Tell us if it works.

Belgi

Member

Registered: 2013-06-23

Posts: 12

Re: WiFI extremely slow in Arch

Thanks for the suggestion Hector. I seem to be getting 4.97 which is a little better. Sorry for the late reply, something has gone wrong and my Arch install won't automatically connect anymore. It's taken me a while to find a way to get online. I am now having to run wifi-menu to connect. Using "systemctl enable" isn't working. Not sure what I've done wrong there.

WonderWoofy

Member

From: Los Gatos, CA

Registered: 2012-05-19

Posts: 8,414

Re: WiFI extremely slow in Arch

Is systemctl working at all?  Try just running it without any arguments and see if you get output. It should list all the units that are running/have run.  I suspect that if it is not connecting automatically, you might have some services in there that have failed.  This is usually caused when people enable a service that handles their intenets, for get about it, and then go and try to set up others, enableing even more.  This has the very small possibility of being the cause of your slow network, but I think it is more likely that conflicting services will just result in a failure to connect.

Belgi

Member

Registered: 2013-06-23

Posts: 12

Re: WiFI extremely slow in Arch

I think you're right WonderWoofy. For some reason or other it is showing as inactive, even though I issued the command to enable it (same command as below but with enable instead of status), which created a symlink. I've checked it a couple of times but can't understand what is wrong.

systemctl status netctl-auto@wlp0s29u1u1-BTHub3-4RGK.service

netctl-auto@wlp0s29u1u1-BTHub3-4RGK.service - Automatic wireless network connection using netctl profiles
   Loaded: loaded (/usr/lib/systemd/system/netctl-auto@.service; enabled)
   Active: inactive (dead)
     Docs: man:netctl.special(7)

systemctl

netctl@w...\x2d4RGK.service loaded active exited    Networking for netctl profile wlp0s29u1u1-BTHub3-4RGK

As you can see I have changed USB ports, but I did update the symlink. I was trialing incase one port was slower than the others. Maybe there is somewhere else I should have also updated it?

wifi-menu is working, but would be good to have it connecting at boot.

Thanks

Last edited by Belgi (2013-06-27 19:14:41)

WonderWoofy

Member

From: Los Gatos, CA

Registered: 2012-05-19

Posts: 8,414

Re: WiFI extremely slow in Arch

If you are using a USB WiFi device that can potentially change names with different ports, it would probably make sense to either create a persistent name for that particular piece of hardware, or go back to the old naming scheme if you don't have another wireless card.  The idea of these crazy names is that if you have two wireless cards, two ethernet cards, or even an ethernet card and a broadcom wireless card (which also uses the eth* namespace), you will never know which will be 0 and which will be 1.  But if you tell the system what to name them, then you can at least have your netctl service run on a given interface name and know what it is going to be.

Having said all that, you should also be aware that other network management solutions deal with changing interface names much better then netctl.  Netctl needs the interface name to be specified in the profile, so if it changes you are kind sh*t out of luck until you make the manual changes necessary. 

To see if you have multiple network management services trying to handle things, run "systemctl --type=service" to see all the services you have going.  If you see more than one that should be handling the network (for example, if you enabled dhcpcd@.service during setup) then you need to figure out which single management solution is going to best fit your use case and go with that one only.  Most commonly, people still ahve dhcpcd.service or dhcpcd@<interface>.service around.  But it is also not uncommon to see people with netctl-ifplugd@<interface>.service running along with netctl-auto@<interface> at the same time, which will also cause issues.