Problems with Raspberry Pi Zero, external WiFi and Pimoroni PHAT (continues part of #686) #689
Comments
|
The log you uploaded, shown again here, indicates a poor network situation. The "Error 11" messages indicate that it is taking too long to send resend requests, probably due to a network problem. The high level resend request numbers (e.g. request of level 7 means this is the seventh resend request for this packet) indicate that resend request messages are being lost or dropped somewhere, and are not being answered. Other messages indicate timing pings being lost, very high of intervals between successive packets of audio (up to 1.748793 second in one case, whereas the interval should be around 0.008 seconds (!)). Generally, all these indicators point to network problems. So, if you turn off power management on WiFi in the way suggested (not by blacklisting -- that's a pretty dangerous way to go about things, IMHO), then let's see how things are. To check if power save mode is on or off, do: To turn it off, do: To turn off power management on power-up, put: In That way, it will always be executed at power-up. |
|
|
Seems with the last batch of updates, for no reason both my Pi Zero and Pi Three will at the same time have stuttering issues... I suspect this may actually be due to me running MacOS 10.13.5 Beta (17F45c). I have also observed this issue running from my iPhone X, again on a Beta, iOS 10.4 Beta 2. What leads me to suspect the above is that from my iPhone, I run the SomaFM App and when I Airplay streaming from that app to the Pi's, I never have this issue! I use my Pi Zero the most, as my Pi 3 is connected to my Main Tube Based Rig, whereas the Pi Zero is connected to a nifty Class D Amp and basically is always running. Must stress this part.. the Stuttering, Cracking, Buffering, Dropouts happen simultaneously to the Zero and the Three.. leading to believe this is a Source Issue! More perplexing is this is either once in a blue moon... or its constant till I reboot the Pi's and even then, you never know if its going to hum along or go into crazy mode! As the Zero is the life blood, here are the Specs: Raspbian GNU/Linux 9.4 (stretch) 3.2RC4-mbedTLS-Avahi-ALSA-sysconfdir:/etc |
|
That’s interesting. But that the simultaneous stuttering could be caused by a network problem, no? |
|
As mentioned, never had any issues until recently.. Nothing has changed network side! I was just after Firmware Updates, System Updates and the Update to the latest Shairport that this issue began happening! |
|
It’s really curious. Has anything else changed that might change the wireless environment, like new sources of interference? Anyhow, let’s keep the issue under review... |
|
I live in a tiny Apartment... The Airport Extreme is in line of sight of the Pi Three... maybe all of 4 meters away! The Pi Zero is all of 12 meters away! I stress, other than Updates to Firmware, OS Updates and finally Shairport Updates did this issue arise! Hope there is something Duh! to solve this! |
|
Mike, is there a way to revert back to 3.1.7? I'm sure that if I revert back the issues will go away! |
|
Sure thing. You should follow the UPDATING.md guide, but after the That will check out version 3.1.7 and you can then build it as explained in the guide. In the future, if you want to revert to the latest version, follow the updating procedure again, but this time, after the That will check out the latest in the [PS, it would be very interesting to hear the outcome!] |
|
Thanks! Back on 3.1.7 and yarp.. Issue Persists! Remember this is the Original Zero where I'm using a suggested generic Wi-Fi Adapter. The 3 is using the on board Wi-Fi Chip. I've done multiple Wi-Fi Tests and cannot find anything wrong with the Apple Airport Extreme 6th Gen! This is getting annoying as I'm beginning to think that the new neighbours may have equipment that is causes this issue. That or is it something as simple as the latest builds of Stretch or even Firmware on the Pi's? |
|
Thanks for the update. While it is of no consolation to you, I'm somewhat relieved that the problem doesn't appear to be something introduced after 3.1.7 -- it would be a real surprise! Anyhow, my strong suspicion is that it's a network related problem. It could come from some change in the environment, like a microwave oven, or even a new Bluetooth device or a DECT phone. The Airport Extreme is a very good access point and router, so, on the face of it, it should not be a problem. However, it can't really be excluded, as it might by failing slowly. All the same, it would be low on my list of suspects. Likewise, I'd say that the latest builds of Linux and of firmware are probably safe enough. (Also, I'm running the latest of the on my Pi Zero W and Pi 3s with no problems.) Do things improve, in general, if you turn off the Pi Zero completely (or the Pi 3 completely) and leave the other devices running? Does simply restarting the router help at all? |
mikebrady
changed the title
|
After a bit of research, I've opted to acquire a new Router. The Netgear Nighthawk AC2300 (R7000P). If Apple no longer makes Routers and thus does not support what I have, might as well go with a company that supports its products. Once it arrives, and the tedious setup has been completed; hopefully that resolves the issue! |
|
Yeah. I've had these problems too, and ended up with a Ubiquiti AP AC Pro, and am very pleased with it. It's only a WiFi access point though -- you need a router and NAT and all that other stuff. I have that, based on the community version of pfSense. It's quite a bit or work to put all this together, but now it 'just works'. |
|
Wish you had told me what you Wi-Fi setup was earlier... Been tempted to Build a PFsense router for sometime as I now get faster Internet Speeds. I was looking for quality Wi-Fi AC's to go with my planned setup and the Ubiquiti was on the list. Anyway, with that said, just after I ordered the Netgear Nighthawk, I recalled that I had the last Gen Apple Express sitting around previously being my AirTunes unit. Dusked it it off and replaced the Extreme with the Express. So far... touch electrons.. appears the problem has been solved! Will keep this ticket open for a day or so.. just in case! |
|
That’s encouraging! Let’s see how it goes. |
|
Hey Mike, think its safe to say this was a Wi-Fi issue. Not a single problem since replacing the Extreme with the Express! How sad it is that a little Express is performing better... guess even routers die with age! Would love to know what your setup for PFSense is, but seeing as this is Issue Area.. not sure if you will share that with me before getting my blessing to close this ticket! ;) |
|
FYI, I also have the Ubiquiti AP AC Pro (2 of them) and it’s amazingly good, rock solid. For router, I recently evaluated various options incl pfSense and went with the Ubiquiti Edge Router Lite, $99 and higher performance than the pfSense boxes on a price parity basis. This combination is working extremely well for me. However, I did end up putting an antenna WiFi dongle (http:https://a.co/fQnx2Ic <http:https://a.co/fQnx2Ic>) on the RPi instead of the little Edimax WiFi stub which solved all my network issues related to the RPi. Streaming over Shaiport Sync is totally flawless for me now.
… On Apr 25, 2018, at 2:16 PM, rockrabbit ***@***.***> wrote:
Wish you had told me what you Wi-Fi setup was earlier... Been tempted to Build a PFsense router for sometime as I now get faster Internet Speeds. I was looking for quality Wi-Fi AC's to go with my planned setup and the Ubiquiti was on the list.
Anyway, with that said, just after I ordered the Netgear Nighthawk, I recalled that I had the last Gen Apple Express sitting around previously being my AirTunes unit.
Dusked it it off and replaced the Extreme with the Express.
So far... touch electrons.. appears the problem has been solved!
Will keep this ticket open for a day or so.. just in case!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#689 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABZk7xrsker03izrtGP7TyyUrSalx8KJks5tsOe7gaJpZM4Tfj8H>.
|
|
Thanks for that. My pfSense system is running in a VMWare VM on a PC Engines APU 4 board and provides NAT, DHCP, port mapping and a firewall. Broadband is 240 Mb and the box can routinely deliver 210 Mb. It is absolutely rock solid. There is nothing special about the setup though. |
|
After a little digging, seeing as I get can get 1000MB/s from my provider, I'd have to go with the EdgeRouter 4 and an AC PRO... so $350 odd later... would have a overkill network wi-fi system in my tiny one room NY apartment! ;) |
|
Please tell me it’s 1000 Mb (megabits) rather than 1000 MB (megabytes) per second! You would have more connectivity than some small countries :) |
|
I stand corrected! https://www.greenlightnetworks.com/residential/ 1,000 Mbps Download |
|
Think I'm over thinking all of this.. just need to get a USB Wi-Fi Adapter for the Pi Zero that has an antenna! The one mentioned above is not available and everything else I've found requires drivers... no thanks.. just want something that is plug and play! |
|
Just got this... Edimax AC600 Followed this Install Guide Unreal difference in performance... so even though I have to keep on top a driver, this is 10 times faster than the Generic 8-2.11n nub I initially had! |
|
Looks interesting, and the guide for compiling and installing looks fine. I might refer to this issue -- a saga! -- from the troubleshooting page. Would it be okay to close the issue now? |
|
Make with the closing! |
|
Thanks -- it was a particularly illuminating issue, this one. I've liked to it from the Troubleshooting page. |
|
In summary, it turns out that the issue was a failing 802.11n nub on the Pi Zero. Once this was replaced with an Edimax EW-7811 AC600, not only did this resolve the Shairport Sync issue, but various other slow updates. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a continuation of @rockrabbit's issue from #686.
The text was updated successfully, but these errors were encountered: