Jump to content

Active threads

Showing topics posted in for the last 365 days.

This stream auto-updates

  1. Past hour
  2. Even just someone kicking in with yes I think it's possible but not sure how or whatever I'd been thinking to ad the armbian repo hosting firmware files but I doubt it's so simple in practice
  3. @Jeeva Kandasamy I noticed the same problem with my older builds. Should be fixed now. Install Docker. Also use ARTIFACT_IGNORE_CACHE=yes to get rid of this cache error. artifact [ armbian-base-files :: armbian-base-files() ] jq: error: syntax error, unexpected '/', expecting end of file (Unix shell quoting issues?) at <top-level>, line 1: /armbian/.tmp/work-ab5594e5-34ea-495c-8cb4-4b8f7de401da/tmp.dhbvd4U9ZM jq: 1 compile error ./compile.sh ARTIFACT_IGNORE_CACHE=yes
  4. Today
  5. These are forums for Armbian Linux, not Android.
  6. Thanks for replying, I hadn't noticed the android thing, I have two sd cards one with the radxa android 14 and the other with the debian bullseye from radxa. I didn't mess with the SPI flash because both work correctly, does android flash the spi when booting, I don't understand how it works with the default debian but not here? I will try to maskrom mode and update. Btw here is the whole boot sequence in case it helps (I tried an older armbian build here but still the same). serial_log.txt
  7. Did someone managed to make it work on this model below? I tried creating the image with different allwinner chips but its not booting when I burn the sd and insert on the device. The tv box is a Mortal T1 Android 13 2gb ram and 16gb rom
  8. I am glad that you have the first 15% done: get your kernel module in the OS, and the uboot accepting the DTBO Now you are stuck in correcting the DTS, so that it configures the SPI pins correctly. My last advice for you (through this stage) is: make sure you don't have anything else using SPI pins. Deactivate "spi_dev" in armbian-config. Since I only had experience with H3 and H618 CPUs, I can't help with confidence. Post your question in the appropriate Rockchip forum section for up-to-date reliable advice. I can say that Radxa/Waveshare DTS is very out of date: it uses the fb_ili9486, which is "framebuffer" (poor fps), instead of the modern "DRM" display driver (high fps, will allow wayland). You should stay with that DTS with fb_ili9486, because it is still the closest starting point for you, and when you have it working, claiming all the GPIO pins needed, I can help again to use the DRM driver panel-mipi-dbi. Regarding MISO and MOSI, I only meant to change that nomenclature in the graphic that you show in the forum. I did't mean to change it in the DTS, if that's how other people make it work. Maybe you need to have the full linux source, so you can decompile the DTBO correctly, showing the gpio pin addresses or symbols. Is it possible that you get the Radxa/Waveshare original DTS?
  9. @laibsch: Thanks, but your objections are worthless. You have zero sense of humor, son. @esalarm: As a Debian user since 1997 I did an aptitude purge between trying daemons. I can not make any of them set the time, as they usually do in normal Debian. There is something missing in the most current stable Armbian. I wish you would try it on an N2+. I am happy to use chrony, as I have for several years, although in this case it has no effect. But the new Debians seem to be moving to systemd for everything such as this, so I adapted. But that didn't work either. I can't be the only one; maybe the first?
  10. Yesterday
  11. Thanks @dale I'll test it out on my box first and add it later on today.
  12. Apologies! I managed to find another post after a while and the answer was to untick the panthor device tree! It works now, amazing!
  13. @thanh_tan You found one armbian image to boot on Orangepi4A?
  14. Still not. Debian starts to load but then gets stuck (see photo above). I have tested again with a bookworm image and it worked. So there may be something wrong with the trixie image unfortunately 😕
  15. We don't deal with Android here. Ask vendor or at some place like xda developer forums.
  16. Hi @djurny, Yes it’s nice to tinker just so busy/tired that I’m not even doing that on the Windows side anymore. Still like the helios64 and would love to bring it up and running stable when needed, was just curious if worth the effort so looking for some success stories. I only plan to use it as a handy backup device which does sound strange for something unsupported. I think I’m still on buster as well on the sd card and never had the instability issues discussed around here (I think I mostly let it run 3 or 4 days at once in the first couple of years just to see if anything happens and did not). But I do read around here every couple of weeks. Thank you for your time!
  17. bunducafe

    Odroid M1

    I used the latest official image for a brand new install and set up OMV afterwards. So far everything works, but I ran into the "sata-reboot" bug. That said: Once I reboot after an update for example the sata drive is not being recognized. M2 nvme does come up as usual but not the sata ssd. Only remedy: Shutdown the M1, unplug, replug power cable and this cold reboot does the trick and the sata drive comes up again properly. It seems to be a kernel bug somehow and via armbian-config I tried several kernels but the bug unfortunately persists. Any ideas?
  18. I tried several options, each time on a clean system. 1) echo "deb http://apt.armbian.com bookworm main bookworm-utils" | sudo tee /etc/apt/sources.list.d/armbian.list wget -qO - https://apt.armbian.com/armbian.key | sudo gpg --dearmor -o /etc/apt/trusted.gpg.d/armbian.gpg sudo apt-get update sudo apt-get install make sudo apt-get install git sudo apt-get upgrade sudo reboot sudo apt install linux-headers-current-meson64 -y git clone https://github.com/xProbe/aic8800d80-wifi-driver.git sudo cp aic.rules /lib/udev/rules.d/ sudo cp -r ./fw/aic8800D80 /lib/firmware/ cd ./drivers/aic8800 make sudo make install sudo modprobe aic8800_fdrv lsmod | grep aic Вывод aic8800_fdrv 499712 0 aic_load_fw 65536 1 aic8800_fdrv cfg80211 385024 3 mac80211,rtl8xxxu,aic8800_fdrv dmesg выдаёт: [ 14.463892] Bluetooth: hci0: command 0xfc18 tx timeout [ 14.471627] Bluetooth: hci0: BCM: failed to write update baudrate (-110) [ 14.477696] Bluetooth: hci0: Failed to set baudrate [ 14.765636] wlan0: authenticate with 58:f8:5c:58:72:6c (local address=00:c6:a 2:25:44:eb) [ 14.770507] systemd[1]: Finished armbian-ramlog.service - Armbian memory supp orted logging. [ 14.772632] wlan0: send auth to 58:f8:5c:58:72:6c (try 1/3) [ 14.783084] wlan0: authenticated [ 14.791828] wlan0: associate with 58:f8:5c:58:72:6c (try 1/3) [ 14.796409] wlan0: RX AssocResp from 58:f8:5c:58:72:6c (capab=0x411 status=0 aid=4) [ 14.803902] usb 1-2: rtl8xxxu_bss_info_changed: HT supported [ 14.809513] wlan0: associated [ 14.809799] systemd[1]: Starting systemd-journald.service - Journal Service.. . [ 14.972227] systemd-journald[1340]: Collecting audit messages is disabled. [ 15.122032] systemd[1]: Started systemd-journald.service - Journal Service. [ 15.252235] systemd-journald[1340]: Received client request to flush runtime journal. [ 15.342582] systemd-journald[1340]: /var/log/journal/d44cb1f74dea4809a2af30db 6816ca18/system.journal: Realtime clock jumped backwards relative to last journa l entry, rotating. [ 15.410914] systemd-journald[1340]: Rotating system journal. [ 16.511866] Bluetooth: hci0: command 0xfc18 tx timeout [ 16.514129] Bluetooth: hci0: BCM: Reset failed (-110) [ 17.317977] systemd-journald[1340]: Received client request to relinquish /va r/log/journal/d44cb1f74dea4809a2af30db6816ca18 access. [ 950.587521] aic_load_fw: loading out-of-tree module taints kernel. [ 950.600781] aic_bluetooth_mod_init [ 950.606085] RELEASE DATE:2025_0423_71b66e7b [ 950.611193] AICWFDBG(LOGINFO) aicwf_prealloc_init enter [ 950.635622] AICWFDBG(LOGINFO) pre alloc rxbuff list len: 1000 [ 950.640969] usbcore: registered new interface driver aic_load_fw [ 950.678054] AICWFDBG(LOGINFO) rwnx v6.4.3.0 - 1a4b0054d2M (master) [ 950.680449] AICWFDBG(LOGINFO) RELEASE DATE:2025_0423_71b66e7b [ 950.686449] usbcore: registered new interface driver aic8800_fdrv 2) 3) 4) I tried it, it didn't help. 5)
  19. keep pushing, this device is not brickable, you can make your trip worry-free
  20. We don't support 3rd party forks. Ask at the place where you got this OS from.
  21. Because they sell you the hardware only. Their software support is very poorly made since for the price they cannot afford proper software support and - even more important - maintenance. They leave this burden to - mostly unpaid - random developers across the world like us. At least I'd go for a device with Standard Support which the Ultra and Max hasn't: https://www.armbian.com/download/?device_support=Standard support For the raspberry you would need additional hardware (an AI kit I guess). No clue though about how they both perform in comparsion. For RK3588 you have two choices for now: The rockchip bsp implementation and https://github.com/rockchip-linux/rknn-toolkit2. Or using 6.18 kernel using the reverse engineered Rocket driver and latest bleeding edge mesa to get npu access. I personally did not play with either of these options and have no intention to do so for the moment.
  22. Armbian 25.8.1 Noble XFCE (BSD Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + box64 3.9 (https://ryanfortner.github.io/box64-debs/) + wine-10.15-staging-tkg-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/tag/10.15) + DXVK-stripped v2.7.1 ~20fps@720p (low settings) Skyrim SE
  23. I have a working img that boots fine from sd card. However the dtb is not perfectly working. Below are dts from android and linux (partial working). I hope that someone can help me with rewriting device tree source for it. Thank you! rk3399-emb3531.dts.txtrk3399-emb3531-android.dts.txt
  24. Last week
  25. Scroll back and read all my posts from April 11 onwards (page 17). On Radxa's github there are Wifi/BT drivers for AIC8800. They are at version 4 now : https://github.com/radxa-pkg/aic8800/releases/tag/4.0%2Bgit20250410.b99ca8b6-3 Also to fix BT : sudo crontab -e then add the line : @reboot sudo hciattach -s 1500000 /dev/ttyS1 any 1500000 flow nosleep then reboot the H96.
  26. We are slowly releasing v25.11 images and here I did some mess-up, fixed now. We don't offer Bookworm anymore, so Trixie it is. If you need to Bookworm for some reason, you can build on your own or use the one from archive: http://archive.armbian.com/ Attached torrent will download super fast. Armbian_25.11.1_Helios64_trixie_current_6.12.58_minimal.img.xz.torrent
  27. Im trying to flash armbian into the eMMC but its not detected, only the SD card. What should i do? Useful info: CPU/Chip/Idk: sun8iw7p1 PCB Model(?): H3 Q44 V4.0 Uname -a: Linux orangepipcplus 6.12.58-current-sunxi #1 SMP Thu Nov 13 20:34:41 UTC 2025 armv7l GNU/Linux dmesg | grep -i mmc [ 0.000000] Kernel command line: root=UUID=cf60c629-17b3-4fb8-91bb-24bd021f8c6b rootwait rootfstype=ext4 splash=verbose console=ttyS0,115200 console=tty1 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 consoleblank=0 loglevel=1 ubootpart=def8ba6d-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory [ 0.000000] Unknown kernel command line parameters "splash=verbose ubootpart=def8ba6d-01 ubootsource=mmc sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory", will be passed to user space. [ 4.995824] sunxi-mmc 1c0f000.mmc: Got CD GPIO [ 5.019105] sunxi-mmc 1c0f000.mmc: initialized, max. request size: 16384 KB [ 5.031030] sunxi-mmc 1c11000.mmc: initialized, max. request size: 16384 KB [ 5.048053] mmc2: Failed to initialize a non-removable card [ 5.063249] mmc0: host does not support reading read-only switch, assuming write-enable [ 5.067129] mmc0: new high speed SDXC card at address aaaa [ 5.071189] mmcblk0: mmc0:aaaa SC64G 59.5 GiB [ 5.080563] mmcblk0: p1 [ 5.316321] ubootsource=mmc [ 7.603641] sunxi-mmc 1c10000.mmc: allocated mmc-pwrseq [ 7.635175] sunxi-mmc 1c10000.mmc: initialized, max. request size: 16384 KB [ 7.687081] mmc1: new high speed SDIO card at address 0001 [ 8.364751] EXT4-fs (mmcblk0p1): mounted filesystem cf60c629-17b3-4fb8-91bb-24bd021f8c6b ro with writeback data mode. Quota mode: none. [ 14.091111] EXT4-fs (mmcblk0p1): re-mounted cf60c629-17b3-4fb8-91bb-24bd021f8c6b r/w. dmesg | grep -i mmc2 [ 5.048053] mmc2: Failed to initialize a non-removable card I also extracted a DTB file and DTS file from the android of the TV box, if that is useful (I used AI for that, and dont really know if they are useful) Thanks. dts.txt
  28. I found this thread https://forum.armbian.com/topic/47929-banana-pi-bpi-m2-ultra-with-armbian-stops-load-after-scanning-for-btrfs-filesystems/
  1. Load more activity
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines