Print

[Confusticated]

I downloaded Mira-RescueDisk.rar, unarchived, and examined the kernel file 'mirabox'

Code: [Select]

[[email protected] Mira-RescueDisk]$ mkimage -l mirabox
Image Name:   Linux-3.4.2
Created:      Wed Nov 14 14:11:52 2012
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    3944280 Bytes = 3851.84 kB = 3.76 MB
Load Address: 00008000
Entry Point:  00008000
The kernel version is different from that in your posts ?!?
Are you sure you wrote the kernel to the correct partition ?

[shazled]

Hello,
  I just got my Mirabox today and I have the same problem.

I reflashed the kernel and rootfs to:
uImage_3.2.6_nand_new
rootfs_mira_debian7_v5_v7_arm8766.img

Output from uboot:

Code: [Select]

Marvell>> mtdparts

device nand0 <armada-nand>, # parts = 2
 #: name                size                    offset                  mask_flags
 0: boot                0x000000600000          0x000000000000          0
 1: rootfs              0x00003fa00000          0x000000600000          0

active partition: nand0,0 - (boot) 0x000000600000 @ 0x000000000000

defaults:
mtdids  : none
mtdparts: none
Marvell>> printenv mtdparts
mtdparts=mtdparts=armada-nand:6m(boot),-(rootfs)

Kernel panic:

Code: [Select]

VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00            6144 mtdblock0  (driver?)
1f01         1042432 mtdblock1  (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Does anyone have any ideas?
Thanks for the help
Saul