All Activity

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.

If I understand you correctly: root via ssh is not allowed by default I usually setup (new) SBC's in a different way, but last time testing 2 of my boards with 26.2 minimal/IoT fresh image was via serial console, have not used ssh and certainly not putty. If no (serial) console, you might also have sme networking firewall issues somewhere in Windows or so, although would be vary rare. Have you setup a normal user first via (serial) console first?

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.

having the same issiue , would like to improve the situation since most of the monitor that i use come in 16:10 format, and those resolution seem not easily available. also read here on a site it should be capable of 4k output. https://www.electromaker.io/blog/article/pine64-rockpro64-review-a-beefy-single-board-computer

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.

Trouble with SSH client or failed SD card could explain this. We didn't change anything in this regard. SSH settings are Debian / Ubuntu defaults. We are not altering this. I tested latest image on XU4 and - it worked.

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

that is why i am confused, I used the one image from here (armbian.com) https://www.armbian.com/odroid-xu4/ edit: what happens if the SBC starts the first time and you cut the power before hooking up with ssh - does it fall back to other credentials? P.P.S: did a new install and 1234 just got me a "access denied" on the first attempt directly after boot

Why are you expecting this to work?

Moved to amlogic TV ox forum

@kisgezenguz you're welcome. You can check the UART RX/TX paths with the multimeter in diode/continuity mode and checking the continuity against RX (or TX) and the various SMD components. But anyway, if you read 3.3v on all the UART pins, I can guess there are three other hypothesis: * the UART RX/TX pins are correctly connected, but not to the usual debug UART. rk3399 has several uarts, so perhaps that exposed UART is not the same configured in software to be used to log the debug. * MCU_D makes me think that UART is used for the little MCU embedded into rk3399. rk3399 has two small Cortex-M0 cores for very low power tasks. So again that UART is not what you are looking for. * the RX/TX pins are just shorted to high voltage level/pulled ups on purpose (improbable) edit: I just paid attention to the schematic you posted, but it looks it does not match what you've discovered: the schematic says you should read 5.0v on the VCC pin, instead you read 3.3v. Perhaps that MCU_D connector it's definitely not the one you are looking for.

Armbian default login and password is always root and 1234. If this does not work, the image is not genuine.

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

U-Boot SPL 2025.07-armbian-2025.07-Se37d-P526e-H8869-V8e92-Bb703-R448a (Aug 19 2025 - 04:10:01 +0000) DRAM: 4096 MiB Trying to boot from MMC2 NOTICE: BL31: v2.12.5(debug):armbian NOTICE: BL31: Built : 04:09:39, Aug 19 2025 NOTICE: BL31: Detected Allwinner H616 SoC (1823) NOTICE: BL31: Found U-Boot DTB at 0x4a0b5100, model: BananaPi BPI-M4-Zero INFO: ARM GICv2 driver initialized INFO: Configuring SPC Controller INFO: Probing for PMIC on I2C: INFO: PMIC: found AXP313 INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for erratum 855873 was applied INFO: BL31: cortex_a53: CPU workaround for erratum 1530924 was applied INFO: PSCI: Suspend is unavailable INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 INFO: Changed devicetree. ns16550_serial serial@5000000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 U-Boot 2025.07-armbian-2025.07-Se37d-P526e-H8869-V8e92-Bb703-R448a (Aug 19 2025 - 04:10:01 +0000) Allwinner Technology CPU: Allwinner H616 (SUN50I) Model: BananaPi BPI-M4-Zero DRAM: 4 GiB Core: 65 devices, 22 uclasses, devicetree: separate WDT: Not starting watchdog@30090a0 MMC: mmc@4020000: 0, mmc@4022000: 1 Loading Environment from FAT... Unable to use mmc 1:1... In: serial@5000000 Out: serial@5000000 Err: serial@5000000 Allwinner mUSB OTG (Peripheral) Net: using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in MAC de:ad:be:ef:00:01 HOST MAC de:ad:be:ef:00:00 RNDIS ready eth0: usb_ether starting USB... USB EHCI 1.00 USB OHCI 1.0 Bus usb@5311000: 1 USB Device(s) found Bus usb@5311400: 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 4641 bytes read in 1 ms (4.4 MiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 280 bytes read in 0 ms Load fdt: /boot/dtb/allwinner/sun50i-h618-bananapi-m4-zero.dtb MMC: no card present ** Bad device specification mmc 0 ** 43728 bytes read in 4 ms (10.4 MiB/s) Working FDT set to 4fa00000 1358 bytes read in 3 ms (441.4 KiB/s) Applying kernel provided DT overlay sun50i-h616-bananapi-m4-sdio-wifi-bt.dtbo 4203 bytes read in 2 ms (2 MiB/s) Applying kernel provided DT fixup script (sun50i-h616-fixup.scr) ## Executing script at 45000000 17177939 bytes read in 543 ms (30.2 MiB/s) 38219784 bytes read in 1207 ms (30.2 MiB/s) Moving Image from 0x40080000 to 0x40200000, end=0x42760000 ## Loading init Ramdisk from Legacy Image at 4ff00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 17177875 Bytes = 16.4 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 48f9e000, end 49fffd13 ... OK Loading Device Tree to 0000000048f2a000, end 0000000048f9dfff ... OK Working FDT set to 48f2a000 Starting kernel ... Armbian 25.8.1 Trixie ttyS0 bananapim4zero login: root Password: _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| v25.8.1 for BananaPi BPI-M4-Zero running Armbian Linux 6.12.35-current-sunxi64 Packages: Debian stable (trixie) Updates: Kernel upgrade enabled and 6 packages available for upgrade IPv4: (LAN) xx.xx.xx.xx (WAN) xx.xx.xx.xx Performance: Load: 16% Uptime: 0 min Memory usage: 4% of 3.83G CPU temp: 46°C Usage of /: 5% of 29G Commands: Configuration : armbian-config Upgrade : armbian-upgrade Monitoring : htop root@bananapim4zero:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mmcblk2 179:0 0 29.1G 0 disk └─mmcblk2p1 179:1 0 28.8G 0 part /var/log.hdd / mmcblk2boot0 179:32 0 4M 1 disk mmcblk2boot1 179:64 0 4M 1 disk zram0 252:0 0 1.9G 0 disk [SWAP] zram1 252:1 0 50M 0 disk zram2 252:2 0 0B 0 disk root@bananapim4zero:~# https://www.armbian.com/bananapi-m4-zero/ Seems fine to me?

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.

not getting internal wifi from "amlogic s905x3" "x96 max plus" tv box wifi chip "CDTech 47W3155" board version "Q5X3-141 V4.1"

Good day. We have a medical device project. We always wanted to have bananapi m4 zero hardware on our main board, with armbian as an OS seeing as it is up to date and fit for purpose. However, our Hardware supplier has not been able to solve the full hardware stack. We currently are able to boot the orangepi zero 3 image... and as far as I understand the hardware chips are very close to each other. We also have emmc on the board. But not working. We desperately need hardware development help so we can get banana pi m4 zero armbian supported OS working. Any advise please. We have 2GB RAM , allwinner h618, axp313. All the same as orangepi zero 3. Please help. Desperate help needed.

@jock Than you for the hints. If I measure on all (except GND) UART Pin 3.3V is not indicate that all resistor in place? Regarding the rk3399 schematic design, there should be some 100 ohm resistors there. To be honest for me was also very difficult to find the MaskRom pins, search something what is not there is a bit challenging. I measure all black SMD item (far as I know they are resistors), but non of them 100 ohm. (The board other side I do not see any missing resistor) Could you please advise me what I need to look? There is 3 point where possible to solder resistor, how to identify which one I need?