Hi all,
I installed HA os on a raspberry pi5. The install was fine and HA works, but I get on the screen connected to my pi5 the message macb 1f00100000.ethernet end0: not whole frame pointed by descriptor. My pi5 is connected directly to my internet box with an ethernet cable. I thought it was a pi5 problem. Of course everything is updated, but my screen continues to print lines and lines of the same message. Then after a while, HA doesn’t work properly and I have to reboot. I thought that this issue came from my pi5. I used another one that was new and I got the same message on lines and lines. Is it an issue of HA os? How to fix the problem? Does anyone get the same message?
Thanks for your help
Kind regards
C
tom_l
June 2, 2025, 10:23am
2
Seems to be a problem with the pi5 ethernet drivers.
opened 07:53PM - 06 Sep 24 UTC
closed 05:40AM - 12 Jan 25 UTC
bug
board/raspberrypi
stale
### Describe the issue you are experiencing
### The problem
Since I am on `2… 024.8.x`, I am seeing my ha CLI screen being flooded with error message that looks like the following:
```
macb 1f00100000.ethernet eth0: not whole frame pointed by descriptor
```
I would love to know if this needs attention. I am not seeing any side effect in regular usage so far.
My online exploration tells me that this is connected to the config of the network adapter and if I increase the rx buffer size this should be okay. I wanted to check here before I go down the process of enabling SSH and doing these changes, which may or may not persist through updates.
### What operating system image do you use?
rpi5-64 (Raspberry Pi 5 64-bit OS)
### What version of Home Assistant Operating System is installed?
6.6.31-haos-raspi
### Did the problem occur after upgrading the Operating System?
Yes
### Hardware details
Running on Pi5 with wired ethernet to my TP-Link ER605 router.
### Steps to reproduce the issue
-
### Anything in the Supervisor logs that might be useful for us?
```txt
-
```
### Anything in the Host logs that might be useful for us?
```txt
-
```
### System information
## System Information
version | core-2024.8.3
-- | --
installation_type | Home Assistant OS
dev | false
hassio | true
docker | true
user | root
virtualenv | false
python_version | 3.12.4
os_name | Linux
os_version | 6.6.31-haos-raspi
arch | aarch64
timezone | Asia/Calcutta
config_dir | /config
<details><summary>Home Assistant Cloud</summary>
logged_in | true
-- | --
subscription_expiration | September 26, 2024 at 5:30 AM
relayer_connected | true
relayer_region | ap-southeast-1
remote_enabled | true
remote_connected | true
alexa_enabled | false
google_enabled | false
remote_server | ap-southeast-1-2.ui.nabu.casa
certificate_status | ready
instance_id | 8b1ce8c77a6e4f01a24fbf0a36ba482a
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok
</details>
<details><summary>Home Assistant Supervisor</summary>
host_os | Home Assistant OS 13.1
-- | --
update_channel | stable
supervisor_version | supervisor-2024.08.0
agent_version | 1.6.0
docker_version | 26.1.4
disk_total | 228.5 GB
disk_used | 8.2 GB
healthy | true
supported | true
host_connectivity | true
supervisor_connectivity | true
ntp_synchronized | true
virtualization |
board | rpi5-64
supervisor_api | ok
version_api | ok
installed_addons | Matter Server (6.4.2), Terminal & SSH (9.14.0), AdGuard Home (5.1.1), UniFi Network Application (3.2.0)
</details>
<details><summary>Dashboards</summary>
dashboards | 5
-- | --
resources | 0
views | 4
mode | storage
</details>
<details><summary>Recorder</summary>
oldest_recorder_run | August 29, 2024 at 3:13 PM
-- | --
current_recorder_run | September 3, 2024 at 1:47 PM
estimated_db_size | 145.27 MiB
database_engine | sqlite
database_version | 3.45.3
</details>
### Additional information
I am running only AdGuard as an additional addon that serves DNS.
opened 03:56PM - 15 Oct 24 UTC
### Describe the bug
My raspberry Pi 5 sometimes (about one in seven) boots has… no network connection. The Rpi receives an IP address from the DHCP server, but cannot ping any IP address from it. Interestingly, it is possible to ping the Rpi's IP address. The problem will be solved by disconnecting and then connecting the LAN cable or sudo ip link set end0 down and sudo ip link set end0 up. It's totally frustrating. I'm using Raspbian Bookworm with the latest update with Network manager. I know a similar problem was solved with Raspberry Pi 4 by adding genet.force_reneg=n to cmdline.txt. Unfortunately this doesn't work. Can anyone advise how to resolve this?
### Steps to reproduce the behaviour
I turn on or reboot the RPI5.
Sometimes the RPI does not have LAN access.
If this happens, the RPI will receive an IP address from the DHCP server and can be pinged from the router. It is not possible to ping any IP address from the RPI5.
Disconnecting and reconnecting the LAN cable will solve the problem. Or using sudo ip link set end0 down and sudo ip link set end0 up.
### Device (s)
Raspberry Pi 5
### System
cat /etc/rpi-issue
Raspberry Pi reference 2024-03-15
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, f19ee211ddafcae300827f953d143de92a5c6624, stage2
vcgencmd version
2024/10/10 00:36:47
Copyright (c) 2012 Broadcom
version 0e63dd5e (release) (embedded)
uname -a
Linux raspi5 6.6.44-v8+ #1789 SMP PREEMPT Mon Aug 5 15:22:52 BST 2024 aarch64 GNU/Linux
### Logs
ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: end0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 2c:cf:67:5a:36:5b brd ff:ff:ff:ff:ff:ff
inet 192.168.100.180/24 brd 192.168.100.255 scope global dynamic noprefixroute end0
valid_lft 42914sec preferred_lft 42914sec
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 2c:cf:67:5a:36:5c brd ff:ff:ff:ff:ff:ff
ping 192.168.100.1
PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data.
From 192.168.100.180 icmp_seq=10 Destination Host Unreachable
ip route
default via 192.168.100.1 dev end0 proto dhcp src 192.168.100.180 metric 20100
192.168.100.0/24 dev end0 proto kernel scope link src 192.168.100.180 metric 100
dmesg | grep end0
[ 1.047081] macb 1f00100000.ethernet end0: renamed from eth0
[ 5.046914] macb 1f00100000.ethernet end0: PHY [1f00100000.ethernet-ffffffff:01] driver [Broadcom BCM54213PE] (irq=POLL)
[ 5.046925] macb 1f00100000.ethernet end0: configuring for phy/rgmii-id link mode
[ 9.150906] macb 1f00100000.ethernet end0: Link is Up - 1Gbps/Full - flow control tx
dmesg | grep eth0
[ 0.698702] macb 1f00100000.ethernet eth0: Cadence GEM rev 0x00070109 at 0x1f00100000 irq 112 (2c:cf:67:5a:36:5b)
[ 1.047081] macb 1f00100000.ethernet end0: renamed from eth0
sudo journalctl -e -f -u NetworkManager.service
říj 15 17:42:07 raspi5 systemd[1]: Starting NetworkManager.service - Network Manager...
říj 15 17:42:07 raspi5 NetworkManager[896]: <info> [1729006927.8410] NetworkManager (version 1.42.4) is starting... (boot:4edd5f59-d5c3-4290-9682-c5fcf3adc2ba)
říj 15 17:42:07 raspi5 NetworkManager[896]: <info> [1729006927.8411] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity-debian.conf, no-mac-addr-change.conf)
říj 15 17:42:07 raspi5 NetworkManager[896]: <info> [1729006927.8454] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
říj 15 17:42:07 raspi5 systemd[1]: Started NetworkManager.service - Network Manager.
říj 15 17:42:07 raspi5 NetworkManager[896]: <info> [1729006927.8701] manager[0x55b29b5000]: monitoring kernel firmware directory '/lib/firmware'.
říj 15 17:42:07 raspi5 NetworkManager[896]: <info> [1729006927.8701] monitoring ifupdown state file '/run/network/ifstate'.
říj 15 17:42:07 raspi5 NetworkManager[896]: <info> [1729006927.8910] hostname: hostname: using hostnamed
říj 15 17:42:07 raspi5 NetworkManager[896]: <info> [1729006927.8911] hostname: static hostname changed from (none) to "raspi5"
říj 15 17:42:07 raspi5 NetworkManager[896]: <info> [1729006927.8966] dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink (auto)
říj 15 17:42:07 raspi5 NetworkManager[896]: <info> [1729006927.8981] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/platform/axi/1001100000.mmc/mmc_host/mmc1/mmc1:0001/mmc1:0001:1/ieee80211/phy0/rfkill1) (driver brcmfmac)
říj 15 17:42:07 raspi5 NetworkManager[896]: <info> [1729006927.8984] manager[0x55b29b5000]: rfkill: Wi-Fi hardware radio set disabled
říj 15 17:42:07 raspi5 NetworkManager[896]: <info> [1729006927.8984] manager[0x55b29b5000]: rfkill: WWAN hardware radio set enabled
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.0543] Loaded device plugin: NMAtmManager (/usr/lib/aarch64-linux-gnu/NetworkManager/1.42.4/libnm-device-plugin-adsl.so)
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.0701] Loaded device plugin: NMTeamFactory (/usr/lib/aarch64-linux-gnu/NetworkManager/1.42.4/libnm-device-plugin-team.so)
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.0748] Loaded device plugin: NMWwanFactory (/usr/lib/aarch64-linux-gnu/NetworkManager/1.42.4/libnm-device-plugin-wwan.so)
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.0839] Loaded device plugin: NMBluezManager (/usr/lib/aarch64-linux-gnu/NetworkManager/1.42.4/libnm-device-plugin-bluetooth.so)
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.0920] Loaded device plugin: NMWifiFactory (/usr/lib/aarch64-linux-gnu/NetworkManager/1.42.4/libnm-device-plugin-wifi.so)
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.0925] manager: rfkill: Wi-Fi disabled by radio killswitch; disabled by state file
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.0926] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.0927] manager: Networking is enabled by state file
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.1042] settings: Loaded settings plugin: ifupdown ("/usr/lib/aarch64-linux-gnu/NetworkManager/1.42.4/libnm-settings-plugin-ifupdown.so")
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.1043] settings: Loaded settings plugin: keyfile (internal)
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.1044] ifupdown: management mode: unmanaged
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.1044] ifupdown: interface-parser: parsing file /etc/network/interfaces
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.1044] ifupdown: interface-parser: finished parsing file /etc/network/interfaces
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.1423] dhcp: init: Using DHCP client 'internal'
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.1434] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.1470] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.1476] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.1485] device (lo): Activation: starting connection 'lo' (fa31e53f-7d8c-4a5a-8223-623068cd7bea)
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.1500] manager: (end0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.1504] device (end0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.1672] device (wlan0): driver supports Access Point (AP) mode
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.1680] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.1683] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.1780] device (lo): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.1783] device (lo): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.1785] device (lo): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.1793] device (lo): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.1853] modem-manager: ModemManager available
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.1956] device (lo): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.1959] device (lo): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
říj 15 17:42:08 raspi5 NetworkManager[896]: <info> [1729006928.1965] device (lo): Activation: successful, device activated.
říj 15 17:42:12 raspi5 NetworkManager[896]: <info> [1729006932.2622] device (end0): carrier: link connected
říj 15 17:42:12 raspi5 NetworkManager[896]: <info> [1729006932.2626] device (end0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
říj 15 17:42:12 raspi5 NetworkManager[896]: <info> [1729006932.2633] policy: auto-activating connection 'LAN' (2d47b88d-061d-4612-87bb-0bc3164bb538)
říj 15 17:42:12 raspi5 NetworkManager[896]: <info> [1729006932.2639] device (end0): Activation: starting connection 'LAN' (2d47b88d-061d-4612-87bb-0bc3164bb538)
říj 15 17:42:12 raspi5 NetworkManager[896]: <info> [1729006932.2639] device (end0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
říj 15 17:42:12 raspi5 NetworkManager[896]: <info> [1729006932.2641] manager: NetworkManager state is now CONNECTING
říj 15 17:42:12 raspi5 NetworkManager[896]: <info> [1729006932.2643] device (end0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
říj 15 17:42:12 raspi5 NetworkManager[896]: <info> [1729006932.2695] device (end0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
říj 15 17:42:12 raspi5 NetworkManager[896]: <info> [1729006932.2700] dhcp4 (end0): activation: beginning transaction (timeout in 45 seconds)
říj 15 17:42:12 raspi5 NetworkManager[896]: <info> [1729006932.2961] dhcp4 (end0): state changed new lease, address=192.168.100.180
říj 15 17:42:12 raspi5 NetworkManager[896]: <info> [1729006932.2969] policy: set 'LAN' (end0) as default for IPv4 routing and DNS
říj 15 17:42:12 raspi5 NetworkManager[896]: <info> [1729006932.3175] device (end0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
říj 15 17:42:12 raspi5 NetworkManager[896]: <info> [1729006932.3485] device (end0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
říj 15 17:42:12 raspi5 NetworkManager[896]: <info> [1729006932.3488] device (end0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
říj 15 17:42:12 raspi5 NetworkManager[896]: <info> [1729006932.3492] manager: NetworkManager state is now CONNECTED_SITE
říj 15 17:42:12 raspi5 NetworkManager[896]: <info> [1729006932.3495] device (end0): Activation: successful, device activated.
říj 15 17:42:12 raspi5 NetworkManager[896]: <info> [1729006932.3607] manager: startup complete
říj 15 17:42:12 raspi5 NetworkManager[896]: <info> [1729006932.4731] manager: NetworkManager state is now CONNECTED_GLOBAL
říj 15 17:42:19 raspi5 NetworkManager[896]: <info> [1729006939.7174] agent-manager: agent[795c5166a532d1cc,:1.56/org.freedesktop.nm-applet/1000]: agent registered
### Additional context
_No response_
Thank you for your answer. The issue only occurred with HA os. If I use raspbian OS, the issue does not appear. Is it something that is comprehensive?
If the rasp ethernet driver would some problem, we would get the issue for everything, wouldn’t we?
Kind regard
C
tom_l
June 3, 2025, 11:16am
4
Those links are not related to Home Assistant. So it seems a general pi5 thing.