Active threads

So out of luck, I have tried multiple fixes that I can find, tested other SD cards and still ending up with the same error. Booting: mmc 0 error: no such partition grub rescue> Will try to do some more digging and keep the post updated

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.

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

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.

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.

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?

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.

@fensoft I am using your current image 3.0.0_r2 in H96 Max M1 with USB Hub + USB to Ethernet adapter successfully. Its really energy efficient solution which can run 24 x 7 without costing much. However I am trying to set this up on a dq08 box with 4 GB/64 GB Model. I am able to install dq08_ha_supervised_3.0.0_r2.zip without any issue. However due to recent support changes from the application, I am unable to continue further with the setup. I tried to install docker version to set this up but getting error "invalid argument: in-kernel BTF is malformed (1 line(s) omitted)". Not seeing much on this error in the interwebs but there are suggestions that this could be due to old kernels/. Is there a way we can update this kernel and OS to Armbian Trixie or will it brick the dq08? Have you got a chance to look at the updated installer image?

same here: RADXA 4SE

Okay so then we have some issues here This is clearly wrong since these packages come from upstream Debian and cannot/will not work with Armbian kernels. This shall be reported here: https://github.com/armbian/configng/ Then you were lucky some working headers were present https://docs.armbian.com/Developer-Guide_Build-Preparation/ Or in very short: git clone the repo ./compile.sh BOARD=rockpi-4bplus BRANCH=current kernel Check output/debs for your packages Install via dpkg -i on the target board

Aiee! Installed my old "Noble" image. Updating will remove kernel 6.18.18 and install 6.6.99 and also has the error in the firmware package as decribed above by @VBB. Also, that funny "cli.github.com/packages" repo does not work. While that kernel downgrade is probably caused by linux-image-current-spacemit moved from 6.6.99 to 6.18.x recently (and the Armbian repos are out of date somehow) that firmware package should update without any errors. Will need time to sort this out. Anyhow, the "Noble" image works with GPU-activated Gnome desktop as long as you do not update (downgrade)...

I published my Vontar H618 bring-up patch set here: https://github.com/aco-art/vontar-h618-armbian-patche It includes the Armbian userpatches, U-Boot/kernel changes, and diagnostics tools I used for this box. Tested on my 4 GiB DDR3 Vontar H618 unit and shared in case it helps with similar H618/H616-class TV boxes. On my tested unit, Wi-Fi, Bluetooth, LAN, HDMI output, and the basic GPU/display path are working with this baseline.

I'm having the same issue after upgrading. I do backups on an HDD via USB for the two drives on my HC4 I was on Bullseye this year and was planning on moving up to Bookworm for a bit, but was hit with the issue. I decided to jump then into Trixie in the hopes that a more recent kernel would fix it, but I'm still facing it. kernel: Linux odroidhc4 6.18.10-current-meson64 dmesg error msg: usb usb1-port2: connect-debounce failed

The orange pi zero 2w is configured to only start u-boot from the microSD in the built-in microSD. You would have to: * recompile that uboot to load the initramfs and the kernel from your alternative storage (did you really mean HDD? which connector would you use?) or * load initramfs and kernel from the typical microsd /boot partition, but configure the kernel argument line to accept the HDD as the rootfs (make sure that the initramfs contains the kernel modules, and the hdd name is in the /etc/fstab file) or https://jamesachambers.com/orange-pi-zero-2-usb-ssd-boot-guide/

@lsdlsd88 hello! Thanks for sharing the photos and the serial logs; it looks like the stock firmware did not pick up the sdcard at all. The sdcard seems to be detected, but for some reason the rockchip miniloader of the stock firmware does not it as first source. Are you able to retrieve the first 100-200 megabytes of the original firmware via serial? You should be able to use dd even within Android. edit: ah-ha ok, I understand! there is misconfiguration in the webserver and the link changes; thanks, I updated it!

Yes, you can completely resize it. You can also turn it to ZFS volume, and boot off of it. Just rebuild u-boot with ZFS support. Or ask, and I will provide patches required to have it.

It is. Before I managed to rebuild u-boot with ZFS support, I had to boot off of EMMC. I shrunk first partition with kernel, initrd etc, and then made another one with actual FS. Temporary solution for me back then. But gave me time to rebuild everything and enable native ZFS boot. Since then, I use EMMC only as a ZFS volume (another one in the mirror is NVME drive). never used armbian-config though - I am old-schooler, so I had to build whole stack myself to get what I wanted.

Use armbian imager for flashing it, arduino flasher cli is not compatible

current_6.6.99_minimal (desktop build has the snd-usb-audio module)