[FS#3539] ramips/mt7620 snapshot does not boot

OpenWrt Bugs openwrt-bugs at lists.openwrt.org
Wed Dec 30 05:55:53 EST 2020


THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#3539 - ramips/mt7620 snapshot does not boot
User who did this - Russell Senior (russell)

----------
Fwiw, /proc/mtd doesn't tell you the layout, it only tells you the mapping of partition number to name and size, not offset. You can get offset by looking in dmesg output not too long after boot. I typically pipe dmesg through grep 0x0 for something like this:

# dmesg | grep 0x0
[    0.000000]   Normal   [mem 0x0000000000000000-0x0000000007ffffff]
[    0.000000]   node   0: [mem 0x0000000000000000-0x0000000007ffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000007ffffff]
[    0.600627] 0x000000000000-0x000000030000 : "u-boot"
[    0.611598] 0x000000030000-0x000000040000 : "u-boot-env"
[    0.623275] 0x000000040000-0x000000050000 : "factory"
[    0.634397] 0x000000050000-0x000002000000 : "firmware"
[    0.670696] 0x000000000000-0x0000001dad67 : "kernel"
[    0.681597] 0x0000001dad67-0x000001fb0000 : "rootfs"
[    0.717737] 0x0000006a0000-0x000001fb0000 : "rootfs_data"


The kernel, rootfs and rootfs_data offsets are relative to the firmware partition, in this case.
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=3539#comment9238

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.



More information about the openwrt-bugs mailing list