INTL 3:770/1 3:770/3
REPLYADDR chris@internal.net
REPLYTO 3:770/3.0 UUCP
MSGID: 2ac5e3d0
REPLY: 249ffab1
PID: SoupGate-Win32 v1.05
On 15/09/2024 at 11:16, The Natural Philosopher wrote:
> On 14/09/2024 22:25, Chris Elvidge wrote:
>> On 14/09/2024 at 19:32, The Natural Philosopher wrote:
>>> On 14/09/2024 16:38, Chris Elvidge wrote:
>>>> On 14/09/2024 at 15:37, The Natural Philosopher wrote:
>>>>> On 14/09/2024 11:33, The Natural Philosopher wrote:
>>>>>> On 14/09/2024 08:12, Pancho wrote:
>>>>>
>>>>>
>>>>>> Prolly easier to get an HDMI and USB adapter and pop a monitor and
>>>>>> keyboard on it.
>>>>>> I spent hours yesterday googling for PI ZERO 2 W WIFI DISCONNECTS
>>>>>> and everybody has the same problem. Must be 1000 posts out there.
>>>>>> It seems that the 2W is basically a piece of shit. People try SD
>>>>>> cards that work perfectly in the Zero W, but don't work in the 2W.
>>>>>>
>>>>>> I tried every methodology suggested, and its still doing it.
>>>>>>
>>>>>> I am tempted to buy the old version, two of which have been
>>>>>> faultlessly connected to the same wifi point for several years....
>>>>>>
>>>>>> Unfortunately I soldered a header block to this one so I can't
>>>>>> return it. Bin job probably.
>>>>>>
>>>>>>
>>>>> Well another day of configgling
>>>>>
>>>>> Tried to make it talk to a different wifi point. Bricked it.
>>>>> Reinstalled OS lite and started setting up. (again!)
>>>>>
>>>>> The Pi ZERO 2W apparently uses a different wifi chip - SYMANTEC
>>>>> SYN43436, not the old BROADCOMM BCM43438
>>>>
>>>> Where did you get this info?
>>>> On mine module cfg80211 is loaded by brcmfmac (broadcom?).
>>>>
>>> Apparently there are two possible chips. Broadcomm and symantec
>>> I THINK I have the broadcomm
>>>
>>> dmesg | grep brcmfmac
>>> [ 12.461334] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
>>> [ 12.467893] brcmfmac: brcmf_fw_alloc_request: using
>>> brcm/brcmfmac43430-sdio for chip BCM43430/1
>>> [ 12.468806] usbcore: registered new interface driver brcmfmac
>>> [ 12.731339] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob
>>> available (err=-2)
>>> [ 12.732079] brcmfmac: brcmf_c_preinit_dcmds: Firmware: *
>>> BCM43430/1* wl0: Jun 14 2023 07:27:45 version 7.45.96.s1 (gf031a129)
>>> FWID 01-70bd2af7 es7
>>> [ 15.888471] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save
>>> enabled
>>>
>>> That's exactly the same as my 'working perfectly' Pi Zero 1W...
>>>
>>> So its probably not that.
>>>
>>>
>>>
>>>> Model : Raspberry Pi Zero 2 W Rev 1.0
>>>> Revision : 902120
>>>> Raspberry Pi OS (bookworm, full); kernel 6.6.47+rpt-rpi-v8
>>>>
>>>> No problems with wifi over the last few weeks.
>>>> Wavlink M30HG4.V5030.191116
>>>>
>>>> Now bluetooth, there's a whole nother story!!
>>>>
>>> Disabled that baby straight off.
>>>
>>> Its very strange.
>>>
>>> Its 64 bit instead of 32 bit.
>>>
>>> But that's all that seems radically different hardware wise.
>>>
>>> Again some rumours are that the zero 2 being power hungry may be
>>> loading the PSU more.
>>>
>>> But in the middle of the night? Doing NOTHING?
>>>
>>
>> I started with 32bit lite but swapped to 64bit full just to see what
>> happened. I had had no problems with 32bit lite (except bluetooth, see
>> above). However I haven't stopped bluetooth, just don't (as yet) use
>> it. My dmesg looks much the same as yours.
>>
>> I feed mine from a 2.4 amp source.
>> But I also have USB3 hub + ethernet port feeding 256Gb SSD and USB
>> speaker.
>>
>
> Mmm. I was feeding mine, on the basis that it was drawing less than half
> an amp, from a very small PSU I normally use for Pi Picos.
>
> I swapped that for a generic phone charger PSU and added a line that
> someone suggested to config.txt:
>
> over_voltage=2
>
> Its been stable doing an rsync backup of itself overnight, and is still
> up this morning.
>
> Power saving is in fact on, on the wifi interface.
>
> Journalctl reveals no entries to do with wifi AT ALL since 8 o clock
> yesterday evening when it was rebooted.
>
> I think the key was in realising that on mine at least the wifi hardware
> was the same as on the 32 bit zeros.
>
> So if they connected to my old POS Netgear ex ADSL router transgendered
> into a wifi access point, so should this one.
>
> I will probably try reverting to the PICO power supply and see if that
> makes any difference.
>
> And get a voltmeter or scope on the supply rails.
>
> Maybe there is trash...
>
>
>
>
>
Perhaps you could use vcgencmd to look at/monitor various internals.
E.g. vcgencmd [measure_temp|measure_clock core|measure_volts]
I think over_voltage is a red herring, it limits the CPU/GPU upper
voltage doesn't set it (AFAICS).
https://www.raspberrypi.com/documentation/computers/config_txt.html
--
Chris Elvidge, England
SUBSTITUTE TEACHERS ARE NOT SCABS
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
SEEN-BY: 10/0 1 90/1 103/705 105/81 106/201 124/5016 129/305 153/757
SEEN-BY: 153/7715 218/0 1 601 700 840 870 930 220/70 221/1 6 360 226/17
SEEN-BY: 226/30 100 227/114 229/110 111 114 200 206 300 317 400 426
SEEN-BY: 229/428 470 550 616 664 700 240/1120 266/512 267/800 282/1038
SEEN-BY: 291/111 292/854 301/1 113 812 310/31 320/219 322/757 335/364
SEEN-BY: 341/66 342/200 396/45 460/58 633/280 712/848 770/1 3 100
SEEN-BY: 770/330 340 772/210 220 230 5020/400 1042 5058/104 5075/35
PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426
|
