04-04-2021, 04:27 PM
Oh, I fully understand armbian in this regard.
I have 4 4GB rock64. None of them has a serial number, either printed on them, or set in the efuse. In fact the efuse is empty. This results in stuff like this:
https://forum.armbian.com/topic/14653-ro...wo-boards/
This was not such an issue before uboot got proper efuse-support, because before that the MAC was set random at first boot. However, with any new enough uboot (and I think we are talking a release at least 1-2 year old) and the more of the proper hardware that is brought up in mainline expose more problems like this in the rock64.
For me this shows very much by downloading the buster minimal image from https://github.com/ayufan-rock64/linux-b...ag/0.10.12 to an SD card and use the same card to boot all 4 boards .
uboot will for all 4 boards report:
And Linux will report:
The last one should not be all 0.
The same if I boot Fedora 33 on it.
Also my boards have problems to reboot from time to time, or rather sometimes they do not come up afterwards.
There has also been unstable eth and USB.
For a community project like armbian having to deal with this kind of support is not sustainable.
I have 4 4GB rock64. None of them has a serial number, either printed on them, or set in the efuse. In fact the efuse is empty. This results in stuff like this:
https://forum.armbian.com/topic/14653-ro...wo-boards/
This was not such an issue before uboot got proper efuse-support, because before that the MAC was set random at first boot. However, with any new enough uboot (and I think we are talking a release at least 1-2 year old) and the more of the proper hardware that is brought up in mainline expose more problems like this in the rock64.
For me this shows very much by downloading the buster minimal image from https://github.com/ayufan-rock64/linux-b...ag/0.10.12 to an SD card and use the same card to boot all 4 boards .
uboot will for all 4 boards report:
Code:
cpuid#=300bf2fc000000008c79f4fe00000000
ethaddr=a2:f5:47:18:b2:e3And Linux will report:
Code:
root@rock64:~# xxd /sys/bus/nvmem/devices/rockchip-efuse0/nvmem
00000000: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000010: 0000 0000 0000 0000 0000 0000 0000 0000 ................The last one should not be all 0.
The same if I boot Fedora 33 on it.
Also my boards have problems to reboot from time to time, or rather sometimes they do not come up afterwards.
There has also been unstable eth and USB.
For a community project like armbian having to deal with this kind of support is not sustainable.