[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Dreamplug support



On Mon, Feb 22, 2021 at 9:17 AM Alexandre GRIVEAUX
<agriveaux@deutnet.info> wrote:

>
> Replacing x_bootcmd_kernel=fatload usb 0 0x6400000 uImage by x_bootcmd_kernel=ext2load usb 0 0x6400000 uImage or x_bootcmd_kernel=ext4load usb 0 0x6400000 uImage
>
> But the only most result i was getting is:
>
>
> [   10.724017] List of all partitions:
> [   10.727522] No filesystem could mount root, tried:
> [   10.727525]
> [   10.733946] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
> [   10.742248] CPU: 0 PID: 1 Comm: swapper Not tainted 4.19.0-14-marvell #1 Debian 4.19.171-2
> [   10.750543] Hardware name: Marvell Kirkwood (Flattened Device Tree)
> [   10.756855] [<c00166dc>] (unwind_backtrace) from [<c0013640>] (show_stack+0x18/0x1c)
> [   10.764636] [<c0013640>] (show_stack) from [<c03e5224>] (panic+0xb8/0x250)
> [   10.771551] [<c03e5224>] (panic) from [<c05135a4>] (mount_block_root+0x244/0x2e8)
> [   10.779074] [<c05135a4>] (mount_block_root) from [<c0513820>] (prepare_namespace+0x14c/0x18c)
> [   10.787636] [<c0513820>] (prepare_namespace) from [<c05130e8>] (kernel_init_freeable+0x1e0/0x260)
> [   10.796550] [<c05130e8>] (kernel_init_freeable) from [<c03e6bcc>] (kernel_init+0x10/0xf8)
> [   10.804763] [<c03e6bcc>] (kernel_init) from [<c00090e0>] (ret_from_fork+0x14/0x34)
> [   10.812360] Exception stack(0xdf4bdfb0 to 0xdf4bdff8)
> [   10.817438] dfa0:                                     00000000 00000000 00000000 00000000
> [   10.825653] dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> [   10.833866] dfe0: 00000000 00000000 00000000 00000000 00000013 00000000
> [   10.840514] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---
>
>
> I admit I do most work on armhf were u-boot search for a script (or EFI, extlinux, ...) and boot, do i need to correct armel u-boot do the same ?

The message above tells you that it could find no block devices,
presumably because
the kernel does not have the USB or MMC/SD drivers loaded.

Most likely this means that it failed to unpack the initramfs for some
reason, see in
the earlier boot log if u-boot passed the correct uInitrd file, and if
the kernel has
any messages about unpacking it failing for some reason.

       Arnd


Reply to: