Re: eqos on Panther X2 RK3566

On Thu, 20 Nov 2025 07:01:26 +0000
qroxana <qroxana@protonmail.com> wrote:

> Hi,
> 
> I'm trying to running FreeBSD on Panther X2, the eqos0 is up however
> it's not able to send or receive any packets. Any help would be
> appreciated!
> 
> root@generic:~ # ifconfig eqos0
> eqos0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP>
> metric 0 mtu 1500 options=80008<VLAN_MTU,LINKSTATE>
> ether f2:00:2f:a2:cc:66
> inet 10.10.30.90 netmask 0xff000000 broadcast 10.255.255.255

Where does this IP address come from? How is it being set?

[ snip ]

> Unresolved linked clock found: clk_32k_pvtm
> Unresolved linked clock found: usb480m_phy
> Unresolved linked clock found: mpll
> Unresolved linked clock found: i2s0_mclkin
> Unresolved linked clock found: i2s1_mclkin
> Unresolved linked clock found: i2s2_mclkin
> Unresolved linked clock found: i2s3_mclkin
> Unresolved linked clock found: gpu_pvtpll_out
> Unresolved linked clock found: npu_pvtpll_out
> Unresolved linked clock found: gmac0_clkin
> Unresolved linked clock found: clk_gmac0_xpcs_mii
> Unresolved linked clock found: clk_gmac1_xpcs_mii
> Unresolved linked clock found: dummy

I am not an expert in this area, but this shows me you could have some
issue with clocks being not properly initialized.

Are you able to use tcpdump to see ethernet communication? In my past
experience, it's possible to have just one-way communication working
caused by wrong clock setup.

Regards,
Milan