AR8216 switch doesn't initialize

Lately I've been playing with some arcadyan ARV45PW2 devices (Netfaster IAD 2), very similar to the ARV4518PW, except the switch is an atheros AR8216.Default bootloader is brnboot, and is running some custom firmware.
I now have uboot as main bootloader and LEDE trunk on it, with everything working, USB, dsl, wireless, etc.
The only problem I found is that on one device the switch would never initialize., no reaction when an ethernet cable was attached, no leds or anything.
After inspecting the pcb it seems that the board that has no ethernet is missing a 25mhz crystal and some passives next to the ar8216 chip.
Here's a device with the crystal
https://postimg.org/image/4ewx0r3nf/
and one without
https://postimg.org/image/q1bxhnk6j/
Here's the bootlog from uboot with debug enabled

Net: bring up ebu gpio
initializing ar8216 switch... Port 0, Negotiation timeout
Port 1, Negotiation timeout
Port 2, Negotiation timeout
Port 3, Negotiation timeout
eth0: Phy Specific Status=ffffb35c
eth0: Phy Specific Status=ffffb35c
eth0: Phy Specific Status=ffffb35c
eth0: Phy Specific Status=ffffb35c
failed ...
lq_cpe_eth

and LEDE

[ 0.721355] libphy: Fixed MDIO Bus: probed
[ 0.728643] libphy: ltq_mii: probed
[ 0.730647] ltq_etop 1e180000.etop eth0 (uninitialized): no PHY found
[ 0.737099] etop: mdio probe failed

and what it looks when the switch initializes fine

initializing ar8216 switch...
Port 0, Negotiation Success
Port 1, Negotiation Success
Port 2, Negotiation Success
Port 3, Negotiation Success
eth0: Phy Specific Status=10b3bc
eth0: Phy Specific Status=10b3bc
eth0: Phy Specific Status=10b3bc
eth0: Phy Specific Status=10b3bc
initialized
lq_cpe_eth

[ 0.720573] libphy: Fixed MDIO Bus: probed
[ 0.733446] switch0: Atheros AR8216 rev. 1 switch registered on 1e180000.etop-ff
[ 0.770398] libphy: ltq_mii: probed
[ 0.813358] Atheros AR8216/AR8236/AR8316 1e180000.etop-ff:00: attached PHY driver [Atheros AR8216/AR8236/AR8316] (mii_bus:phy_addr=1e180000.etop-ff:00, irq=-1)

Default firmware somehow takes care of this and works fine.

I have worked on this for quite some time when I was free, but I have found no solution.I know some programming, but I have almost no idea about drivers. Can anyone point me in the right direction?
Thank you :slightly_smiling_face: