This is expected as the default boot sequence doesn't expect the user to
provide an uInitrd. The hanging you're seeing is probably because of
wrong cmdline arguments, as you're also just using the default one
instead of the supported one by ubuntu.
Marking it as Invalid, but let me know if this
So the question is why not attempt to install the uInitrd and boot
whether or not it's present? It's a rare case for Ubuntu to not provide
an uInitrd; if we have pre-programmed uImage and uInitrd memory
addresses why wouldn't we try and load both (not just uImage) and then
boot?
--
You received
But as you'll need to provide at least a valid kernel cmdline (otherwise
it's not going to boot), asking u-boot to load uInitrd seems the best
way to go. I believe the only default behavior we want is to fallback to
pxe when nothing is found at the sd card.
--
You received this bug notification
