All Activity

So I can confirm that this solved the compiling issues, Thank you very much @Werner Now I am facing another issue with EFI when trying to boot. Will try to see if I can identify the problem and solve it.

Ohhh thank you so much, I spent so much time trying to find the solution

https://github.com/armbian/build/pull/9724

Confirmed. From first glance it looks like dts files are missing.

https://paste.armbian.com/rapohapofe

Good Morning, I am running into an issue when trying to compile an image for a SM8250 device. Most of the process is working fine until it gets to the Grub Section, at which point I get the following error: " cp: cannot stat '/usr/lib/linux-image-6.18.24-current-sm8250/qcom/sm8250-retroidpocket-rp5.dtb': No such file or directory" I have attached the logs, and would love to know if anyone has had a similar issue when trying to build an image for any device, and if so what you have done to solve it. Thanks all in advance for the support

When SPI is erased, the board falls back to the bootloader on the SD card. If you want to run Armbian, or Linux in general, the bootloader often needs to be updated - in this case on SPI. This can be done with armbian-install. Android support is not verified and is outside the scope of Linux maintainers. It may continue to work, or it may break.

I apologize again, as I am using a translator. Hello, good evening. I had forgotten to reply. To rule out any problems, I decided to reinstall everything from scratch. I reinstalled Android 12 (microphone works). I installed Armbian (microphone works). The problem starts when I want to use my eMMC unit. Armbian doesn't detect it, and I read that I have to delete the SPI Flash. After deleting it, it detects it, but my Android system stops working. In the end, I ended up going back to a Linux distribution other than Armbian.

@qq20739111 The compilation was successful, but ollama was unable to call NPU

Hi @xuyitao, My repository is focused on moving toward a usable mainline kernel. As of this week, there are no longer any dependencies on BSP NPU drivers. I plan to remove those, along with the BSP GPU drivers, to avoid any potential confusion. Could you take a look at the mainline etnaviv driver? Hopefully it meets your needs.

I had some success, I start it via pxe + nfs, some systemd services are not starting, I think I can also prepare the correct USB image, it will be interesting, thanks everyone 😃

Starting from Trixie, some paths have changed. Here is the complete walkthrough for the process: Install necessary tools (i2c-tools and hwclock are not present by default in Armbian trixie): sudo apt install i2c-tools util-linux-extra Edit armbianEnv.txt: sudo nano /boot/armbianEnv.txt Append i2c0 to the line that says overlays=...: overlays=... i2c0 ("..." denotes some overlays already written, do not delete them). Reboot (compulsory to load i2c module): sudo reboot now Inquire availability of module rtc-ds1307 in the kernel (present in trixie): sudo modinfo rtc-ds1307 If it returns some description, the module is present. If not, then install its driver from GitHub. Open modules file: sudo nano /etc/modules Add line rtc-ds1307 in it. Save and close. Run the following command: sudo i2cdetect -y 0 It should return 68 in the grid: 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- Then add module to start up: sudo modprobe rtc-ds1307 sudo echo ds1307 0x68 > /sys/class/i2c-dev/i2c-0/device/new_device The DS1307 should now be available at /dev/rtc1, which you can check: sudo ls /dev/ | grep rtc Initialize rtc1 (once) sudo hwclock --rtc /dev/rtc1 --systohc Create a new file rtc_ds1307.sh: sudo nano /usr/local/bin/rtc_ds1307.sh Add following lines in it: #!/bin/bash echo "Creating entry for rtc_1307 service" | systemd-cat -p info sudo echo ds1307 0x68 > /sys/class/i2c-dev/i2c-0/device/new_device echo "Done" | systemd-cat -p info echo "Symlinking /dev/rtc1 to /dev/rtc" | systemd-cat -p info sudo ln -f -s /dev/rtc1 /dev/rtc echo "Done" echo "Syncing RTC time to system time" | systemd-cat -p info sudo hwclock --hctosys --noadjfile --utc -f /dev/rtc1 echo "Done" Save and exit. Make this file executable: sudo chmod +x /usr/local/bin/rtc_ds1307.sh Create a systemd service to run this script at startup: sudo nano /etc/systemd/system/rtc_ds1307.service Add following lines in it: [Unit] Description=Synchronize system clock to RTC Requires=systemd-modules-load.service After=systemd-modules-load.service ConditionPathExists=/sys/class/i2c-dev [Service] Type=oneshot RemainAfterExit=yes ExecStart=/usr/local/bin/rtc_ds1307.sh [Install] WantedBy=multi-user.target Save and exit. Enable the service: sudo chmod 644 /etc/systemd/system/rtc_ds1307.service sudo systemctl enable rtc_ds1307.service Reboot and check system date time by running: timedatectl

@Sergioclr output of USB-to-TTL converter. sudo dmesg

Is there an armbian with home-assistant installed?

So I'm fairly new to Armbian (although I have already managed to successfully create a custom build with most of what I need). Sadly, I've very much hit a blocker. I really need to use linux-tools/perf on an RK3588 board with a vendor kernel (I'm using the Mali OpenCL, and the ARM packages are mostly locked) and I need to do some performance tuning. I cannot figure out how to get these tools deployed. 1. There are no linux-tools packages build -- which is fair enough, I'm probably in a minority. Some parts of the tools directories are culled during a cleaning process for the headers, I can see that 2. I am happy to copy over the kernel source and build on the device, but this is a patched vendor kernel. Can I just rsync across `cache/sources/linux-kernel-worktree`? Is that the patched kernel source tree? 3. There are some old allusions in the forums to using armbian-config to get sources -- I'm guessing that's long deprecated 4. Would it be appropriate at some point to create a .deb for the actual kernel sources, just in case -- or even, ideally, the linux-tools packages themselves? I am very happy to invest effort into helping make this happen, but I am starting from cold into this fairly complex build infrastructure, so any help or pointers I'd be extremely grateful.

How to install Armbian on an eMMC module? Simply using Armbian Imager with the image file doesn't work—the system won't boot. The official Radxa OS boots fine from the same eMMC module.

Newbie question: how can I do that (boot logs)? 🤔

Hello everyone, I bought an H96 Max M9 TV box. I mainly use it for YouTube and watching movies, but later I wanted to use it for gaming, including emulators and modern community-made ports. This TV box, with its 8GB of RAM, has a lot of potential, but it is being wasted due to a common issue: the file manager. The problem is not the file explorer apps you install—I’ve tried them all—but the system’s storage manager (Android’s SAF), which seems to be poorly implemented or limited by the firmware. This causes issues such as: Selecting folders in PPSSPP (memory stick) Access for emulators like Dolphin Emulator Installing game ports that should run perfectly on this TV box, but cannot be installed due to bugs in the system file manager To be honest, I’m not very knowledgeable about these topics, but if anyone has experienced this or knows a possible solution and can share the information, I would really appreciate it in advance.

@Sergioclr Can you post your boot logs? both android and armbian. Try this. phy-supply = <&reg_dldo1>; /* Try reg_dldo1 if aldo1 (1.8V) fails */

Hi, trying to build custom image, from your repo. Building from branch mxq-pro couldn't get to booting from emmc, but your provided firmware does fine, what am i missing there?

@jock Please help. Worst TV-box PCB I've ever seen in my life. Hardware: H96 Max "8K Ultra HD" (round case) PCB: RK3528_DDR3_8X4_V12 SoC: Rockchip RK3528 4GB DDR3 (8x Samsung K4B4G0446B) 64GB eMMC Samsung KLMCG2KETM WiFi: SKYWB8800 / SG-WB800E (AIC8800) Android 13, kernel 5.10.157, build RZX.V01.20240924.1740 I have TWO boards (same PCB revision, same markings). Both have DEBUG pads clearly labeled TX / GND / RX. UART completely silent in all combinations. Tried two different adapters: FTDI FT232 (ID 0403:6001) Silicon Labs CP2102 (ID 10c4:ea60) Both show up in dmesg fine, /dev/ttyUSB0 created, picocom opens. When powering device on — silence or garbage at all baud rates (115200, 230400, 460800, 921600, 1000000, 1152000, 1500000, 2000000, 3000000). Soldering done by a professional, crossover connection: adapter TX → board RX adapter RX → board TX GND ↔ GND VCC NOT connected (device powered separately) Loopback test on adapters works — adapters are OK. Devices are alive — Android boots normally, AIDA64 shows everything fine. Tested on both boards with both adapters — silence everywhere. Only garbage appears when physically jiggling wires (clearly body static, not device signal). My hypotheses: Vendor disabled UART output in stock loader/TPL for boot speed TX/RX pads repurposed as GPIO (LED / IR / etc.) DEBUG pads are actually NOT UART but JTAG/something else UART works but on some non-standard baud rate In fensoft U-Boot defconfig (https://github.com/fensoft/rk3528-tvbox) I see: CONFIG_BAUDRATE=1500000 CONFIG_DEBUG_UART_BASE=0xff9f0000 CONFIG_DEBUG_UART_CLOCK=24000000 Meaning fensoft uses this UART on similar boards. Why doesn't mine work? Background: spent 3 days trying to PXE boot Armbian. U-Boot (Ilya's + fensoft) works, TFTP/NFS works, kernel loads, initrd loads, DTB loads. But after booti the kernel dies instantly, so I need UART to see panic message. Tried many DTBs: evb1-ddr4, evb2-ddr3, android-native, nanopi-zero2, armsom-sige1, vontar-dq08, even stock Android DTB extracted from boot.img — all silent. Anyone experienced this on H96 Max RK3528 DDR3? Any way to force UART enable via some fastboot/adb command on Android before reboot? Attaching photos: PCB with RK3528_DDR3_8X4_V12 marking Close-up of DEBUG pads with soldered wires SG-WB800E WiFi module Thanks in advance for anyone who reads this!

Help needed (previous update): What should be edited is this file? sudo pico arch/arm64/boot/dts/allwinner/sun50i-h313-x96q-lpddr3.dts Thanks in advance.

@xuyitao Did your build pass? Can the NPU handle Ollama?

As a workaround I installed Armbian_community_26.2.0-trunk.732_Orangepi3b_trixie_vendor_6.1.115_minimal .img.xz and USB is OK, anyway ethernet is functional.