Hi moscar,
First of all, please keep in mind that I'm trying to find out what is different between a cubieboard2 and a cubietruck. That is why I started with a fresh install following the current instructions for the cubieboard2, looking for what must be changed.
In the current tarball for the cubieboard2, /boot/uEnv.txt has a single line 'machid=0xf35', which is not the correct id for an A20 CPU. If I try to boot your kernel with this line, I get the following error message, as expected:
$this->bbcode_second_pass_code('', '
Error: unrecognized/unsupported machine ID (r1 = 0x00000f35).
Available machine support:
ID (hex) NAME
000010bb sun7i
000010bb sun7i
0000102a sun5i
0000102a sun5i
00001008 sun4i
00001008 sun4i
Please check your kernel config and/or bootloader.')
Omiting machid from uEnv.txt works fine, as the sunxi kernel detects the correct machine:
$this->bbcode_second_pass_code('', '[ 0.000000] sunxi: Allwinner A20 (AW1651/sun7i) detected.')
Looks like the provided /boot/uEnv.txt will have to be changed in order to have a working combination of recent sunxi kernel + u-boot + uEnv.txt.
I am looking into the fex file right now and will let you know as soon as I make some progress.
Finally, I have tested my cubietruck with one of the Android images provided by
http://cubieboard.org/download/, so the ethernet port does work. I guess there is something with the hardware description in the fex.
Thanks for your time and patience,