I used kwboot to test the u-boot.kwb you were so kind to provide. Just as a side node. The image is a regular NAND one, and therefore the -p command line option must be given vor kwboot.
I works almost like a charm, I have 3.12.8 up and running. The only downside is, that the networt devices (there are two) are not recongnized while booting, see the statement "No ethernet found." in the log at the end. In turn, no valid MAC is assigned to the devices, and therefore, they can not brought up by dhcp. Once I assign a MAC by hand using e.g.
sudo ifconfig eth0 hw ether 02:01:02:03:04:08
dhcp picks up the device and networking is there again. This flaw is also documented in the excito forum where also the workarround is mentioned.
http://forum.excito.net/viewtopic.php?f ... 677#p24677My question here is, why does this u-boot image not recognize the devices, and why can this be "fixed" by setting the MAC manually.
As always, I am happy to provide any info needed. I also would not mind the get my hands dirty, but somehow moonman seems to have one of those rare marble bowls which gives you to power to do remote debugging w/o a connection...
Thanks again!
###
U-Boot 2013.01-rc1-g64525a2-dirty (Nov 27 2013 - 23:26:07)
BUBBA|3
SoC: Kirkwood 88F6281_A1
DRAM: 512 MiB
WARNING: Caches not enabled
SF: Detected M25P16 with page size 64 KiB, total 2 MiB
In: serial
Out: serial
Err: serial
Net: Net Initialization Skipped
No ethernet found.
88E1116 Initializing on egiga0No such device: egiga0
88E1116 Initializing on egiga1No such device: egiga1
Hit any key to stop autoboot: 0
3821896 bytes read
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.12.8-1-ARCH
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3821832 Bytes = 3.6 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Initializing cgroup subsys cpuset
###