Solved "status: no carrier" for ethernet port?

My ClearFog Base can boot into FreeBSD 12.0-ALPHA7 7fe1a714461(master) ARMADA38X, but the second ethernet port next to the SFP socket doesn't seem to be configured properly. The first ethernet port, the one near the USB connectors, works well. The base device tree dtb is compiled using sys/gnu/dts/arm/armada-388-clearfog-base.dts from the FreeBSD source.

The two ethernet ports are connected to an unmanaged switch. When in u-boot, both link lights on the switch are on; both lights on the ClearFog are on with a high duty cycle, but constantly flickering. After control is passed to the FreeBSD kernel, the link light on the switch corresponding to the second ethernet port goes out and the link light on the ClearFog stays on without flickering.

The console (and dmesg) indicate that the second ethernet port has no carrier. I don't think that is a hardware problem, because, without touching the connections or the switch, an SD card with a Debian image can be inserted and both ethernet ports are fully functional.

What configuration might be required so that the interface detects a carrier?

pygr
 
ifconfig:

Code:
root@:~ # ifconfig
mvneta0: flags=8a02<BROADCAST,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE>
        ether 00:50:43:23:4e:40
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
mvneta1: flags=8a02<BROADCAST,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=800bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE>
        ether e4:57:30:6f:54:01
        media: Ethernet autoselect (none)
        status: no carrier
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
mvneta2: flags=8a02<BROADCAST,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM>
        ether 84:a7:fb:6c:81:02
        media: Ethernet autoselect
        status: no carrier
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
        inet 127.0.0.1 netmask 0xff000000
        groups: lo
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

dmesg | grep -i ether:

Code:
root@:~ # dmesg | grep -i ether

mvneta0: Ethernet address: 00:50:43:23:4e:40

mvneta1: Ethernet address: e4:57:30:6f:54:01

mvneta2: Ethernet address: 84:a7:fb:6c:81:02
 
Is strange that mvneta0 and mvneta1 has different vendor, looking that MAC in the vendor lookup
Code:
00:50:43:23:4e:40 MARVELL SEMICONDUCTOR, INC.
e4:57:30:6f:54:01 No Vendor Exists
But since the mvneta driver is attached (I did not find the manual mvneta()), lets assume is the correct driver, try with a configuration of 1Gbps

ifconfig mvneta1 up debug media 1000baseT mediaopt full-duplex

And also try with 100Mbps

ifconfig mvneta1 up debug media 100baseTX mediaopt full-duplex

The 1000baseT needs a UTP CAT 5e or 6 and use the 4 pairs (Does your switch is compatible?)
The 100baseTX needs a UTP CAT 5 and use 2 pairs

Try exchange the cord and the switch port

To see the logs, what is the output of dmesg | grep mvneta1 and grep mvneta1 /var/log/messages
 
Hi Martin,

Thank you for your interest in this.

After ifconfig mvneta1 up debug media 1000baseT mediaopt full-duplex

Code:
root@:~ # dmesg | grep mvneta1
mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
mvneta1: version is 10
mvneta1: Ethernet address: 14:0a:8c:64:71:01
miibus1: <MII bus> on mvneta1
mvneta1: link state changed to DOWN

Code:
root@:~ # grep mvneta1 /var/log/messages
Sep 25 12:12:31  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 25 12:12:31  kernel: mvneta1: version is 10
Sep 25 12:12:31  kernel: mvneta1: Ethernet address: e4:f3:8b:21:ff:01
Sep 25 12:12:31  kernel: miibus1: <MII bus> on mvneta1
Sep 25 12:12:31  kernel: mvneta1: link state changed to DOWN
Sep 25 12:18:17  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 24 on simplebus1
Sep 25 12:18:17  kernel: mvneta1: version is 10
Sep 25 12:18:17  kernel: mvneta1: Ethernet address: bc:07:c9:b4:c8:01
Sep 25 12:18:17  kernel: miibus1: <MII bus> on mvneta1
Sep 25 12:18:17  kernel: mvneta1: link state changed to DOWN
Sep 25 12:37:11  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 25 12:37:11  kernel: mvneta1: version is 10
Sep 25 12:37:11  kernel: mvneta1: Ethernet address: e4:f3:8b:21:ff:01
Sep 25 12:37:11  kernel: miibus1: <MII bus> on mvneta1
Sep 25 12:37:11  kernel: mvneta1: link state changed to DOWN
Sep 25 13:35:52  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 25 13:35:52  kernel: mvneta1: version is 10
Sep 25 13:35:52  kernel: mvneta1: Ethernet address: 60:53:4f:3a:e1:01
Sep 25 13:35:52  kernel: mdio0: <MDIO> on mvneta1
Sep 25 13:35:52  kernel: mvneta1: link state changed to UP
Sep 25 13:42:48  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 24 on simplebus1
Sep 25 13:42:48  kernel: mvneta1: version is 10
Sep 25 13:42:48  kernel: mvneta1: Ethernet address: 8c:ed:1e:c6:0f:01
Sep 25 13:42:48  kernel: miibus1: <MII bus> on mvneta1
Sep 25 13:42:48  kernel: mvneta1: link state changed to DOWN
Sep 25 14:00:08  kernel: mvneta1: <NETA controller> mem 0x34000-0x37fff irq 27 on simplebus1
Sep 25 14:00:08  kernel: mvneta1: Use in-band link status.
Sep 25 14:00:08  kernel: mvneta1: version is 10
Sep 25 14:00:08  kernel: mvneta1: Ethernet address: f8:fd:bf:68:6b:01
Sep 25 14:00:08  kernel: mvneta1: link state changed to DOWN
Sep 25 14:49:15  kernel: mvneta1: <NETA controller> mem 0x34000-0x37fff irq 27 on simplebus1
Sep 25 14:49:15  kernel: mvneta1: Use in-band link status.
Sep 25 14:49:15  kernel: mvneta1: version is 10
Sep 25 14:49:15  kernel: mvneta1: Ethernet address: 14:14:c4:cf:24:01
Sep 25 14:49:15  kernel: mvneta1: link state changed to DOWN
Sep 25 15:18:39  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 25 15:18:39  kernel: mvneta1: version is 10
Sep 25 15:18:39  kernel: mvneta1: Ethernet address: 80:53:e2:50:8a:01
Sep 25 15:18:39  kernel: miibus1: <MII bus> on mvneta1
Sep 25 15:18:39  kernel: mvneta1: link state changed to DOWN
Sep 25 15:37:26  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 25 15:37:26  kernel: mvneta1: version is 10
Sep 25 15:37:26  kernel: mvneta1: Ethernet address: 4c:cc:40:f1:7f:01
Sep 25 15:37:26  kernel: miibus1: <MII bus> on mvneta1
Sep 25 15:37:26  kernel: mvneta1: link state changed to DOWN
Sep 25 15:41:51  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 25 15:41:51  kernel: mvneta1: version is 10
Sep 25 15:41:51  kernel: mvneta1: Ethernet address: a4:61:47:f5:ff:01
Sep 25 15:41:51  kernel: miibus1: <MII bus> on mvneta1
Sep 25 15:41:51  kernel: mvneta1: link state changed to DOWN
Sep 25 23:11:03  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 25 23:11:03  kernel: mvneta1: version is 10
Sep 25 23:11:03  kernel: mvneta1: Ethernet address: 70:5d:a1:8f:17:01
Sep 25 23:11:03  kernel: miibus1: <MII bus> on mvneta1
Sep 25 23:11:03  kernel: mvneta1: link state changed to DOWN
Sep 25 23:40:30  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 24 on simplebus1
Sep 25 23:40:30  kernel: mvneta1: version is 10
Sep 25 23:40:30  kernel: mvneta1: Ethernet address: e4:37:ce:4a:47:01
Sep 25 23:40:30  kernel: miibus1: <MII bus> on mvneta1
Sep 25 23:40:30  kernel: mvneta1: link state changed to DOWN
Sep 25 23:58:51  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 25 23:58:51  kernel: mvneta1: version is 10
Sep 25 23:58:51  kernel: mvneta1: Ethernet address: e4:f3:8b:21:ff:01
Sep 25 23:58:51  kernel: miibus1: <MII bus> on mvneta1
Sep 25 23:58:51  kernel: mvneta1: link state changed to DOWN
Sep 26 10:38:28  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 26 10:38:28  kernel: mvneta1: version is 10
Sep 26 10:38:28  kernel: mvneta1: Ethernet address: 6c:05:05:2a:0c:01
Sep 26 10:38:28  kernel: miibus1: <MII bus> on mvneta1
Sep 26 10:38:28  kernel: mvneta1: link state changed to DOWN
Sep 26 12:34:58  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 26 12:34:58  kernel: mvneta1: version is 10
Sep 26 12:34:58  kernel: mvneta1: Ethernet address: a0:3c:33:4d:54:01
Sep 26 12:34:58  kernel: miibus1: <MII bus> on mvneta1
Sep 26 12:34:58  kernel: mvneta1: link state changed to DOWN
Sep 26 12:40:37  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 26 12:40:37  kernel: mvneta1: version is 10
Sep 26 12:40:37  kernel: mvneta1: Ethernet address: 94:e5:25:7c:13:01
Sep 26 12:40:37  kernel: miibus1: <MII bus> on mvneta1
Sep 26 12:40:37  kernel: mvneta1: link state changed to DOWN
Sep 26 18:16:19  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 26 18:16:19  kernel: mvneta1: version is 10
Sep 26 18:16:19  kernel: mvneta1: Ethernet address: e4:57:30:6f:54:01
Sep 26 18:16:19  kernel: miibus1: <MII bus> on mvneta1
Sep 26 18:16:19  kernel: mvneta1: link state changed to DOWN
Sep 27 10:32:49  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 27 10:32:49  kernel: mvneta1: version is 10
Sep 27 10:32:49  kernel: mvneta1: Ethernet address: 88:62:79:4c:33:01
Sep 27 10:32:49  kernel: miibus1: <MII bus> on mvneta1
Sep 27 10:32:49  kernel: mvneta1: link state changed to DOWN
Sep 27 14:31:41  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 27 14:31:41  kernel: mvneta1: version is 10
Sep 27 14:31:41  kernel: mvneta1: Ethernet address: 14:0a:8c:64:71:01
Sep 27 14:31:41  kernel: miibus1: <MII bus> on mvneta1
Sep 27 14:31:41  kernel: mvneta1: link state changed to DOWN

After a reboot followed by ifconfig mvneta1 up debug media 100baseTX mediaopt full-duplex

Code:
root@:~ # dmesg | grep mvneta1
mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
mvneta1: version is 10
mvneta1: Ethernet address: ec:a2:18:57:1e:01
miibus1: <MII bus> on mvneta1
mvneta1: link state changed to DOWN

Code:
grep mvneta1 /var/log/messages
Sep 25 12:12:31  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 25 12:12:31  kernel: mvneta1: version is 10
Sep 25 12:12:31  kernel: mvneta1: Ethernet address: e4:f3:8b:21:ff:01
Sep 25 12:12:31  kernel: miibus1: <MII bus> on mvneta1
Sep 25 12:12:31  kernel: mvneta1: link state changed to DOWN
Sep 25 12:18:17  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 24 on simplebus1
Sep 25 12:18:17  kernel: mvneta1: version is 10
Sep 25 12:18:17  kernel: mvneta1: Ethernet address: bc:07:c9:b4:c8:01
Sep 25 12:18:17  kernel: miibus1: <MII bus> on mvneta1
Sep 25 12:18:17  kernel: mvneta1: link state changed to DOWN
Sep 25 12:37:11  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 25 12:37:11  kernel: mvneta1: version is 10
Sep 25 12:37:11  kernel: mvneta1: Ethernet address: e4:f3:8b:21:ff:01
Sep 25 12:37:11  kernel: miibus1: <MII bus> on mvneta1
Sep 25 12:37:11  kernel: mvneta1: link state changed to DOWN
Sep 25 13:35:52  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 25 13:35:52  kernel: mvneta1: version is 10
Sep 25 13:35:52  kernel: mvneta1: Ethernet address: 60:53:4f:3a:e1:01
Sep 25 13:35:52  kernel: mdio0: <MDIO> on mvneta1
Sep 25 13:35:52  kernel: mvneta1: link state changed to UP
Sep 25 13:42:48  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 24 on simplebus1
Sep 25 13:42:48  kernel: mvneta1: version is 10
Sep 25 13:42:48  kernel: mvneta1: Ethernet address: 8c:ed:1e:c6:0f:01
Sep 25 13:42:48  kernel: miibus1: <MII bus> on mvneta1
Sep 25 13:42:48  kernel: mvneta1: link state changed to DOWN
Sep 25 14:00:08  kernel: mvneta1: <NETA controller> mem 0x34000-0x37fff irq 27 on simplebus1
Sep 25 14:00:08  kernel: mvneta1: Use in-band link status.
Sep 25 14:00:08  kernel: mvneta1: version is 10
Sep 25 14:00:08  kernel: mvneta1: Ethernet address: f8:fd:bf:68:6b:01
Sep 25 14:00:08  kernel: mvneta1: link state changed to DOWN
Sep 25 14:49:15  kernel: mvneta1: <NETA controller> mem 0x34000-0x37fff irq 27 on simplebus1
Sep 25 14:49:15  kernel: mvneta1: Use in-band link status.
Sep 25 14:49:15  kernel: mvneta1: version is 10
Sep 25 14:49:15  kernel: mvneta1: Ethernet address: 14:14:c4:cf:24:01
Sep 25 14:49:15  kernel: mvneta1: link state changed to DOWN
Sep 25 15:18:39  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 25 15:18:39  kernel: mvneta1: version is 10
Sep 25 15:18:39  kernel: mvneta1: Ethernet address: 80:53:e2:50:8a:01
Sep 25 15:18:39  kernel: miibus1: <MII bus> on mvneta1
Sep 25 15:18:39  kernel: mvneta1: link state changed to DOWN
Sep 25 15:37:26  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 25 15:37:26  kernel: mvneta1: version is 10
Sep 25 15:37:26  kernel: mvneta1: Ethernet address: 4c:cc:40:f1:7f:01
Sep 25 15:37:26  kernel: miibus1: <MII bus> on mvneta1
Sep 25 15:37:26  kernel: mvneta1: link state changed to DOWN
Sep 25 15:41:51  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 25 15:41:51  kernel: mvneta1: version is 10
Sep 25 15:41:51  kernel: mvneta1: Ethernet address: a4:61:47:f5:ff:01
Sep 25 15:41:51  kernel: miibus1: <MII bus> on mvneta1
Sep 25 15:41:51  kernel: mvneta1: link state changed to DOWN
Sep 25 23:11:03  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 25 23:11:03  kernel: mvneta1: version is 10
Sep 25 23:11:03  kernel: mvneta1: Ethernet address: 70:5d:a1:8f:17:01
Sep 25 23:11:03  kernel: miibus1: <MII bus> on mvneta1
Sep 25 23:11:03  kernel: mvneta1: link state changed to DOWN
Sep 25 23:40:30  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 24 on simplebus1
Sep 25 23:40:30  kernel: mvneta1: version is 10
Sep 25 23:40:30  kernel: mvneta1: Ethernet address: e4:37:ce:4a:47:01
Sep 25 23:40:30  kernel: miibus1: <MII bus> on mvneta1
Sep 25 23:40:30  kernel: mvneta1: link state changed to DOWN
Sep 25 23:58:51  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 25 23:58:51  kernel: mvneta1: version is 10
Sep 25 23:58:51  kernel: mvneta1: Ethernet address: e4:f3:8b:21:ff:01
Sep 25 23:58:51  kernel: miibus1: <MII bus> on mvneta1
Sep 25 23:58:51  kernel: mvneta1: link state changed to DOWN
Sep 26 10:38:28  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 26 10:38:28  kernel: mvneta1: version is 10
Sep 26 10:38:28  kernel: mvneta1: Ethernet address: 6c:05:05:2a:0c:01
Sep 26 10:38:28  kernel: miibus1: <MII bus> on mvneta1
Sep 26 10:38:28  kernel: mvneta1: link state changed to DOWN
Sep 26 12:34:58  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 26 12:34:58  kernel: mvneta1: version is 10
Sep 26 12:34:58  kernel: mvneta1: Ethernet address: a0:3c:33:4d:54:01
Sep 26 12:34:58  kernel: miibus1: <MII bus> on mvneta1
Sep 26 12:34:58  kernel: mvneta1: link state changed to DOWN
Sep 26 12:40:37  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 26 12:40:37  kernel: mvneta1: version is 10
Sep 26 12:40:37  kernel: mvneta1: Ethernet address: 94:e5:25:7c:13:01
Sep 26 12:40:37  kernel: miibus1: <MII bus> on mvneta1
Sep 26 12:40:37  kernel: mvneta1: link state changed to DOWN
Sep 26 18:16:19  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 26 18:16:19  kernel: mvneta1: version is 10
Sep 26 18:16:19  kernel: mvneta1: Ethernet address: e4:57:30:6f:54:01
Sep 26 18:16:19  kernel: miibus1: <MII bus> on mvneta1
Sep 26 18:16:19  kernel: mvneta1: link state changed to DOWN
Sep 27 10:32:49  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 27 10:32:49  kernel: mvneta1: version is 10
Sep 27 10:32:49  kernel: mvneta1: Ethernet address: 88:62:79:4c:33:01
Sep 27 10:32:49  kernel: miibus1: <MII bus> on mvneta1
Sep 27 10:32:49  kernel: mvneta1: link state changed to DOWN
Sep 27 14:31:41  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 27 14:31:41  kernel: mvneta1: version is 10
Sep 27 14:31:41  kernel: mvneta1: Ethernet address: 14:0a:8c:64:71:01
Sep 27 14:31:41  kernel: miibus1: <MII bus> on mvneta1
Sep 27 14:31:41  kernel: mvneta1: link state changed to DOWN
Sep 27 14:50:42  kernel: mvneta1: <NETA controller> mem 0x30000-0x33fff irq 25 on simplebus1
Sep 27 14:50:42  kernel: mvneta1: version is 10
Sep 27 14:50:42  kernel: mvneta1: Ethernet address: ec:a2:18:57:1e:01
Sep 27 14:50:42  kernel: miibus1: <MII bus> on mvneta1
Sep 27 14:50:42  kernel: mvneta1: link state changed to DOWN

The switch is a TRENDnet TEG-s50g V2.0R Gigabit Switch. One patch cable is CAT5e the other is CAT6. Swapping cables at the Clearfog end leaves the behavior of mvneta0 and mvneta1 the same. The only change is which switch link lights are on, which have exchanged positions.

Are the MAC addresses passed from u-boot to the kernel or does the kernel read them directly from the hardware?
 
Hi Martin,

Thank you for your efforts and insight.

It turns out that the missing piece was an instance of u-boot tailored for the ClearFog Base. See the last post here.

Since u-boot itself seemed to work well enough to boot the OS, I was thinking that the suggested modifications weren't necessary. That thinking was wrong.

Apparently, the OS relies on some ethernet functionality of u-boot to do its job, even long after boot. A device tree and OS tailored to the ClearFog Base is not sufficient.

After making the modifications to u-boot suggested in the link above, both ethernet ports are fully functional.
 
Great, you could solve it :D
Your ClearFog isn't the Pro model, and don't have the switch integrated as the Pro model have and the problem was that the code you were using was for the Pro model and was expecting to find a switch in the 2nd ethernet port (mvneta1).
 
Hi Martin,

Thank you for your efforts and insight.

It turns out that the missing piece was an instance of u-boot tailored for the ClearFog Base. See the last post here.

Since u-boot itself seemed to work well enough to boot the OS, I was thinking that the suggested modifications weren't necessary. That thinking was wrong.

Apparently, the OS relies on some ethernet functionality of u-boot to do its job, even long after boot. A device tree and OS tailored to the ClearFog Base is not sufficient.

After making the modifications to u-boot suggested in the link above, both ethernet ports are fully functional.
I ran into this same issue… The link above is no longer working. Is there anyway you can provide the steps taken to modify u-boot for the ClearFog Base?
 
Back
Top