Re: [SlimDevices: Unix] RPI ZERO W - wifi unstable
Do you have a WIFI network with AP roaming enabled? This caused a bunch of problems with my RasPI based systems and I had to turn it off. StevenEllis's Profile: http://forums.slimdevices.com/member.php?userid=69979 View this thread: http://forums.slimdevices.com/showthread.php?t=115095 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] RPI ZERO W - wifi unstable
Mellon wrote: > It may be worth remembering that packet loss is not ALWAYS a result of a > network malfunction. > > For example, if the device you are pinging is already working hard > trying to do something else, that could be a reason for it to drop the > ping request, rather than the ping request not making it there, or back, > on the network. I'm not sure if there is any way to check CPU load, or > any other process which may cause it to not respond promptly in Picore? > > Is the ping response you provided an example of the Wifi going down > regularly, or does it run like this and then you get nothing but Request > timed out? It's also worth remembering that the whole Pi range is very cheap and quality control is, as a result, patchy. Another apparently identical Pi Zero-W may work perfectly. Jim https://jukeradio.double6.net VB2.4[/B] STORAGE *QNAP TS419P (NFS) [B]Living Room* Joggler & Pi4/Khadas -> Onkyo TXNR686 -> Celestion F20s *Office* Joggler & Pi3 -> Denon RCD N8 -> Celestion F10s *Dining Room* SB Radio *Bedroom (Bedside)* Pi Zero+DAC ->ToppingTP21 ->AKG Headphones *Bedroom (TV) & Bathroom* SB Touch ->Denon AVR ->Mordaunt Short M10s + Kef ceiling speakers *Guest Room* Joggler > Topping Amp -> Wharfedale Modus Cubes d6jg's Profile: http://forums.slimdevices.com/member.php?userid=44051 View this thread: http://forums.slimdevices.com/showthread.php?t=115095 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] RPI ZERO W - wifi unstable
pascal! wrote: > Hi, > I have RPI ZERO W - with piCore > piCorePlayer v7.0.0 | www v00011 | linux 5.4.83-pcpCore | piCore > v12.0pCP | Squeezelite v1.9.9-1386-pCP > And the WiFi goes down regurlarly and it is ok after the reboot for some > minutes. > My WiFi is quite good and I have another RPI ZERO W further from my wap > that goes w/o any trouble > Could you help oo solve this problem? > > Code: > > Reply from 192.168.9.123: bytes=32 time=13ms TTL=64 > Reply from 192.168.9.123: bytes=32 time=17ms TTL=64 > Reply from 192.168.9.123: bytes=32 time=12ms TTL=64 > Reply from 192.168.9.123: bytes=32 time=17ms TTL=64 > Reply from 192.168.9.123: bytes=32 time=16ms TTL=64 > Request timed out. > Reply from 192.168.9.123: bytes=32 time=15ms TTL=64 > Reply from 192.168.9.123: bytes=32 time=12ms TTL=64 > Reply from 192.168.9.123: bytes=32 time=16ms TTL=64 > Reply from 192.168.9.123: bytes=32 time=16ms TTL=64 > Reply from 192.168.9.123: bytes=32 time=17ms TTL=64 > Reply from 192.168.9.123: bytes=32 time=30ms TTL=64 > Reply from 192.168.9.123: bytes=32 time=16ms TTL=64 > Reply from 192.168.9.123: bytes=32 time=13ms TTL=64 > Request timed out. > Reply from 192.168.9.123: bytes=32 time=14ms TTL=64 > Reply from 192.168.9.123: bytes=32 time=15ms TTL=64 > Reply from 192.168.9.123: bytes=32 time=13ms TTL=64 > Reply from 192.168.9.123: bytes=32 time=9ms TTL=64 > Reply from 192.168.9.123: bytes=32 time=16ms TTL=64 > Request timed out. > Reply from 192.168.9.123: bytes=32 time=130ms TTL=64 > Reply from 192.168.9.123: bytes=32 time=9ms TTL=64 > Reply from 192.168.9.123: bytes=32 time=692ms TTL=64 > Request timed out. > Reply from 192.168.9.123: bytes=32 time=58ms TTL=64 > Request timed out. > Reply from 192.168.9.123: bytes=32 time=19ms TTL=64 > Reply from 192.168.9.123: bytes=32 time=10ms TTL=64 > > It may be worth remembering that packet loss is not ALWAYS a result of a network malfunction. For example, if the device you are pinging is already working hard trying to do something else, that could be a reason for it to drop the ping request, rather than the ping request not making it there, or back, on the network. I'm not sure if there is any way to check CPU load, or any other process which may cause it to not respond promptly in Picore? Is the ping response you provided an example of the Wifi going down regularly, or does it run like this and then you get nothing but Request timed out? Mellon's Profile: http://forums.slimdevices.com/member.php?userid=69383 View this thread: http://forums.slimdevices.com/showthread.php?t=115095 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] RPI ZERO W - wifi unstable
[WiFi Settings] > [Diagnostics] gives all (most) of the answers.
Code:
Wifi:on
SSID:GE2
Password:xx
Passphrase:
Security:WPA-PSK
Country:
Hidden SSID: 0
MAC address: 00:0f:13:28:20:85
Uptime: 0 days 13 hours 2 minutes 32 seconds
dmesg
===
[5.262529] usb 1-1.3: New USB device found, idVendor=148f,
idProduct=5370, bcdDevice= 1.01
[5.262569] usb 1-1.3: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[5.262591] usb 1-1.3: Product: 802.11 n WLAN
[5.262609] usb 1-1.3: Manufacturer: Ralink
[5.262631] usb 1-1.3: SerialNumber: 1.0
.
[ 25.694152] usbcore: registered new interface driver rt2800usb
.
[ 23.820161] cfg80211: Loading compiled-in X.509 certificates for
regulatory database
[ 23.998036] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
.
lsmod
=
Module Size Used by
aes_arm 16384 4
aes_generic 40960 1 aes_arm
libaes 16384 2 aes_arm,aes_generic
rt2800usb 28672 0
rt2x00usb 24576 1 rt2800usb
rt2800lib 126976 1 rt2800usb
rt2x00lib 61440 3 rt2800lib,rt2800usb,rt2x00usb
mac80211 819200 3 rt2800lib,rt2x00lib,rt2x00usb
libarc4 16384 1 mac80211
sha256_generic 16384 0
libsha256 20480 1 sha256_generic
cfg80211 774144 2 rt2x00lib,mac80211
rfkill 32768 2 cfg80211
raspberrypi_hwmon 16384 0
wifi usb report (lsusb)
===
Bus 001 Device 004: ID 148f:5370
wpa supplicant configuration (wpa_supplicant.conf)
===
# Maintained by piCorePlayer
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=staff
update_config=1
network={
#enc_ssid="GE2"
ssid="GExxx2"
psk=""
key_mgmt=WPA-PSK
auth_alg=OPEN
}
Extensions in onboot.lst (onboot.lst)
===
pcp.tcz
pcp-8.1.0-www.tcz
firmware-atheros.tcz
firmware-brcmwifi.tcz
firmware-ralinkwifi.tcz
firmware-rtlwifi.tcz
firmware-rpi-wifi.tcz
wireless_tools.tcz
wpa_supplicant.tcz
Wifi extensions installed
=
[ OK ] wireless_tools installed.
[ OK ] wpa_supplicant installed.
[ OK ] firmware-atheros installed.
[ OK ] firmware-brcmwifi installed.
[ OK ] firmware-ralinkwifi installed.
[ OK ] firmware-rtlwifi installed.
[ OK ] firmware-rpi-wifi installed.
iwconfig
wlan0 IEEE 802.11 ESSID:"GEwireless2"
Mode:Managed Frequency:2.452 GHz Access Point: B0:95:75:18:E6:E6
Bit Rate=65 Mb/s Tx-Power=20 dBm
Retry short long limit:2 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=57/70 Signal level=-53 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:418 Invalid misc:1860 Missed beacon:0
ifconfig
=
wlan0 Link encap:Ethernet HWaddr 00:0F:13:28:20:85
inet addr:192.168.1.108 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5900946 errors:0 dropped:9529 overruns:0 frame:0
TX packets:817740 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8642565281 (8.0 GiB) TX bytes:73854866 (70.4 MiB)
iwlist
Cell 02 - Address: B0:95:75:18:E6:E6
Channel:9
Frequency:2.452 GHz (Channel 9)
Quality=57/70 Signal level=-53 dBm
Encryption key:on
ESSID:"GEwireless2"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=0044290cb11d
Extra: Last beacon: 210ms ago
IE: Unknown: 000B4745776972656C65737332
IE: Unknown: 010882848B962430486C
IE: Unknown: 030109
IE: Unknown: 2A0104
IE: Unknown: 32040C121860
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
IE: Unknown: 0B05070017
IE: Unknown: 4605320801
IE: Unknown: 2D1ABC091B01
IE: Unknown: 3D1609001700
IE: Unknown: 4A0E14000A002C01C800140005001900
IE: Unknown: 7F0805000840
IE: Unknown: DD090010180207000C
IE: Unknown: DD180050F202010184000332273242225E0062212F00
Cell 03 - Address: BC:30:D9:F5:63:45
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=33/70 Signal level=-77 dBm
Encryption key:on
ESSID:"TelstraF56343"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5
Re: [SlimDevices: Unix] RPI ZERO W - wifi unstable
...or neighbours on the same (or close) WiFi channel, of course. Can you use something like InSSIDer (on Windows) to check the WiFi channels in use in your vicinity: their strength and channel numbers? Martin mooblie's Profile: http://forums.slimdevices.com/member.php?userid=15378 View this thread: http://forums.slimdevices.com/showthread.php?t=115095 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] RPI ZERO W - wifi unstable
Paul Webster wrote: > Maybe if you move it even further away it will work even better! Maybe! The quality and level did drop though. Code: Pos QualityLevel 1. 100 -11dBm 2. 75-57dBm I think the problems start to occur when the neighbours wifi router have a higher quality and level than your own. Greg Erskine's Profile: http://forums.slimdevices.com/member.php?userid=7403 View this thread: http://forums.slimdevices.com/showthread.php?t=115095 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] RPI ZERO W - wifi unstable
Aren't the clever PCB-based antennae on Pis _orientation_sensitive_? I got better WiFi reception with a Pi (Pi3 actually) VERTICAL, rather than horizontal. Martin mooblie's Profile: http://forums.slimdevices.com/member.php?userid=15378 View this thread: http://forums.slimdevices.com/showthread.php?t=115095 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] RPI ZERO W - wifi unstable
Maybe if you move it even further away it will work even better! Paul Webster http://dabdig.blogspot.com author of \"now playing\" plugins covering radio france (fip etc), planetradio (bauer - kiss, absolute, scala, jazzfm etc), kcrw, supla finland, abc australia, cbc/radio-canada and rte ireland Paul Webster's Profile: http://forums.slimdevices.com/member.php?userid=105 View this thread: http://forums.slimdevices.com/showthread.php?t=115095 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] RPI ZERO W - wifi unstable
Moved 7 meters away thru 1 interior wall. Code: PING 192.168.1.52 (192.168.1.52): 56 data bytes 64 bytes from 192.168.1.52: seq=0 ttl=64 time=6.003 ms 64 bytes from 192.168.1.52: seq=1 ttl=64 time=5.625 ms 64 bytes from 192.168.1.52: seq=2 ttl=64 time=7.219 ms 64 bytes from 192.168.1.52: seq=3 ttl=64 time=6.813 ms 64 bytes from 192.168.1.52: seq=4 ttl=64 time=8.311 ms 64 bytes from 192.168.1.52: seq=5 ttl=64 time=6.084 ms 64 bytes from 192.168.1.52: seq=6 ttl=64 time=7.394 ms 64 bytes from 192.168.1.52: seq=7 ttl=64 time=6.307 ms 64 bytes from 192.168.1.52: seq=8 ttl=64 time=6.868 ms 64 bytes from 192.168.1.52: seq=9 ttl=64 time=6.880 ms 64 bytes from 192.168.1.52: seq=10 ttl=64 time=7.075 ms 64 bytes from 192.168.1.52: seq=11 ttl=64 time=6.677 ms 64 bytes from 192.168.1.52: seq=12 ttl=64 time=21.689 ms 64 bytes from 192.168.1.52: seq=13 ttl=64 time=7.040 ms 64 bytes from 192.168.1.52: seq=14 ttl=64 time=6.527 ms 64 bytes from 192.168.1.52: seq=15 ttl=64 time=7.239 ms 64 bytes from 192.168.1.52: seq=16 ttl=64 time=6.736 ms 64 bytes from 192.168.1.52: seq=17 ttl=64 time=6.373 ms 64 bytes from 192.168.1.52: seq=18 ttl=64 time=6.804 ms 64 bytes from 192.168.1.52: seq=19 ttl=64 time=6.422 ms --- 192.168.1.52 ping statistics --- 20 packets transmitted, 20 packets received, 0% packet loss round-trip min/avg/max = 5.625/7.504/21.689 ms Greg Erskine's Profile: http://forums.slimdevices.com/member.php?userid=7403 View this thread: http://forums.slimdevices.com/showthread.php?t=115095 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] RPI ZERO W - wifi unstable
There is a [Diagnostics] button on the [Wifi Settings] page. The diagnostics log is then available under [Main Page] > [Diagnostics] > [Logs]. Here is part of the log from my Raspberry Pi ZeroW (located 100mm from wifi router). Code: PING 192.168.1.52 (192.168.1.52): 56 data bytes 64 bytes from 192.168.1.52: seq=0 ttl=64 time=6.927 ms 64 bytes from 192.168.1.52: seq=1 ttl=64 time=6.457 ms 64 bytes from 192.168.1.52: seq=2 ttl=64 time=6.993 ms 64 bytes from 192.168.1.52: seq=3 ttl=64 time=6.285 ms 64 bytes from 192.168.1.52: seq=4 ttl=64 time=7.810 ms 64 bytes from 192.168.1.52: seq=5 ttl=64 time=6.660 ms 64 bytes from 192.168.1.52: seq=6 ttl=64 time=6.867 ms 64 bytes from 192.168.1.52: seq=7 ttl=64 time=7.274 ms 64 bytes from 192.168.1.52: seq=8 ttl=64 time=7.289 ms 64 bytes from 192.168.1.52: seq=9 ttl=64 time=8.026 ms 64 bytes from 192.168.1.52: seq=10 ttl=64 time=18.112 ms 64 bytes from 192.168.1.52: seq=11 ttl=64 time=47.287 ms 64 bytes from 192.168.1.52: seq=12 ttl=64 time=6.841 ms 64 bytes from 192.168.1.52: seq=13 ttl=64 time=6.244 ms 64 bytes from 192.168.1.52: seq=14 ttl=64 time=6.797 ms 64 bytes from 192.168.1.52: seq=15 ttl=64 time=7.531 ms 64 bytes from 192.168.1.52: seq=16 ttl=64 time=7.160 ms 64 bytes from 192.168.1.52: seq=17 ttl=64 time=13.358 ms 64 bytes from 192.168.1.52: seq=18 ttl=64 time=12.290 ms 64 bytes from 192.168.1.52: seq=19 ttl=64 time=6.615 ms --- 192.168.1.52 ping statistics --- 20 packets transmitted, 20 packets received, 0% packet loss round-trip min/avg/max = 6.244/10.141/47.287 ms No timeout errors or packet loss. Greg Erskine's Profile: http://forums.slimdevices.com/member.php?userid=7403 View this thread: http://forums.slimdevices.com/showthread.php?t=115095 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] RPI ZERO W - wifi unstable
Try swapping the two ZeroW locations to see if the problem is with the specific ZeroW or with the location. John On 9/5/21 8:37 AM, pascal! wrote: Hi, I have RPI ZERO W - with piCore piCorePlayer v7.0.0 | www v00011 | linux 5.4.83-pcpCore | piCore v12.0pCP | Squeezelite v1.9.9-1386-pCP And the WiFi goes down regurlarly and it is ok after the reboot for some minutes. My WiFi is quite good and I have another RPI ZERO W further from my wap that goes w/o any trouble Could you help oo solve this problem? Code: Reply from 192.168.9.123: bytes=32 time=13ms TTL=64 Reply from 192.168.9.123: bytes=32 time=17ms TTL=64 Reply from 192.168.9.123: bytes=32 time=12ms TTL=64 Reply from 192.168.9.123: bytes=32 time=17ms TTL=64 Reply from 192.168.9.123: bytes=32 time=16ms TTL=64 Request timed out. Reply from 192.168.9.123: bytes=32 time=15ms TTL=64 Reply from 192.168.9.123: bytes=32 time=12ms TTL=64 Reply from 192.168.9.123: bytes=32 time=16ms TTL=64 Reply from 192.168.9.123: bytes=32 time=16ms TTL=64 Reply from 192.168.9.123: bytes=32 time=17ms TTL=64 Reply from 192.168.9.123: bytes=32 time=30ms TTL=64 Reply from 192.168.9.123: bytes=32 time=16ms TTL=64 Reply from 192.168.9.123: bytes=32 time=13ms TTL=64 Request timed out. Reply from 192.168.9.123: bytes=32 time=14ms TTL=64 Reply from 192.168.9.123: bytes=32 time=15ms TTL=64 Reply from 192.168.9.123: bytes=32 time=13ms TTL=64 Reply from 192.168.9.123: bytes=32 time=9ms TTL=64 Reply from 192.168.9.123: bytes=32 time=16ms TTL=64 Request timed out. Reply from 192.168.9.123: bytes=32 time=130ms TTL=64 Reply from 192.168.9.123: bytes=32 time=9ms TTL=64 Reply from 192.168.9.123: bytes=32 time=692ms TTL=64 Request timed out. Reply from 192.168.9.123: bytes=32 time=58ms TTL=64 Request timed out. Reply from 192.168.9.123: bytes=32 time=19ms TTL=64 Reply from 192.168.9.123: bytes=32 time=10ms TTL=64 pascal!'s Profile: http://forums.slimdevices.com/member.php?userid=64395 View this thread: http://forums.slimdevices.com/showthread.php?t=115095 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
