BeagleBone: Problems with booting the Arago AM33XX kernel

Hi everyone!

I’ve been trying to compile the Arago AM33XX kernel repository for my BeagleBone A6 board. The compilation goes fine, however, I am unable to boot the kernel correctly. I am attaching a log of the boot. It seems to be a root fs related issue, but I have no idea where to start fixing it.

If I were to switch to the stock 3.2.28 kernel, the board boots no problem.

Thanks in advance to any suggestions!

kernelLog.txt (13 KB)

Hi,

Did you checked your partitions?

You would have to be a little bit more descriptive than that :slight_smile:

I am somewhat doubtful it’s a problem with the partitions as a simple change of the uImage of the kernel to v3.2.28 (which was the original kernel that I got my board with) results in a successful boot.

– Stefan

Stefan <videvstefan@...> writes:

You would have to be a little bit more descriptive than that :slight_smile:

I am somewhat doubtful it's a problem with the partitions as a simple

change of the uImage of the kernel to v3.2.28 (which was the original kernel
that I got my board with) results in a successful boot.

-- StefanOn Monday, October 22, 2012 5:47:15 PM UTC+1, RANGERS wrote:
Hi,
Did you checked your partitions?
>
> Hi everyone!
>
> I've been trying to compile the Arago AM33XX kernel repository for my

BeagleBone A6 board. The compilation goes fine, however, I am unable to boot
the kernel correctly. I am attaching a log of the boot. It seems to be a
root fs related issue, but I have no idea where to start fixing it.

>
> If I were to switch to the stock 3.2.28 kernel, the board boots no problem.
>
> Thanks in advance to any suggestions!
>
> --
>
>

Hi Stefan, we have the same problem occurring i.e. we get the error :
Failed to mount /dev: No such device

Can you please tell us how you solved the issue?
We are using TI's pre-built JB 4.2.2 image, and therefore, we haven't made
any changes to the image.
We tried an image from elinux.org yesterday, and it worked fine.
We really want to find out what we might've done wrong, so we don't do it
again; earlier the very same image was working perfectly fine on the very
same SD card and same beaglebone black.
Thanks for any help.