Jump to content

initramfs-tools issue "unsupported architecture" unable to write to uboot


Go to solution Solved by pinebookpro-owner,

Recommended Posts

Hello,

unfortunatelly I post again, because of the latest problem with broken install of initramfs .... The system is unable to write it to uboot and gives the error about unsupported architecure. Every standard commands are probed, without result. it comes always the same error.

 

Quote

update-initramfs: Generating /boot/initrd.img-6.6.2-edge-rockchip64
update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.6.2-edge
-rockchip64

Invalid architecture, supported are:
    alpha            Alpha
    arc              ARC
    arm              ARM
    arm64            AArch64
    avr32            AVR32
    blackfin         Blackfin
    ia64             IA64
    invalid          Invalid ARCH
    m68k             M68K
    microblaze       MicroBlaze
    mips             MIPS
    mips64           MIPS 64 Bit
    nds32            NDS32
    nios2            NIOS II
    or1k             OpenRISC 1000
    powerpc          PowerPC
    riscv            RISC-V
    s390             IBM S390
    sandbox          Sandbox
    sh               SuperH
    sparc            SPARC
    sparc64          SPARC 64 Bit
    x86              Intel x86
    x86_64           AMD x86_64
    xtensa           Xtensa

Error: Invalid architecture
Usage: mkimage -l image
          -l ==> list image header information
       mkimage [-x] -A arch -O os -T type -C comp -a addr -e ep -n name -d data_
file[:data_file...] image
          -A ==> set architecture to 'arch'
          -O ==> set operating system to 'os'
          -T ==> set image type to 'type'
          -C ==> set compression type 'comp'
          -a ==> set load address to 'addr' (hex)
          -e ==> set entry point to 'ep' (hex)
          -n ==> set image name to 'name'
          -d ==> use image data from 'datafile'
          -x ==> set XIP (execute in place)
       mkimage [-D dtc_options] [-f fit-image.its|-f auto|-F] [-b <dtb> [-b <dtb
>]] [-E] [-B size] [-i <ramdisk.cpio.gz>] fit-image
           <dtb> file is used with -f auto, it may occur multiple times.
          -D => set all options for device tree compiler
          -f => input filename for FIT source
          -i => input filename for ramdisk file
          -E => place data outside of the FIT structure
          -B => align size in hex for FIT structure and header
Signing / verified boot options: [-k keydir] [-K dtb] [ -c <comment>] [-p addr]
[-r] [-N engine]
          -k => set directory containing private keys
          -K => write public keys to this .dtb file
          -G => use this signing key (in lieu of -k)
          -c => add comment in signature node
          -F => re-sign existing FIT image
          -p => place external data at a static position
          -r => mark keys used as 'required' in dtb
          -N => openssl engine to use for signing
       mkimage -V ==> print version information and exit
Use '-T list' to see a list of available image types
run-parts: /etc/initramfs/post-update.d//99-uboot exited with return code 1
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned
error exit status 1
Errors were encountered while processing:
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

 

Link to comment
Share on other sites

Armbian & Khadas are rewarding contributors

I am experiencing same problem but on pine64.

 

update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.7.12-edge-sunxi64

Invalid architecture, supported are:
    alpha            Alpha
    arc              ARC
    arm              ARM
    arm64            AArch64
    avr32            AVR32
    blackfin         Blackfin
    ia64             IA64
    invalid          Invalid ARCH
    m68k             M68K
    microblaze       MicroBlaze
    mips             MIPS
    mips64           MIPS 64 Bit
    nds32            NDS32
    nios2            NIOS II
    or1k             OpenRISC 1000
    powerpc          PowerPC
    riscv            RISC-V
    s390             IBM S390
    sandbox          Sandbox
    sh               SuperH
    sparc            SPARC
    sparc64          SPARC 64 Bit
    x86              Intel x86
    x86_64           AMD x86_64
    xtensa           Xtensa

Error: Invalid architecture
Usage: mkimage [-T type] -l image
          -l ==> list image header information
          -T ==> parse image file as 'type'
          -q ==> quiet
       mkimage [-x] -A arch -O os -T type -C comp -a addr -e ep -n name -d data_file[:data_file...] image
          -A ==> set architecture to 'arch'
          -O ==> set operating system to 'os'
          -T ==> set image type to 'type'
          -C ==> set compression type 'comp'
          -a ==> set load address to 'addr' (hex)
          -e ==> set entry point to 'ep' (hex)
          -n ==> set image name to 'name'
          -R ==> set second image name to 'name'
          -d ==> use image data from 'datafile'
          -x ==> set XIP (execute in place)
          -s ==> create an image with no data
          -v ==> verbose
       mkimage [-D dtc_options] [-f fit-image.its|-f auto|-f auto-conf|-F] [-b <dtb> [-b <dtb>]] [-E] [-B size] [-i <ramdisk.cpio.gz
>] fit-image
           <dtb> file is used with -f auto, it may occur multiple times.
          -D => set all options for device tree compiler
          -f => input filename for FIT source
          -i => input filename for ramdisk file
          -E => place data outside of the FIT structure
          -B => align size in hex for FIT structure and header
          -b => append the device tree binary to the FIT
          -t => update the timestamp in the FIT
Signing / verified boot options: [-k keydir] [-K dtb] [ -c <comment>] [-p addr] [-r] [-N engine]
          -k => set directory containing private keys
          -K => write public keys to this .dtb file
          -g => set key name hint
          -G => use this signing key (in lieu of -k)
          -c => add comment in signature node
          -F => re-sign existing FIT image
          -p => place external data at a static position
          -r => mark keys used as 'required' in dtb
          -N => openssl engine to use for signing
          -o => algorithm to use for signing
       mkimage -V ==> print version information and exit
Use '-T list' to see a list of available image types
Long options are available; read the man page for details
run-parts: /etc/initramfs/post-update.d//99-uboot exited with return code 1
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 linux-image-current-sunxi64
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1

Link to comment
Share on other sites

I got it working again. Installed "current" kernel but the same issue was showing during an attempt to update initramfs. So I uninstalled initramfs-tools and did apt autoremove to remove package leftovers.

 

Then I installed armbian-bsp-cli-pine64-current and I got strange response 'version <none>' but then everything started working included broken initramfs update.

 

aptitude install armbian-bsp-cli-pine64-current
W: Package initramfs-tools had been marked to reinstall, but the file for the current installed version <none> is not available
The following NEW packages will be installed:
  armbian-bsp-cli-pine64-current busybox-initramfs{a} dracut-install{a} fping{a} initramfs-tools{a} initramfs-tools-bin{a}
  initramfs-tools-core{a} klibc-utils{a} libklibc{a}

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines