Bad Linux ARM64 Image magic
On all pi devices we are testing (rpi3, 3b+, cm3, rpi4, etc. ) when refreshing the kernel snap to the 5.4 kernel in 18-pi (r333), it fails to boot. Here’s the serial log on the failed boot from one of those devices:
Hit any key to stop autoboot: 0
WARNING at /build/ u-boot- GPcj9K/ u-boot- 2019.07+ dfsg/drivers/ mmc/bcm2835_ sdhost. c:408/bcm2835_ send_command( )!
WARNING at /build/ u-boot- GPcj9K/ u-boot- 2019.07+ dfsg/drivers/ mmc/bcm2835_ sdhost. c:408/bcm2835_ send_command( )!
switch to partitions #0, OK
mmc0(part 0) is current device
LOADBOOTENV
Running uenvcmd .
ENVCMD
Saving Environment to FAT. OK
8624908 bytes read in 367 ms (22.4 MiB/s)
3947036 bytes read in 171 ms (22 MiB/s)
67581 bytes read in 22 ms (2.9 MiB/s)
Bad Linux ARM64 Image magic!
Armhf seems to be booting just fine after the refresh.
[Where Problems Could Occur]
The worst that can probably happen is that the device won’t boot, which is the current behavior. Well, since the kernel image is bigger I guess we could run out of disk space on the vfat partition.
I also noticed just now that this kernel from the 20 track does seem to work fine on uc20 systems:
pi-kernel 5.4.0-1042.46 331 20/beta
| Changed in linux-raspi-5.4 (Ubuntu Bionic): | |
| status: | New → Fix Committed |
| Changed in linux-raspi-5.4 (Ubuntu): | |
| status: | New → Invalid |
| Changed in linux-raspi-5.4 (Ubuntu Bionic): | |
| assignee: | nobody → Juerg Haefliger (juergh) |
| importance: | Undecided → High |
This appears to be fixed in the current beta kernel for 18-pi — 5.4.0-1042. 46~18.04. 3 r337
This bug was fixed in the package linux-raspi-5.4 — 5.4.0-1042. 46~18.04. 3
—————
linux-raspi-5.4 (5.4.0- 1042.46~ 18.04.3) bionic; urgency=medium
* bionic/ linux-raspi- 5.4: 5.4.0-1042. 46~18.04. 3 -proposed tracker
(LP: #1938917)
* Bad Linux ARM64 Image magic (LP: #1938912)
— [Packaging] raspi-bionic: Build uncompressed arm64 kernel images
linux-raspi-5.4 (5.4.0- 1042.46~ 18.04.1) bionic; urgency=medium
* bionic/ linux-raspi- 5.4: 5.4.0-1042. 46~18.04. 1 -proposed tracker
(LP: #1938037)
* focal/linux-raspi: 5.4.0-1042.46 -proposed tracker (LP: #1936532)
* Packaging resync (LP: #1786013)
— update dkms package versions
* large_dir in ext4 broken (LP: #1933074)
— SAUCE: ext4: fix directory index node split corruption
* Some test in kselftest/net on focal source tree were not tested at all
(LP: #1934282)
— selftests/net: add missing tests to Makefile
* curtin: install flash-kernel in arm64 UEFI unexpected (LP: #1918427)
— [Packaging] Allow grub-efi-arm* to satisfy recommends on ARM
* Add l2tp.sh in net from ubuntu_ kernel_ selftests back (LP: #1934293)
— Revert «UBUNTU: SAUCE: selftests/net — disable l2tp.sh test»
* icmp_redirect.sh in net from ubuntu_ kernel_ selftests failed on F-OEM-5.6 /
F-OEM-5.10 / F-OEM-5.13 / F / G / H (LP: #1880645)
— selftests: icmp_redirect: support expected failures
* Focal update: v5.4.128 upstream stable release (LP: #1934179)
— dmaengine: ALTERA_MSGDMA depends on HAS_IOMEM
— dmaengine: QCOM_HIDMA_MGMT depends on HAS_IOMEM
— dmaengine: stedma40: add missing iounmap() on error in d40_probe()
— afs: Fix an IS_ERR() vs NULL check
— mm/memory-failure: make sure wait for page writeback in memory_failure
— kvm: LAPIC: Restore guard to prevent illegal APIC register access
— batman-adv: Avoid WARN_ON timing related checks
— net: ipv4: fix memory leak in netlbl_ cipsov4_ add_std
— vrf: fix maximum MTU
— net: rds: fix memory leak in rds_recvmsg
— net: lantiq: disable interrupt before sheduling NAPI
— udp: fix race between close() and udp_abort()
— rtnetlink: Fix regression in bridge VLAN configuration
— net/sched: act_ct: handle DNAT tuple collision
— net/mlx5e: Remove dependency in IPsec initialization flows
— net/mlx5e: Fix page reclaim for dead peer hairpin
— net/mlx5: Consider RoCE cap before init RDMA resources
— net/mlx5e: allow TSO on VXLAN over VLAN topologies
— net/mlx5e: Block offload of outer header csum for UDP tunnels
— netfilter: synproxy: Fix out of bounds when parsing TCP options
— sch_cake: Fix out of bounds when parsing TCP options and header
— alx: Fix an error handling path in ‘alx_probe()’
— net: stmmac: dwmac1000: Fix extended MAC address registers definition
— net: make get_net_ns return error if NET_NS is disabled
— qlcnic: Fix an error handling path in ‘qlcnic_probe()’
— netxen_nic: Fix an error handling path in ‘netxen_ nic_probe( )’
— net: qrtr: fix OOB Read in qrtr_endpoint_post
— ptp: improve max_adj check against unreasonable values
— net: cdc_ncm: switch to eth%d interface naming
— lanti.
ODROID
[SOLVED] Bad Linux ARM64 Image magic error on fastboot
bonar Posts: 75 Joined: Mon Aug 03, 2015 3:46 pm languages_spoken: english, Japanese ODROIDs: C1 Has thanked: 0 Been thanked: 0 Contact:
[SOLVED] Bad Linux ARM64 Image magic error on fastboot
Post by bonar » Fri Jun 03, 2016 7:40 pm
I failed to update kernel with fastboot command.
source build/envsetup.sh lunch odroidc2-eng-32 make -j4 selfinstall Buid process completed successfully, and binary files were generated on out/target/product/odroidc2 directory.
(2) I setup v1.5 android sdcard from selfinstall-odroidc2.bin. It worked fine.
(3) I wrote binaries with fastboot command.
adb shell reboot fastboot sudo fastboot flash bootloader u-boot.bin sudo fastboot flash dtb meson64_odroidc2.dtb sudo fastboot flash boot kernel sudo fastboot flash recovery recovery.img sudo fastboot flash logo hardkernel-720.bmp sudo fastboot flash system rootsystem.img sudo fastboot flash cache cache.img sudo fastboot reboot target reported max download size of 536870912 bytes sending 'bootloader' (576 KB). OKAY [ 0.021s] writing 'bootloader'. OKAY [ 0.163s] finished. total time: 0.185s target reported max download size of 536870912 bytes sending 'dtb' (27 KB). OKAY [ 0.004s] writing 'dtb'. OKAY [ 0.018s] finished. total time: 0.022s target reported max download size of 536870912 bytes sending 'boot' (6558 KB). OKAY [ 0.214s] writing 'boot'. OKAY [ 1.658s] finished. total time: 1.872s target reported max download size of 536870912 bytes sending 'recovery' (11604 KB). OKAY [ 0.378s] writing 'recovery'. OKAY [ 2.956s] finished. total time: 3.334s error: cannot load 'hardkernel-720.bmp' target reported max download size of 536870912 bytes sending 'system' (478515 KB). OKAY [ 15.398s] writing 'system'. OKAY [ 66.906s] finished. total time: 82.304s target reported max download size of 536870912 bytes sending 'cache' (70844 KB). OKAY [ 2.293s] writing 'cache'. OKAY [ 7.659s] finished. total time: 9.952s rebooting. After rebooting, it stopped with first Hardkernel logo.
Here is the minicom log. Booting proccess stoped at «Bad Linux ARM64 Image magic!» Error.
Saving Environment to MMC. Writing to MMC(0). done cfgload: showlogo $ reading boot-logo.bmp.gz ** Unable to read file boot-logo.bmp.gz ** reading boot-logo.bmp ** Unable to read file boot-logo.bmp ** movi: the partiton 'logo' is reading. MMC read: dev # 0, block # 58976, count 4096 . 4096 blocks read: OK hpd_state=1 [720p60hz] is invalid for cvbs. set hdmitx VIC = 4 hdmitx phy setting done set hdmitx VIC = 4 hdmitx phy setting done cfgload: movi read dtb 0 $ movi: the partiton 'dtb' is reading. MMC read: dev # 0, block # 1504, count 128 . 128 blocks read: OK cfgload: movi read boot 0 $ movi: the partiton 'boot' is reading. MMC read: dev # 0, block # 1632, count 32768 . 32768 blocks read: OK cfgload: booti $ - $ Bad Linux ARM64 Image magic! reading boot-logo.bmp.gz ** Unable to read file boot-logo.bmp.gz ** reading boot-logo.bmp ** Unable to read file boot-logo.bmp ** movi: the partiton 'logo' is reading. MMC read: dev # 0, block # 58976, count 4096 . 4096 blocks read: OK hpd_state=1 [720p60hz] is invalid for cvbs. set hdmitx VIC = 4 hdmitx phy setting done set hdmitx VIC = 4 hdmitx phy setting done movi: the partiton 'dtb' is reading. MMC read: dev # 0, block # 1504, count 128 . 128 blocks read: OK movi: the partiton 'boot' is reading. MMC read: dev # 0, block # 1632, count 32768 . 32768 blocks read: OK Bad Linux ARM64 Image magic! odroidc2# Saved searches
Use saved searches to filter your results more quickly
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bad Linux ARM64 Image magic! #1
Bad Linux ARM64 Image magic! #1
Comments
Hi there! Thank you for the tutorial. I followed the instructions and booted from the SD card but I get the following message:
.
reading system.dtb
33975 bytes read in 18 ms (1.8 MiB/s)
Bad Linux ARM64 Image magic!
ZynqMP>
Can you help me to resolve this issue?
The text was updated successfully, but these errors were encountered:
Looking at the on-screen logs more closely, I noticed the boot process uses the mmcblk1p2 for SD drive and not the mmcblk0p2 so I updated the PetaLinux project configuration using the petalinux-config accordingly.
Then I found the posts below which are basically stating that the SD is configured read-only for some reason and needs to be writable.
- Added the «disable-wp» to the sdhci1 section in the «petalinux-project-path/project-spec/meta-user/recipes-bsp/device-tree/files/system-user.dtsi:
Please refer to the following links for more information: