[solved] Meraki MR52 eth0 not working, no phy

Recently flashed MR52 to 22.03.3 but eth0 is not working. PoE on eth0 works for power.
Using eth1 for lan connectivity, after moving both interfaces to br-lan

and Wi-Fi connection is not as stable as it was on MR33. [forgot to disable DHCP on access point, wi-fi is now stable]

Dont believe its a hardware issue, because during the tftp of the
openwrt-ipq806x-generic-meraki_mr52-initramfs-fit-uImage.itb image
, uboot shows port2:10Mbps and port3: 1000Mbps

Both LEDs are lit on the PoE / eth0 NIC without a cable plugged in, seems like incorrect device tree or something?

Here's the log:

[ 2797.074003] br-lan: port 1(eth0) entered disabled state
[ 2797.122621] device eth1 left promiscuous mode
[ 2797.356527] ipq806x-gmac-dwmac 37400000.ethernet eth0: no phy at addr -1
[ 2797.356576] ipq806x-gmac-dwmac 37400000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
[ 2797.363670] br-lan: port 1(eth0) entered blocking state
[ 2797.371445] br-lan: port 1(eth0) entered disabled state
[ 2797.377096] device eth0 entered promiscuous mode

How to get eth0 working?

To be clear, you have eth0 plugged in and are using it for LAN, correct?

If not, does it work when eth0 is used?

Currently using eth1 for lan connection

eth0 cannot establish lan connection.

are you sure eth0 hasn't been configured as wan, by openwrt ?

1 Like

Should be the other way around according to git:

         ucidef_set_interfaces_lan_wan "eth0" "eth1"

Using as an access point per the instructions from https://openwrt.org/docs/guide-user/network/wifi/dumbap

Moved eth0 and eth1 to br-lan, deleted wan and wan6 interfaces

config device
	option name 'br-lan'
	option type 'bridge'
	list ports 'eth0'
	list ports 'eth1'

config interface 'lan'
	option device 'br-lan'
	option proto 'static'
	option ipaddr ''
	option netmask ''
	option ip6assign '60'
	option gateway ''
	list dns ''

side note: forgot to disable dhcp on the access point, after doing so the Wi-Fi connection is stable

Sanity checked with a cable directly to each port using original firmware.. no connection on eth0 (no lights), established on eth1. Chalking this up as a hardware issue.

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.