Is anyone else having an issue booting today's (JAN 23 2021) images?
I had a device freeze on un-compressing image.
Workaround: I was running a snapshot from MAR 2020, I reverted/manually moved the configs to 19.07.6.
Is anyone else having an issue booting today's (JAN 23 2021) images?
I had a device freeze on un-compressing image.
Workaround: I was running a snapshot from MAR 2020, I reverted/manually moved the configs to 19.07.6.
I have the same issue. Could have bumped over some kernel size limit. Or, well, that's what I thought initially, but ---
Surprisingly this issue doesn't apply when you are booting from initramfs.
Still not fixed on 16 March Snapshot...
@hnyman ...what do you suggest (while I revert again)?
No idea.
No knowledge about apm821xx target.
U-Boot 2009.08-00049-g0ee25dd Meraki MX60 (Jul 27 2012 - 14:59:20)
CPU: AMCC PowerPC UNKNOWN (PVR=12c41c83) at 800 MHz (PLB=200, OPB=100, EB)
Bootstrap Option D - Boot ROM Location NAND wo/ECC 2k page (8 bits), D
32 kB I-Cache 32 kB D-Cache
Board: Buckminster Wireless - Meraki Buckminster Wireless Cloud Managed Routr
============================
BoardID: 0 0
Reset Button Status: 1
============================
SDR0_PERCLK=0x40000300
I2C: ready
DRAM: 512 MB
NAND: 1024 MiB
I2c read: failed 4
I2c read: failed 4
I2c read: failed 4
Net: ppc_4xx_eth0
Initializing Bluestone Ethernet Port ...
Disabling port 0
Disabling port 1
Disabling port 2
Disabling port 3
ENET Speed is 1000 Mbps - FULL duplex connection (EMAC0)
*** ERROR: ping address not given
RESET is un-pushed
Set serverpath and run meraki_netboot to netboot
Hit any key to stop autoboot: 0
Creating 1 MTD partitions on "nand0":
0x000000240000-0x000040000000 : "mtd=2"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=2"
UBI: MTD device size: 1021 MiB
UBI: number of good PEBs: 8171
UBI: number of bad PEBs: 3
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 5
UBI: available PEBs: 76
UBI: total number of reserved PEBs: 8095
UBI: number of PEBs reserved for bad PEB handling: 81
UBI: max/mean erase counter: 207/155
Volume kernel found at volume id 2
read 0 bytes from volume 2 to 800000(buf address)
Read [3999744] bytes
UBI: fixable bit-flip detected at PEB 3078
UBI: schedule PEB 3078 for scrubbing
setting meraki addr env fdt: 0x800400, kernel: 0x810000, ramdisk: 0xbffc00
## Booting kernel from Legacy Image at 00810000 ...
Image Name: POWERPC OpenWrt Linux-5.4.105
Created: 2021-03-15 19:30:21 UTC
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 3808345 Bytes = 3.6 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 00800400
Booting using the fdt blob at 0x800400
Uncompressing Kernel Image ... OK
The Snapshot freezes there.
EDIT: My fear is this issue might have made its way into version 21. I haven't had a chance to test it yet.
Wait...so you were able to sysupgrade the same image after booting?
I'm very curious.
(I never tired to boot the snapshot image, I reverted to a version 19 image to boot.)
I believe that is reflashed in the partition - which should be approximately all remaining space (for my device).
I booted the snapshot initramfs just fine -- the reboot post-sysupgrade on top of it failed. This was after the initial sysupgrade based on 19.07.5 (at the time) failed to boot up after reboot.
Have you had a chance to test 21.02.0-rc1 @hurricos?
So, as of 21.02.0-rc3, the MX60W works just fine:
BusyBox v1.33.1 (2021-06-13 22:02:19 UTC) built-in shell (ash)
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt 21.02.0-rc3, r16172-2aba3e9784
-----------------------------------------------------
root@mx60w:~#
I'm going to now try to sysupgrade to 21.02.0 full release and see what happens.
Works fine:
BusyBox v1.33.1 (2021-08-31 22:20:08 UTC) built-in shell (ash)
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt 21.02.0, r16279-5cc0535800
-----------------------------------------------------
root@mx60w:~#
Please post test results here