Liste des Groupes | Revenir à cs raspberry-pi |
Apolgies for the mixup. I meant to report that the behavior ofThat does sound like some of the Network Manager behaviour I've experienced on a couple of Linux Mint laptops.
the internal wifi seems to be affected by both use of wired ethernet
and use of usb wifi. The internal wifi connected spontaneously after
connecting either a wired ethernet cable or a usb-wifi dongle. Alas,
that behavior is not repeatable. In the present config the usb-wifi
dongle connects, I can't get the internal wifi to connect though
it does detect the access point.
There does seem to be a large discrepancy between wlan0 and wlan1The WiFi antenna on the motherboard is very small, as long as it's a normal sized USB WiFi stuck and not one of the tiny nub ones, it's antenna will be far bigger.
signal strength: wlan1 reports 93-96%, internal wlan0 only 79%.
Prior to the recent upgrades (but still bookworm) wlan0 reporting
more than about 70% gave a decent connection.
So it's a vanilla install using NetWork Manager and not an upgrade from Bullseye as I've been doing to retain the old well working DHCPCD and WPA supplicant networking.Did you start with a fresh Bookworm image?Initialy, yes. It was customized on microSD,
moved to a USB hard disk using Raspberry Pi Imager.
It can be, but not usually to networking.What have you installed since?Nothing apart from supplied upgrades, but I am using wayland, which
has been described as troublesome.
Normally on Pi's I'd be looking at a hardware issue to do with the power supply and the amount of USB devices connected, but I think you are right in this case, and it's Network Manager getting confused about what interfaces are available.What other hardware is connected?One powered hub, running the added usb-wifi dongle
(old Ralink RT5370) plus an old Dell keyboard and mouse..
Are you using an official power supply?No, but the Pi5 reads 5.07 volts at the GPIO header.
As this saga plays out the USB-Wifi dongle seems to
work quite well. Maybe it's all down to the better
signal strength. Because the problem appeared shortly
after an OS upgrade I tended to blame that. Perhaps
I'm mistaken.
Les messages affichés proviennent d'usenet.