by mlitke » Wed May 15, 2013 5:56 am
If you have a serial connection and can access the UBoot environment directly, the command is "printenv" and look for the ethaddr variable. If you are able to boot back into a Arch Linux ARM environment, make sure you have the uboot-env package installed, and run "fw_printenv", also look for the ethaddr variable.
I ran a test where in the UBoot environment I cleared/unset the ethaddr variable (it looks like you cannot set or unset the variable with fw_setenv) and rebooted a few times. Each time I rebooted, I got a different MAC address. They all started with 02:50:43. So, my guess is somehow your ethaddr variable got unset.