INTL 3:770/1 3:770/3   
   REPLYADDR bp@www.zefox.net   
   REPLYTO 3:770/3.0 UUCP   
   MSGID:  4eacbdbc   
   REPLY:  7c51f413   
   PID: SoupGate-Win32 v1.05   
   The Natural Philosopher  wrote:   
   > On 29/11/2024 23:13, bp@www.zefox.net wrote:   
   >> The Natural Philosopher  wrote:   
   >>> On 27/11/2024 20:22, bp@www.zefox.net wrote:   
   >>>> It turns out that letting the system stand for ~4 hrs reproduced some   
   >>>> of the problems. Ping times with both interfaces up eventually rose to   
   >>>> 7-10 ms but didn't fail completely. Several of the ssh connections   
   >>>> open from the Pi5 to other hosts either froze or disconnected.   
   >>>   
   >>> That's exactly what I got with an inadequate PSU.   
   >>>   
   >>   
   >> Since a software update this morning it appears that both interfaces   
   >> are co-existing without problems. Re-checking the supply voltage   
   >> reveals 5.05 volts, 10 mV below the value seen earlier, measured on   
   >> the GPIO header.   
   >>   
   > I got sag when USB was drawing current I think.   
   >   
   >> That's not to claim the problem is resolved: It took about four hours   
   >> to misbehave in the previous instance, now it might merely take longer.   
   >>   
   > Fingers crossed.   
   >   
   >> uname -a now reports   
   >> Linux raspberrypi 6.6.62+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.62-1+rpt1   
   (2024-11-25) aarch64 GNU/Linux   
   >>   
      
   Through this morning the networking functioned normally. Then I noticed a   
   batch of new system updates. After installing and rebooting the trouble   
   returned, slightly worse. Now the internal wifi simply fails to connect.   
   The external usb-wifi adapter works as expected. I'm again seeing failures   
   reported for networkmanager-wait-online, but don't understand what they mean.   
      
   Looking through journalctl output, filtered for wlan0, I see a torrent of   
   output, some of which states:   
      
   Nov 30 09:19:00 raspberrypi NetworkManager[852]:   [1732987140.7820]   
   device (wlan0): Activation: (wifi) association took too long   
   Nov 30 09:19:00 raspberrypi NetworkManager[852]:   [1732987140.7821]   
   device (wlan0): state change: config -> failed (reason 'no-secrets',   
   sys-iface-state: 'managed')   
   Nov 30 09:19:00 raspberrypi NetworkManager[852]:   [1732987140.7826]   
   device (wlan0): Activation: failed for connection 'Wi-Fi connection 1'   
   Nov 30 09:19:00 raspberrypi NetworkManager[852]:   [1732987140.7828]   
   device (wlan0): state change: failed -> disconnected (reason 'none',   
   sys-iface-state: 'managed')   
      
   The mismash of reasons looks inconsistent to me.   
      
   The only changes have been disconnecting and reconnecting the usb-wifi   
   dongle, right now it's connected and the gpio is showing 5.08 volts. I   
   suspect the small fluctuations seen reflect line voltage drift more   
   than load.   
      
   In any case, I've now navigated successfully from the frying pan back   
   to the fire 8-)   
      
   Thanks for reading,   
      
   bob prohaska   
      
   --- SoupGate-Win32 v1.05   
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)   
   SEEN-BY: 4/0 19/10 88/0 90/0 105/81 106/201 128/187 129/305 153/757   
   SEEN-BY: 153/7715 218/700 840 220/70 221/1 6 360 226/17 30 100 227/114   
   SEEN-BY: 229/110 111 114 200 206 300 317 400 426 428 470 550 616 664   
   SEEN-BY: 229/700 266/512 267/800 282/1038 291/111 292/854 301/1 310/31   
   SEEN-BY: 320/219 322/757 335/364 341/66 342/200 396/45 460/58 633/280   
   SEEN-BY: 712/848 770/1 3 100 330 340 772/210 220 230 880/1 900/0 102   
   SEEN-BY: 900/106 902/0 19 26 930/1 5020/400 5075/35   
   PATH: 770/3 1 218/840 221/6 341/66 902/26 229/426