Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Clearfog Base second ethernet interface

Featured Replies

I'm running into a problem using the second interface with my Clearfog Base. I don't have an SFP to test the third interface, but the first works fine, though the second does not. I've tried images with 3.x and 4.x kernels from both SolidRun and Armbian and they all have the same behavior.

 

My first concern is whether this has worked for anyone else so that I can rule out faulty hardware. Can anyone chime in with whether they've successfully used the 2nd copper interface on a Clearfog Base?  If so, did it work out of the box, or did it require any extra steps?

 

Next, can someone more familiar with ARM SOCs and device trees comment as to whether the same device tree for the Pro should work for the Base?

 

In case it helps, here is some output I cherry-picked from the boot sequence that seems related to the NICs:

 

Board configuration detected:

Net:

|  port  | Interface | PHY address  |

|--------|-----------|--------------|

| egiga0 |   RGMII   |     0x00     |

| egiga1 |   SGMII   |   In-Band    |

| egiga2 |   SGMII   |   In-Band    |

egiga0 [PRIME], egiga1, egiga2

 

 | Lane # | Speed|    Type     |

 ------------------------------|

 |   0    |  3   |  SATA0      |

 |   1    |  0   |  SGMII1     |

 |   2    |  5   |  PCIe1      |

 |   3    |  5   |  USB3 HOST1 |

 |   4    |  5   |  PCIe2      |

 |   5    |  0   |  SGMII2     |

 -------------------------------

PCIe, Idx 1: detected no link

PCIe, Idx 2: detected no link

High speed PHY - Ended Successfully

DDR3 Training Sequence - Ver TIP-1.39.0

DDR3 Training Sequence - Switching XBAR Window to FastPath Window

DDR3 Training Sequence - Ended Successfully

BootROM: Image checksum verification PASSED

 

SoC: model = 0x6828, revision = 0x4

mvPncVirtBase = 0xf0400000, pncTcamSize = 1024

  o 3 Giga ports supported

  o SKB recycle supported for SWF (Disabled)

  o NETA acceleration mode 4

  o BM supported for CPU: 4 BM pools

  o PnC supported (Enabled)

  o RX Queue support: 8 Queues * 256 Descriptors

  o TX Queue support: 8 Queues * 532 Descriptors

  o GSO supported

  o GRO supported

  o Receive checksum offload supported

  o Transmit checksum offload supported

  o Driver ERROR statistics enabled

  o Driver INFO statistics enabled

  o Driver DEBUG statistics enabled

 

port #0: is_sgmii=0, is_rgmii=1, phy_addr=0

  o Loading network interface(s) for port #0: cpu_mask=0x3, tx_csum_limit=9800

 

  o Port 0 is connected to Linux netdevice

    o eth0, ifindex = 3, GbE port = 0

        giga p=0: mtu=1500, mac=00:50:43:02:02:01 (platform)

 

port #1: is_sgmii=1, is_rgmii=0, phy_addr=-1

  o Loading network interface(s) for port #1: cpu_mask=0x3, tx_csum_limit=2048

 

  o Port 1 is connected to Linux netdevice

    o eth1, ifindex = 4, GbE port = 1

        giga p=1: mtu=1500, mac=00:50:43:02:02:02 (platform)

 

port #2: is_sgmii=1, is_rgmii=0, phy_addr=-1

  o Loading network interface(s) for port #2: cpu_mask=0x3, tx_csum_limit=2048

 

  o Port 2 is connected to Linux netdevice

    o eth2, ifindex = 5, GbE port = 2

        giga p=2: mtu=1500, mac=00:50:43:02:02:03 (platform)

 

libphy: orion_mdio_bus: probed

 

  • Author

I think I found a workaround for this.

 

Is there a way to make the existing Clearfog images handle both boards? Should there be distinct images for the Base and Pro versions of the Clearfog boards?

Guest
This topic is now closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.