nanasi Wrote:buddyrm Wrote:Maybe it is the Version 1.3 Looks like it is waiting for some hardware readiness that never finished.
I suppose that a uninitialized cpu-fuse is the cause for the phenomenon.
I remember the non-unique MAC-address trouble.
Probably not because I have such version without mac address. That's why in this case it is set to 1E:ED:19:27:1A:B2 in u-boot.