Magnets Posted Friday at 04:28 PM Posted Friday at 04:28 PM (edited) I am running a old buster image and ran apt-get upgrade, now it won't boot. Armbian 21.02.3 Buster with Linux 5.15.93-sunxi64 Get:8 http://netcup.armbian.com/apt buster/main arm64 linux-u-boot-orangepipc2-current arm64 25.2.3 [336 kB] ... Unpacking armbian-firmware (25.2.3) over (23.08.0-trunk--1-SA1251-B226d) ... dpkg: error processing archive /tmp/apt-dpkg-install-RjldFI/034-armbian-firmware_25.2.3_all.deb (--unpack): trying to overwrite '/lib/firmware/ath10k/QCA9377/hw1.0/board-2.bin', which is also in package firmware-atheros 20190114+really20220913-0+deb10u2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) ... Preparing to unpack .../089-linux-dtb-current-sunxi64_25.2.3_arm64.deb ... Armbian 'linux-dtb-current-sunxi64' for '6.6.75-current-sunxi64': 'preinst' starting. Armbian 'linux-dtb-current-sunxi64' for '6.6.75-current-sunxi64': 'preinst' finishing. Unpacking linux-dtb-current-sunxi64 (25.2.3) over (23.02.2) ... dpkg: warning: unable to delete old directory '/boot/dtb-5.15.93-sunxi64/allwinner': Directory not empty dpkg: warning: unable to delete old directory '/boot/dtb-5.15.93-sunxi64': Directory not empty Preparing to unpack .../090-linux-image-current-sunxi64_25.2.3_arm64.deb ... Armbian 'linux-image-current-sunxi64' for '6.6.75-current-sunxi64': 'preinst' starting. update-initramfs: Deleting /boot/initrd.img-5.15.93-sunxi64 Removing obsolete file uInitrd-5.15.93-sunxi64 Armbian 'linux-image-current-sunxi64' for '6.6.75-current-sunxi64': 'preinst' finishing. Unpacking linux-image-current-sunxi64 (25.2.3) over (23.02.2) ... Preparing to unpack .../091-linux-u-boot-orangepipc2-current_25.2.3_arm64.deb ... Unpacking linux-u-boot-orangepipc2-current (25.2.3) over (23.02.2) ... ... Errors were encountered while processing: /tmp/apt-dpkg-install-RjldFI/034-armbian-firmware_25.2.3_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ... Preparing to unpack .../armbian-firmware_25.2.3_all.deb ... Unpacking armbian-firmware (25.2.3) over (23.08.0-trunk--1-SA1251-B226d) ... dpkg: error processing archive /var/cache/apt/archives/armbian-firmware_25.2.3_all.deb (--unpack): trying to overwrite '/lib/firmware/ath10k/QCA9377/hw1.0/board-2.bin', which is also in package firmware-atheros 20190114+really20220913-0+d eb10u2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/armbian-firmware_25.2.3_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) after rebooting U-Boot SPL 2019.10-armbian (Feb 17 2020 - 08:45:21 +0100) DRAM: 1024 MiB Trying to boot from MMC1 NOTICE: BL31: v2.2(debug):572fcdd-dirty NOTICE: BL31: Built : 08:45:08, Feb 17 2020 NOTICE: BL31: Detected Allwinner H5 SoC (1718) NOTICE: BL31: Found U-Boot DTB at 0x40a1650, model: Xunlong Orange Pi PC 2 INFO: ARM GICv2 driver initialized INFO: Configuring SPC Controller NOTICE: PMIC: Assuming H5 reference regulator design INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for 855873 was applied INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 U-Boot 2019.10-armbian (Feb 17 2020 - 08:45:21 +0100) Allwinner Technology CPU: Allwinner H5 (SUN50I) Model: Xunlong Orange Pi PC 2 DRAM: 1 GiB MMC: mmc@1c0f000: 0 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** In: serial Out: serial Err: serial Allwinner mUSB OTG (Peripheral) Net: phy interface7 eth0: ethernet@1c30000 Warning: usb_ether using MAC address from ROM , eth1: usb_ether 230454 bytes read in 18 ms (12.2 MiB/s) starting USB... Bus usb@1c1a000: USB EHCI 1.00 Bus usb@1c1a400: USB OHCI 1.0 Bus usb@1c1b000: USB EHCI 1.00 Bus usb@1c1b400: USB OHCI 1.0 Bus usb@1c1c000: USB EHCI 1.00 Bus usb@1c1c400: USB OHCI 1.0 Bus usb@1c1d000: USB EHCI 1.00 Bus usb@1c1d400: USB OHCI 1.0 scanning bus usb@1c1a000 for devices... 1 USB Device(s) found scanning bus usb@1c1a400 for devices... 1 USB Device(s) found scanning bus usb@1c1b000 for devices... 1 USB Device(s) found scanning bus usb@1c1b400 for devices... 1 USB Device(s) found scanning bus usb@1c1c000 for devices... 2 USB Device(s) found scanning bus usb@1c1c400 for devices... 1 USB Device(s) found scanning bus usb@1c1d000 for devices... 2 USB Device(s) found scanning bus usb@1c1d400 for devices... 1 USB Device(s) found scanning usb for storage devices... 2 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3069 bytes read in 6 ms (499 KiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 165 bytes read in 2 ms (80.1 KiB/s) libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! Bad Linux ARM64 Image magic! SCRIPT FAILED: continuing... Device 0: Vendor: ACASIS Rev: 0508 Prod: Type: Hard Disk Capacity: 228936.5 MB = 223.5 GB (468862128 x 512) ... is now current device ** Unrecognized filesystem type ** ethernet@1c30000 Waiting for PHY auto negotiation to complete....... done BOOTP broadcast 1 DHCP client bound to address 10.0.0.126 (7 ms) *** Warning: no boot file name; using '0A00007E.img' Using ethernet@1c30000 device TFTP from server 10.0.0.136; our IP address is 10.0.0.126 Filename '0A00007E.img'. Load address: 0x42000000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/01-02-01-1a-9a-1c-cb Using ethernet@1c30000 device TFTP from server 10.0.0.136; our IP address is 10.0.0.126 Filename 'pxelinux.cfg/01-02-01-1a-9a-1c-cb'. Load address: 0x4fd00000 Loading: T T T T T T T T T T armbianEnv.txt verbosity=1 console=both overlay_prefix=sun50i-h5 rootdev=UUID=5d4a9712-49dd-4566-8f99-28aba89a7816 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u boot.cmd mw.l 0x01C20020 0x80101810 # DO NOT EDIT THIS FILE # # Please edit /boot/armbianEnv.txt to set supported parameters # # default values setenv load_addr "0x44000000" setenv rootdev "/dev/mmcblk0p1" setenv verbosity "1" setenv rootfstype "ext4" setenv console "both" setenv docker_optimizations "on" # Print boot source itest.b *0x10028 == 0x00 && echo "U-boot loaded from SD" itest.b *0x10028 == 0x02 && echo "U-boot loaded from eMMC or secondary SD" itest.b *0x10028 == 0x03 && echo "U-boot loaded from SPI" echo "Boot script loaded from ${devtype}" if test -e ${devtype} ${devnum} ${prefix}armbianEnv.txt; then load ${devtype} ${devnum} ${load_addr} ${prefix}armbianEnv.txt env import -t ${load_addr} ${filesize} fi if test "${console}" = "display" || test "${console}" = "both"; then setenv consoleargs "console=ttyS0,115200 console=tty1"; fi if test "${console}" = "serial"; then setenv consoleargs "console=ttyS0,115200"; fi # get PARTUUID of first partition on SD/eMMC it was loaded from # mmc 0 is always mapped to device u-boot (2016.09+) was loaded from if test "${devtype}" = "mmc"; then part uuid mmc 0:1 partuuid; fi setenv bootargs "root=${rootdev} rootwait rootfstype=${rootfstype} ${consoleargs} panic=10 consoleblank=0 loglevel=${verbosity} ubootpart=${partuuid} usb-storage.quirks=${usbstoragequirks} ${extraargs} ${extraboardargs}" if test "${docker_optimizations}" = "on"; then setenv bootargs "${bootargs} cgroup_enable=memory swapaccount=1"; fi load ${devtype} ${devnum} ${fdt_addr_r} ${prefix}dtb/${fdtfile} fdt addr ${fdt_addr_r} fdt resize 65536 for overlay_file in ${overlays}; do if load ${devtype} ${devnum} ${load_addr} ${prefix}dtb/allwinner/overlay/${overlay_prefix}-${overlay_file}.dtbo; then echo "Applying kernel provided DT overlay ${overlay_prefix}-${overlay_file}.dtbo" fdt apply ${load_addr} || setenv overlay_error "true" fi done for overlay_file in ${user_overlays}; do if load ${devtype} ${devnum} ${load_addr} ${prefix}overlay-user/${overlay_file}.dtbo; then echo "Applying user provided DT overlay ${overlay_file}.dtbo" fdt apply ${load_addr} || setenv overlay_error "true" fi done if test "${overlay_error}" = "true"; then echo "Error applying DT overlays, restoring original DT" load ${devtype} ${devnum} ${fdt_addr_r} ${prefix}dtb/${fdtfile} else if load ${devtype} ${devnum} ${load_addr} ${prefix}dtb/allwinner/overlay/${overlay_prefix}-fixup.scr; then echo "Applying kernel provided DT fixup script (${overlay_prefix}-fixup.scr)" source ${load_addr} fi if test -e ${devtype} ${devnum} ${prefix}fixup.scr; then load ${devtype} ${devnum} ${load_addr} ${prefix}fixup.scr echo "Applying user provided fixup script (fixup.scr)" source ${load_addr} fi fi load ${devtype} ${devnum} ${ramdisk_addr_r} ${prefix}uInitrd load ${devtype} ${devnum} ${kernel_addr_r} ${prefix}Image booti ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r} # Recompile with: # mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr /boot dir -rw-r--r-- 1 root root 263 Mar 18 2019 armbianEnv.bad.bak -rw-r--r-- 1 root root 165 Mar 1 13:17 armbianEnv.txt -rw-r--r-- 1 root root 165 Mar 18 2019 armbianEnv.txt.fresh -rw-r--r-- 1 root root 165 Jul 6 2024 armbianEnv.txt.good -rw-r--r-- 1 root root 0 Jan 14 2019 armbianEnv.txt.out -rw-r--r-- 1 root root 1536 Jan 9 2019 armbian_first_run.txt.template -rw-r--r-- 1 root root 230454 Jan 9 2019 boot.bmp -rw-r--r-- 1 root root 2997 Jan 11 2019 boot.cmd -rw-r--r-- 1 root root 4882 Jan 9 2019 boot-desktop.png -rw-rw-r-- 1 root root 3069 Jan 11 2019 boot.scr -rw-r--r-- 1 root root 223045 Feb 26 15:06 config-6.6.75-current-sunxi64 drwxr-xr-x 3 root root 4096 Mar 9 2020 dtb-4.19.104-sunxi64 drwxr-xr-x 2 root root 4096 Feb 1 2019 dtb-4.19.13-sunxi64 drwxr-xr-x 3 root root 4096 Feb 12 2019 dtb-4.19.20-sunxi64 drwxr-xr-x 3 root root 4096 Apr 16 2019 dtb-4.19.25-sunxi64 drwxr-xr-x 3 root root 4096 May 14 2019 dtb-4.19.38-sunxi64 drwxr-xr-x 3 root root 4096 Jul 6 2019 dtb-4.19.57-sunxi64 drwxr-xr-x 3 root root 4096 Aug 3 2019 dtb-4.19.63-sunxi64 drwxr-xr-x 3 root root 4096 Feb 11 2021 dtb-5.10.12-sunxi64 drwxr-xr-x 3 root root 4096 Feb 18 2021 dtb-5.10.16-sunxi64 drwxr-xr-x 3 root root 4096 Mar 29 2021 dtb-5.10.21-sunxi64 drwxr-xr-x 3 root root 4096 May 14 2021 dtb-5.10.34-sunxi64 drwxr-xr-x 3 root root 4096 Jan 10 2021 dtb-5.10.4-sunxi64 drwxr-xr-x 3 root root 4096 Sep 25 2021 dtb-5.10.60-sunxi64 drwxr-xr-x 3 root root 4096 Mar 10 2022 dtb-5.15.25-sunxi64 drwxr-xr-x 3 root root 4096 Aug 3 2022 dtb-5.15.48-sunxi64 drwxr-xr-x 3 root root 4096 Nov 5 2022 dtb-5.15.74-sunxi64 drwxr-xr-x 3 root root 4096 Mar 1 2023 dtb-5.15.93-sunxi64 drwxr-xr-x 3 root root 4096 May 10 2020 dtb-5.4.28-sunxi64 drwxr-xr-x 3 root root 4096 Jun 6 2020 dtb-5.4.43-sunxi64 drwxr-xr-x 3 root root 4096 Aug 23 2020 dtb-5.7.15-sunxi64 drwxr-xr-x 3 root root 4096 Sep 24 2020 dtb-5.8.10-sunxi64 drwxr-xr-x 3 root root 4096 Sep 26 2020 dtb-5.8.11-sunxi64 drwxr-xr-x 3 root root 4096 Oct 9 2020 dtb-5.8.13-sunxi64 drwxr-xr-x 3 root root 4096 Oct 18 2020 dtb-5.8.14-sunxi64 drwxr-xr-x 3 root root 4096 Oct 27 2020 dtb-5.8.16-sunxi64 drwxr-xr-x 3 root root 4096 Sep 8 2020 dtb-5.8.6-sunxi64 drwxr-xr-x 3 root root 4096 Dec 17 2020 dtb-5.9.14-sunxi64 drwxr-xr-x 3 root root 4096 Mar 21 15:49 dtb-6.6.75-current-sunxi64 lrwxrwxrwx 1 root root 20 Mar 9 2020 dtb.old -> dtb-4.19.104-sunxi64 lrwxrwxrwx 1 root root 23 Mar 1 2023 Image -> vmlinuz-5.15.93-sunxi64 -rw-r--r-- 1 root root 3584829 Feb 26 15:06 System.map-6.6.75-current-sunxi64 lrwxrwxrwx 1 root root 23 Aug 2 2023 uInitrd -> uInitrd-5.15.93-sunxi64 Edited Friday at 06:29 PM by Magnets 0 Quote
Magnets Posted Friday at 11:31 PM Author Posted Friday at 11:31 PM (edited) I tried copying dtb and initrd for 6.6.75 but it wouldn't boot. I managed to mount the system using chroot on x64 machine using binfmt-support and qemu-user-static, downgraded kernel using what I had available in apt-cache 5.15.93-sunxi64 #23.02.2 i also had to downgrade dtb package as suggested here No FDT memory address configured. Please configure ERROR: Did not find a cmdline Flattened Device Tree all working Edited Friday at 11:31 PM by Magnets 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.