Active threads

I have not personally modified armbianEnv.txt, I do not know how to. As I say I think the machine has been messed around with, i.e. it has been hacked.As I say I am trying to work out how to reenable /dev/mmcblk1.

I don’t understand why playing videos with this board is a problem under Debian and not under Android for example. Thanks however. Denis

Weird its doing it on all distros and builds have tried so far including Debian. I can only think it must be the boards firmware ?

i also have issues to move the system to the nvme ssd 😞 my base is the Armbian 25.5.1 with 6.1.115 (vendor kernel) image .... "copied" (usbimager) it to the sdcard and its booting ... 🙂 so I upgraded the system on the sdcard, still running 🙂 I read some posts and advices .... so I partioned the nvme with one big partition (/dev/nvme0n1p1) running armbian-install choosing option 7, (loading/upgrading bootloader to mtd ) after this i choose option 4 (boot from mtd, system on sata, usb ... ) only possible selection was /dev/nvme0n1 ... looked ok said yes to everything no Error system goes to shutdown /power off removed power, removed sdcard plugin power again .... and ... no boot 😞 serial console saying: DDR 9fa84341ce typ 24/09/06-09:51:11,fwver: v1.18 ch0 ttot10 ch1 ttot10 ch2 ttot10 ch3 ttot10 ch0 ttot18 LPDDR4X, 2112MHz channel[0] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB ch1 ttot18 channel[1] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB ch2 ttot18 channel[2] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB ch3 ttot18 channel[3] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB Manufacturer ID:0xff DQS rds:h1,h1 CH0 RX Vref:27.1%, TX Vref:21.8%,22.8% DQ rds:h1 l0 h2 l0 h1 h5 l0 l0, l0 h3 l0 h3 h7 h2 l0 h1 DQS rds:l0,h1 CH1 RX Vref:28.5%, TX Vref:23.8%,23.8% DQ rds:h1 h2 h1 h3 h1 h3 l0 h1, h1 h4 h1 h4 h1 h3 l0 h4 DQS rds:l0,h1 CH2 RX Vref:27.5%, TX Vref:23.8%,22.8% DQ rds:h1 h3 h2 h1 h1 h6 h4 h1, h1 h2 h6 l0 h6 h2 h6 h3 DQS rds:h1,l0 CH3 RX Vref:29.7%, TX Vref:21.8%,20.8% DQ rds:h5 h3 h2 h1 h3 h2 h2 h2, h5 h2 h1 h2 h4 l0 l0 h5 stride=0x2, ddr_config=0x4 hash ch_mask0-1 0x20 0x40, bank_mask0-3 0xa00 0x1400 0x2800 0x0, rank_mask0 0x401000 change to F1: 528MHz ch0 ttot10 ch1 ttot10 ch2 ttot10 ch3 ttot10 change to F2: 1068MHz ch0 ttot14 ch1 ttot14 ch2 ttot14 ch3 ttot14 change to F3: 1560MHz ch0 ttot16 ch1 ttot16 ch2 ttot16 ch3 ttot16 change to F0: 2112MHz ch0 ttot18 ch1 ttot18 ch2 ttot18 ch3 ttot18 out U-Boot SPL board init U-Boot SPL 2017.09-armbian-2017.09-S3e40-P187d-He5fc-Ve691-Bb703-R448a (May 30 2025 - 10:51:06) sfc cmd=03H(6BH-x4) Trying to boot from MMC2 MMC: no card present mmc_init: -123, time 0 spl: mmc init failed with error: -123 Trying to boot from MTD2 Trying fit image at 0x4000 sector ## Verified-boot: 0 ## Checking atf-1 0x00040000 ... sha256(7612223b82...) + OK ## Checking uboot 0x00200000 ... sha256(11a994b967...) + OK ## Checking fdt 0x00354c30 ... sha256(e3b0c44298...) + OK fdt_record_loadable: FDT_ERR_BADMAGIC ## Checking atf-2 0xff100000 ... sha256(70505bb764...) + OK fdt_record_loadable: FDT_ERR_BADMAGIC ## Checking atf-3 0x000f0000 ... sha256(b2af21b504...) + OK fdt_record_loadable: FDT_ERR_BADMAGIC Jumping to U-Boot(0x00200000) via ARM Trusted Firmware(0x00040000) Total: 496.285/765.931 ms INFO: Preloader serial: 2 NOTICE: BL31: v2.3():v2.3-868-g040d2de11:derrick.huang, fwver: v1.48 NOTICE: BL31: Built : 15:02:44, Dec 19 2024 INFO: spec: 0x1 INFO: code: 0x88 INFO: ext 32k is valid INFO: ddr: stride-en 4CH INFO: GICv3 without legacy support detected. INFO: ARM GICv3 driver initialized in EL3 INFO: valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0 INFO: l3 cache partition cfg-0 INFO: system boots from cpu-hwid-0 INFO: disable memory repair INFO: idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001 INFO: dfs DDR fsp_params[0].freq_mhz= 2112MHz INFO: dfs DDR fsp_params[1].freq_mhz= 528MHz INFO: dfs DDR fsp_params[2].freq_mhz= 1068MHz INFO: dfs DDR fsp_params[3].freq_mhz= 1560MHz INFO: BL31: Initialising Exception Handling Framework INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 No valid device tree binary found - please append one to U-Boot binary, use u-boot-dtb.bin or define CONFIG_OF_EMBED. For sandbox, use -d <file.dtb> initcall sequence 00000000002d2af8 failed at call 00000000002c502c (err=-1) ### ERROR ### Please RESET the board ### if im boot with sdcard in the system and mount /dev/nvm0n1p1 there is the whole system .... inklusive /boot und boot/dtb ..... what didd I miss ? Does anyone hav a link to a working tutorial ?

I would try the cma=256M argument anyway... this kernel argument eliminated my video glitches and dma errors. I don't know how a dtsi or dtbo parameter (loaded after linux is started) would override a kernel argument (given before the linux kernel is started).

It exists and has been working for a long time , why does someone change it while it does't hinder you? Who changed it , and who should rollback, yes, we're community. Thank you.

moved

https://docs.armbian.com/User-Guide_Autoconfig/

You're right - the dtb is gxbb-p200. However, actual RAM is 1 GB total. Booting Emuelec 4.3 will show you that info. But that particular game-stick does not have an Android boot-loader so maybe that's why Armbian is unable to boot. 🤔

Well other option is the upstream broke somehow. KDE neon is based on their testing branch so if there is a faulty package uploaded desktop breaks. Though we won't dive into this since KDE is no officially supported desktop environment by us. We mostly do GNOME and XFCE only. We don't have resources to deal with more while we wish we would/could.

Hello, I have a NanoPi R6S and have just attempted the presented adjustment on my Armbian Install but it looks like udev fails to rename the interfaces at boot due to the fact that the kernel is doing that before ? I don't really have a lot of experience here but becaus of this the NetworkManager vlan mapping and IP addresses get mangled up thus resulting in my device not working as intended. Could there be something that I am doing wrong ?

I didn't have that much time to look at my Orange Pi board. On work, i have to deal with similar issues, but regarding another Soc (imx8mp with vivante GPU). But on work i have support from other people / offices. Meanwhile the grafik looks like to work, but also with lot of kernel patches and fixing involved (we have a yocto based build, and even Qt is somehow patched to work with our yocto base, wtf) on my orange pi board testet out some kernels. tried the official debian / ubuntu kernels (from orangepi.org) the version 5.10 kernels versions are booting (from sd) but no Grafik support ... the version 6.1.43 kernels are not even booting .... wtf 😞 i tried a SPI flushing, no change the armbian Kernels are booting !!! yay ! but : Armbian 25.5.1 with 6.1.115 (vendor kernel) looks like it has gpu support ! yay ! at least glxinfo shows the gpu string 🙂 but no emmc support 😞 even with booting from sd the kernel does not find /dev/mmcblk0 (mmcblk1 is detected as the sd card) 😞 Desktop images with Armbian Linux v6.12: it detects the emmc, so booth /dev/mmcblk0 and /dev/mmcblk1 are present, yay ! 🙂 but no grafik card support 😞 what do Im missing ? on the newer kernel Im need the device tree overlay for panthor (gpu_panthor) right? But didnt manage to get the gpu up ... mesa always fail to create the context and than switching back to the software renderer (regarding glxinfo logs) So im stuck atm .... and yes, its frustrating!

Hi all, Sorry for such a kiddy question but I couldn’t find the answer. I have a bit another device than expected. I have Banana Pi 3 device with Armbian-bpi-SpacemiT 24.5.0-trunk Noble and i'm trying to install a new kernel to it. I've installed linux-allwinner kernel 6.8.0-60.63.1 and all the stuff with it. linux-allwinner/noble-security,noble-updates,now 6.8.0-60.63.1 riscv64 [installed] linux-headers-allwinner/noble-security,noble-updates,now 6.8.0-60.63.1 riscv64 [installed,automatic] linux-image-allwinner/noble-security,noble-updates,now 6.8.0-60.63.1 riscv64 [installed,automatic] linux-tools-allwinner/noble-security,noble-updates,now 6.8.0-60.63.1 riscv64 [installed] And current boot kernel looks like ``` # mkimage -l /boot/Image FIT description: Linux 6.1.15-legacy-k1 Created: Wed May 1 17:17:59 2024 Image 0 (kernel) Description: Linux 6.1.15-legacy-k1 Created: Wed May 1 17:17:59 2024 Type: Kernel Image Compression: uncompressed Data Size: 32397312 Bytes = 31638.00 KiB = 30.90 MiB Architecture: RISC-V OS: Linux Load Address: 0x01400000 Entry Point: 0x01400000 Hash algo: crc32 Hash value: f571b82e Default Configuration: 'conf-default' Configuration 0 (conf-default) Description: Generic Linux kernel Kernel: kernel ``` The question is - How to make from vmlinuz-6.8.0-60-generic a kernel with the same format like above ? When I try to make it like this `mkimage -A riscv -O linux -T kernel -C none -a 0x01400000 -e 0x01400000 -d /boot/vmlinuz-6.8.0-60-generic /tmp/Image` I have another kernel format. ``` Created: Fri Jul 18 15:49:58 2025 Image Type: RISC-V Linux Kernel Image (uncompressed) Data Size: 38608384 Bytes = 37703.50 KiB = 36.82 MiB Load Address: 01400000 Entry Point: 01400000 ```

I got a radxa rock 5t and trying to install armbian(https://www.armbian.com/radxa-rock-5t), arimbian NOT boot and I can see the indicator light on the board is showing a steady green light. I boot with the official image https://docs.radxa.com/en/rock5/rock5t/low-level-dev/maskrom/linux and insert the sd card(with armbian img), and run such command, then I can boot armbian from SD card sudo dd if=/dev/mmcblk0 of=working_idbloader.img bs=512 skip=64 count=8000 sudo dd if=/dev/mmcblk0 of=working_u-boot.itb bs=512 skip=16384 count=8000 sudo dd if=working_idbloader.img of=/dev/mmcblk1 bs=512 seek=64 conv=notrunc sudo dd if=working_u-boot.itb of=/dev/mmcblk1 bs=512 seek=16384 conv=notrunc BTW, it seems there's no rock-5t tag, so I selected the 5b one

moved to off-topic since not about Armbian but 3rd party img.

expected. HDMI or hw support in general in 6.12.y is very basic and I am often impressed that hdmi actually works on some boards with this kernel. tl;dr: use vendor or edge kernels If need stuff running. current won't receive any further feature updates but security fixed only.

Hi, I have a few sbcs live while most are laying on the shelf waiting for tests. I have a PiHole on an Orangepi One Plus. On a ROC RK3399 PC PLUS I have paperless-ngx running in Docker. On an OPi5 Plus I have Invidious, yourspotify and something else I frequently forget about. Most likely something from similar importance

Hi @C127, any progress on the DTS?

Probably worth a shot - I had an install one time that gave me fits at initial boot. For giggles I expanded the FS using Gparted in linux to fill the entire card. It solved that problem for me.

Thanks! My opi zero 2w was intermittently crashing, I think I bumped a component off soldering the pin header on, so I am going to get a new one and see if it does any better. Will update in a few days once it arrives.

@psygnosis Do you have any heat sink or other cooling on your orangepione? Is your environment hot? At idle (480MHz) your machine is running quite hot, over 55 deg. The idle cpu speed is the minimum that the os can manage and so the os it doing the best it can.

Ok, thank you! I've made an issue on github: https://github.com/armbian/build/issues/8403

You will have to uninstall the upstream wireguard as that will remove the dependancy on the non-armbian kernel.

Accidentally included a duplicate in the previous post's image. Here is the missing SBC...I note this one has 32gb of ram vs the other's 16gb.

works great for me in productive environment for 2+ years