Network on the RPi3 is terribly slow

Created by: PureTryOut

@drebrez you have made the original raspberry-pi package, and @yangxuan8282 you have added wifi and Bluetooth functionality. Can any of you reproduce this issue?

By * postmarketOS Bot on 2018-06-09T18:41:49

@PureTryOut the PR I created was related to RPi 3B+ wifi, have nothing to do with RPi 3B wifi I remember used to got same issues on 3B, many packet loss when use wifi connection. But my current pmos installation not have this issues, the kernel is from this PR https://github.com/postmarketOS/pmbootstrap/pull/1543

ping 192.168.2.106
PING 192.168.2.106 (192.168.2.106) 56(84) bytes of data.
64 bytes from 192.168.2.106: icmp_seq=1 ttl=64 time=7.40 ms
64 bytes from 192.168.2.106: icmp_seq=2 ttl=64 time=6.00 ms
64 bytes from 192.168.2.106: icmp_seq=3 ttl=64 time=5.69 ms
64 bytes from 192.168.2.106: icmp_seq=4 ttl=64 time=6.47 ms
64 bytes from 192.168.2.106: icmp_seq=5 ttl=64 time=7.44 ms
64 bytes from 192.168.2.106: icmp_seq=6 ttl=64 time=8.45 ms
64 bytes from 192.168.2.106: icmp_seq=7 ttl=64 time=7.49 ms
64 bytes from 192.168.2.106: icmp_seq=8 ttl=64 time=5.95 ms
64 bytes from 192.168.2.106: icmp_seq=9 ttl=64 time=6.18 ms
64 bytes from 192.168.2.106: icmp_seq=10 ttl=64 time=21.6 ms
^C
--- 192.168.2.106 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9007ms
rtt min/avg/max/mdev = 5.696/8.274/21.631/4.531 ms

the last one take 21.6ms, and I did more test, sometimes it take long time, but at least no packet loss

the info about RPi 3b wifi as far as I know is:

the firmware we need:

https://github.com/RPi-Distro/firmware-nonfree/blob/master/brcm/brcmfmac43430-sdio.bin

https://github.com/RPi-Distro/firmware-nonfree/blob/master/brcm/brcmfmac43430-sdio.txt

you can find related info from dmesg with:

dmesg | grep brcmfmac

on kernel side (this is for downstream 4.14.y, because I only know this one), after read some issues ( https://github.com/raspberrypi/linux/issues/2124 ), quote from this issues:

The WiFi interface is connected via SDIO on mmc1 using GPIOs 34-39

to make mmc1 appears (so that wifi will works) need to enable mmc drivers

and also from that issues, there are three mmc drivers for RPi exist in downstream kernel:

CONFIG_MMC_BCM2835 (upstream)

CONFIG_MMC_SDHCI_IPROC (upstream)

CONFIG_MMC_BCM2835_MMC (downstream)

we should use the downstream one, and disable the upstream one ( the CONFIG_MMC_BCM2835_MMC I guess was renamed from 4.9.y CONFIG_MMC_BCM2835 )

and we also need enable brcmfmac related options in kernel config:

CONFIG_BRCMFMAC=m
CONFIG_BRCMFMAC_PROTO_BCDC=y
CONFIG_BRCMFMAC_SDIO=y
CONFIG_BRCMFMAC_USB=y

maybe you can re-download the latest firmware ( should put them in /lib/firmware/brcm/ ), and check the dmesg output, if that not work, maybe you can try the latest 4.14 kernel from https://github.com/postmarketOS/pmbootstrap/pull/1543

By yangxuan8282 on 2018-06-10T02:34:27

Created by: PureTryOut

Well, re-downloading the latest firmware from the links you posted and putting them in the proper directory seems to have caused the RPi to not boot any more. Either that, or wlan was down entirely. I've also tried the kernel from your PR, but that didn't resolve anything either.

By * postmarketOS Bot on 2018-06-10T13:35:06

@PureTryOut well, I want know if you download the link above or raw file? we should use raw one, because that is real file instead of html

would you mind check the md5sum of the firmware, here is my output:

md5sum /lib/firmware/brcm/brcmfmac43430*
ba679a85c1dc76e9775603af45440bc0  /lib/firmware/brcm/brcmfmac43430-sdio.bin
9a88b55134d9f8f3ad2331b93f4b7b79  /lib/firmware/brcm/brcmfmac43430-sdio.txt
8c97a1fb04a8c2c0ca0a8ed0814f38ae  /lib/firmware/brcm/brcmfmac43430a0-sdio.bin

you should have first two file with same md5sum, because those file latest update was 3 month ago

here is the raw links:

https://github.com/RPi-Distro/firmware-nonfree/raw/master/brcm/brcmfmac43430-sdio.bin

https://github.com/RPi-Distro/firmware-nonfree/raw/master/brcm/brcmfmac43430-sdio.txt

By yangxuan8282 on 2018-06-10T14:39:19

@PureTryOut sry but I don't own a RPI3 so I cannot test the wifi. I only have a RPI2

By Daniele Debernardi on 2018-06-11T08:18:58

@PureTryOut hi, I don't know if you have solve the wifi problems, but I'm pretty sure the firmware is the correct one, it's from raspberry pi official, and most distros use it, like raspbian and archlinux arm, the upstream linux-firmware-brcm( the subpackage of linux-firmware, which is also the dependency of linux-rpi ) also use it as sources

but in case you still got issues, here is my local rpi2 pmos image build by pmbootstrap, the kernel is 4.14.44

https://send.firefox.com/download/5ab7466713/#exFi26Ex2Zsa0QlccrQk3g

you can flash it to sdcard with dd or Etcher

By yangxuan8282 on 2018-06-11T12:58:15

Created by: PureTryOut

It seems my downloaded firmware was corrupt. Connected it via ethernet, placed the firmware in correct place, and it connected again. However, still insane packet loss. It already runs a kernel compiled from your PR, so that didn't really help either...

I must say, ethernet isn't the greatest connection either, although the delays are way less. Maybe it's a general networking issue? I'd really like someone else with a RPi3 to confirm this issue.

By * postmarketOS Bot on 2018-06-12T17:09:33

Created by: eMPee584

@PureTryOut : maybe your pi has some electronic troubles.. signal noise or so for whatever reason?

By * postmarketOS Bot on 2018-06-12T17:25:06

Created by: PureTryOut

Well it doesn't happen on Raspbian, so it seems postmarketOS specific.

By * postmarketOS Bot on 2018-06-12T17:29:22

@PureTryOut maybe worth to try the latest upstream linux-rpi 4.14.49, it basically use raspbian kernel config file

By yangxuan8282 on 2018-06-14T09:10:59

Created by: PureTryOut

Didn't resolve anything sadly, it's still insanely slow. I can now confirm it's also really bad on ethernet, just a little bit less. So I guess it has something to do with the entire network stack rather than the specific interfaces.

By * postmarketOS Bot on 2018-06-14T17:27:41

Created by: ollieparanoid

@PureTryOut: maybe someone on #alpine-devel has an idea, they were discussing the raspberry pi today. @yangxuan8282: consider joining there as well for better raspberry pi related coordination with Alpine.

By * postmarketOS Bot on 2018-06-14T20:33:02

Created by: montvid

I have a badly working wifi in asus flo too. Either it is the drivers fault or it is a bad wpa supplicant config. udhcpd does not get an ip as dhcpcd starts with networkmanager....

PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: seq=2 ttl=42 time=1021.732 ms 64 bytes from 8.8.8.8: seq=3 ttl=42 time=635.403 ms 64 bytes from 8.8.8.8: seq=4 ttl=42 time=249.332 ms 64 bytes from 8.8.8.8: seq=5 ttl=42 time=1092.097 ms 64 bytes from 8.8.8.8: seq=6 ttl=42 time=704.731 ms 64 bytes from 8.8.8.8: seq=7 ttl=42 time=318.946 ms 64 bytes from 8.8.8.8: seq=8 ttl=42 time=751.767 ms 64 bytes from 8.8.8.8: seq=9 ttl=42 time=365.776 ms 64 bytes from 8.8.8.8: seq=10 ttl=42 time=1208.758 ms 64 bytes from 8.8.8.8: seq=11 ttl=42 time=208.455 ms ^C --- 8.8.8.8 ping statistics --- 12 packets transmitted, 10 packets received, 16% packet loss round-trip min/avg/max = 208.455/655.699/1208.758 ms

By * postmarketOS Bot on 2018-06-25T20:44:16

Created by: montvid

Cmon' guys are still fixing a wcn36xx driver bug for 2 years 2016-2018 :) Oh I will wait :) i see this a lot https://bugs.96boards.org/show_bug.cgi?id=319 https://patchwork.kernel.org/patch/10338447/

By * postmarketOS Bot on 2018-06-25T20:44:28

after tested on several devices(rpi 3b/3b+, xps13 9343), test include iperf and sftp speed, I think there is serious network issues on alpine (use networkmanager and current config), almost every interfaces on every devices is incredible slow

for example on rpi 3b+, with raspbian use eth0 the sftp speed is about 15MB/s, and alpine it's 6MB/s

on xps13 9343, the 5G wifi is basically broken

By yangxuan8282 on 2018-07-23T03:13:05

mentioned in issue pmbootstrap#1593 (closed)

By Oliver Smith on 2018-07-23T21:34:58

Thank you very much for these valuable data points! I guess the best way to go from here is comparing the NetworkManager config, and if that does not help, comparing the version numbers of NetworkManager, the kernel etc. and narrow down the cause that way.

By Oliver Smith on 2018-07-23T22:06:33

added pmbootstrap~~6902358 pmbootstrap~~6902372 labels

By Oliver Smith on 2018-07-23T22:06:54

mentioned in commit pmbootstrap@16612eaa

By Oliver Smith on 2018-08-04T11:07:34

moved from pmbootstrap#1547 (closed)

By Bart Ribbers on 2018-09-17T21:50:55

I'm currently testing pmOS on a rpi3b again. This issue seems to be caused by networkmanager and IPv6. On my device the log gets flooded by nm messages, nm seems to reconnect constantly:

Sep 27 13:01:35 rpi daemon.info NetworkManager[1053]: <info>  [1538049695.9884] dhcp6 (eth0): activation: beginning transaction (timeout in 45 seconds)
Sep 27 13:01:35 rpi daemon.warn NetworkManager[1053]: <warn>  [1538049695.9885] dhcp6 (eth0): the dhcpcd backend does not support IPv6
Sep 27 13:01:35 rpi daemon.info NetworkManager[1053]: <info>  [1538049695.9886] device (eth0): state change: activated -> failed (reason 'dhcp-start-failed', sys-iface-state: 'managed')
Sep 27 13:01:35 rpi daemon.info NetworkManager[1053]: <info>  [1538049695.9903] manager: NetworkManager state is now DISCONNECTED
Sep 27 13:01:36 rpi daemon.warn NetworkManager[1053]: <warn>  [1538049696.0063] device (eth0): Activation: failed for connection 'Wired connection 1'

Forum threads for other distros suggest to set dhcp=internal in /etc/NetworkManager/NetworkManager.conf, but that didn't work for me.

Only after setting ipv6.disable=1 in /boot/cmdline.txt my connection stays perfectly stable.

By Sebastian Fleer on 2018-09-27T13:12:23

I just realized that /etc/NetworkManager/conf.d/postmarketos.conf also sets dhcp=dhcpd, which seems to overwrite the setting of NetworkManager.conf. So I left NetworkManager.conf empty, re-enabled IPv6 and tested dhcp=internal and dhcp=dhclient (after installing it) in postmarketos.conf. Both seem to work fine, so this seems to be an issue with dhcpd. I don't know why, because it obviously supports DHCPv6.

Maybe others can test to set dhcp=internal in /etc/NetworkManager/conf.d/postmarketos.conf and see if the networking problems get better that way. If so, I suggest to make it the default, at least on Raspberry Pis.

By Sebastian Fleer on 2018-09-28T15:45:18

Upstream issue: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/5

On old bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=707464

By Sebastian Fleer on 2018-10-01T08:10:06

mentioned in merge request !31 (merged)

By Sebastian Fleer on 2018-10-01T08:30:41

Benchmarks on Rpi3 (100 Mbit/s):

with dhcp=dhcpd

rpi:~$ iperf3 -c 192.168.1.183
Connecting to host 192.168.1.183, port 5201
[  5] local 192.168.1.170 port 52352 connected to 192.168.1.183 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   308 KBytes  2.52 Mbits/sec    0   1.41 KBytes       
[  5]   1.00-2.00   sec  4.60 MBytes  38.6 Mbits/sec    1    232 KBytes       
[  5]   2.00-3.00   sec  1.10 MBytes  9.18 Mbits/sec    0   1.41 KBytes       
[  5]   3.00-4.00   sec  4.29 MBytes  36.0 Mbits/sec    2    214 KBytes       
[  5]   4.00-5.00   sec  10.1 MBytes  85.1 Mbits/sec    0    246 KBytes       
[  5]   5.00-6.00   sec  7.23 MBytes  60.7 Mbits/sec    3    154 KBytes       
[  5]   6.00-7.00   sec  9.70 MBytes  81.4 Mbits/sec    0    198 KBytes       
[  5]   7.00-8.00   sec  2.33 MBytes  19.5 Mbits/sec    0   1.41 KBytes       
[  5]   8.00-9.00   sec  2.78 MBytes  23.3 Mbits/sec    3   99.0 KBytes       
[  5]   9.00-10.00  sec  9.17 MBytes  76.9 Mbits/sec    0    153 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  51.6 MBytes  43.3 Mbits/sec    9             sender
[  5]   0.00-10.00  sec  51.2 MBytes  42.9 Mbits/sec                  receiver

iperf Done.

with dhcp=internal

rpi:~$ iperf3 -c 192.168.1.183
Connecting to host 192.168.1.183, port 5201
[  5] local 192.168.1.171 port 51394 connected to 192.168.1.183 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  10.8 MBytes  90.6 Mbits/sec    0    467 KBytes       
[  5]   1.00-2.00   sec  10.4 MBytes  87.3 Mbits/sec   17    400 KBytes       
[  5]   2.00-3.00   sec  10.6 MBytes  88.9 Mbits/sec    0    458 KBytes       
[  5]   3.00-4.00   sec  10.4 MBytes  86.9 Mbits/sec    0    498 KBytes       
[  5]   4.00-5.00   sec  10.4 MBytes  86.9 Mbits/sec    8    378 KBytes       
[  5]   5.00-6.00   sec  10.1 MBytes  85.1 Mbits/sec    0    402 KBytes       
[  5]   6.00-7.00   sec  10.7 MBytes  89.7 Mbits/sec    0    416 KBytes       
[  5]   7.00-8.00   sec  10.8 MBytes  90.2 Mbits/sec    0    423 KBytes       
[  5]   8.00-9.00   sec  10.4 MBytes  87.6 Mbits/sec    0    424 KBytes       
[  5]   9.00-10.00  sec  9.97 MBytes  83.6 Mbits/sec    0    424 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec   105 MBytes  87.7 Mbits/sec   25             sender
[  5]   0.00-10.00  sec   104 MBytes  87.3 Mbits/sec                  receiver

iperf Done.

By Sebastian Fleer on 2018-10-01T09:01:36

closed via merge request !31 (merged)

By Oliver Smith on 2018-10-02T06:00:44

mentioned in commit 24bd1631

By Sebastian Fleer on 2018-10-05T15:51:13

mentioned in commit b7af4cd9

By Sebastian Fleer on 2018-10-29T09:09:21

mentioned in commit e7f828b0

By Sebastian Fleer on 2018-11-27T07:32:58

mentioned in merge request !2212 (merged)

By Pablo Correa Gomez on 2021-07-18T19:01:10

mentioned in issue #2198 (closed)

By Daniel Fancsali on 2023-12-13T20:25:15

Network on the RPi3 is terribly slow

Child items ...

Activity