All Activity

You can find them here https://imola.armbian.com/cache/artifacts/ In case you / someone want to help fixing this - this script https://github.com/armbian/armbian.github.io/blob/main/.github/workflows/generate-web-index.yml needs to be adjusted to add additional entries to the download JSON file for those three variants https://github.com/armbian/armbian.github.io/blob/main/.github/workflows/generate-web-index.yml#L140-L142 Few months ago GitHub introduced limitations on number of artifacts per release to 1000. And in order to keep providing CLI + desktop combo - especially for - community targets, we had to drop uploading sha, asc and torrent files to GitHub release storage. Instead, they are moved to cache.armbian.com under predicted structure, but links are missing from JSON as they don't exists on the release page where current script is scrapping from.

I type the root password once, press enter to retype it, but it jumps straight to the login prompt. Do not pass Go, do not collect $200. I’ve been dealing with this for the past month. At first, I thought it was just my 2GB model acting weird, but today I had two 4GB units do the same thing. It only happens with the Debian 13 Minimal/IOT image. I didn't want the overhead, but I am using the Debian 12/XFCE Desktop image that works.

As a follow up. Armbian doesnt seem to have proper pinebook pro support in its firmware package (i.e `armbian-firmware`) Someone was up until recently keeping track of different firmwares on the pinebook pro (link https://github.com/cobratbq/pinebook-pro) On mine I have just symlinked the raspberry pi4 versions, which has improved wifi and bluetooth. As far as i can tell, an appropriate pull request is needed against this repo? https://github.com/armbian/firmware/tree/master/brcm I was also able to update to trixie without any problems.

the software i used to flash the sd card, was balenaEtcher and Rufus, i did not validate the checksum both the SHA ASC are 404 file not found.

Are you saying you are missing further steps in between setting root passwd and being logged in?

How did you flash the Armbian image? Did you validate the checksum for the image? What software did you use for flashing the image?

I don't even have an HDMI device connected. Running it headless. And when you say Debian 13, are you describing a way to convert Armbian to Debian in-place? Because honestly, with its inability to set time and missing i2c buss, I've lost confidence in Armbian. But I don't understand the effect of your commands. Is this converting Armbian to Debian 13? Is there any way to just build Debian 13 on the SD card or internal EMMC?

Ok, will try wiFi by doing that. I posted more testing in the thread of my device.

hi, im trying to make my radxa 4d in to a open media vault server, iv down loaded the file from armbian's web side but it wont boot, pluging it in to one of my raspberry pi's and useing gparted, i can only see one partision for it and can view it, dose this need a boot loader? iv also tryed downloading Debian 14 (Forky) from the armbian web site and got that to boot, but the script from armbian-config is broken ( missing stuff like php) and iv tryed the script from open media vault but that errors with eth0 missing. do i need to install a boot loader on the armbian open media vault image ?

Hi, I've tried to setup the latest Debian 13 (Trixie) for the Renegade board. I can flash the image with no issue. The problem comes it boots up, prompts for root password. I can type in then press enter, and then it goes to login. This only happens on the Debian 13 (Trixie). I am using the Debian 12 XFCE imange no issue. I am not sure if this is a bug or what, but I loved to use Debian 13, I am trying to setup Docker with the latest OS.

thanks~

I Installed radxa os (debian) again which works fine and tried to scan SPI flash via terminal but It was sequences of all zeros and then all ones, so no I presume no information stored in SPI, just to be safe I also erased it. After some experimentation I found that I cannot control armbian terminal through UART and that's why I thought it hanged but I managed to connect via SSH (ty @eselarm) with ethernet to my laptop and custom DHCP and everything worked okay. The only problem is that HDMI still does not work. HDMI shows connected but I get this error from dmesg:

I guess this should do:

As the wifi device is the same please see my last post in this thread : Viz : Also to fix BT : sudo crontab -e then add the line : @reboot sudo hciattach -s 1500000 /dev/ttyS1 any 1500000 flow nosleep It could also be your dtb though. You could decompile my dtb from this thread and use the Bluetooth related section.

Usually people switch off the HDMI monitor of the computer and and walk away. Or they put a mirror against the monitor and ask the person they see why they bought a computer that does not have Debian installed?. Why am I here? Do I need a CD-ROM drive to install from ISO myself? How do I enter the BIOS? Does it have BIOS? But there is hope. Aarch64 Debian13: root@odroidn2:/boot# apt install linux-image-arm64 root@odroidn2:/boot# ln -sf vmlinuz-6.12.57+deb13-arm64 Image reboot root@odroidn2:/boot# apt install u-boot-amlogic-binaries root@odroidn2:/boot# dpkg -L u-boot-amlogic-binaries | grep odroid-n2 /usr/lib/u-boot/odroid-n2 /usr/lib/u-boot/odroid-n2/u-boot.bin /usr/lib/u-boot/odroid-n2/uboot.elf /usr/share/doc/u-boot-amlogic-binaries/configs/config.odroid-n2.gz

Hi @robertoj and @WDR_s I am having a similar screen ILI9486 from waveshare that i am trying to make it work with Milk-v duo S board. https://www.waveshare.com/wiki/3.5inch_RPi_LCD_(B) I was able to drive ST7789v and see content on screen with below code dts file &spi3 { status = "okay"; /delete-node/ spidev@0; st7789v: st7789v@0 { compatible = "sitronix,st7789v"; reg = <0>; spi-max-frequency = <48000000>; spi-cpol; spi-cpha; rotate = <0>; fps = <60>; rgb; buswidth = <8>; dc = <&porta 18 GPIO_ACTIVE_HIGH>; reset = <&porta 28 GPIO_ACTIVE_HIGH>; debug = <0x0>; status = "okay"; }; }; But trying to make ILi9486 work is next to impossible for me. I tried the dts file modification that worked for @WDR_s before he implemented touch. But this also does not work for me. And just for information dc-gpios and reset-gpios does not work for me and i have to name it dc and reset or else device /dev/fb0 is not created. &spi3 { status = "okay"; #address-cells = <1>; #size-cells = <0>; /delete-node/ spidev@0; ili9486: ili9486@0 { /* IMPORTANT: fb_tft binds MUCH more reliably to this */ compatible = "ilitek,ili9341"; reg = <0>; status = "okay"; /* SPI MODE 0 (correct for Waveshare ILI9486) */ spi-max-frequency = <24000000>; /* Use SAME pins that worked for ST7789V */ dc = <&porta 18 GPIO_ACTIVE_HIGH>; reset = <&porta 28 GPIO_ACTIVE_HIGH>; rotate = <0>; bgr = <0>; fps = <30>; regwidth = <16>; buswidth = <8>; txbuflen = <65536>; debug = <3>; /* Long, safe init sequence */ init = <0x10000b0 0x00 0x1000011 0x20000ff 0x10000C0 0x0D 0x0D 0x10000C1 0x43 0x10000C5 0x00 0x48 0x80 0x10000C7 0x00 0x1000036 0x28 0x100003A 0x55 0x10000B1 0xB0 0x11 0x10000F0 0x01 0x10000F6 0x00 0x01 0x32 0x1000026 0x01 0x10000E0 0x0F 0x31 0x2B 0x0C 0x0E 0x08 0x4E 0xF1 0x37 0x07 0x10 0x03 0x0E 0x09 0x00 0x10000E1 0x00 0x0E 0x14 0x03 0x11 0x07 0x31 0xC1 0x48 0x08 0x0F 0x0C 0x31 0x36 0x0F 0x10000B6 0x02 0x02 0x3B 0x1000011 0x20000ff 0x1000029>; }; }; This is very critical for me and i would really appreciate if you could make things work for me. Is the kernel 5.10 a issue here? as my SPI pins work for other display but not just for this display.

`idbloader.img` is device-specific code that is created from firmware build artifacts with U-Boot as payload using proprietary tools available only in binary form. SBC providers rarely offer ready-to-use code. I therefore prefer to load my firmware from microSD cards. Since it has apparently become increasingly common lately to provide only the MASKROM mode as the sole reliable recovery method, I have started building my firmware for Rockchip devices as RAM images as well. I can then simply upload them using MASKROM mode and start my work from there without having to rely on proprietary, binary-only tools.

Agree. @Igor

Thank you Werner, I propose to put this statement red boxed on top of this rpi landing page. Too many rpi5 help seekers get puzzled, they should be informed, to find more stuff in forum discussions. Greetings

While having this sent to mainline would be overall best, the faster approach in the mean time would be to send a patch via PR to this location to have it included into Armbian kernel packages: https://github.com/armbian/build/tree/main/patch/kernel/archive/rockchip64-6.18

At this time we do not have plans to support it. However anyone is free to step up and provide support with a pull request. We'll happily review. Perhaps chainxs will do this since they're an active volunteer contributor already

When support for Raspberry Pis has been added there was no model 5 yet. With the intention to only support the flagship the board configuration was added as rpi4b.conf. Since then support was extended across all models from 3 and up. However renaming a board config file is an issue. I already had the idea to address that but gave up on it: https://github.com/armbian/build/pull/7881 tl;dr: rpi4b image will work on all models from 3 to 5. https://www.armbian.com/rpi4b/

Hi All, Just coming across this now, and struggling with EMMC boot on 5B seems to be a theme on various forums.. May I ask where to retrieve `idbloader.img`? Thanks! Mark

I have verified that Wi-Fi is working, and I have also figured out how to install to eMMC. However, after running armbian-install, the system only boots if I put MiniLoaderAll.bin into the firmware field of the “Upgrade Firmware” session in Rockchip-AndroidTool while the device is in Maskrom mode, and then press the Upgrade button. MiniLoaderAll.bin It appears to be an SPI-related issue, but at the moment I don’t see any way to resolve it. I am also having difficulty getting Bluetooth to work. If you have any information on this, your assistance would be appreciated.

I see. Ok so Armbian sees only one IRL i2c buss, and stuffs any 'inconvenient' other devices into a useless buss. IOW Armbian is busted, at least for the ODroid N2+. Why use it then?