WI-FI very slow on Arch after new WIFI hub installed.

glyons · 2019-06-18 19:59:52

Hi

I have been dual booting with Arch GNU plus linux/windows 10 for a couple of years now with zero WIFI issues.
Then I got new WIFI hub/router CH7465LG.
Windows 10 is still perfect after reconnect and password.
all other devices in household are perfect Including various linux(non-arch) computers.

but on arch the WIFI has slowed to a crawl I am measuring speeds in the 100 kps range instead of 50Mbps.
If I get a measurement at all.
I can see the device and connect to it. and reporting tools like wavemon are reporting high bit rates and strong signal strength.

Output of $iw wlp2s0b1 info

Interface wlp2s0b1
	ifindex 3
	wdev 0x1
	addr 84:4b:f5:b4:9f:d3
	ssid VM0840441
	type managed
	wiphy 0
	channel 1 (2412 MHz), width: 20 MHz, center1: 2412 MHz
       txpower 19.00 dBm

output of lspci -vnn -d 14e4:

02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless Network Adapter [14e4:4727] (rev 01)
	Subsystem: Dell Inspiron M5010 / XPS 8300 [1028:0010]
	Flags: bus master, fast devsel, latency 0, IRQ 19
	Memory at f7200000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: bcma-pci-bridge
	Kernel modules: bcma

Any idea why this happened and how I can resolve it?

Regards

ewaller · 2019-06-18 20:39:35

What are the output of iw phy and of iw dev wlp2s0b1 info

And, as a sanity check, systemctl list-unit-files --state enabled

glyons · 2019-06-18 21:12:08

iw dev wlp2s0b1 info

Interface wlp2s0b1
	ifindex 3
	wdev 0x100000001
	addr 84:4b:f5:b4:9f:d3
	ssid VM0840441
	type managed
	wiphy 1
	channel 1 (2412 MHz), width: 20 MHz, center1: 2412 MHz
	txpower 19.00 dBm

output $iw phy

Wiphy phy1
	max # scan SSIDs: 4
	max scan IEs length: 2257 bytes
	max # sched scan SSIDs: 0
	max # match sets: 0
	max # scan plans: 1
	max scan plan interval: -1
	max scan plan iterations: 0
	Retry short limit: 7
	Retry long limit: 4
	Coverage class: 0 (up to 0m)
	Device supports RSN-IBSS.
	Supported Ciphers:
		* WEP40 (00-0f-ac:1)
		* WEP104 (00-0f-ac:5)
		* TKIP (00-0f-ac:2)
		* CCMP-128 (00-0f-ac:4)
		* CCMP-256 (00-0f-ac:10)
		* GCMP-128 (00-0f-ac:8)
		* GCMP-256 (00-0f-ac:9)
	Available Antennas: TX 0 RX 0
	Supported interface modes:
		 * IBSS
		 * managed
		 * AP
		 * AP/VLAN
		 * monitor
	Band 1:
		Capabilities: 0x7c
			HT20
			SM Power Save disabled
			RX Greenfield
			RX HT20 SGI
			RX HT40 SGI
			No RX STBC
			Max AMSDU length: 3839 bytes
			No DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: 8 usec (0x06)
		HT Max RX data rate: 72 Mbps
		HT TX/RX MCS rate indexes supported: 0-7
		Bitrates (non-HT):
			* 1.0 Mbps
			* 2.0 Mbps (short preamble supported)
			* 5.5 Mbps (short preamble supported)
			* 11.0 Mbps (short preamble supported)
			* 6.0 Mbps
			* 9.0 Mbps
			* 12.0 Mbps
			* 18.0 Mbps
			* 24.0 Mbps
			* 36.0 Mbps
			* 48.0 Mbps
			* 54.0 Mbps
		Frequencies:
			* 2412 MHz [1] (19.0 dBm)
			* 2417 MHz [2] (19.0 dBm)
			* 2422 MHz [3] (19.0 dBm)
			* 2427 MHz [4] (19.0 dBm)
			* 2432 MHz [5] (19.0 dBm)
			* 2437 MHz [6] (19.0 dBm)
			* 2442 MHz [7] (19.0 dBm)
			* 2447 MHz [8] (19.0 dBm)
			* 2452 MHz [9] (19.0 dBm)
			* 2457 MHz [10] (19.0 dBm)
			* 2462 MHz [11] (19.0 dBm)
			* 2467 MHz [12] (19.0 dBm) (no IR)
			* 2472 MHz [13] (19.0 dBm) (no IR)
			* 2484 MHz [14] (disabled)
	Supported commands:
		 * new_interface
		 * set_interface
		 * new_key
		 * start_ap
		 * new_station
		 * new_mpath
		 * set_mesh_config
		 * set_bss
		 * authenticate
		 * associate
		 * deauthenticate
		 * disassociate
		 * join_ibss
		 * join_mesh
		 * set_tx_bitrate_mask
		 * frame
		 * frame_wait_cancel
		 * set_wiphy_netns
		 * set_channel
		 * set_wds_peer
		 * probe_client
		 * set_noack_map
		 * register_beacons
		 * start_p2p_device
		 * set_mcast_rate
		 * connect
		 * disconnect
		 * set_qos_map
		 * set_multicast_to_unicast
	Supported TX frame types:
		 * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
	Supported RX frame types:
		 * IBSS: 0x40 0xb0 0xc0 0xd0
		 * managed: 0x40 0xd0
		 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		 * mesh point: 0xb0 0xc0 0xd0
		 * P2P-client: 0x40 0xd0
		 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		 * P2P-device: 0x40 0xd0
	software interface modes (can always be added):
		 * AP/VLAN
		 * monitor
	interface combinations are not supported
	HT Capability overrides:
		 * MCS: ff ff ff ff ff ff ff ff ff ff
		 * maximum A-MSDU length
		 * supported channel width
		 * short GI for 40 MHz
		 * max A-MPDU length exponent
		 * min MPDU start spacing
	Device supports TX status socket option.
	Device supports HT-IBSS.
	Device supports SAE with AUTHENTICATE command
	Device supports low priority scan.
	Device supports scan flush.
	Device supports AP scan.
	Device supports per-vif TX power setting
	Driver supports full state transitions for AP/GO clients
	Driver supports a userspace MPM
	Device supports configuring vdev MAC-addr on create.
	Supported extended features:
		* [ RRM ]: RRM
		* [ FILS_STA ]: STA FILS (Fast Initial Link Setup)
		* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
		* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211

systemctl list-unit-files --state enabled

UNIT FILE                                   STATE  
org.cups.cupsd.path                         enabled
autovt@.service                             enabled
cronie.service                              enabled
dbus-org.freedesktop.NetworkManager.service enabled
dbus-org.freedesktop.nm-dispatcher.service  enabled
getty@.service                              enabled
lm_sensors.service                          enabled
NetworkManager-dispatcher.service           enabled
NetworkManager.service                      enabled
org.cups.cupsd.service                      enabled
systemd-timesyncd.service                   enabled
ufw.service                                 enabled
org.cups.cupsd.socket                       enabled
remote-fs.target                            enabled
fstrim.timer                                enabled

ewaller · 2019-06-18 21:17:06

Sorry, I meant iw dev wlp2s0b1 link not info,

The unit files that are enabled looks just fine.

glyons · 2019-06-18 21:22:58

iw dev wlp2s0b1 link

Connected to 38:43:7d:a7:0d:b0 (on wlp2s0b1)
	SSID: VM0840441
	freq: 2412
	RX: 62418233 bytes (141772 packets)
	TX: 2385493 bytes (23396 packets)
	signal: -35 dBm
	rx bitrate: 48.0 MBit/s
	tx bitrate: 65.0 MBit/s MCS 6 short GI

	bss flags:	short-slot-time
	dtim period:	1
	beacon int:	100

ewaller · 2019-06-18 21:53:38

The link looks reasonable. The 20MHz bandwidth will limit you to 50Mb/s or so. The link says ir is 48 down and 65 up. And your signal strength is very strong (30 dB better than my system). You must be right on top of the router.

Is this a dynamic address, or is it static?
How is the bit rate communicating with other devices on the LAN (as opposed to the Internet)
Any chance there is an address colision?
Do you have any other network interfaces, and are they up?

What are the output of cat /proc/net/wireless and of /proc/net/dev

seth · 2019-06-18 22:21:51

Drop the firewall and check the journal on whether networkmanager goes on a re-connect orgy.
Also consult dmesg on whether bcma/brcmsmac pops up.

You can also try the broadcom-wl and b43-legacy drivers, see https://wiki.archlinux.org/index.php/Broadcom_wireless

glyons · 2019-06-18 23:51:39

ewaller wrote:

The link looks reasonable. The 20MHz bandwidth will limit you to 50Mb/s or so. The link says ir is 48 down and 65 up. And your signal strength is very strong (30 dB better than my system). You must be right on top of the router.
Is this a dynamic address, or is it static?
How is the bit rate communicating with other devices on the LAN (as opposed to the Internet)
Any chance there is an address colision?
Do you have any other network interfaces, and are they up?
What are the output of cat /proc/net/wireless and of /proc/net/dev

The original router is still there as it is a multipurpose device its runs Cable TV as well and phone.
but even with it switched off, problem persists, no other network interfaces and it is dynamic address.

cat/proc/net/wireless high level of discarded packets in misc category
A lot of discarded packets

Inter-| sta-|   Quality        |   Discarded packets               | Missed | WE
 face | tus | link level noise |  nwid  crypt   frag  retry   misc | beacon | 22
wlp2s0b1: 0000   70.  -36.  -256        0      0      0      0  10107        0

/proc/net/dev

Inter-|   Receive                                                |  Transmit
 face |bytes    packets errs drop fifo frame compressed multicast|bytes    packets errs drop fifo colls carrier compressed
wlp2s0b1: 62804753   46885    0    0    0     0          0         0  3367309   35087    0    0    0     0       0          0
    lo:   13448     167    0    0    0     0          0         0    13448     167    0    0    0     0       0          0
  eno1:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0

Just ran journalctl -p 3 -xb , found this, that was not there before router change.

Jun 19 00:08:31 570Dell kernel: b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 10, Type 8 (LCN), Revision 1)

Last edited by glyons (2019-06-19 00:01:22)

seth · 2019-06-19 06:07:02

b43 doesn't support the BCM4313 so that message is irrelevant (at least as a single occurrence)

Check the whole "sudo journalctl -b" (if you intend to post it, please omit the "-x")

glyons · 2019-06-24 13:00:19

seth wrote:

Drop the firewall and check the journal on whether networkmanager goes on a re-connect orgy.
Also consult dmesg on whether bcma/brcmsmac pops up.
You can also try the broadcom-wl and b43-legacy drivers, see https://wiki.archlinux.org/index.php/Broadcom_wireless

Thanks for replies

I am still down here , I have been busy and only now have time to look at this computer again.

dmesg | grep wlp2s0b

    5.512474] brcmsmac bcma0:1 wlp2s0b1: renamed from wlan0
[   10.304731] wlp2s0b1: authenticate with 38:43:7d:a7:0d:b0
[   10.307643] wlp2s0b1: send auth to 38:43:7d:a7:0d:b0 (try 1/3)
[   10.311541] wlp2s0b1: authenticated
[   10.314056] wlp2s0b1: associating with AP with corrupt probe response
[   10.317511] wlp2s0b1: associate with 38:43:7d:a7:0d:b0 (try 1/3)
[   10.328864] wlp2s0b1: RX AssocResp from 38:43:7d:a7:0d:b0 (capab=0x1411 status=0 aid=1)
[   10.331642] wlp2s0b1: associated
[   10.406438] wlp2s0b1: Limiting TX power to 20 (20 - 0) dBm as advertised by 38:43:7d:a7:0d:b0
[   10.491119] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0b1: link becomes ready
[   82.594958] wlp2s0b1: deauthenticating from 38:43:7d:a7:0d:b0 by local choice (Reason: 3=DEAUTH_LEAVING)
[   82.594976] audit: type=1111 audit(1561241280.974:50): pid=566 uid=0 auid=4294967295 ses=4294967295 msg='op=device-disconnect interface="wlp2s0b1" ifindex=3 pid=715 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
[  108.612789] wlp2s0b1: authenticate with 38:43:7d:a7:0d:b0
[  108.612867] wlp2s0b1: send auth to 38:43:7d:a7:0d:b0 (try 1/3)
[  108.628475] wlp2s0b1: authenticated
[  108.628573] wlp2s0b1: associating with AP with corrupt probe response
[  108.630582] wlp2s0b1: associate with 38:43:7d:a7:0d:b0 (try 1/3)
[  108.636700] wlp2s0b1: RX AssocResp from 38:43:7d:a7:0d:b0 (capab=0x1411 status=0 aid=1)
[  108.637235] wlp2s0b1: associated
[  108.710988] wlp2s0b1: Limiting TX power to 20 (20 - 0) dBm as advertised by 38:43:7d:a7:0d:b0
[  108.874300] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0b1: link becomes ready

journalctl -f

Jun 22 23:41:01 570Dell kernel: wlp2s0b1: Limiting TX power to 20 (20 - 0) dBm as advertised by 38:43:7d:a7:0d:b0
Jun 22 23:41:01 570Dell kernel: brcmsmac bcma0:1: wl0: brcms_c_d11hdrs_mac80211: AC_VO txop exceeded phylen 159/256 dur 1778/1504
Jun 22 23:41:01 570Dell NetworkManager[566]: <info>  [1561243261.9887] device (wlp2s0b1): supplicant interface state: associated -> 4-way handshake
Jun 22 23:41:02 570Dell wpa_supplicant[607]: wlp2s0b1: WPA: Key negotiation completed with 38:43:7d:a7:0d:b0 [PTK=CCMP GTK=TKIP]
Jun 22 23:41:02 570Dell wpa_supplicant[607]: wlp2s0b1: CTRL-EVENT-CONNECTED - Connection to 38:43:7d:a7:0d:b0 completed [id=0 id_str=]
Jun 22 23:41:02 570Dell kernel: brcmsmac bcma0:1: wl0: brcms_c_d11hdrs_mac80211: AC_VO txop exceeded phylen 137/256 dur 1602/1504
Jun 22 23:41:02 570Dell NetworkManager[566]: <info>  [1561243262.0940] device (wlp2s0b1): supplicant interface state: 4-way handshake -> completed
Jun 22 23:41:02 570Dell wpa_supplicant[607]: wlp2s0b1: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-37 noise=9999 txrate=6500
Jun 22 23:41:05 570Dell wpa_supplicant[607]: wlp2s0b1: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD

un 22 23:58:10 570Dell systemd[1]: Starting Network Manager Script Dispatcher Service...
Jun 22 23:58:10 570Dell dbus-daemon[565]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jun 22 23:58:10 570Dell systemd[1]: Started Network Manager Script Dispatcher Service.
Jun 22 23:58:10 570Dell audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 22 23:58:10 570Dell nm-dispatcher[13812]: req:1 'connectivity-change': new request (0 scripts)
Jun 22 23:58:10 570Dell nm-dispatcher[13812]: req:1 'connectivity-change': completed: no scripts
Jun 22 23:58:10 570Dell kernel: audit: type=1130 audit(1561244290.229:77): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 22 23:58:20 570Dell systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Jun 22 23:58:20 570Dell kernel: audit: type=1131 audit(1561244300.239:78): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 22 23:58:20 570Dell audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 22 23:58:24 570Dell wpa_supplicant[607]: wlp2s0b1: CTRL-EVENT-BEACON-LOSS
Jun 22 23:58:29 570Dell kernel: brcmsmac bcma0:1: wl0: 2 rx fifo 0 overflows!
Jun 22 23:59:34 570Dell wpa_supplicant[607]: wlp2s0b1: CTRL-EVENT-BEACON-LOSS

journalctl -p 3 -b

Jun 24 12:37:39 570Dell kernel: DMAR: Failed to find handle for ACPI object \_SB.PCI0.I2C0
Jun 24 12:37:39 570Dell kernel: DMAR: Failed to find handle for ACPI object \_SB.PCI0.I2C1
Jun 24 12:37:39 570Dell kernel: DMAR: Failed to find handle for ACPI object \_SB.PCI0.UA01
Jun 24 12:37:39 570Dell kernel: DMAR: Failed to find handle for ACPI object \_SB.PCI0.SDHC
Jun 24 12:37:40 570Dell kernel: mei_me 0000:00:16.0: less data available than length=00000008.
Jun 24 12:37:41 570Dell kernel: MXM: GUID detected in BIOS
Jun 24 12:37:41 570Dell kernel: b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 10, Type 8 (LCN), Revision 1)
Jun 24 12:37:43 570Dell kernel: nouveau 0000:03:00.0: DRM: Pointer to TMDS table invalid
Jun 24 12:37:45 570Dell kernel: brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement)
Jun 24 12:37:45 570Dell kernel: brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement)
Jun 24 12:37:45 570Dell kernel: brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement)
Jun 24 12:37:45 570Dell kernel: brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement)
Jun 24 12:37:46 570Dell kernel: brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement)
Jun 24 12:37:46 570Dell kernel: brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement)
Jun 24 12:37:47 570Dell kernel: brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated
Jun 24 12:37:47 570Dell kernel: brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement)
Jun 24 12:37:48 570Dell kernel: brcmsmac bcma0:1: brcms_ops_bss_info_changed: arp filtering: 1 addresses (implement)
Jun 24 12:37:58 570Dell kernel: nouveau 0000:03:00.0: bus: MMIO write of 0000001f FAULT at 6013d4 [ IBUS ]
Jun 24 12:38:16 570Dell kernel: brcmsmac bcma0:1: wl0: 3 rx fifo 0 overflows!
Jun 24 12:38:21 570Dell kernel: sd 3:0:0:0: [sdc] No Caching mode page found
Jun 24 12:38:21 570Dell kernel: sd 3:0:0:0: [sdc] Assuming drive cache: write through
Jun 24 12:41:58 570Dell kernel: brcmsmac bcma0:1: brcms_ops_bss_info_changed: arp filtering: 0 addresses (implement)
Jun 24 12:41:58 570Dell kernel: brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: disassociated
Jun 24 12:41:58 570Dell kernel: brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement)
Jun 24 12:41:59 570Dell kernel: brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement)
Jun 24 12:41:59 570Dell kernel: brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement)

I tried to install "broadcom-wl" but after re-boot , the wifi interface disappeared from network manager and no option to reconnect to it.
So then I unistalled it and tried the b43-firmware and in turn the b43-firmware-legacy but cannot see any difference.
Not sure what the procedure is for changing drivers like this.

Last edited by glyons (2019-06-24 13:00:44)

glyons · 2019-06-24 22:46:10

I put in a LIve CD into same computer that has many distros on it and with KNoppix and Mint I am able to get much faster use-able wifi.

Mint uses network manger and same driver and kernel module as Arch.

Kernel driver in use: bcma-pci-bridge
Kernel modules: bcma

This suggests to my mind the brcmsmac driver is not the problem,

Should I continue to try and get "broadcom-wl" working or do you think the problem/solution lies elsewhere?

Last edited by glyons (2019-06-24 22:47:00)

seth · 2019-06-25 03:20:52

You could try the lts kernel and there're also some logged issues (corrupt AP responses, beacon losses, disconnects by local choice) - I'd suggest to post a complete journal to show what exactly is going on on that system and in what time/order.
You can "sudo journalcl -b | curl -F 'f:1=<-' ix.io" to upload a complete journal.

glyons · 2019-06-25 13:51:15

Hi

I tried the Lts kernal , no difference

here's the log , I had to connect to the Ethernet wired connection to upload it at end as wifi is so slow.
So there is some chatter about that connection at end of log, as i plugged it in.

http://ix.io/1MKB

Last edited by glyons (2019-06-25 13:52:28)

seth · 2019-06-25 14:52:23

Does the PREV_AUTH_NOT_VALID happen more often in a longer session?
What if you stop networkmanager and connect w/ wifi-menu?

Arch Linux

#1 2019-06-18 19:59:52

WI-FI very slow on Arch after new WIFI hub installed.

#2 2019-06-18 20:39:35

Re: WI-FI very slow on Arch after new WIFI hub installed.

#3 2019-06-18 21:12:08

Re: WI-FI very slow on Arch after new WIFI hub installed.

#4 2019-06-18 21:17:06

Re: WI-FI very slow on Arch after new WIFI hub installed.

#5 2019-06-18 21:22:58

Re: WI-FI very slow on Arch after new WIFI hub installed.

#6 2019-06-18 21:53:38

Re: WI-FI very slow on Arch after new WIFI hub installed.

#7 2019-06-18 22:21:51

Re: WI-FI very slow on Arch after new WIFI hub installed.

#8 2019-06-18 23:51:39

Re: WI-FI very slow on Arch after new WIFI hub installed.

#9 2019-06-19 06:07:02

Re: WI-FI very slow on Arch after new WIFI hub installed.

#10 2019-06-24 13:00:19

Re: WI-FI very slow on Arch after new WIFI hub installed.

#11 2019-06-24 22:46:10

Re: WI-FI very slow on Arch after new WIFI hub installed.

#12 2019-06-25 03:20:52

Re: WI-FI very slow on Arch after new WIFI hub installed.

#13 2019-06-25 13:51:15

Re: WI-FI very slow on Arch after new WIFI hub installed.

#14 2019-06-25 14:52:23

Re: WI-FI very slow on Arch after new WIFI hub installed.

Board footer