Date: Tue, 2 Oct 2018 05:42:48 +0200 From: Marcin Wojtas <mw@semihalf.com> To: pygr@sonic.net Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: ClearFog Base -- "status: no carrier" for mvneta1 Message-ID: <CAPv3WKeDxTnqh_fnz8MYYU-QRCos7-7sN898Pc0=pt9wZTT1=w@mail.gmail.com> In-Reply-To: <03261C47-F7E5-46D6-9A91-B8FFDD96FDE3@sonic.net> References: <03261C47-F7E5-46D6-9A91-B8FFDD96FDE3@sonic.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Glenn, I can see, that armada-388-clearfog-base.dts connects eth1 to a PHY via MDI= O. Unfortunately my Clearfog boards have the SFP cage connected only to the SGMII lanes only (no PHY). Can you please try to boot with armada-388-clearfog.dts, where the SFP cage is configured as the 'fixed-link' and let know? Best regards, Marcin pt., 28 wrz 2018 o 18:47 glenn <pygr@sonic.net> napisa=C5=82(a): > > With a recent build from source (FreeBSD 12.0-ALPHA7 FreeBSD 12.0-ALPHA7= 7fe1a714461(master) ARMADA38X arm) the ethernet port on a ClearFog Base n= ear the USB sockets works well, but the port near the SFP cage doesn=E2=80= =99t. ifconfig shows "mvneta1: status: no carrier=E2=80=9D. > > Both ports are connected to a gigabit switch. The green link LED on the C= learFog Base for mvneta0 is on most of the time, but flickering; the green = link LED for mvneta1 is on without flickering. On the switch, the correspon= ding link LED for mvneta0 is on constantly, the LED for mvneta1 is off. > > I don=E2=80=99t believe it=E2=80=99s a hardware issue, because, if the pa= tch cables are swapped at the board, mvneta1 still shows no carrier and whi= ch LED on the switch is illuminated swaps. Also, without touching the cable= s or switch, Debian can be booted up using a different SD card, and both et= hernet ports are functional with no special action taken. > > The device tree file being used is compiled from armada-388-clearfog-base= .dts in the FreeBSD source, but edited to allow the serial console to work. > > What might it take to get that second ethernet port to work? A modificati= on of the device tree file? A modification of the mvneta or miibus driver? = A modification of u-boot? Or, perhaps, just a simple configuration step? > > Glenn > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPv3WKeDxTnqh_fnz8MYYU-QRCos7-7sN898Pc0=pt9wZTT1=w>