INTL 3:770/1 3:770/3
REPLYADDR tnp@invalid.invalid
REPLYTO 3:770/3.0 UUCP
MSGID: 530c2839
REPLY: 5612801f
PID: SoupGate-Win32 v1.05
On 16/09/2024 21:19, druck wrote:
> On 14/09/2024 19:32, The Natural Philosopher wrote:
>> [ 15.888471] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save
>> enabled
>
> You may find it is slightly more reliable with power saving disabled.
>
I have done this. I think it is more stable. It is more appropriate in a
server anyway
> To disable temporarily use:-
>
> sudo /sbin/iw dev wlan0 set power_save off
>
> To make persistent create a file called
> /etc/udev/rules.d/71-wifi_power_save_off.rules containing the line:-
>
I used nmcli I think...yes. I have recorded everything I have done on
this implementation in case I have to do it again.
sudo nmcli c modify [SSID] 802-11-wireless.powersave 2
I had to do it for the other SSID as well.
I made a decision - as with systemd,- that in NetworkManager was the
'supported' way to do stuff, I might as well [learn to] use it.
I am less interested in learning the more recondite areas of the distro,
than achieving a stable platform on which to build an application.
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="brcmfmac", KERNEL=="wlan0",
> RUN="/sbin/iw dev wlan0 set power_save off"
>
> ---druck
I am not saying 'solved' BUT since using the bigger power supply, it
hasn't *dropped* at all, however there are still the odd reconnects that
occasionally take too long...on one wifi point. Oddly I have two now
configured and after retrying the first one a few times it decided to
try the one literally inches away and has been solid on that one ever
since.
And interesting discovery was that the configuration of a static address
applies to one SSID only - a 'connection' in Network Manager parlance -
not to the *interface* wlan0..
Which is why I thought it had bricked when I changed wifi access points
on the fly. The next time I did that I realised it was now back on
DHCP...and was available on a different IP address...
Anyway the final conclusions seem to be :
1. The ZERO 2W is hungrier for electrons than the old ZERO W.
2. The symptoms of starvation are evident first in the WiFi hardware.
The CPU and nearly everything else is fed from 3.3V, 1.8V and 1.3V
downconverted supplies. No documentation showing what voltage was used
by the WiFi chip exists that I could find.
3. On at least my model, whilst the name of the company may have
changed, the old Broadcomm wifi chip and driver is still used.
4. Apart from having to use journalctl, it is unusually not possible to
blame systemd for these issues.
5. Whilst a chinesium USB source *may* be able to deliver the quoted
current, it is not necessarily able to deliver it in a noise free or
voltage-retaining fashion.
I never got round to putting a meter or a scope on the thing - it's a
bit awkward especially with a 'hat' on.
Interestingly the Pi PICO W uses a chip that works down to 3V.
Now I have achieved stability, the unit will go to a different location
to further development where it will naturally connect to the original
POS wifi point.
But I now have a microwave with a burnt out magnetron to fix...
Sigh.
--
The lifetime of any political organisation is about three years before
its been subverted by the people it tried to warn you about.
Anon.
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
SEEN-BY: 1/19 16/0 19/37 80/1 90/1 105/81 106/201 123/130 129/305
SEEN-BY: 134/100 142/104 153/135 143 148 151 757 7715 203/0 218/700
SEEN-BY: 218/840 220/70 221/1 6 242 360 226/17 30 100 227/114 229/110
SEEN-BY: 229/111 114 200 206 300 317 400 426 428 470 550 616 664 700
SEEN-BY: 230/0 240/5832 266/512 267/800 280/5003 282/1038 291/111
SEEN-BY: 292/854 301/1 310/31 320/119 219 319 2119 322/757 762 325/304
SEEN-BY: 335/364 341/66 342/200 396/45 423/81 460/58 633/280 712/848
SEEN-BY: 770/1 3 100 330 340 772/210 220 230 5020/400 5053/58 5058/104
SEEN-BY: 5075/35
PATH: 770/3 1 153/757 221/6 1 320/219 229/426
|
