Agreed - if I can get a wired connection, that is preferrable (if throughput matters - I won't bother plugging in an ethernet cable to transfer some small amount of data to my laptop).
However, there is nothing inherent in wifi that explains the observed problems with the two adapters on one machine.
cu Michael
TCP/IP / 802 is well enough designed to make this sort of stuff work as well as it can...
Smart chaps with beards and tweed jackets have spent their whole summers trying to make it work like that, and it dies.
Shame they never get enough time to get laid and pass their genes on...
There probably is, we just do not know what it is...
All I know is that my onboard Pi Wifi problems were resolved with a better PSU.
"I'm a Linux geek. My machines crash about as often as I get laid."
Time to re-watch
cu Michael
Love that movie.
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.
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.
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
Thanks for writing,
bob prohaska
>
I got sag when USB was drawing current I think.
Fingers crossed.
Reminds me of that old BT advert where an old lady discovers her phone isn't working. Cut to engineers in vans climbing poles, remaking connections and so on, cut to old lady lifting the handset 'Oh, its fixed itself!'...
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]: <warn> [1732987140.7820] device (wlan0): Activation: (wifi) association took too long Nov 30 09:19:00 raspberrypi NetworkManager[852]: <info> [1732987140.7821] device (wlan0): state change: config -> failed (reason 'no-secrets', sys-iface-state: 'managed') Nov 30 09:19:00 raspberrypi NetworkManager[852]: <warn> [1732987140.7826] device (wlan0): Activation: failed for connection 'Wi-Fi connection 1' Nov 30 09:19:00 raspberrypi NetworkManager[852]: <info> [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
I find it hard to disagree. ;)
I have Ethernet connections running into both my bedroom and living room. The wi-fi is fine for basic web browsing (not including watching videos), but anything more traffic-intensive, and I plug the nearest handy cable into my laptop.
Have something to add? Share your thoughts — no account required.
Ask the community — no account required