Active threads

@shexplorer I am in the same situation with my x88pro13 box not booting and I do not manage to go in Maskrom mode. Any progress on your side ?

Hello everyone, I am new to Armbian and need some help. I tried to install Armbian 26.2.0-trunk (https://www.armbian.com/nanopi-neo/#collapse-widget-5-0-0-0) on a NanoPi NEO Core SBC. I used Armbian Imager and wrote the latest official image (the only one available) to the SD card. After writing the image, I see only one partition on the SD card named armbi_root. When I insert the card into the device and power it on, nothing happens — there are no boot messages or logs. I think the image is missing a bootloader. So my questions are: 1) If I’m right that the bootloader is missing, how can I add a bootloader to the image? 2) How can I apply OverlayFS to this setup? 3) Do you have a link to a good article or tutorial on these topics? Thanks in advance!

Unless they have changed something very recently, you can login as root via ssh on first-run. I double checked /etc/ssh/sshd_config on an armbian install image I had downloaded, and: # Authentication: #LoginGraceTime 2m PermitRootLogin yes #StrictModes yes #MaxAuthTries 6 #MaxSessions 10 PubkeyAuthentication yes <snip> # To disable tunneled clear text passwords, change to no here! #PasswordAuthentication yes #PermitEmptyPasswords no And inside /etc/shadow (default 1234 passwd): root:$y$j9T$SAPCtO/l2ZIj6A2frqTza/$.Z8dP41gzqRHoIS8PvXFn9fghf9rgkGqAWgXVRW4dg6:20234:0:99999:7::: So that should not be an issue here. (and there are keys inside /etc/ssh that I assume can be used at first login, I have never tried) Sounds more like a faulty sd-card that gets mounted read-only, that can cause stuff like this happening. (as mentioned earlier by Igor) Try with a different sd-card (and use armbian-imager instead of balena) and see if the same happens on another card.

I managed to do it thanks

Hello averyone I'm trying to download the multitool.img.xz can someone please help me find it or share a valide link?

The paste armbian URL displays nothing (anymore?) so without any (new) info from you, no-one can help you. AFAIR, 4K via HDMI connector is only recently available (on RK3588, not sure about RK3399), so make sure you can manage various combinations of U-Boot, kernel, rootfs. So sort of act like a developer, als make sure you have a serial console (debug) cable, else you cannot get any step further. Use a 26.2 based U-Boot and 6.19 rockchip64 kernel I would say, then see what happens.

@ag123 thank you for your response. I donated to the project in the past (search my messages, peytote was an awesome guy that helped with some specific SPI issue i had many years ago on a Orange PI i think), i am donating to few open source projects (Like FreeCAD) , will make recurring donations to Armbian for sure. Yeah i am not using any OrangePi with their original OS, no way. I need a more powerful board than OPi Zero 3, will look into the maintained and supported ones here on Armbian. Thanks for your reply.

I'll add my 2 cents with my more recent findings. Mind that I am using an Orange PI 5 Plus, your mileage might vary with other models. I started booting the official Orange PI (Arch) distro to clear the SPI bootloader, as suggested by @Igor sudo pacman -Syy sudo pacman -S mtd-utils sudo flash_erase /dev/mtd0 I've tried multiple flavours of the available downloads for Armbian, but I've found that all versions with kernel 6.12.58 would fail to load (the LED stays red, instead of flashing red & blue). This includes both Debian trixie and Ubuntu noble, with their desktop and minimal editions. Back in December 20204 @Igor V described similar boot issues that got resolved with kernel 6.1.75, the one that was highlighted in green at the time. So that led me to try with kernel 6.1.115 instead, and that has worked just fine. Not sure if this is an issue introduced with the newer kernel, or whether it's to be expected as it has not been officially stabilised yet. Anyway, I thought I'd share in case this can help others in the future.

I tried it with a desktop PC, but couldn't select a resolution higher than 1024x768. I read that there's a bug in newer kernel versions that's already been fixed. However, I couldn't find out if the fix is included in the downloaded image. Then I tried an older imager with kernel 4.4, and with that one, I was able to select higher resolutions. @jock I only tested it with Wi-Fi. You could also try a version with an older kernel.

If you want to add new board with its own device tree, this is a good example: https://github.com/armbian/build/pull/9423 Remember to add pictures - this way https://github.com/armbian/armbian.github.io/pull/236

Tried your image on an SD card but tried several way to get it to boot from SD was unsuccessful. I tried the toothpick on the button inside the 3.5 mm port. I tired ADB reboot update and ADB reboot recovery. But all those times, I just receive the android recovery menu when failed to boot SD. Is there any thing special I need to do to get this box to boot from SD? I will solder some dupont pins soon so I can get a better reading what is happening with serial console. But for now, do you know why it is so difficult to boot from SD. I never had this much issue with an AMLogic S9xx before.

Auto generated images: https://dl.armbian.com/nightly/orangepirv2/Forky_current_minimal https://dl.armbian.com/nightly/orangepirv2/Noble_current_xfce

Why are you expecting this to work?

I am asking if someone can refer me somewhere so I can update my current orangepi zero 3 hardware to bananpi m4 zero hardware.

Armbian 25.11.2 Noble XFCE (BSP Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + Box64 arm64 v0.4.1 ed9827920 (https://ryanfortner.github.io/box64-debs/) + ge-proton10-29 (https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/GE-Proton10-29) (GE-proton is more likely to be segment fault-proof than other wine-proton versions) + dgVoodoo2 (https://github.com/dege-diosg/dgVoodoo2/releases) + DXVK-stripped v2.7.1 ~30fps@720p (high settings - the lowest settings in game) box64 environment variables: Crysis 2 Maximum Edition

Just tried stock DietPI & Armbian builds using both current-rockchip64 and edge-rockchip64 utilizing U-Boot - thus completely eliminating the EDK2 UEFI factor. None handle multichannel audio correctly so I guess there is something still not mature enough in mainline/upstream for this. kernel-rk35xx-vendor:6.1.115 works perfectly even with EDK2 UEFI. Perhaps the Armbian devs need to take a look at what LibreELEC is doing as they managed to get it working in their mainline/upstream kernels.

You would just burn your downloaded image file to any USB storage, just like you would to an SD card (i.e. plug the USB storage into another device and burn the image to the storage)

With a lot of trial and error I figured out the issue but not the cause. This seems to only effect HEVC (x265) videos when drm is successfully enabled with MPV from this repository. If I try a different player, they play fine but no hardware acceleration. If I encode the videos to x264 they play but hardware acceleration fails with the following error [ffmpeg/video] h264: v4l2_request_probe_video_device: set controls failed. Invalid argument (22) The issue is the width of the video. Outside of certain ranges it will display a black video (audio works). It doesn't seem to matter what the height is set to. Eg) 704x480, 704x960 image is displayed. 706x480, 706x960 black screen The ranges go for 14 pixels and each range is separated by 50 pixels. eg) widths in the range of 690 to 704 display an image. Widths between 706 and 752 display a black screen. 754 to 768 display an image. It's a strange one.... Here is a list of ranges that work. Any widths outside of these ranges produces a black screen. It only goes up to 1984 but I'm sure the same rules would apply above this value.

PREEMPT_RT is fully merged in mainline Linux as of 2024 (https://en.wikipedia.org/wiki/PREEMPT_RT).

Here is the updated image with Wifi and EMMC boot https://github.com/sicXnull/armbian-build/releases/download/mxqpro/Armbian-unofficial_26.02.0-trunk_Mxqpro-h313_trixie_current_6.12.74_cinnamon_desktop.img.xz

I don't know, perhaps the author knows. Try. If it doesn't work, then fe's wiki is misleading.

thank you for your reply! I reverted to the stock ubuntu for opi5 for now. I will have a new device in my hands in the next days, I will then try this

Hello NickA, fire-hound from discord here ... You do a tremendous service for us all, keep it up buddy! I loaded your recent build from here: https://github.com/NickAlilovic/build/releases and can confirm it works on my A7A. It correctly detected my Pimorony NVME Base lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mtdblock0 31:0 0 8M 0 disk mmcblk0 179:0 0 29.2G 0 disk ├─mmcblk0p1 179:1 0 256M 0 part /boot └─mmcblk0p2 179:2 0 28.6G 0 part /var/lib/containers/storage/overlay /var/log.hdd / zram0 254:0 0 3.9G 0 disk [SWAP] zram1 254:1 0 50M 0 disk /var/log zram2 254:2 0 0B 0 disk nvme0n1 259:0 0 238.5G 0 disk └─nvme0n1p1 259:1 0 238.5G 0 part /srv/dev-disk-by-uuid-b28b2f5c-ee2e-4ded-959e-22bc63051b1d and: screenfetch _,met$$$$$gg. root@radxa-cubie-a7a ,g$$$$$$$$$$$$$$$P. OS: Debian 13 trixie ,g$$P"" """Y$$.". Kernel: aarch64 Linux 6.6.98-vendor-sun60iw2 ,$$P' `$$$. Uptime: 11h 14m ',$$P ,ggs. `$$b: Packages: 661 `d$$' ,$P"' . $$$ Shell: bash 5.2.37 $$P d$' , $$P Disk: 4.9G / 271G (2%) $$: $$. - ,d$$' CPU: ARM Cortex-A55 Cortex-A76 @ 8x 1.794GHz $$\; Y$b._ _,d$P' RAM: 534MiB / 7928MiB Y$$. `.`"Y$$$$P"' `$$b "-.__ `Y$$ `Y$$. `$$b. `Y$$b. `"Y$b._ `"""" So far so good The issues: 1. The typical Armbian image has a module in the armbian-config and radxa's rsetup where one can set up the two leds conveiently to other than full on and heartbeat for the green and blue gpio leds respectively. I find it to be a nuisance to dig for that manually 2. The Ovralys module in armbian-config is returning an error - when entering DTO001 module (Device Tree Overlays) saying: Invalid overlay_prefix that might require deeper digging into the issue i guess? What works: Open Media Vault registers the NVME nicely as additional storage. I suspect booting off that NVME would work for an updated SPI bootloader i could test that if you want me to? If you need any other info or output I stand at Your disposal 😁

Hello, I would like to use Armbian on control hub too but without disassembling it. I tried latest renegade image and usb and internet were not working. What is exactly everything I need to change in the image to make the usb at least work? I tried enabling the rk3318-box-led-conf3 in some file I forgot but it did not work, maybe else more needed or I did it wrong. I would be very grateful if you could write what I need to change! I do not want to disassemble since it's legality in FTC rules is ambigous for me.

Neither of these is good advice. dd does not verify written data and balena etcher has known issues, hence it is not recommended either. Either use Armbian Imager (https://docs.armbian.com/User-Guide_Getting-Started/) or USBimager (https://gitlab.com/bztsrc/usbimager). Both are known to work.