I've been complaining here about WiFi problems for some time and it's finally dawned on me that rfkill is a frequent visitor to the scene.
Is it plausible that running the "updates available" routine somehow un-sets the WiFi region selection? The selections look unchanged, but re-running the configuration seems to fix WiFi operation.
Thanks for reading!
bob prohaska
Interesting you should say that. My last automatic update killed my BIND configuration and also my DVB configuration.
Or something. DVB hat disappeared until I explicitly loaded its driver using dtoverlay= etc in config.txt. I never needed that before.
I wonder if in the absence of a controlling tty, the default behaviour is to overwrite config files...
After much pissing about with Bookworm + Pi Zero 2W - losing wifi regularly - even tried replacing NetworkManager with dhcpcd - I went back to Bullseye (11). No problems at all in the last week. No NetworkManager (well disabled) bur dhcpcd working.
Not a chance.
One german it site stated they had problems with the wifi stability after the update to bookworm. It was the avahi-daemon for them, which showed with log entried like
Sep 26 10:37:41 frigate avahi-daemon[651]: Withdrawing address record for 2003:aa:bb:ccc:feed:dead:beef:be61 on wlan0.
Their fix was to just disable avahi-daemon and the problem was gone for good:
sudo systemctl disable avahi-daemon.socket sudo systemctl disable avahi-daemon
BYe Thomas
PS: Original link:
I had that, but stuck with bookworm and put a better PSU on it.
Let see...how long its been up...
$ uptime 10:12:59 up 35 days, 22:31, 1 user, load average: 0.09, 0.02, 0.01
Essentially since the last power cut
Hasn't worked here. Back to 11, I suppose.
As I mentioned in one of my posts; 512MB Pi's such as the Zero 2W and
3A+ seem to have problems running 32 bit Bookworm that none of the 1MB do.All my Pi's with 4GB or more are running 64 bit Bookworm and they seem to be OK, except for Network Manager occasionally not connecting to WiFi if they have also have Ethernet.
---druck
I have found Bookworm on a Pi ZeroW to be less than confidence inspiring.
I have 2 i7 laptops, 2 Xeon VMs and an i5 desktop all running Bookworm without problems. Runs just like any Debian distro should and all were upgraded in situ from Bullseye without issue. Follow the instructions to the letter and everything just worked.
The Pi ZeroW was updated the same way which is against the Raspbian/PIOS guide (can't remember what it is called any more). The upgrade worked but it turned to be a mishmash of old and NetworkManager networking. I don't know or care why it ended up this way, I simply restarted from a clean Bookworm image and made changes etc. to get it the way I like.
Since then it's been anything but great. Sure what is installed works and stays working but every update/upgrade feels like juggling hand grenades with greasy hands. I now expect something to fail every upgrade and that when it actually works I get a pleasant surprise.
Last update had all sorts of initramfs errors now fixed.
Bookworm behaves perfectly on amd64 hardware.
YMMV
Have something to add? Share your thoughts — no account required.
Ask the community — no account required