JuanEsf Posted July 11 Posted July 11 @re.ADW You can generate and share the "SHA256" hash of the image that was used on your board, please... 0 Quote
re.ADW Posted July 12 Posted July 12 @JuanEsf Yep, here it is a080ed7128c898bec1cad6ec68c57bae159169d2fa06fb18008100ad63e4445c 0 Quote
Randy Joshua Simorangkir Posted July 18 Posted July 18 i used OPi4a then using image, but no one USB sound card working, lsusb found the device but not registered as sound device, alsamixer,pulse audio does not detect device. how to fix ? i'm using image : Orangepi4a_1.0.4_ubuntu_jammy_desktop_gnome_linux5.15.147 frome here : Gdrive 0 Quote
Werner Posted July 18 Posted July 18 56 minutes ago, Randy Joshua Simorangkir said: Orangepi4a_1.0.4_ubuntu_jammy_desktop_gnome_linux5.15.147 This is not an Armbian image. We do not support 3rd party images. 1 Quote
Randy Joshua Simorangkir Posted July 18 Posted July 18 ah i see, sorry. is there armbian OS for Opi4A? i didnt found yet, on official page armbian, only for OPI4 and OPI4 LTs. thank you in advance 0 Quote
Werner Posted July 18 Posted July 18 No, this board isn't supported. However anyone from the community can step up and add support for it. Found an attempt on Github:https://github.com/juanesf/build/pull/1 1 Quote
cvxx Posted July 28 Posted July 28 @JuanEsf in case you need testing - I own both OrangePi 4A and Radxa Cubie A5E. So far I tried to build the image from your repo (https://github.com/juanesf/build) - neither board boots for me. 0 Quote
ioncube Posted August 9 Posted August 9 I think this OS for T527 Allwinner should work on 4A. Official 4A releases are stuck at jammy while this has Noble https://github.com/AvaotaSBC/AvaotaOS/releases If you observe the contents inside `linux-dtb-sun55i-t527-bsp_0.3.0.4_arm64.deb` you will realise it's doesn't have 4A `dtb` So after burning image copy `dtb` File from jammy. Kernel is same so I belive it should work 0 Quote
ioncube Posted August 9 Posted August 9 Regarding the VPU under jammy I have compiled a guide here https://github.com/defencedog/orangepi4A/tree/main/GPU_VPU Gstreamer players like clapper do use HW acceleration for H264 & H265 (however 10bit HEVC) are not working ad per my tests Version 1.0 of `libcedarc` is used. In v2.0 HEVC 10bit support is added. If anyone can provide git links & some help to compile I am ready to spend time on it In whole internet I only got x1 git for this https://gitlab.com/tina5.0_aiot/media/cedarc-release/libcedarc_v2.0 0 Quote
ioncube Posted August 25 Posted August 25 I further expanded kernel because VPN clients like twingate needed a module `tun` more on this here https://github.com/defencedog/orangepi4A/tree/main/kernels#update-2 0 Quote
BillyBlaze Posted September 7 Posted September 7 (edited) None of the images are no longer working for me, no matter which recent image I take, the A5E board just remains stuck with a solid blue light (with some green light flickering). I even tried compiling armbian myself, but that also didn't work. The only image working for me is the 25.02 version from earlier this year. I am using the Radxa A5E v1.2 version with 4gb ram. I also mounted the SD card to a linux machine and looked into /var/log for a boot file or reading the journal but I don't see any logs written. Have somebody stumbled unto a solution or does somebody have advice me how I can get the logs to find the culprit? Edited September 7 by BillyBlaze 0 Quote
BillyBlaze Posted September 10 Posted September 10 I was able to find a UART module to read out the boot. See the file attached of the full log I was able to capture. It seems to fail on this part: Starting kernel ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. done. Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! UUID=0a0755af-1936-4167-9d26-9ca9a87a9103 does not exist. Dropping to a shell! U-Boot SPL 2025.10-rc3-armbian-2025.txt 0 Quote
Marvin-03 Posted 1 hour ago Posted 1 hour ago Zitat ny Ubuntu Noble release? https://mega.nz/folder/Gv5VjKqL#SLnQdtk8XS8j3twNSFLsVQ I uploaded a Trixie and Noble image, I didnt test the noble one yet. I added pcie and spi support in U-Boot and the Kernel yet somehow if I try to directly load the kernel from the nvme I get stuck on Starting Kernel. I just added the nvme to the boot targets and set bootcmd_nvme to 'devnum=0; run nvme_boot', did I miss any steps? The Led blinks one time and then light in blue permanently. U-Boot SPL 2026.01-rc2-armbian-2026.01-rc2-S365a-Pd317-He0b4-V52aa-Bb703-R448a (Nov 11 2025 - 08:59:26 +0000) DRAM: 4096 MiB Trying to boot from sunxi SPI NOTICE: BL31: v2.12.0(debug):armbian NOTICE: BL31: Built : 14:59:35, Jul 18 2025 NOTICE: BL31: Detected Allwinner A523 SoC (1890) NOTICE: BL31: Found U-Boot DTB at 0xa0bbf80, model: Radxa Cubie A5E INFO: GICv3 without legacy support detected. INFO: ARM GICv3 driver initialized in EL3 INFO: Maximum SPI INTID supported: 287 INFO: Configuring SPC Controller INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a55: CPU workaround for erratum 1530923 was applied INFO: PSCI: Suspend is unavailable INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 ns16550_serial serial@2500000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 U-Boot 2026.01-rc2-armbian-2026.01-rc2-S365a-Pd317-He0b4-V52aa-Bb703-R448a (Nov 11 2025 - 08:59:26 +0000) Allwinner Technology CPU: Allwinner A523 (SUN55I) Model: Radxa Cubie A5E DRAM: 4 GiB sunxi_set_gate: (CLK#35) unhandled Core: 89 devices, 25 uclasses, devicetree: separate WDT: Not starting watchdog@2050000 MMC: mmc@4020000: 0 Loading Environment from SPIFlash... SF: Detected w25q128fw with page size 256 Bytes, erase size 4 KiB, total 16 MiB OK In: serial@2500000 Out: serial@2500000 Err: serial@2500000 Net: eth0: ethernet@4500000 starting USB... sun4i_usb_phy phy@4100400: External vbus detected, not enabling our own vbus USB EHCI 1.00 USB OHCI 1.0 USB EHCI 1.00 USB OHCI 1.0 Bus usb@4101000: 1 USB Device(s) found Bus usb@4101400: 1 USB Device(s) found Bus usb@4200000: 1 USB Device(s) found Bus usb@4200400: 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 PCIe: Acquiring resources... PCIe: All resources acquired. Starting power-on sequence... PCIe: Toggling external device reset (PERST#)... PCIe: Hardware power-on sequence successful. PCIe: Disabling DBI write protection... PCIe: DBI region: 0x04800000-0x04c80000 PCIe: IO region: 0x21000000-0x22000000 PCIe: MEM region: 0x22000000-0x30000000 PCIe: CFG region: 0x20000000-0x21000000 PCIe: Lanes: 1, Max Speed: Gen2 Link Status: 0x00000004 RDLH_LINK_UP: 0 SMLH_LINK_UP: 0 LINK_SPEED: 0 LINK_WIDTH: 0 Link Status: 0x00000004 RDLH_LINK_UP: 0 SMLH_LINK_UP: 0 LINK_SPEED: 0 LINK_WIDTH: 0 Link Status: 0x00000017 RDLH_LINK_UP: 1 SMLH_LINK_UP: 1 LINK_SPEED: 0 LINK_WIDTH: 0 pcie link up success PCIe: Link active at Gen2 Device 0: Vendor: 0x1e0f Rev: AEMS0104 Prod: 41KPHGXCQQWL Type: Hard Disk Capacity: 122104.3 MB = 119.2 GB (250069680 x 512) ... is now current device Scanning nvme 0:1... Found U-Boot script /boot.scr 4641 bytes read in 0 ms ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from nvme 190 bytes read in 0 ms The file sun55i-a527-radxa-a5e.dtb was not found in the path /dtb/allwinner Load fdt: /dtb/allwinner/sun55i-a527-cubie-a5e.dtb 43273 bytes read in 1 ms (41.3 MiB/s) Working FDT set to 4fa00000 Failed to load '/dtb/overlay/sun55i-a527-fixup.scr' 23607275 bytes read in 61 ms (369.1 MiB/s) 34167296 bytes read in 87 ms (374.5 MiB/s) Moving Image from 0x40080000 to 0x40200000, end=0x42390000 ## Loading init Ramdisk from Legacy Image at 4ff00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 23607211 Bytes = 22.5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Working FDT set to 4fa00000 Loading Ramdisk to 4897c000, end 49fff7ab ... OK Loading Device Tree to 0000000048909000, end 000000004897bfff ... OK Working FDT set to 48909000 Starting kernel ... 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.