I have a Virtual Machine with RPIOS64 Bookworm (vanilla Debian arm64 6.1. kernel) that also is remarkably 'slow' to show network connection. It is not dist-upgraded in-place like other computers/instances where I have not noticed it. This VM is just to see what RPIOS64 is different from Debian, so I haven't looked at it as it is not a problem for my real RPI3/4.I don't know if this is a Trixie only issue, but I've noticed this a few times now. I just updated my Trixie build with a `sudo apt update` and `sudo apt upgrade` so I have the latest. My console / tty (monitor connected to the Raspberry Pi 5) shows the login prompt. It first shows a self signed IP address 169.254.200.241 then once it get's an IP address, it re-prints the console after the login prompt.I hadn't noticed that before. It's a "bug" but only lightly so. It's more of just an annoyance. LOL.Code:
Debian GNU/Linux 13 HOSTNAME tty1MY IP address is 169.254.200.241 fe80::8ffe:91c:80f0:991eHOSTNAME login:Debian GNU Linux 13 HOSTNAME tty1My IP address is 192.168.0.173 fe80:8ffe:91c:80f0:991eHOSTNAME login:
I did setup some iSCSI storage systems yesterday with RPI4B-8GB (RPiOS64 Trixie) as target of a 300GiB partition on SSD. So for that it is good/nice it can do restart within 120 seconds, at least IP dis-connectivity not lasting longer than that. So I will need to look into the journal:
Code:
journalctl --boot -u NetworkManager.service Code:
Sep 16 13:57:50 raspi3 systemd[1]: Starting NetworkManager.service - Network Manager...[...]Sep 16 13:57:50 raspi3 NetworkManager[804]: <info> [1758023870.5037] monitoring ifupdown state file '/run/network/ifstate'.Sep 16 13:58:15 raspi3 NetworkManager[804]: <info> [1758023895.5267] hostname: hostname: hostnamed not used as proxy creation failed with: Error calling StartServiceByName for org.freedesktop.hostname1: Timeo>[...]Sep 16 13:58:48 raspi3 NetworkManager[804]: <info> [1758023928.6682] device (vnet8): Activation: successful, device activated.This is just an example where to look for yourself. It might be the specific interaction with your router and/or LAN/network. I would not be surprised it a router (DHCP-server) shows several interactions or rejects before success that could be avoided.
Statistics: Posted by redvli — Wed Sep 17, 2025 7:05 am