truthadjustr
Posts: 2
Joined: Sun Apr 24, 2016 9:15 am
Contact: Website

Re: RPi 3 - Very poor wifi performance

Sun Apr 24, 2016 9:53 am

I have the same problem with my wlan0 ping latency. During this problem, I have:
Linux raspberrypi 4.1.18-v7+ #846 SMP Thu Feb 25 14:22:53 GMT 2016 armv7l GNU/Linux

The `iwconfig wlan0 power off` solved the problem for me for that kernel.

Then next, I tried `BRANCH=next rpi-update` and I rebooted. I now have:

Linux raspberrypi 4.4.6-v7+ #871 SMP Mon Apr 4 19:59:50 BST 2016 armv7l GNU/Linux

My WIFI wlan0 is ok now. And I no longer needed to call the `iwconfig wlan0 power off` command.

james942
Posts: 3
Joined: Sun May 08, 2016 11:43 am

Re: RPi 3 - Very poor wifi performance

Sun May 08, 2016 11:57 am

Hi everyones,
thanks for this talk, so far there is a matter with this integrated chip
ive tried using an other usb wifi key, both as master and client, inverted the roles, also from and to en ethernet network.
Changed the maximum usage of usb key to gain power (1max), upgraded the kernel, stopped the power management on any wlan, changed frequencies...
So far, the only stuff missing is the power supply : im using a 2A ; but an other user in this forum tried with a powerful one without better performance.

The maximum speed with the chip is about 1,2Mo/s up or down.
When input and output are used : it just drop down one stream.
This poor performance is defenitely not related to an other interface or the network or the power supply to me.

The chip by itself or the internal bus should be responsible.
What next? A new driver?

Ill probably try to use two usb keys and see if power is sufficient and shutdown the internal chip, included bluetooth.
Have you ever tried this? On a PI2 maybe?

Plz let us know if anyone get better performance with the internal WIFI chip cause so far, it's almost useless.

Regards,
James

User avatar
VascoFerraz
Posts: 78
Joined: Thu Aug 30, 2012 11:54 am

Re: RPi 3 - Very poor wifi performance

Fri Jun 10, 2016 10:10 pm

james942 wrote: Plz let us know if anyone get better performance with the internal WIFI chip cause so far, it's almost useless.
You're right! So far, the internal wifi chip is useless.
Vasco Ferraz

kodr
Posts: 2
Joined: Thu Jun 23, 2016 6:33 pm

Re: RPi 3 - Very poor wifi performance

Thu Jun 23, 2016 6:39 pm

just bought my rPi3, I wanted to use it as a media center, but I also confirm that it's impossible by wifi.
I have a shared NFS directory, I can play 1080p movies through wired network, I can barely play 480p video through wireless.
I have a netgear R7000 router with tomato.

edit: I was able to fix my problem.
I noticed that the bitrate for my connection was quite low (6Mb/s) by using iwconfig.
I couldn't set it with iw, and 'iwlist wlan0 bitrate' would return my current bitrate, not a list of available ones.

In the end, the problem was how my router was configured. I was using channel 6, which was overcrowded (as well as channel 11), because I live in an apartment.
I changed the channel to 10, where there was only one other router at the time I scanned, and after reconfiguring my rpi, my bitrate went up to 72 Mb/s and I was able to play 1080p video through wifi.

james942
Posts: 3
Joined: Sun May 08, 2016 11:43 am

Re: RPi 3 - Very poor wifi performance

Thu Jun 23, 2016 9:50 pm

I got low performance because the internal wifi and the usbwifikey were too closed.
After adding an usb wire extension and got space betwwen the two wifi, it was much better.
It didnt changed the maximum bandwith of the internal wifi by the way.

Then, i've noticed a performance degradation when power management was off the internal wifi.
In opposition of most messaged and comment read on the internet.

Also, in general, ive apt-get upgrade the pi3 (2016 06), including several soft and brcmfmac, 80211 drivers, rt2800usb.. since then, the brcmfmac seems to be better but the external wifi key has its performance really lower (130ko/s max)... ive really angry.
In addition of a quite similar upgrade on an other pi(2), the power USB management wasnt anymore capable to power the USB drive (boot/config patched w usbmaxcurrent1) i had t install wringpi and use gpio usbp high command to make it circle again.

Has anyone noticed it?
Some working on a double wifi PI hotspot project?

regards,
James

georg3003
Posts: 7
Joined: Tue Jun 28, 2016 3:26 pm

Every 10sec wireless slowdRe: RPi 3 - Very poor wifi perform

Tue Jun 28, 2016 3:31 pm

Hi,

have an Question my ping slows down every 10 seconds does somebody have an idea what is happening and why?



Code: Select all

64 bytes from 192.168.42.1: icmp_seq=3533 ttl=64 time=7.284 ms
64 bytes from 192.168.42.1: icmp_seq=3534 ttl=64 time=1.745 ms
64 bytes from 192.168.42.1: icmp_seq=3535 ttl=64 time=4.717 ms
64 bytes from 192.168.42.1: icmp_seq=3536 ttl=64 time=236.453 ms
64 bytes from 192.168.42.1: icmp_seq=3537 ttl=64 time=91.343 ms
64 bytes from 192.168.42.1: icmp_seq=3538 ttl=64 time=4.767 ms
64 bytes from 192.168.42.1: icmp_seq=3539 ttl=64 time=7.251 ms
64 bytes from 192.168.42.1: icmp_seq=3540 ttl=64 time=5.978 ms
64 bytes from 192.168.42.1: icmp_seq=3541 ttl=64 time=10.041 ms
64 bytes from 192.168.42.1: icmp_seq=3542 ttl=64 time=7.332 ms
64 bytes from 192.168.42.1: icmp_seq=3543 ttl=64 time=7.212 ms
64 bytes from 192.168.42.1: icmp_seq=3544 ttl=64 time=4.632 ms
64 bytes from 192.168.42.1: icmp_seq=3545 ttl=64 time=104.154 ms
64 bytes from 192.168.42.1: icmp_seq=3546 ttl=64 time=77.883 ms
64 bytes from 192.168.42.1: icmp_seq=3547 ttl=64 time=13.599 ms
64 bytes from 192.168.42.1: icmp_seq=3548 ttl=64 time=6.882 ms
64 bytes from 192.168.42.1: icmp_seq=3549 ttl=64 time=7.094 ms
64 bytes from 192.168.42.1: icmp_seq=3550 ttl=64 time=10.233 ms
64 bytes from 192.168.42.1: icmp_seq=3551 ttl=64 time=7.323 ms
64 bytes from 192.168.42.1: icmp_seq=3552 ttl=64 time=6.592 ms
64 bytes from 192.168.42.1: icmp_seq=3553 ttl=64 time=140.169 ms
64 bytes from 192.168.42.1: icmp_seq=3554 ttl=64 time=116.720 ms
64 bytes from 192.168.42.1: icmp_seq=3555 ttl=64 time=95.172 ms
64 bytes from 192.168.42.1: icmp_seq=3556 ttl=64 time=7.450 ms
64 bytes from 192.168.42.1: icmp_seq=3557 ttl=64 time=7.431 ms
64 bytes from 192.168.42.1: icmp_seq=3558 ttl=64 time=7.369 ms
64 bytes from 192.168.42.1: icmp_seq=3559 ttl=64 time=7.231 ms
64 bytes from 192.168.42.1: icmp_seq=3560 ttl=64 time=7.209 ms
64 bytes from 192.168.42.1: icmp_seq=3561 ttl=64 time=7.268 ms
64 bytes from 192.168.42.1: icmp_seq=3562 ttl=64 time=152.408 ms
64 bytes from 192.168.42.1: icmp_seq=3563 ttl=64 time=191.598 ms
64 bytes from 192.168.42.1: icmp_seq=3564 ttl=64 time=160.322 ms
64 bytes from 192.168.42.1: icmp_seq=3565 ttl=64 time=11.119 ms
64 bytes from 192.168.42.1: icmp_seq=3566 ttl=64 time=7.182 ms
64 bytes from 192.168.42.1: icmp_seq=3567 ttl=64 time=7.251 ms
64 bytes from 192.168.42.1: icmp_seq=3568 ttl=64 time=7.266 ms
64 bytes from 192.168.42.1: icmp_seq=3569 ttl=64 time=4.710 ms
64 bytes from 192.168.42.1: icmp_seq=3570 ttl=64 time=4.853 ms
64 bytes from 192.168.42.1: icmp_seq=3571 ttl=64 time=152.411 ms
64 bytes from 192.168.42.1: icmp_seq=3572 ttl=64 time=4.707 ms
64 bytes from 192.168.42.1: icmp_seq=3573 ttl=64 time=114.246 ms
64 bytes from 192.168.42.1: icmp_seq=3574 ttl=64 time=85.374 ms
64 bytes from 192.168.42.1: icmp_seq=3575 ttl=64 time=7.946 ms

georg3003
Posts: 7
Joined: Tue Jun 28, 2016 3:26 pm

Re: RPi 3 - Very poor wifi performance

Fri Jul 01, 2016 12:04 pm

Hello,
Small update on this issue, I remarked that also the normal ping on eth0 is raising in time. Maybe it's the interrupt? It's a new install.
Thanks.

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5145
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: RPi 3 - Very poor wifi performance

Fri Jul 01, 2016 1:34 pm

Im not seeing a slow ping issue from Pi3 over ethernet:

Code: Select all

$ sudo ping server
PING server.pitowers (10.3.14.9) 56(84) bytes of data.
64 bytes from 10.3.14.9: icmp_seq=1 ttl=64 time=0.860 ms
64 bytes from 10.3.14.9: icmp_seq=2 ttl=64 time=0.463 ms
64 bytes from 10.3.14.9: icmp_seq=3 ttl=64 time=0.457 ms
64 bytes from 10.3.14.9: icmp_seq=4 ttl=64 time=0.452 ms
64 bytes from 10.3.14.9: icmp_seq=5 ttl=64 time=0.478 ms
64 bytes from 10.3.14.9: icmp_seq=6 ttl=64 time=0.492 ms
64 bytes from 10.3.14.9: icmp_seq=7 ttl=64 time=0.479 ms
64 bytes from 10.3.14.9: icmp_seq=8 ttl=64 time=0.453 ms
64 bytes from 10.3.14.9: icmp_seq=9 ttl=64 time=0.457 ms
64 bytes from 10.3.14.9: icmp_seq=10 ttl=64 time=0.450 ms
64 bytes from 10.3.14.9: icmp_seq=11 ttl=64 time=0.487 ms
64 bytes from 10.3.14.9: icmp_seq=12 ttl=64 time=0.435 ms
64 bytes from 10.3.14.9: icmp_seq=13 ttl=64 time=0.449 ms
64 bytes from 10.3.14.9: icmp_seq=14 ttl=64 time=0.410 ms
64 bytes from 10.3.14.9: icmp_seq=15 ttl=64 time=0.462 ms
64 bytes from 10.3.14.9: icmp_seq=16 ttl=64 time=0.460 ms
64 bytes from 10.3.14.9: icmp_seq=17 ttl=64 time=0.456 ms
64 bytes from 10.3.14.9: icmp_seq=18 ttl=64 time=0.488 ms
64 bytes from 10.3.14.9: icmp_seq=19 ttl=64 time=0.459 ms
64 bytes from 10.3.14.9: icmp_seq=20 ttl=64 time=0.512 ms
64 bytes from 10.3.14.9: icmp_seq=21 ttl=64 time=0.490 ms
64 bytes from 10.3.14.9: icmp_seq=22 ttl=64 time=0.466 ms
64 bytes from 10.3.14.9: icmp_seq=23 ttl=64 time=0.460 ms
64 bytes from 10.3.14.9: icmp_seq=24 ttl=64 time=0.490 ms
64 bytes from 10.3.14.9: icmp_seq=25 ttl=64 time=0.549 ms
64 bytes from 10.3.14.9: icmp_seq=26 ttl=64 time=0.570 ms
64 bytes from 10.3.14.9: icmp_seq=27 ttl=64 time=0.473 ms
64 bytes from 10.3.14.9: icmp_seq=28 ttl=64 time=0.424 ms
64 bytes from 10.3.14.9: icmp_seq=29 ttl=64 time=0.443 ms
64 bytes from 10.3.14.9: icmp_seq=30 ttl=64 time=0.480 ms
64 bytes from 10.3.14.9: icmp_seq=31 ttl=64 time=0.460 ms
64 bytes from 10.3.14.9: icmp_seq=32 ttl=64 time=0.438 ms
64 bytes from 10.3.14.9: icmp_seq=33 ttl=64 time=0.454 ms
64 bytes from 10.3.14.9: icmp_seq=34 ttl=64 time=0.455 ms
64 bytes from 10.3.14.9: icmp_seq=35 ttl=64 time=0.479 ms
64 bytes from 10.3.14.9: icmp_seq=36 ttl=64 time=0.454 ms
64 bytes from 10.3.14.9: icmp_seq=37 ttl=64 time=0.475 ms
64 bytes from 10.3.14.9: icmp_seq=38 ttl=64 time=0.453 ms
64 bytes from 10.3.14.9: icmp_seq=39 ttl=64 time=0.454 ms
64 bytes from 10.3.14.9: icmp_seq=40 ttl=64 time=0.496 ms
64 bytes from 10.3.14.9: icmp_seq=41 ttl=64 time=0.412 ms
64 bytes from 10.3.14.9: icmp_seq=42 ttl=64 time=0.457 ms
64 bytes from 10.3.14.9: icmp_seq=43 ttl=64 time=0.470 ms
64 bytes from 10.3.14.9: icmp_seq=44 ttl=64 time=0.622 ms
64 bytes from 10.3.14.9: icmp_seq=45 ttl=64 time=0.494 ms
64 bytes from 10.3.14.9: icmp_seq=46 ttl=64 time=0.481 ms
64 bytes from 10.3.14.9: icmp_seq=47 ttl=64 time=0.518 ms
64 bytes from 10.3.14.9: icmp_seq=48 ttl=64 time=0.487 ms
64 bytes from 10.3.14.9: icmp_seq=49 ttl=64 time=0.499 ms
64 bytes from 10.3.14.9: icmp_seq=50 ttl=64 time=0.418 ms
64 bytes from 10.3.14.9: icmp_seq=51 ttl=64 time=0.594 ms
64 bytes from 10.3.14.9: icmp_seq=52 ttl=64 time=0.443 ms
64 bytes from 10.3.14.9: icmp_seq=53 ttl=64 time=0.405 ms
64 bytes from 10.3.14.9: icmp_seq=54 ttl=64 time=0.443 ms
64 bytes from 10.3.14.9: icmp_seq=55 ttl=64 time=0.438 ms
64 bytes from 10.3.14.9: icmp_seq=56 ttl=64 time=0.476 ms
64 bytes from 10.3.14.9: icmp_seq=57 ttl=64 time=0.446 ms
64 bytes from 10.3.14.9: icmp_seq=58 ttl=64 time=0.448 ms
64 bytes from 10.3.14.9: icmp_seq=59 ttl=64 time=0.461 ms
64 bytes from 10.3.14.9: icmp_seq=60 ttl=64 time=0.494 ms
Perhaps it is your router or something else on your network?
Can you test the ping command from another machine on your network?

Enigma01
Posts: 3
Joined: Mon Jul 04, 2016 6:32 pm

Re: RPi 3 - Very poor wifi performance

Sun Jul 10, 2016 9:29 am

Hi there, I'm also having problems with RPi3 integrated WiFi, have any of you tried to use arpspoof with it?

jheizer
Posts: 4
Joined: Wed Jul 18, 2012 5:06 pm

Re: RPi 3 - Very poor wifi performance

Fri Jul 15, 2016 1:54 am

I too have horribly slow wifi. I feel like I tried everything in every thread I've come across and this seems to be one of the most recently active ones. Is there a trick out there that we all are just missing still?

Latest Jessie on 4.4.15-v7+ with power management disabled and everything up to date. pi is sitting 6" away from the AP and the throughput and latency is still horrible. I had used the pi to build a wifi enabled digital picture frame for my wife's birthday. So far it has been pretty unexciting since built it all and wrote the software on ethernet on my desk only to be deployed via wifi. You can just sit there and watch each picture download 56k style.

Code: Select all

[email protected]:~ $ iwconfig
wlan0     IEEE 802.11bgn  ESSID:"dd-wrt"
          Mode:Managed  Frequency:2.437 GHz  Access Point: 28:C6:8E:90:97:0C
          Bit Rate=5.5 Mb/s   Tx-Power=31 dBm
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=70/70  Signal level=-17 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:310  Invalid misc:0   Missed beacon:0

wlan0     Link encap:Ethernet  HWaddr b8:27:eb:f7:c7:9f
          inet addr:10.0.0.184  Bcast:10.0.0.255  Mask:255.255.255.0
          inet6 addr: 2601:246:8201:9dbf:7a37:4048:bde9:a614/64 Scope:Global
          inet6 addr: fe80::c517:5286:2a26:6a7b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:49423 errors:0 dropped:419 overruns:0 frame:0
          TX packets:32295 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:70389950 (67.1 MiB)  TX bytes:5651600 (5.3 MiB)

Ping from a wired machine

PING 10.0.0.184 (10.0.0.184) 56(84) bytes of data.
64 bytes from 10.0.0.184: icmp_seq=1 ttl=64 time=3498 ms
64 bytes from 10.0.0.184: icmp_seq=2 ttl=64 time=2493 ms
64 bytes from 10.0.0.184: icmp_seq=3 ttl=64 time=2038 ms
64 bytes from 10.0.0.184: icmp_seq=4 ttl=64 time=1030 ms
64 bytes from 10.0.0.184: icmp_seq=5 ttl=64 time=91.0 ms
64 bytes from 10.0.0.184: icmp_seq=6 ttl=64 time=674 ms
64 bytes from 10.0.0.184: icmp_seq=7 ttl=64 time=572 ms
64 bytes from 10.0.0.184: icmp_seq=8 ttl=64 time=2591 ms
64 bytes from 10.0.0.184: icmp_seq=9 ttl=64 time=3114 ms
64 bytes from 10.0.0.184: icmp_seq=10 ttl=64 time=2776 ms
64 bytes from 10.0.0.184: icmp_seq=11 ttl=64 time=2635 ms
64 bytes from 10.0.0.184: icmp_seq=12 ttl=64 time=2027 ms
64 bytes from 10.0.0.184: icmp_seq=13 ttl=64 time=2103 ms
64 bytes from 10.0.0.184: icmp_seq=14 ttl=64 time=1739 ms
64 bytes from 10.0.0.184: icmp_seq=15 ttl=64 time=3159 ms
64 bytes from 10.0.0.184: icmp_seq=16 ttl=64 time=4632 ms
64 bytes from 10.0.0.184: icmp_seq=17 ttl=64 time=3732 ms
64 bytes from 10.0.0.184: icmp_seq=18 ttl=64 time=2733 ms
64 bytes from 10.0.0.184: icmp_seq=19 ttl=64 time=2449 ms
64 bytes from 10.0.0.184: icmp_seq=20 ttl=64 time=1689 ms
64 bytes from 10.0.0.184: icmp_seq=21 ttl=64 time=991 ms
64 bytes from 10.0.0.184: icmp_seq=22 ttl=64 time=807 ms
64 bytes from 10.0.0.184: icmp_seq=23 ttl=64 time=760 ms
64 bytes from 10.0.0.184: icmp_seq=24 ttl=64 time=189 ms
64 bytes from 10.0.0.184: icmp_seq=25 ttl=64 time=688 ms
64 bytes from 10.0.0.184: icmp_seq=26 ttl=64 time=302 ms
64 bytes from 10.0.0.184: icmp_seq=27 ttl=64 time=642 ms
64 bytes from 10.0.0.184: icmp_seq=28 ttl=64 time=243 ms
64 bytes from 10.0.0.184: icmp_seq=29 ttl=64 time=895 ms
64 bytes from 10.0.0.184: icmp_seq=30 ttl=64 time=307 ms
^C
--- 10.0.0.184 ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29050ms
rtt min/avg/max/mdev = 91.089/1720.491/4632.566/1213.675 ms, pipe 5

Any tips or things I've missed?

jheizer
Posts: 4
Joined: Wed Jul 18, 2012 5:06 pm

Re: RPi 3 - Very poor wifi performance

Tue Jul 19, 2016 6:53 pm

Well I've finally given up and I rewrote my software to scale down all the images on the server side before sending them to the pi so the amount of bandwidth needed is reduced. I'd still be interested in a fix if anyone ever does figure it out.

jb63
Posts: 116
Joined: Mon May 11, 2015 6:41 pm

Re: RPi 3 - Very poor wifi performance

Tue Jul 19, 2016 8:41 pm

Not sure what the issue is. I have an RPI3 running OSMC via WIFI and no issues ... what am I missing?

MaxK1
Posts: 1047
Joined: Sun Aug 26, 2012 11:34 pm

Re: RPi 3 - Very poor wifi performance

Wed Jul 20, 2016 3:18 pm

Jheiser
Take a look at your bit rate and tx retries. Something is interfering from the looks of it...
You are in a maze of twisty little passages, all alike.
When General Failure and Major Disaster get together, Private Parts usually suffers.

mattgwwalker
Posts: 6
Joined: Thu May 09, 2013 10:54 am

Re: RPi 3 - Very poor wifi performance

Mon Nov 07, 2016 6:50 am

Hi,

I too am frustrated by the Wifi performance of the Raspberry Pi 3 (well, at least the one we have). Connection to the Pi (for example with SSH) will freeze for about 10 seconds every two or three minutes. I've tried many of the suggestions recommended in this thread, but I cannot improve performance. I would like the Pi's Wifi connection to be consistent, but I do not know what else to try.

I have tried turning off power management (sudo iwconfig wlan0 power off). This has no noticeable impact.

I have checked to ensure that the Pi's country configuration matches the router's (NZ).

I have run the Wireless Diagnostics on my Mac while connected to the same Wifi network. It suggested that the channel I was on was crowded. I moved the router from "automatic" to a recommended channel (number 9). The diagnostics tool stopped complaining about the crowded channel. However no performance improvement was noticed.

I have turned off all the other nearby access points I can get to. This had no impact.

I have moved the access point so that it is about three meters from the Raspberry Pi, and within line-of-sight. No improvement.

I ran a ping command for about two hours. Using the ICMP sequence numbers as a timer of one-second intervals, the results were really consistent, for example:
109 seconds up, then
7 seconds down
109 seconds up
9 seconds down
109 seconds up
11 seconds down
167 seconds up (I can't explain this increase)
9 seconds down
168 seconds up
10 seconds down
168 seconds up
9 seconds down
169 seconds up
10 seconds down... and so on

At the same time I ran another ping session to another computer on the same Wifi network. At no point did any of the pings drop. I therefore concluded that it wasn't the computers, nor was it the router, but rather the problem must lie with the Raspberry Pi.


Examples of the ping results:

Code: Select all

64 bytes from 192.168.0.102: icmp_seq=451 ttl=64 time=8.610 ms
64 bytes from 192.168.0.102: icmp_seq=452 ttl=64 time=14.675 ms
64 bytes from 192.168.0.102: icmp_seq=453 ttl=64 time=12.801 ms
64 bytes from 192.168.0.102: icmp_seq=454 ttl=64 time=14.736 ms
64 bytes from 192.168.0.102: icmp_seq=455 ttl=64 time=77.624 ms
Request timeout for icmp_seq 456
Request timeout for icmp_seq 457
Request timeout for icmp_seq 458
Request timeout for icmp_seq 459
Request timeout for icmp_seq 460
Request timeout for icmp_seq 461
Request timeout for icmp_seq 462
Request timeout for icmp_seq 463
Request timeout for icmp_seq 464
Request timeout for icmp_seq 465
Request timeout for icmp_seq 466
Request timeout for icmp_seq 467
64 bytes from 192.168.0.102: icmp_seq=466 ttl=64 time=2014.833 ms
64 bytes from 192.168.0.102: icmp_seq=467 ttl=64 time=1014.643 ms
64 bytes from 192.168.0.102: icmp_seq=468 ttl=64 time=14.019 ms
64 bytes from 192.168.0.102: icmp_seq=469 ttl=64 time=6.460 ms
I have turned off all security for the network in the hope that this might improve things.

Here is the output from iwconfig:

Code: Select all

$ iwconfig
wlan0     IEEE 802.11bgn  ESSID:"Tech Futures Lab - Open Network"  
          Mode:Managed  Frequency:2.452 GHz  Access Point: EC:08:6B:EA:19:54   
          Bit Rate=72.2 Mb/s   Tx-Power=31 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=61/70  Signal level=-49 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

lo        no wireless extensions.

eth0      no wireless extensions.
I updated the Raspberry Pi using rpi-update a few days ago. At the same time I upgraded all the packages.

If anyone has any further suggestions, I'd be all ears. Would a Wifi dongle be an option perhaps?

Thanks in advance,

Matthew

User avatar
RaTTuS
Posts: 10061
Joined: Tue Nov 29, 2011 11:12 am
Location: North West UK

Re: RPi 3 - Very poor wifi performance

Mon Nov 07, 2016 8:32 am

mattgwwalker wrote:Hi,

I too am frustrated by the Wifi performance of the Raspberry Pi 3 (well, at least the one we have). Connection to the Pi (for example with SSH) will freeze for about 10 seconds every two or three minutes. I've tried many of the suggestions recommended in this thread, but I cannot improve performance. I would like the Pi's Wifi connection to be consistent, but I do not know what else to try.
..
is this using the pi-3 onboard wireless ?
if so is it in a case ?
a metal case ?
is it close to other things that may interfere
what is the strength of the signal as measured on the RPi?
How To ask Questions :- http://www.catb.org/esr/faqs/smart-questions.html
WARNING - some parts of this post may be erroneous YMMV

1QC43qbL5FySu2Pi51vGqKqxy3UiJgukSX
Covfefe

User avatar
DougieLawson
Posts: 33616
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website

Re: RPi 3 - Very poor wifi performance

Mon Nov 07, 2016 9:55 am

Is this another case of the WiFi driver ToS bug?

For NTP performance use
/sbin/iptables -t mangle -I POSTROUTING 1 -o wlan0 -p udp --dport 123 -j TOS --set-tos 0x00

Other protocols may suffer in the same way.
Microprocessor, Raspberry Pi & Arduino Hacker
Mainframe database troubleshooter
MQTT Evangelist
Twitter: @DougieLawson

2012-18: 1B*5, 2B*2, B+, A+, Z, ZW, 3Bs*3, 3B+

Any DMs sent on Twitter will be answered next month.

mattgwwalker
Posts: 6
Joined: Thu May 09, 2013 10:54 am

Re: RPi 3 - Very poor wifi performance

Mon Nov 07, 2016 11:06 pm

is this using the pi-3 onboard wireless ?
if so is it in a case ?
a metal case ?
is it close to other things that may interfere
what is the strength of the signal as measured on the RPi?
Yes, this is using the Pi 3 onboard wireless. I do not own a Wifi dongle, but I am thinking about buying one to test if that would improve performance.

No, the Pi is not in a case. It is attached to a basic robotic platform (see image). However I believe all the testing I did yesterday was with everything else unplugged, thus I don't believe the other components could have produced any interference. I will double check this and get back to you.

How should I measure the signal strength on the RPi? Is the result from iwconfig not acceptable? If I understood the output correctly, is it not saying that the Pi is receiving signals at -49 dBm? Would you like me to poll that regularly to check? Or is there a better alternative?

In my testing yesterday I moved the access point in an effort to eliminate other possible interference sources. Is there a way to measure possible interference? The issue repeats consistently and for about 10 seconds, thus there is plenty of opportunity for testing.

Thanks greatly for your thoughts.

Matthew
Attachments
IMG_0058.jpg
IMG_0058.jpg (59.18 KiB) Viewed 3032 times

mattgwwalker
Posts: 6
Joined: Thu May 09, 2013 10:54 am

Re: RPi 3 - Very poor wifi performance

Mon Nov 07, 2016 11:34 pm

Is this another case of the WiFi driver ToS bug?

For NTP performance use
/sbin/iptables -t mangle -I POSTROUTING 1 -o wlan0 -p udp --dport 123 -j TOS --set-tos 0x00

Other protocols may suffer in the same way.
I'm not at all sure what that iptables command does, but I attempted to modify it for SSH on port 22. I ran:

sudo /sbin/iptables -t mangle -I POSTROUTING 1 -o wlan0 -p udp --dport 22 -j TOS --set-tos 0x00

Unfortunately, this had no impact on network performance. It is still dropping off regularly every 168 seconds. So either my modification of the command wasn't right or that's not the problem.

Thanks for your suggestion. If you have any others I'd be very pleased to try them!

Matthew

mattgwwalker
Posts: 6
Joined: Thu May 09, 2013 10:54 am

Re: RPi 3 - Very poor wifi performance

Mon Nov 07, 2016 11:37 pm

I believe all the testing I did yesterday was with everything else unplugged, thus I don't believe the other components could have produced any interference. I will double check this and get back to you.
I have just checked this. With everything else disconnected, and the Raspberry Pi powered through the USB port via a 2.5A transformer, the same network issues still exist.

Matthew

User avatar
DougieLawson
Posts: 33616
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website

Re: RPi 3 - Very poor wifi performance

Mon Nov 07, 2016 11:56 pm

mattgwwalker wrote: I'm not at all sure what that iptables command does, but I attempted to modify it for SSH on port 22. I ran:

sudo /sbin/iptables -t mangle -I POSTROUTING 1 -o wlan0 -p udp --dport 22 -j TOS --set-tos 0x00

Unfortunately, this had no impact on network performance. It is still dropping off regularly every 168 seconds. So either my modification of the command wasn't right or that's not the problem.

Thanks for your suggestion. If you have any others I'd be very pleased to try them!

Matthew

SSH uses TCP not UDP.

sudo /sbin/iptables -t mangle -I POSTROUTING 1 -o wlan0 -p tcp --dport 22 -j TOS --set-tos 0x00
Microprocessor, Raspberry Pi & Arduino Hacker
Mainframe database troubleshooter
MQTT Evangelist
Twitter: @DougieLawson

2012-18: 1B*5, 2B*2, B+, A+, Z, ZW, 3Bs*3, 3B+

Any DMs sent on Twitter will be answered next month.

mattgwwalker
Posts: 6
Joined: Thu May 09, 2013 10:54 am

Re: RPi 3 - Very poor wifi performance

Tue Nov 08, 2016 8:12 am

I seem to have resolved the Wifi issue simply by starting from scratch with Raspbian.

For those who might read this in the future: I obtained another Raspberry Pi 3 from a colleague. With this new Pi I used the SD card from the original Pi and noticed exactly the same issue with the Wifi network. Given this, I concluded it must be a software issue. I downloaded Raspbian Jessie with Pixel (2016-09-23) and found that my Wifi network issues went away when I used this image.

I think it's a little strange that starting from scratch helped. The original image on the SD card had had all the packages updated only a few days ago. Perhaps I'd installed something else incorrectly in the old image.

Thanks to those who made suggestions, it was fantastic to have your support.

Matthew

dmoneyblah
Posts: 1
Joined: Sun Nov 27, 2016 2:28 am

Re: RPi 3 - Very poor wifi performance

Sun Nov 27, 2016 2:53 am

For what it's worth, the aluminum case that I bought for the RPi3 was the cause of poor wifi performance. With the case on, the wifi was unstable and slow. As soon as I took it off, it was stable and fast(ish).

This is the case in question:
https://www.amazon.com/gp/product/B01H8L4EM8

It sure was a lovely case tho ...

User avatar
ab1jx
Posts: 660
Joined: Thu Sep 26, 2013 1:54 pm
Location: Heath, MA USA
Contact: Website

Re: RPi 3 - Very poor wifi performance

Tue Dec 20, 2016 4:34 pm

I'm investigating a problem whereby my Pi3 WiFis drop their connections after about 1 - 24 hours, my thread is at viewtopic.php?f=28&t=159950&p=1084439#p1084439

Just wanted to add that switching to the current Raspbian with Pixel didn't help in my case. I've been doing updates and upgrades about once a month. My power saving shows as being off, I've added the line to my interfaces file in case it's getting turned on somehow.

I found this thread by this Google search: https://www.google.com/search?oe=utf-8& ... c+bcm43438 I was initially curious about https://github.com/seemoo-lab/bcm-rpi3 because I'd like to watch the status of my bcm43438 and driver more closely, but "monitor" in this context is more like the aircrack context, allowing full duplexing of packets so I'm not trying it. Not sure where I'm going next but back to my own thread mentioned above.

Warjio
Posts: 2
Joined: Sat Jan 07, 2017 1:59 pm

Re: RPi 3 - Very poor wifi performance

Sat Jan 07, 2017 3:53 pm

Hi

I have been having issues with the integrated wifi and dongles like ralink and normal "Pi USB wifi" every time i update & upgrade. :evil:

Edit: A powered USB hub helps! :lol: :D :roll:
Last edited by Warjio on Sun Jan 08, 2017 7:39 pm, edited 1 time in total.

Warjio
Posts: 2
Joined: Sat Jan 07, 2017 1:59 pm

Re: RPi 3 - Very poor wifi performance

Sun Jan 08, 2017 7:36 pm

This helped my wifi

First i disabled ipv6:

Code: Select all

sudo -s

Code: Select all

sudo echo "net.ipv6.conf.all.disable_ipv6 = 1" >> /etc/sysctl.conf

Code: Select all

sudo echo "net.ipv6.conf.default.disable_ipv6 = 1" >> /etc/sysctl.conf

Code: Select all

sudo echo "net.ipv6.conf.lo.disable_ipv6 = 1" >> /etc/sysctl.conf
Edited the interface config:

Code: Select all

sudo nano /etc/network/interfaces
Copied this to the interface:

Code: Select all

wireless-power off
Then i put this under the wlan* like this:

Code: Select all

auto wlan0
iface wlan0 inet manual
wireless-power off
A different take on the interface:

Code: Select all

sudo echo "post-up iwconfig wlan0 power off" >> /etc/network/interfaces
Turned off sound in /boot/config.txt:

Code: Select all

dtparam=audio=off
Disabled Bluetooth in /boot/config.txt

Code: Select all

dtoverlay=pi3-disable-bt
Also like this in /etc/modprobe.d/raspi-blacklist.conf:

Code: Select all

#bt
blacklist btbcm
blacklist hci_uart
Then as root (sudo -i) disabled the bluetooth services:

Code: Select all

systemctl disable bluetooth.service

Code: Select all

systemctl disable hciuart.service
This could also work
Create /etc/modprobe.d/8192cu.conf and add the following:

Code: Select all

options 8192cu rtw_power_mgnt=0 rtw_enusbss=0
Create /etc/modprobe.d/r8188eu.conf and add the following:

Code: Select all

options r8188eu rtw_power_mgnt=0 rtw_enusbss=0
Turned off firmware roaming support:

Code: Select all

sudo nano /etc/modprobe.d/brcmfmac.conf
and added the following:

Code: Select all

options brcmfmac roamoff=1
My setup looks like this:

Router with Internet<--->wlan1<---(Pi as a bridge)--->eth0<--->Home network Router

It has now one USB hub connected to it (self powered)
The USB hub has one "NextG USB-Yagi High Power WiFi Antenna" connected acting as main wifi (wlan1)
http://www.ebay.com/itm/NextG-USB-Yagi- ... Sw2XFUbPKY
ifconfig:

Code: Select all

eth0      Link encap:Ethernet  HWaddr **:**:**:**:**:**  
          inet addr:192.168.3.1  Bcast:192.168.3.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:68586 errors:0 dropped:0 overruns:0 frame:0
          TX packets:79933 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:4864193 (4.6 MiB)  TX bytes:111077104 (105.9 MiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:376 errors:0 dropped:0 overruns:0 frame:0
          TX packets:376 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:33149 (32.3 KiB)  TX bytes:33149 (32.3 KiB)

wlan0     Link encap:Ethernet  HWaddr **:**:**:**:**:**  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan1     Link encap:Ethernet  HWaddr **:**:**:**:**:**  
          inet addr:192.168.1.15  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:153684 errors:0 dropped:7 overruns:0 frame:0
          TX packets:108986 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:179263693 (170.9 MiB)  TX bytes:29873472 (28.4 MiB)
iwconfig:

Code: Select all

wlan0     IEEE 802.11bgn  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          
lo        no wireless extensions.

eth0      no wireless extensions.

wlan1     IEEE 802.11bgn  ESSID:"ASUS"  
          Mode:Managed  Frequency:2.437 GHz  Access Point: **:**:**:**:**:**   
          Bit Rate=72 Mb/s   Tx-Power=1496 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=54/70  Signal level=-56 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
/etc/network/interfaces:

Code: Select all

# interfaces(5) file used by ifup(8) and ifdown(8)

# Please note that this file is written to be used with dhcpcd
# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'

# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet manual
wireless-power off

auto wlan1
iface wlan1 inet dhcp
wireless-power off
     wpa-driver wext
     wpa-ssid YOURSSID
     wpa-ap-scan 1
     wpa-proto RSN
     wpa-pairwise CCMP
     wpa-group CCMP
     wpa-key-mgmt WPA-PSK
     wpa-psk "YOURPASSWORD"

auto eth0
iface eth0 inet static
address 192.168.3.1
netmask 255.255.255.0
broadcast 192.168.3.255

## remove rules and chains first
up /sbin/iptables -F
 up /sbin/iptables -X
  up /sbin/iptables -t nat -F

    ## mask eth0, activate port forwarding and nat
up /sbin/iptables -A FORWARD -o wlan1 -i eth0 -s 192.168.0.0/24 -m conntrack --ctstate NEW -j ACCEPT
 up /sbin/iptables -A FORWARD -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT
  up /sbin/iptables -t nat -A POSTROUTING -o wlan1 -j MASQUERADE
   up /sbin/sysctl -w net.ipv4.ip_forward=1

## use dnsmasq-base
## on range 192.168.3.10 - 192.168.3.20
up /usr/bin/killall dnsmasq
 up /bin/sleep 2
  post-up /usr/sbin/dnsmasq -i eth0 -I wlan1 -F 192.168.3.10,192.168.3.20,infinite

## if you use dnsmasq activate this
## if dnsmasq-base deactive this
## dnsmasq restart
  post-up /etc/init.d/dnsmasq restart
/etc/dnsmasq.conf:

Code: Select all

server=208.67.222.222
server=208.67.220.220
server=8.8.8.8
server=8.8.4.4

cache-size=0

# dhcp active for eth0
interface=eth0

# no dhcp for wlan1
no-dhcp-interface=wlan1

# range / Lease-Time
dhcp-range=interface:eth0,192.168.3.10,192.168.3.20,infinite
dmesg:

Code: Select all

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.1.18-v7+ ([email protected]) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #846 SMP Thu Feb 25 14:22:53 GMT 2016
[    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: Raspberry Pi 3 Model B Rev 1.2
[    0.000000] cma: Reserved 8 MiB at 0x3c400000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 249856
[    0.000000] free_area_init_node: node 0, pgdat 80876f80, node_mem_map bbb6c000
[    0.000000]   Normal zone: 2196 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 249856 pages, LIFO batch:31
[    0.000000] [bcm2709_smp_init_cpus] enter (9420->f3003010)
[    0.000000] [bcm2709_smp_init_cpus] ncores=4
[    0.000000] PERCPU: Embedded 12 pages/cpu @bcfb0000 s20416 r8192 d20544 u49152
[    0.000000] pcpu-alloc: s20416 r8192 d20544 u49152 alloc=12*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 247660
[    0.000000] Kernel command line: 8250.nr_uarts=1 dma.dmachans=0x7f35 bcm2708_fb.fbwidth=640 bcm2708_fb.fbheight=480 bcm2709.boardrev=0xa02082 bcm2709.serial=0x94bec88c smsc95xx.macaddr=**:**:**:**:**:** bcm2708_fb.fbswap=1 bcm2709.uart_clock=48000000 vc_mem.mem_base=0x3dc00000 vc_mem.mem_size=0x3f000000  dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p7 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 971896K/999424K available (6024K kernel code, 534K rwdata, 1660K rodata, 448K init, 757K bss, 19336K reserved, 8192K cma-reserved)
[    0.000000] Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xbd800000 - 0xff000000   (1048 MB)
    lowmem  : 0x80000000 - 0xbd000000   ( 976 MB)
    modules : 0x7f000000 - 0x80000000   (  16 MB)
      .text : 0x80008000 - 0x807895a0   (7686 kB)
      .init : 0x8078a000 - 0x807fa000   ( 448 kB)
      .data : 0x807fa000 - 0x8087fac0   ( 535 kB)
       .bss : 0x80882000 - 0x8093f79c   ( 758 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] 	Additional per-CPU info printed with stalls.
[    0.000000] NR_IRQS:608
[    0.000000] Architected cp15 timer(s) running at 19.20MHz (phys).
[    0.000000] clocksource arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    0.000008] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[    0.000026] Switching to timer-based delay loop, resolution 52ns
[    0.000244] Console: colour dummy device 80x30
[    0.001287] console [tty1] enabled
[    0.001339] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
[    0.001408] pid_max: default: 32768 minimum: 301
[    0.001726] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001769] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.002775] Initializing cgroup subsys blkio
[    0.002824] Initializing cgroup subsys memory
[    0.002871] Initializing cgroup subsys devices
[    0.002914] Initializing cgroup subsys freezer
[    0.002964] Initializing cgroup subsys net_cls
[    0.003034] CPU: Testing write buffer coherency: ok
[    0.003119] ftrace: allocating 20309 entries in 60 pages
[    0.048628] CPU0: update cpu_capacity 1024
[    0.048693] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.048727] [bcm2709_smp_prepare_cpus] enter
[    0.048877] Setting up static identity map for 0x8240 - 0x8274
[    0.050658] [bcm2709_boot_secondary] cpu:1 started (0) 18
[    0.051007] [bcm2709_secondary_init] enter cpu:1
[    0.051051] CPU1: update cpu_capacity 1024
[    0.051057] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.051432] [bcm2709_boot_secondary] cpu:2 started (0) 17
[    0.051688] [bcm2709_secondary_init] enter cpu:2
[    0.051709] CPU2: update cpu_capacity 1024
[    0.051715] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.052071] [bcm2709_boot_secondary] cpu:3 started (0) 18
[    0.052255] [bcm2709_secondary_init] enter cpu:3
[    0.052276] CPU3: update cpu_capacity 1024
[    0.052282] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.052343] Brought up 4 CPUs
[    0.052441] SMP: Total of 4 processors activated (153.60 BogoMIPS).
[    0.052470] CPU: All CPU(s) started in HYP mode.
[    0.052496] CPU: Virtualization extensions available.
[    0.053192] devtmpfs: initialized
[    0.071444] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
[    0.071710] clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.072571] pinctrl core: initialized pinctrl subsystem
[    0.073118] NET: Registered protocol family 16
[    0.078239] DMA: preallocated 4096 KiB pool for atomic coherent allocations
[    0.079208] bcm2709.uart_clock = 48000000
[    0.083166] bcm2709: Mini UART enabled
[    0.083677] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.083725] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.083896] Serial: AMBA PL011 UART driver
[    0.084046] 3f201000.uart: ttyAMA0 at MMIO 0x3f201000 (irq = 83, base_baud = 0) is a PL011 rev2
[    0.084482] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[    0.149347] bcm2708-dmaengine 3f007000.dma: DMA legacy API manager at f3007000, dmachans=0xf35
[    0.149418] bcm2708-dmaengine 3f007000.dma: Initialized 7 DMA channels (+ 1 legacy)
[    0.150008] bcm2708-dmaengine 3f007000.dma: Load BCM2835 DMA engine driver
[    0.150045] bcm2708-dmaengine 3f007000.dma: dma_debug:0
[    0.150621] SCSI subsystem initialized
[    0.150817] usbcore: registered new interface driver usbfs
[    0.150924] usbcore: registered new interface driver hub
[    0.151047] usbcore: registered new device driver usb
[    0.151587] raspberrypi-firmware soc:firmware: Attached to firmware from 2016-02-25 14:25
[    0.178677] Switched to clocksource arch_sys_counter
[    0.220226] FS-Cache: Loaded
[    0.220511] CacheFiles: Loaded
[    0.229724] NET: Registered protocol family 2
[    0.230684] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.230825] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.231036] TCP: Hash tables configured (established 8192 bind 8192)
[    0.231150] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.231219] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.231550] NET: Registered protocol family 1
[    0.231870] RPC: Registered named UNIX socket transport module.
[    0.231902] RPC: Registered udp transport module.
[    0.231930] RPC: Registered tcp transport module.
[    0.231958] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.232903] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
[    0.234006] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.247397] VFS: Disk quotas dquot_6.6.0
[    0.247730] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.249813] FS-Cache: Netfs 'nfs' registered for caching
[    0.250741] NFS: Registering the id_resolver key type
[    0.250804] Key type id_resolver registered
[    0.250833] Key type id_legacy registered
[    0.252893] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[    0.253069] io scheduler noop registered
[    0.253108] io scheduler deadline registered (default)
[    0.253395] io scheduler cfq registered
[    0.255652] BCM2708FB: allocated DMA memory fc800000
[    0.255698] BCM2708FB: allocated DMA channel 0 @ f3007000
[    0.261154] Console: switching to colour frame buffer device 80x30
[    0.266079] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
[    0.271427] console [ttyS0] disabled
[    0.273074] 3f215040.uart: ttyS0 at MMIO 0x3f215040 (irq = 29, base_baud = 50000000) is a 16550
[    1.469890] console [ttyS0] enabled
[    1.478074] vc-cma: Videocore CMA driver
[    1.486148] vc-cma: vc_cma_base      = 0x00000000
[    1.495467] vc-cma: vc_cma_size      = 0x00000000 (0 MiB)
[    1.505862] vc-cma: vc_cma_initial   = 0x00000000 (0 MiB)
[    1.516334] vc-mem: phys_addr:0x00000000 mem_base=0x3dc00000 mem_size:0x3f000000(1008 MiB)
[    1.544047] brd: module loaded
[    1.557378] loop: module loaded
[    1.564776] vchiq: vchiq_init_state: slot_zero = 0xbc880000, is_master = 0
[    1.578979] Loading iSCSI transport class v2.0-870.
[    1.589136] usbcore: registered new interface driver smsc95xx
[    1.600088] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    1.811283] Core Release: 2.80a
[    1.817878] Setting default values for core params
[    1.827203] Finished setting default values for core params
[    2.038145] Using Buffer DMA mode
[    2.045080] Periodic Transfer Interrupt Enhancement - disabled
[    2.056150] Multiprocessor Interrupt Enhancement - disabled
[    2.066826] OTG VER PARAM: 0, OTG VER FLAG: 0
[    2.075528] Dedicated Tx FIFOs mode
[    2.083080] WARN::dwc_otg_hcd_init:1047: FIQ DMA bounce buffers: virt = 0xbc814000 dma = 0xfc814000 len=9024
[    2.102260] FIQ FSM acceleration enabled for :
Non-periodic Split Transactions
Periodic Split Transactions
High-Speed Isochronous Endpoints
[    2.135557] dwc_otg: Microframe scheduler enabled
[    2.135605] WARN::hcd_init_fiq:412: FIQ on core 1 at 0x8040ecc0
[    2.146824] WARN::hcd_init_fiq:413: FIQ ASM at 0x8040f030 length 36
[    2.158633] WARN::hcd_init_fiq:438: MPHI regs_base at 0xbd89c000
[    2.170023] dwc_otg 3f980000.usb: DWC OTG Controller
[    2.179688] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[    2.194778] dwc_otg 3f980000.usb: irq 32, io mem 0x00000000
[    2.205527] Init: Port Power? op_state=1
[    2.213509] Init: Power Port (0)
[    2.220521] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    2.233184] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.248102] usb usb1: Product: DWC OTG Controller
[    2.257371] usb usb1: Manufacturer: Linux 4.1.18-v7+ dwc_otg_hcd
[    2.268762] usb usb1: SerialNumber: 3f980000.usb
[    2.278495] hub 1-0:1.0: USB hub found
[    2.286221] hub 1-0:1.0: 1 port detected
[    2.294521] dwc_otg: FIQ enabled
[    2.294531] dwc_otg: NAK holdoff enabled
[    2.294539] dwc_otg: FIQ split-transaction FSM enabled
[    2.294571] Module dwc_common_port init
[    2.294835] usbcore: registered new interface driver usb-storage
[    2.306378] mousedev: PS/2 mouse device common for all mice
[    2.317676] bcm2835-cpufreq: min=600000 max=1200000
[    2.327428] sdhci: Secure Digital Host Controller Interface driver
[    2.339031] sdhci: Copyright(c) Pierre Ossman
[    2.347926] sdhost: log_buf @ bc813000 (fc813000)
[    2.428708] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[    2.441464] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0
[    2.452549] mmc-bcm2835 3f300000.mmc: DMA channels allocated
[    2.489508] mmc0: host does not support reading read-only switch, assuming write-enable
[    2.498779] sdhci-pltfm: SDHCI platform and OF driver helper
[    2.499127] ledtrig-cpu: registered to indicate activity on CPUs
[    2.499255] hidraw: raw HID events driver (C) Jiri Kosina
[    2.499436] usbcore: registered new interface driver usbhid
[    2.499439] usbhid: USB HID core driver
[    2.499814] Initializing XFRM netlink socket
[    2.499838] NET: Registered protocol family 17
[    2.499951] Key type dns_resolver registered
[    2.500377] Registering SWP/SWPB emulation handler
[    2.549686] registered taskstats version 1
[    2.549882] vc-sm: Videocore shared memory driver
[    2.549891] [vc_sm_connected_init]: start
[    2.559138] [vc_sm_connected_init]: end - returning 0
[    2.627353] Indeed it is in host mode hprt0 = 00021501
[    2.627552] Waiting for root device /dev/mmcblk0p7...
[    2.630249] mmc0: new high speed SDHC card at address 59b4
[    2.630694] mmcblk0: mmc0:59b4 USD   15.0 GiB 
[    2.633820]  mmcblk0: p1 p2 < p5 p6 p7 >
[    2.651302] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[    2.652849] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    2.654394] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    2.657171] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    2.747138] mmc1: new high speed SDIO card at address 0001
[    2.748156] EXT4-fs (mmcblk0p7): mounted filesystem with ordered data mode. Opts: (null)
[    2.748188] VFS: Mounted root (ext4 filesystem) readonly on device 179:7.
[    2.804425] devtmpfs: mounted
[    2.811377] Freeing unused kernel memory: 448K (8078a000 - 807fa000)
[    2.888922] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    2.901023] Indeed it is in host mode hprt0 = 00001101
[    3.108997] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[    3.121453] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.135295] hub 1-1:1.0: USB hub found
[    3.142997] hub 1-1:1.0: 5 ports detected
[    3.282558] random: systemd urandom read with 63 bits of entropy available
[    3.299040] systemd[1]: systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR)
[    3.324296] systemd[1]: Detected architecture 'arm'.
[    3.428726] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    3.483701] NET: Registered protocol family 10
[    3.493876] systemd[1]: Inserted module 'ipv6'
[    3.504757] systemd[1]: Set hostname to <raspberrypi>.
[    3.522951] systemd[1]: Failed to configure loopback device: Permission denied
[    3.539006] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[    3.552110] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.570378] smsc95xx v1.0.4
[    3.632020] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:be:c8:8c
[    3.748718] usb 1-1.4: new high-speed USB device number 4 using dwc_otg
[    3.860181] usb 1-1.4: New USB device found, idVendor=05e3, idProduct=0608
[    3.873265] usb 1-1.4: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    3.888764] usb 1-1.4: Product: USB2.0 Hub
[    3.898178] hub 1-1.4:1.0: USB hub found
[    3.906770] hub 1-1.4:1.0: 4 ports detected
[    3.953430] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[    3.969758] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    3.985754] systemd[1]: Expecting device dev-ttyS0.device...
[    3.999186] systemd[1]: Starting Remote File Systems (Pre).
[    4.012296] systemd[1]: Reached target Remote File Systems (Pre).
[    4.024207] systemd[1]: Starting Encrypted Volumes.
[    4.036192] systemd[1]: Reached target Encrypted Volumes.
[    4.046961] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
[    4.067427] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[    4.086602] systemd[1]: Starting Swap.
[    4.096759] systemd[1]: Reached target Swap.
[    4.105643] systemd[1]: Expecting device dev-mmcblk0p6.device...
[    4.119465] systemd[1]: Starting Root Slice.
[    4.130564] systemd[1]: Created slice Root Slice.
[    4.140164] systemd[1]: Starting User and Session Slice.
[    4.152945] systemd[1]: Created slice User and Session Slice.
[    4.164166] systemd[1]: Starting Delayed Shutdown Socket.
[    4.176921] systemd[1]: Listening on Delayed Shutdown Socket.
[    4.188124] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[    4.188717] usb 1-1.4.1: new high-speed USB device number 5 using dwc_otg
[    4.215740] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[    4.228953] systemd[1]: Starting Journal Socket (/dev/log).
[    4.242092] systemd[1]: Listening on Journal Socket (/dev/log).
[    4.253606] systemd[1]: Starting udev Control Socket.
[    4.265713] systemd[1]: Listening on udev Control Socket.
[    4.276273] systemd[1]: Starting udev Kernel Socket.
[    4.288125] systemd[1]: Listening on udev Kernel Socket.
[    4.298582] systemd[1]: Starting Journal Socket.
[    4.300129] usb 1-1.4.1: New USB device found, idVendor=05e3, idProduct=0608
[    4.300138] usb 1-1.4.1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    4.300145] usb 1-1.4.1: Product: USB2.0 Hub
[    4.308429] hub 1-1.4.1:1.0: USB hub found
[    4.308761] hub 1-1.4.1:1.0: 4 ports detected
[    4.364555] systemd[1]: Listening on Journal Socket.
[    4.374499] systemd[1]: Starting System Slice.
[    4.385548] systemd[1]: Created slice System Slice.
[    4.395248] systemd[1]: Starting File System Check on Root Device...
[    4.408713] usb 1-1.4.4: new high-speed USB device number 6 using dwc_otg
[    4.424047] systemd[1]: Starting system-systemd\x2dfsck.slice.
[    4.437982] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[    4.450035] systemd[1]: Starting system-getty.slice.
[    4.462141] systemd[1]: Created slice system-getty.slice.
[    4.472758] systemd[1]: Starting system-serial\x2dgetty.slice.
[    4.486273] systemd[1]: Created slice system-serial\x2dgetty.slice.
[    4.498328] systemd[1]: Starting Increase datagram queue length...
[    4.514397] systemd[1]: Starting Restore / save the current clock...
[    4.535987] usb 1-1.4.4: New USB device found, idVendor=148f, idProduct=3070
[    4.549267] usb 1-1.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    4.563340] systemd[1]: Starting Load Kernel Modules...
[    4.575349] usb 1-1.4.4: Product: 802.11 n WLAN
[    4.575358] usb 1-1.4.4: Manufacturer: Ralink
[    4.575364] usb 1-1.4.4: SerialNumber: 1.0
[    4.609164] systemd[1]: Mounted Huge Pages File System.
[    4.621029] systemd[1]: Starting udev Coldplug all Devices...
[    4.673262] systemd[1]: Started Set Up Additional Binary Formats.
[    4.685583] systemd[1]: Starting Create list of required static device nodes for the current kernel...
[    4.709233] systemd[1]: Mounting Debug File System...
[    4.724391] systemd[1]: Mounting POSIX Message Queue File System...
[    4.741297] fuse init (API version 7.23)
[    4.743943] systemd[1]: Starting Slices.
[    4.760106] systemd[1]: Reached target Slices.
[    4.774626] systemd[1]: Started Increase datagram queue length.
[    4.826457] systemd[1]: Started Create list of required static device nodes for the current kernel.
[    4.850932] systemd[1]: Started Restore / save the current clock.
[    4.866061] systemd[1]: Mounted Debug File System.
[    4.880360] i2c /dev entries driver
[    4.888575] systemd[1]: Mounted POSIX Message Queue File System.
[    4.904292] systemd[1]: Started Load Kernel Modules.
[    4.917560] systemd[1]: Started udev Coldplug all Devices.
[    4.934971] systemd[1]: Started File System Check on Root Device.
[    4.956456] systemd[1]: Time has been changed
[    5.104956] systemd[1]: Mounting FUSE Control File System...
[    5.120612] systemd[1]: Starting Apply Kernel Variables...
[    5.136499] systemd[1]: Mounting Configuration File System...
[    5.153102] systemd[1]: Starting Create Static Device Nodes in /dev...
[    5.170986] systemd[1]: Starting Syslog Socket.
[    5.182979] systemd[1]: Listening on Syslog Socket.
[    5.183127] systemd[1]: Starting Journal Service...
[    5.190521] systemd[1]: Started Journal Service.
[    5.389266] systemd-udevd[109]: starting version 215
[    5.492598] EXT4-fs (mmcblk0p7): re-mounted. Opts: (null)
[    5.902878] cfg80211: Calling CRDA to update world regulatory domain
[    6.138745] usb 1-1.4.4: reset high-speed USB device number 6 using dwc_otg
[    6.214132] cfg80211: World regulatory domain updated:
[    6.214155] cfg80211:  DFS Master region: unset
[    6.214163] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[    6.214179] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[    6.214191] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[    6.214204] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[    6.214218] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[    6.214232] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[    6.214245] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[    6.214257] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[    6.214269] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[    6.249198] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3070, rev 0201 detected
[    6.265852] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0005 detected
[    6.278114] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[    6.279940] usbcore: registered new interface driver rt2800usb
[    6.455166] cfg80211: Calling CRDA for country: NO
[    6.491421] brcmfmac: brcmf_sdio_drivestrengthinit: No SDIO Drive strength init done for chip 43430 rev 1 pmurev 24
[    6.494980] usbcore: registered new interface driver brcmfmac
[    6.509796] cfg80211: Regulatory domain changed to country: NO
[    6.509848] cfg80211:  DFS Master region: ETSI
[    6.509861] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[    6.509884] cfg80211:   (2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[    6.509901] cfg80211:   (5150000 KHz - 5250000 KHz @ 80000 KHz, 200000 KHz AUTO), (N/A, 2301 mBm), (N/A)
[    6.509915] cfg80211:   (5250000 KHz - 5350000 KHz @ 80000 KHz, 200000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[    6.509928] cfg80211:   (5470000 KHz - 5795000 KHz @ 160000 KHz), (N/A, 2698 mBm), (0 s)
[    6.509950] cfg80211:   (5815000 KHz - 5850000 KHz @ 35000 KHz), (N/A, 3301 mBm), (0 s)
[    6.509963] cfg80211:   (17100000 KHz - 17300000 KHz @ 200000 KHz), (N/A, 2000 mBm), (N/A)
[    6.509976] cfg80211:   (57000000 KHz - 66000000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
[    6.705386] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: May 27 2016 00:13:38 version 7.45.41.26 (r640327) FWID 01-df77e4a7
[    7.132700] systemd-journald[107]: Received request to flush runtime journal from PID 1
[    7.217958] bcm2835-rng 3f104000.rng: hwrng registered
[    7.218248] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[    7.621549] brcmfmac: brcmf_add_if: ERROR: netdev:wlan1 already exists
[    7.621572] brcmfmac: brcmf_add_if: ignore IF event
[    7.624017] random: nonblocking pool is initialized
[   11.569960] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[   11.599199] ip_tables: (C) 2000-2006 Netfilter Core Team
[   11.623068] nf_conntrack version 0.5.0 (15320 buckets, 61280 max)
[   12.010542] Adding 102396k swap on /var/swap.  Priority:-1 extents:1 across:102396k SSFS
[   12.169990] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
[   12.179330] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.29
[   13.127347] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
[ 1187.086237] cfg80211: Calling CRDA to update world regulatory domain
[ 1187.109239] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code
[ 1187.109281] cfg80211: World regulatory domain updated:
[ 1187.109288] cfg80211:  DFS Master region: unset
[ 1187.109293] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 1187.109301] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 1187.109314] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 1187.109326] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[ 1187.109334] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 1187.109341] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[ 1187.109348] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[ 1187.109364] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[ 1187.109377] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[ 1187.109437] cfg80211: Calling CRDA for country: NO
[ 1187.126931] cfg80211: Regulatory domain changed to country: NO
[ 1187.126946] cfg80211:  DFS Master region: ETSI
[ 1187.126951] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 1187.126959] cfg80211:   (2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 1187.126967] cfg80211:   (5150000 KHz - 5250000 KHz @ 80000 KHz, 200000 KHz AUTO), (N/A, 2301 mBm), (N/A)
[ 1187.126975] cfg80211:   (5250000 KHz - 5350000 KHz @ 80000 KHz, 200000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[ 1187.126982] cfg80211:   (5470000 KHz - 5795000 KHz @ 160000 KHz), (N/A, 2698 mBm), (0 s)
[ 1187.126988] cfg80211:   (5815000 KHz - 5850000 KHz @ 35000 KHz), (N/A, 3301 mBm), (0 s)
[ 1187.127000] cfg80211:   (17100000 KHz - 17300000 KHz @ 200000 KHz), (N/A, 2000 mBm), (N/A)
[ 1187.127014] cfg80211:   (57000000 KHz - 66000000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
speedtest-cli --bytes:

Code: Select all

Retrieving speedtest.net configuration...
Retrieving speedtest.net server list...
Testing from YOUR Internett (YOURWANiP)...
Selecting best server based on latency...
Hosted by ISP AS (Moon) [1.79 km]: 13.814 ms
Testing download speed........................................
Download: 3.62 Mbytes/s
Testing upload speed..................................................
Upload: 3.87 Mbytes/s
uname -a:

Code: Select all

Linux raspberrypi 4.1.18-v7+ #846 SMP Thu Feb 25 14:22:53 GMT 2016 armv7l GNU/Linux
lsmod:

Code: Select all

Module                  Size  Used by
ipt_MASQUERADE           955  1 
nf_nat_masquerade_ipv4     1825  1 ipt_MASQUERADE
xt_conntrack            3031  2 
iptable_nat             1601  1 
nf_conntrack_ipv4      12672  3 
nf_defrag_ipv4          1283  1 nf_conntrack_ipv4
nf_nat_ipv4             4792  1 iptable_nat
nf_nat                 12064  2 nf_nat_ipv4,nf_nat_masquerade_ipv4
nf_conntrack           75585  5 nf_nat,nf_nat_ipv4,xt_conntrack,nf_nat_masquerade_ipv4,nf_conntrack_ipv4
iptable_filter          1245  1 
ip_tables              11417  2 iptable_filter,iptable_nat
x_tables               12611  4 ip_tables,ipt_MASQUERADE,xt_conntrack,iptable_filter
brcmfmac              177546  0 
brcmutil                5501  1 brcmfmac
bcm2835_gpiomem         2860  0 
bcm2835_rng             1763  0 
arc4                    1718  2 
rt2800usb              17370  0 
rt2800lib              71591  1 rt2800usb
rt2x00usb               8480  1 r[code]
t2800usb
rt2x00lib 36641 3 rt2x00usb,rt2800lib,rt2800usb
mac80211 503297 3 rt2x00lib,rt2x00usb,rt2800lib
cfg80211 389253 3 brcmfmac,mac80211,rt2x00lib
crc_ccitt 1142 1 rt2800lib
rfkill 16036 2 cfg80211
uio_pdrv_genirq 2944 0
uio 7753 1 uio_pdrv_genirq
i2c_dev 5671 0
fuse 80694 1
ipv6 338574 34 [/code]
lsusb:

Code: Select all

Bus 001 Device 006: ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070 Wireless Adapter
Bus 001 Device 005: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
My gaming computer with Windows on my home network gets 4451.1 kb/s Download & 5130.2 kb/s UPLOAD from speedtest.net

The router the Pi connects has 250/250 Internet and my raspberry pi gets well just in theory 72/72 i guess if read it correctly..
it is a bottleneck! :lol: i know i know..but it must be at least stable and not fall back to the 300kb/s nonsense.

and everything has been updated & upgraded :o

so good so far :D

Return to “Troubleshooting”

Who is online

Users browsing this forum: rpdom and 43 guests