Rock64 flaky ethernet?
Adriaan de Groot <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.arm |
|---|---|
| Organization | FreeBSD |
| Message-ID | <[email protected]> |
I've got an old-ish (2018 .. v2) Rock64 that hasn't been used much. I have fetched and booted it into the 13-RELEASE image: FreeBSD-13.0-RELEASE-arm64-aarch64-ROCK64.img.xz 452690956 2021-Apr-09 06:46 I have written this to an 8GB generic micro-SD card. For good measure, I have written a recent Armbian image to the same brand and age of micro-SD card, so I have comparison material. (I could also write everything to the 32GB eMMC chip that's in the Rock64, if needed, but I'm holding off on that until I have something that works). After boot, dwc0 gets an address from DHCP, and I start pinging 10.0.0.2 in my home network. I get ~3% packet loss if I'm lucky, more often around 7%. If I'm pinging a machine in the network and also pinging my Rock64 from that machine, I hit around 22% packet loss on both sides. Armbian works fine - poweroff, swap SD card, power on - in the same setup. With this kind of packet loss I can't really do anything with the board in FreeBSD; `pkg bootstrap` for instance seems to sit there forever. .. ok, digging in the archives gets me lots of threads from june/july 2020 about dwc timing, I'll dig through those first before carrying on. [ade] PS. Pine H6 never did catch on in FreeBSD-land, did it. Pity, I've got a couple that I'd be happy enough to use instead of the Rock64 if they worked.
signature.asc
(application/pgp-signature, 659 B)
-----BEGIN PGP SIGNATURE----- iQGzBAABCAAdFiEEhrjttu2OP5apuuy1z93JbxKxkVwFAmCWzWoACgkQz93JbxKx kVwj2Av/RHymeTx90spcxKItjHFRq+e07E7vrzLdyn+j31cavzm71IravA3gNxQ/ LjkPuOveVXNizkGtF6Q/naXuBfu1T136xqrq03SN4m7CvqvfM3FWJBNQiu22ndWZ bSq04REgHswfLxBcS76gQbD6yO5GVKes0t1P4lTCLjgGj3FSLb5+WffJZ4BG1hJw zJBHqxOGdXo3VttrRgRWgvo2SaB59Y5SDkRpkjxWTdhGuU/XbGE1iOVhkUhJ9DTc ZSgA3OCFYBTlV9woV2+QApHn6gY10x11cYPLvxQNyQj5WlitIMUz/UuXAGZiGPDY nBnVGKS0qLWpGIKYV6TksQRcdSbO2nIKAXqxwo6/jgNzPQDuwVjFoDor8d+T5Pl3 cIzjBQYOm+zTtxIAhPBYU8jIpwfJ5qUBBUVJke7r+0D1sJd9lWYKUcBsGAtiv+m2 WVhshBbQbsjGL1ZCDqjji3WBDbFEy+DXFA+ndDKmXJt0rJkT66z0hK5jw22E3veS SgWyGqlU =ayQT -----END PGP SIGNATURE-----