All Activity

This is not NVME, but SATA. No surprise it does not work. It might be that the M.2 slot of the OPi5pro is such that with an overlay, you could map SATA signals to that slot and then it should work. Look in rockchip overlays folder for any .dtbo file with name like *rk3588*sata* But you should check HW circuit diagram maybe first, might also be that this is only for the normal OPi5 Maybe search a bit, I found Is old topic, but the principles are still the same.

Power supply: WNB-0504000 5V 4A 20W USB-C. SSD: Intenso Top Performance M.2 128GB SATA-600 I'm gonna buy a new power supply. Looks like I'm needing a 5A one.

ubuntu nor gnome is not relevant what matters is u-boot and kernel (and powersupply and type of nvme ssd ) u-boot logs can be seen via serial console cable

I've tried Ubuntu-gnome. Still no SSD recognition.

I am 95% sure this happens even on a plain Armbian install. I'll double check. Some news: - it does not happen on all SATA devices (booted fine with 1 SSD) - power supply seems fine; marked 4.0 A There is a workaround! press any key to interrupt boot (be fast, 2 second timer) scsi scan # wait under 2 minutes boot # similar output to "failed" boots # but after under 2 minutes, it will continue into the boot process Does anyone know how I could put these steps into the boot process automatically?

Hello everybody, With 6.18.10-current-rockchip64 and rk3399-kobol-helios64.dtb-6.18.18-opp dtb file, Ok With 6.18.35-current-rockchip64 and overlay helios64 patch with armbian-config, Ko With 6.18.35-current-rockchip64 and k3399-kobol-helios64.dtb-6.18.18-opp dtb file, Ko The crash is random... sometime crash: - At the boot with red system light blinking - At the opening of my LUKS ciffers drives - At a high cpu load - With nothing special, all led are blue, system blinking but network and ssh is Ko Is it possible to explain me how to see the problem or how to have log because I am in blind to have more details ? Is it possible to explain me how to pass to the last 6.18.36 kernel to seen if it is better than 6.18.35 ? Thanks a lot.

I suggest to ask at dietpi forums, since we cannot help with 3rd party os/scripts.

Thank you, bro. I'll try it this evening after work. I'll post the results.

I want to install an image from the sd card to the internal memory in x96q tv box, it boots perfectly from sd card, without having to press anything, and everything works ok, even bluetooth adapter and video reproduction, my question is "do i still need to modify boot files to install in emmc or is not necessary? thanks in advance....

You can find everything you need here. H616 is similar to H618. https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/ you can use this tool to extract your dram settings. https://github.com/apritzel/sunxi-fw

@flintduvaд secure boot might be similar to older Allwinner SOCs. https://forum.armbian.com/topic/58803-i-need-secure-image-x98h-pro/#comment-235213

I have an Odroid HC4 I've used as a NAS. Back around 2021, it worked fine. I think I installed plain armbian back then and installed openmediavault on top of it. Then I did all kinds of updates to it. I believe it's now on a hybrid of Debian Bookworm and Debian Trixie - don't ask. The update mechanism is not super clear. I wanted to run a fresh, plain Armbian and install dietpi. But there is a well documented flaw where Armbian cannot exit boot in some cases. In my case, it happens only when SATA drives are attached. I have two WD Red drives that it can't boot with those attached. It seems like the bootloader code was changed over time, which let prior builds boot but not current builds. Admittedly, these drives fail SMART, so they could be reporting bad data. Errors: Scanning bus for devices... [SATA stuff] timeout exit! fs_devread read error - block [SATA stuff - size is off by about 10x - says 700 GB, actually 6 TB] Device 0: [SATA stuff] ... is now current device timeout exit! timeout exit! timeout exit! [etc.] I tried setting the code in /boot to only attempt to boot from emmc0 and emmc1. The farthest I got was this, but I think updating to trixie via armbian-config again broke the boot code: installed old armbian minimal apt install armbian-config # the keys are old and fail with the sha1 ban recently implemented. this fixes that wget https://apt.armbian.com/armbian.key gpg --dearmor < armbian.key | sudo tee /usr/share/keyrings/armbian.gpg > /dev/null armbian-config: disable firmware update (also disables kernel updates) distro full upgrade from armbian-config got: Description: Armbian 26.5.1 trixie Release: 13 https://dietpi.com/docs/hardware/#make-your-own-distribution noticed this in the install script running, i'm worried it will wipe the good old firmware and replace with new bad: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. [ OK ] DietPi-Installer | APT install linux-image-current-meson64 linux-u-boot-odroidhc4-current [ OK ] DietPi-Installer | rm -f /boot/uImage /boot/uInitrd /boot/uInitrd-6.18.34-current-meson64 [ OK ] DietPi-Installer | rm /boot/.next [ OK ] DietPi-Installer | rm /boot/armbianEnv.txt [ OK ] DietPi-Installer | mkimage -C none -A arm64 -T script -d /boot/boot.cmd /boot/boot.scr [ SUB1 ] DietPi-Set_hardware > flash-u-boot-mmc (/dev/mmcblk0) 442+0 records in 442+0 records out 442 bytes copied, 0.00430629 s, 103 kB/s 2626+1 records in 2626+1 records out 1344880 bytes (1.3 MB, 1.3 MiB) copied, 0.162507 s, 8.3 MB/s [ OK ] flash-u-boot-mmc (/dev/mmcblk0) | Completed [ INFO ] DietPi-Installer | Preventing needless kernel and initramfs symlink generation [ OK ] DietPi-Installer | eval echo 'do_symlinks=0' > /etc/kernel-img.conf [ OK ] DietPi-Installer | rm -f /initrd.img /initrd.img.old /vmlinuz /vmlinuz.old [ INFO ] DietPi-Installer | Generating list of minimal packages, required for DietPi installation [ OK ] DietPi-Installer | Marking required packages as manually installed [ OK ] DietPi-Installer | Unhold all packages [ INFO ] DietPi-Installer | APT autopurge gawk original-awk, please wait... Reading package lists... Ideas: - try booting with just one SATA - try another SATA drive - try with petitboot (older / manufacturer boot code) instead of uboot - compare working /boot folder on working microsd with failed /boot folder (I did this, far too many differences to list). I did try copying key differences and recompiling the boot, didn't seem to fix it. - hotswap / hot install the drives after boot (apparently works) related: https://dietpi.com/forum/t/error-on-updating-ombi/25096 https://dietpi.com/forum/t/dietpi-os-apt-update-warnings/24923/31?page=2 https://forum.openmediavault.org/index.php?thread/43298-install-omv-on-odroid-hc4-some-questions-from-a-newbie/ https://dietpi.com/forum/t/odroid-hc4-sata-drives-not-recognized/4795 https://dietpi.com/forum/t/odroid-c2-doesnt-boot-up/6489/14 https://dietpi.com/forum/t/orange-pi-5-boot-from-sata-m-2-ssd/17884/51?page=2 https://github.com/MichaIng/DietPi/issues/7601

Update on 0.7: Led Display works perfectly Wifi works perfectly after reboot (i would suggest it on screen after the driver is built) Unable to test USB3 at the moment Installed Kodi, unable to get video acceleration (it says llvmpipe with CPU at almost 100%, clearly is running software rendering) @serovan did you reboot after first boot? But yes, probably your revision has different pinout for the peripherals (wifi and PHY)

Could you please tell me how to configure my own UBOOT so that the console boots from a flash drive? Is there any wiki information on this? When I loaded various Armbian versions onto the flash drive, the memory wouldn't initialize... U-Boot SPL 2025.04 (Apr 19 2026 - 19:49:57 +0200) DRAM:This DRAM setup is currently not supported. resetting ... U-Boot SPL 2025.04 (Apr 19 2026 - 19:49:57 +0200) DRAM:This DRAM setup is currently not supported. resetting ... U-Boot SPL 2025.04 (Apr 19 2026 - 19:49:57 +0200) DRAM:This DRAM setup is currently not supported. resetting ... U-Boot SPL 2025.04 (Apr 19 2026 - 19:49:57 +0200) DRAM:This DRAM setup is currently not supported. resetting ... Category Parameter Log Value What it is and what it's for Processor (SoC) Model sun50iw9 This is an Allwinner H616. Specified in the build configuration. Memory (DRAM) DRAM Type 3 (DDR3) Memory type. DRAM SIZE 2048 MB Memory capacity. DRAM CLK 600 MHZ Memory frequency. para1 30fb Key timing parameter. para2 8000000 Key configuration parameter. dram_tpr13 6041 Another timing parameter. Power Management Unit (PMU) PMU AXP1530 Critical for stability! Requires driver or compatibility with AXP313. Integrated Memory MMC MMC 5.0, 15032 MB eMMC type and size. Ethernet No ethernet found No Ethernet. We work only via Wi-Fi. U-Boot SPL 2024.01-armbian-2024.01-S866c-P6135-Ha9af-V6d37-Bda0a-R448a (Sep 19 2024 - 19:48:11 -0400) This DRAM setup is currently not supported. resetting ... U-Boot SPL 2024.01-armbian-2024.01-S866c-P6135-Ha9af-V6d37-Bda0a-R448a (Sep 19 2024 - 19:48:11 -0400) This DRAM setup is currently not supported. resetting ... U-Boot SPL 2024.01-armbian-2024.01-S866c-P6135-Ha9af-V6d37-Bda0a-R448a (Sep 19 2024 - 19:48:11 -0400) This DRAM setup is currently not supported. resetting ...

Hello friends. I ask for help in creating firmware with TOC0. Unfortunately, I once launched Android firmware from a Teclast tablet on my A7A board, and apparently eFuse burned out. Now standard firmware with eGON.BT0 will not run on this board. Or tell me where to fix it so that the firmware from the sources is compiled with TOC0.

What is your plan with that camera? My latest try with raspbian (armv6) trixie based failed w.r.t. V4L2. So that is with start.elf, not start_x.elf. The latter works fine on bookworm based raspbian for camara v1. Camera v3 never worked with legacy firmware mode (start_x=1), so needs libcamera. For easy handling, the latest RPL variant of libcamera named rpicam should work, but then you'll be essentially back to RaspberryPiOS. If you have standard Debian Trixie based, all that modified libcamera is not there and more important, you will have other firmware files (bootcode.bin start.elf fixup.dat). Armbian takes the version from Ubuntu AFAIK, Debian is yet another version as is the latest from RaspberryPiOS (64-bit patched Debian or 32-bit patched and re-compiled Raspbian). The package name is raspi-frmware, check which versions there are with sudo apt list -a raspi-frmware and in addition, the 3 files themselves, I did timestamp or suffix them with sha256sum in the past on order to keep track of the various ones delivered for various OSses and images. I assume the Armbian kernel is compiled from same RPi kernel tree as RaspberryPiOS, so overlays for the v3 camera should be there and functionally the same. I currently have 1 camera v1 base RPI3B+ running, still bookworm, but I might boot it with Debian Trixie/Sid and see what mainline libcamera does. Probably then Armbian bcm2711 edge kernel, at least something that provides overlays as Debian kernels have almost none, at least not for camera sensors.

Hello, friends. After a long time, I managed to extract and compile a DTB file from this console. What version of Armbian should I use to run this technological marvel? I'm attaching the DTB file and logs before booting from a flash drive; maybe it'll be useful to someone... h616.txtu-boot-sunxi-with-spl.binsun50iw9.dtb

There is supposed to be a package that automatically handles building a (presumably patched) version of the kernel module for this wifi/bt chip, called `aic8800-usb-dkms`, but for some reason, a kernel upgrade doesn't auto-trigger it. During the last kernel upgrade, I was able to get it working by manually doing `sudo dpkg-reconfigure aic8800-usb-dkms`, but that also does not work since 26.5.1, as it gives Deleting module aic8800-usb-4.0+git20250410.b99ca8b6-3 completely from the DKMS tree. Loading new aic8800-usb-4.0+git20250410.b99ca8b6-3 DKMS files... Building for 6.18.2-current-qcs6490 Building initial module for 6.18.2-current-qcs6490 Error! Bad return status for module build on kernel: 6.18.2-current-qcs6490 (aarch64) Consult /var/lib/dkms/aic8800-usb/4.0+git20250410.b99ca8b6-3/build/make.log for more information. And that file basically says (a bunch is redacted for brevity): DKMS make.log for aic8800-usb-4.0+git20250410.b99ca8b6-3 for kernel 6.18.2-current-qcs6490 (aarch64) Sat Jun 20 06:36:14 PM PDT 2026 make: Entering directory '/usr/src/linux-headers-6.18.2-current-qcs6490' make[1]: Entering directory '/var/lib/dkms/aic8800-usb/4.0+git20250410.b99ca8b6-3/build/USB/driver_fw/drivers/aic8800' warning: the compiler differs from the one used to build the kernel The kernel was built by: aarch64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0 You are using: gcc (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0 ... gcc: error: unrecognized command-line option ‘-fmin-function-alignment=8’; did you mean ‘-flimit-function-alignment’? gcc: error: unrecognized command-line option ‘-fmin-function-alignment=8’; did you mean ‘-flimit-function-alignment’? make[4]: *** [/usr/src/linux-headers-6.18.2-current-qcs6490/scripts/Makefile.build:287: aic_load_fw/aic_txrxif.o] Error 1 ... Apparently, the kernel is now built with gcc 14 (which matches the default in Debian Trixie images but not Ubuntu Noble images which have gcc 13). Not sure how to resolve that inconsistency. 1. Install & replace gcc 13 with gcc 14 (just installing won't work as this dkms module build doesn't respect CC env vars); not sure if this will break other things in Ubuntu 24.04 2. Rebuild the kernel with gcc 13; same issue will re-occur on the next kernel upgrade 3. Or something else Just out of curiosity, did you have to mess around with gcc versions to get it to compile (or are you using Debian Trixie images)?

I have checked .... true.... my fix 7.1 was creted for 7.1-rc1 here we have got 7.1-rc4 so not working... Problably it needs to fix dirver aic8800 as still not supported plus compilation... usb2/usb3/ethernet are working?

just as a statistics/stability report: the DTB with the NPU works very well. Uptime of the device is already a week, it's running armbian and immich on it. While immich lags sometimes because the board can be weak for video processing, but in general it already processed ~20k images with OCR and face detection based on RKNN. I consider it pretty good results.

I'm struggling to get the Pi Camera 3/IMX708 detected by the Zero 2W. It's an IMX708 sensor, and that is correctly showing in dmesg, but the V4L2 devices (/dev/video0, /dev/video1) for the camera are not set up. All the normal encoder devices are fine. I'm using a custom build but it's essentially minimal (and no desktop) current with trixie and no extensions, following the standard command for building an image. The dmesg log reads as follows: [ 10.719672] imx708 10-001a: camera module ID 0x0302 [ 10.719876] imx708 10-001a: ctrl(id:0x9f0902,val:0x232aaf80) is not handled [ 10.722275] imx708 10-001a: ctrl(id:0x9e0902,val:0x2b20) is not handled But I don't think this is problematic, as stock Raspbian shows precisely the same log messages, and it does correctly set up the devices. I've added the overlay and turned off (or tried to) the camera auto detection, but the imx708 messages were being logged even before I added the overlay, so I am not sure it was needed. In any event, nothing changed. Any thoughts on ways to get this up and running?

never heard of that kernel before

depmod: ERROR: failed to load symbols from /lib/modules/7.1.0-rc4-next-20260518-edge-rockchip64/kernel/drivers/net/wireless/aic8800/aic8800_fdrv.ko: Invalid argument

I have wifi and it worked without building or installing anything. During the first boot I was asked if I would like to use wifi, I saw the list of SSIDs, but I was unable to connect. I used nmcli and I'm connected now. dkms status outputs: bcmdhd-spacemit-sdio/101.10.591.84.37-4, 6.18.36-current-spacemit, riscv64: installed Update: It boots from eMMC

As an addon to @sivert: Ubuntu has dkms "3.0.11-1ubuntu13" while Debian has the newer "3.2.2-1~deb13u1". There is a difference in /etc/kernel/prerm.d/dkms: Ubuntu starts "dkms remove..." and Debian starts "dkms kernel_prerm". Both should work normally, because if you update the kernel there are two kernels: the old one and the incoming one. If you happen to have only one kernel, and thus only one compiled dkms module version, the Ubuntu "remove" completely removes anything dkms-module related. Now Armbian is offering a kernel update to the absolute same kernel version number, thus simply overwriting linux-image. Also, a "dpkg-reconfigure linux-image-current-spacemit" (with only one Ubuntu kernel version installed) will also remove the Wifi module. I am not sure how to fix this...