You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to connect my Radxa X4 using LAN (with PoE) but it constantly going down and up. WiFi was up at that time and I didn't see any similar behaviour. There is a connection for a brief moment because I was able to log in to CLI and check the logs. But it lasts for a few seconds. Not sure what the issue could be...I'll try to use different cable but it will take a little bit to prepare...but I don't think that's gonna be the culprit (even though I really would it to be)...
What version of Home Assistant Operating System is installed?
6.6.54-haos
Did the problem occur after upgrading the Operating System?
No
Hardware details
Main hardware is Radxa X4 8GB without eMMC. NVMe disk installed. There's a Zigbee dongle attached to USB2 port /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0.
LAN is made by Intel Foxville I225.
Wi-Fi and it's probably Azurewave AW-XM548NF, or at least Radxa docs says that and this is probably specification of it.
Steps to reproduce the issue
Turn on LAN.
Observe link jumping between up and down.
Anything in the Supervisor logs that might be useful for us?
Nope
Anything in the Host logs that might be useful for us?
2024-11-21 17:15:33.796 homeassistant kernel: igc 0000:02:00.0 enp2s0: NIC Link is Down
2024-11-21 17:15:37.458 homeassistant kernel: igc 0000:02:00.0 enp2s0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
2024-11-21 17:15:37.460 homeassistant NetworkManager[415]: <info> [1732209337.4595] device (enp2s0): carrier: link connected
2024-11-21 17:15:45.759 homeassistant kernel: igc 0000:02:00.0 enp2s0: NIC Link is Down
2024-11-21 17:15:49.427 homeassistant kernel: igc 0000:02:00.0 enp2s0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
2024-11-21 17:15:49.429 homeassistant NetworkManager[415]: <info> [1732209349.4284] device (enp2s0): carrier: link connected
2024-11-21 17:15:49.867 homeassistant kernel: igc 0000:02:00.0 enp2s0: NIC Link is Down
This one doesn't happen all the time but it was there:
So I bought some high quality cable and...it does work. That means it rather looks like some issue with my old cable (which works fine on itself) and maybe something with hardware and PoE. That old one was cat5e and new is cat8 (or at least it claims that), but that shouldn't matter...but maybe with PoE it did. For now I'm checking if it was really the case. Sorry for bothering anyone.
Describe the issue you are experiencing
I tried to connect my Radxa X4 using LAN (with PoE) but it constantly going down and up. WiFi was up at that time and I didn't see any similar behaviour. There is a connection for a brief moment because I was able to log in to CLI and check the logs. But it lasts for a few seconds. Not sure what the issue could be...I'll try to use different cable but it will take a little bit to prepare...but I don't think that's gonna be the culprit (even though I really would it to be)...
What operating system image do you use?
generic-x86-64 (Generic UEFI capable x86-64 systems)
What version of Home Assistant Operating System is installed?
6.6.54-haos
Did the problem occur after upgrading the Operating System?
No
Hardware details
Main hardware is Radxa X4 8GB without eMMC. NVMe disk installed. There's a Zigbee dongle attached to USB2 port /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0.
LAN is made by Intel Foxville I225.
Wi-Fi and it's probably Azurewave AW-XM548NF, or at least Radxa docs says that and this is probably specification of it.
Steps to reproduce the issue
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
This one doesn't happen all the time but it was there:
System information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Spotify
Additional information
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: