Dual BCM57788 PHY detect failure

For Developers
#1

I have a one of these that I was using for a gw that I would like to put LEDE on

However, LEDE does not seem to detect the nic card.

If I boot a systemrescuecd on the device the interfaces are recognized and dmesg looks like the following.

[ 5.635827] tg3.c:v3.137 (May 11, 2014)
[ 5.651242] libphy: tg3 mdio bus: probed
[ 5.715593] tg3 0000:01:00.0 eth0: Tigon3 [partno(BCM57788) rev 57780001] (PCI Express) MAC address 00:e0:66:da:6c:51
[ 5.715604] tg3 0000:01:00.0 eth0: attached PHY driver [Broadcom BCM57780] (mii_bus:phy_addr=100:01)
[ 5.715611] tg3 0000:01:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
[ 5.715617] tg3 0000:01:00.0 eth0: dma_rwctrl[76180000] dma_mask[64-bit]
[ 5.728607] libphy: tg3 mdio bus: probed
[ 5.790312] tg3 0000:02:00.0 eth1: Tigon3 [partno(BCM57788) rev 57780001] (PCI Express) MAC address 00:e0:66:de:f3:bb
[ 5.790325] tg3 0000:02:00.0 eth1: attached PHY driver [Broadcom BCM57780] (mii_bus:phy_addr=200:01)
[ 5.790335] tg3 0000:02:00.0 eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
[ 5.790344] tg3 0000:02:00.0 eth1: dma_rwctrl[76180000] dma_mask[64-bit]
[

If I boot LEDE (git HEAD, my build. built today) I get the following.

[ 3.445333] tg3.c:v3.137 (May 11, 2014)
[ 3.450592] libphy: tg3 mdio bus: probed
[ 3.454675] tg3 0000:01:00.0: No PHY devices
[ 3.459184] tg3 0000:01:00.0: Problem fetching invariants of chip, aborting
[ 3.467589] libphy: tg3 mdio bus: probed
[ 3.471668] tg3 0000:02:00.0: No PHY devices
[ 3.476166] tg3 0000:02:00.0: Problem fetching invariants of chip, aborting

I've looked through my config and I don't see anything that I can enable that will help. Any suggestions?

#2

@rmilecki - any idea about this one?

#3

I've zero experience with tg3. I can only suggest to open tg3.c and start debugging. Was this ASIC detected as ASIC_REV_57780? Has USE_PHYLIB been set? Has tg3_phy_init returned success (0)? Etc.

#4

Rats. I was hoping it was just a missing config setting. I have both kmod-libphy and kmod-phy-broadcom and it looks like lipphy activated. Could there still be something else?

Looking at that message in tg3.c suggests it might be something in the mdio phy scan. I'll start digging into it deeper.

Do you know if there any additional debug flags I can enable that might shed more light on what's happening with the PHY detection?

#5

[quote="smithbone, post:4, topic:838"]Do you know if there any additional debug flags I can enable that might shed more light on what's happening with the PHY detection?[/quote]I'm not aware of them if there are any.

#6

Hi! I had the same problem and was able to resolve it using the solution listed in the following URL.

https://dev.archive.openwrt.org/ticket/19545

I still had to manually create the symlink for everything to work... Is there way to automate that as part of the phy-broadcom installation?

Niten