U-boot stuck at Raspberry logo

[hhjohan]

I am trying to set up a Raspberry pi B model to boot with U-boot, kernel on tftp and file system on NFS.
It loads the kernel from the tftp server I see, but after the kernel is started it comes to a screen with just the raspberry logo, nothing more happens.
I have another SD-card with normal Rasbian installation working fine so the hardware is ok.
I didn’t compile the kernel myself I just copied the kernel.img from the other SD-card to my tftp server
I can't figure out what is wrong.
Any suggestions where the problem could be?

[hhjohan]

I got a little further on this problem.
I added u-boot to an existing working Rasbian installation and loaded the kernel from tftp and that part is working, so I guess the problem is when it tries to mount the NFS share for the file system.
So back to the other SD-card and tried booting I see on my NAS (Freenas 9.2.1.7) that it reports that the pi changed hardware address during boot.

So it seems that between the kernel load from tftp and when it mounts the nfs share to load file system the pi changes hardware address, as my NAS doesn’t update the arp table the pi will be inaccessible from the nas.

This is my current uEnv.txt

ipaddr=192.168.0.20
netmask=255.255.255.0
serverip=192.168.0.91
bootargs=console=ttyAMA0,115200 root=/dev/nfs rw nfsroot=192.168.0.91:mnt/storage1/RaspberryPi1,tcp,vers3 rootwait ip=192.168.0.20:192.168.0.91:192.168.0.1:255.255.255.0:rpi:eth0:off rootfstype=nfs
bootcmd=usb start; dhcp ${kernel_addr_r} zImage; tftp ${fdt_addr_r} bcm2708-rpi-b.dtb; bootz ${kernel_addr_r} - ${fdt_addr_r};

[Aydan]

The linux kernel generates the MAC for the Pi with a fixed prefix and ends with the serial number of the CPU.
If u-boot doesn't do it the same way, you'll get different MAC addresses.
On the other hand it shouldn't matter, since your DHCP server will just see 2 different macs and assign two different IPs.

Regards
Aydan

[hhjohan]

Yes, I solved that part by adding two different static ip-addresses. But it still doesn’t boot.

I am starting to think there is some kind of compatibility issue or bug, I will try to use my Qnap NAS instead and see if that works better.

[hhjohan]

I have just tested to use my Qnap nas instead with no success.
So there must be something wrong in the script (uEnv.txt) or how I place the file system.