| Deutsch English Français Italiano |
|
<tt1qil-vmrj2.ln1@zbox.fritz.box> View for Bookmarking (what is this?) Look up another Usenet article |
Path: news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Thomas Kempkes <news@familie-kempkes.de>
Newsgroups: comp.sys.raspberry-pi
Subject: Re: Bookworm updates killing WiFi
Date: Tue, 24 Jun 2025 09:49:49 +0200
Lines: 32
Message-ID: <tt1qil-vmrj2.ln1@zbox.fritz.box>
References: <103bott$1adnt$1@dont-email.me>
X-Trace: individual.net 2tzDwJAGOySBBaTvVUvxaw3sfotwGC1SjXEWCb8/hUcKSwuLMA
X-Orig-Path: not-for-mail
Cancel-Lock: sha1:x8Impij3aCcil0y7rY/K5iQYkwA= sha1:KIYX12RMnL9CkqzezslMSMhdjLw= sha256:oMIbfvZdgAW5XE6id+3a7fovjuCIULboIP0t3fMM5Cg=
X-No-HTML: yes
X-No-Archive: yes
User-Agent: tin/2.4.4-20191224 ("Millburn") (Linux/5.4.0-211-generic (x86_64))
bp@www.zefox.net 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.