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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 23/06/2025 15:38, [email protected] wrote:

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...



--
“it should be clear by now to everyone that activist environmentalism
(or environmental activism) is becoming a general ideology about humans,
about their freedom, about the relationship between the individual and
the state, and about the manipulation of people under the guise of a
'noble' idea. It is not an honest pursuit of 'sustainable development,'
a matter of elementary environmental protection, or a search for
rational mechanisms designed to achieve a healthy environment. Yet
things do occur that make you shake your head and remind yourself that
you live neither in Joseph Stalin’s Communist era, nor in the Orwellian utopia of 1984.”

Vaclav Klaus

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 23/06/2025 at 15:38, [email protected] wrote:

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

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.


--
Chris Elvidge, England
I WILL NOT SPANK OTHERS

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, 23 Jun 2025 18:49:44 +0100, The Natural Philosopher wrote:

I wonder if in the absence of a controlling tty, the default behaviour
is to overwrite config files...

Not a chance.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

[email protected] wrote:

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

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: https://www.heise.de/ratgeber/Raspi-mit-Debian-verliert-Internet-Verbindung-9998575.html


--
The computer revolution is over. The computers won.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 23/06/2025 22:39, Chris Elvidge wrote:

On 23/06/2025 at 15:38, [email protected] wrote:

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

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.

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


--
“I know that most men, including those at ease with problems of the greatest complexity, can seldom accept even the simplest and most
obvious truth if it be such as would oblige them to admit the falsity of conclusions which they have delighted in explaining to colleagues, which
they have proudly taught to others, and which they have woven, thread by thread, into the fabric of their lives.”

― Leo Tolstoy

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 24/06/2025 at 08:49, Thomas Kempkes wrote:

[email protected] wrote:

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

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: https://www.heise.de/ratgeber/Raspi-mit-Debian-verliert-Internet-Verbindung-9998575.html

Hasn't worked here. Back to 11, I suppose.


--
Chris Elvidge, England
I WILL NOT SAY "SPRINGFIELD" JUST TO GET APPLAUSE

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 23/06/2025 22:39, Chris Elvidge wrote:

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.

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 23/06/2025 22:39, Chris Elvidge wrote:

On 23/06/2025 at 15:38, [email protected] wrote:

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

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.

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)