Bug 239906 - sysutils/u-boot-rock64: Unable to set MAC address, USB 3.0 not working, USB 2.0 not enabled
Summary: sysutils/u-boot-rock64: Unable to set MAC address, USB 3.0 not working, USB 2...
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: arm64 Any
: --- Affects Some People
Assignee: freebsd-uboot (Nobody)
Keywords: needs-qa
Depends on:
Reported: 2019-08-16 11:44 UTC by Denis Polygalov
Modified: 2020-12-13 12:31 UTC (History)
1 user (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Denis Polygalov 2019-08-16 11:44:16 UTC
I'm comparing functionality of ayufun's u-boot for ROCK64
board (hardware v2.0) to sysutils/u-boot-rock64 and found following:

1. MAC addresses are not readied from the hardware 
so a random MAC is assigned at each boot:

Warning: ethernet@ff540000 (eth0) using random MAC address - 3a:c9:e1:25:79:a5
U-Boot's environment variables ethaddr and eth1addr are not assigned.

2. USB 3.0 is not working even after applying of these 2 patches:

3.  USB 2.0 is not working after boot,
but can be enabled manually by this command:

# gpioctl -f /dev/gpioc0 2 0

Unfortunately this is far beyond my experience to fix this
but I'm willing to test if necessary.

Comment 1 Bugzilla Automation freebsd_committer 2019-08-16 11:44:16 UTC
Maintainer informed via mail
Comment 2 Kubilay Kocak freebsd_committer freebsd_triage 2019-08-16 12:38:07 UTC
^Triage: Assign to uboot@ (MAINTAINER of this port) after creating a Bugzilla Account for that address.
Comment 3 Kubilay Kocak freebsd_committer freebsd_triage 2019-08-16 12:39:08 UTC
^Triage: Really, sysutils/u-boot* ports should be maintained by an individual (not a mailing list), so that feedback can be requested from them.
Comment 4 Emmanuel Vadot freebsd_committer 2020-12-13 12:01:28 UTC
Is it still a problem for you ?
Comment 5 Denis Polygalov 2020-12-13 12:31:32 UTC
Unfortunately - no. The board was damaged for a reason not relate to this bug and basically I gave up. Feel free to re-open if it is appropriate.