Active threads

I am unable to reproduce this on BigTreeTech Pi (v1.2). Set wifi up using netplan via NetworkManager. Wifi connects after a reboot, same if I poweroff the device, disconnect power and then connect back up.

Is your monitor a standard 1080p resolution or something else? If you try a server build that doesn't load a graphical interface does it work? Have you tried something more standard like gnome instead of cinnamon?

Copy armbian-install to bin home directory Please replace line 839 as indicated here: Run the corrected version of the script. If everything works correctly for you, confirm it here. I will add a correction to the next pull request.

➜ ~ dmesg| grep mmc [ 1.926019] mmc0: SDHCI controller on fe2e0000.mmc [fe2e0000.mmc] using ADMA [ 2.026282] mmc0: new HS400 Enhanced strobe MMC card at address 0001 [ 2.031712] mmcblk0: mmc0:0001 A3A444 230 GiB [ 2.037074] mmcblk0: p1 [ 2.038122] mmcblk0boot0: mmc0:0001 A3A444 4.00 MiB [ 2.040301] mmcblk0boot1: mmc0:0001 A3A444 4.00 MiB [ 2.042564] mmcblk0rpmb: mmc0:0001 A3A444 4.00 MiB, chardev (243:0) [ 2.150020] dwmmc_rockchip fe2c0000.mmc: IDMAC supports 32-bit address mode. [ 2.150727] dwmmc_rockchip fe2c0000.mmc: Using internal DMA controller. [ 2.155343] dwmmc_rockchip fe2c0000.mmc: Version ID is 270a [ 2.155854] dwmmc_rockchip fe2c0000.mmc: DW MMC controller at irq 98,32 bit host data width,256 deep fifo [ 2.156969] dwmmc_rockchip fe2c0000.mmc: Got CD GPIO [ 2.169374] mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [ 2.432912] mmc_host mmc1: Bus speed (slot 0) = 198000000Hz (slot req 200000000Hz, actual 198000000HZ div = 0) [ 2.714811] dwmmc_rockchip fe2c0000.mmc: Successfully tuned phase to 230 [ 2.717703] mmc1: new UHS-I speed SDR104 SDXC card at address 544c [ 2.719268] mmcblk1: mmc1:544c LX64G 58.9 GiB [ 2.721418] mmcblk1: p1 p2 [ 5.394333] EXT4-fs (mmcblk1p2): mounted filesystem 00560a2f-4a48-4f42-85db-f7197f411193 ro with ordered data mode. Quota mode: none. [ 8.122124] EXT4-fs (mmcblk1p2): re-mounted 00560a2f-4a48-4f42-85db-f7197f411193 r/w. Quota mode: none. ➜ ~ uname -a Linux t6.superkali.lan 6.14.4-edge-rockchip64 #1 SMP PREEMPT Fri Apr 25 08:51:21 UTC 2025 aarch64 GNU/Linux root@t6-2:~# dmesg | grep mmc [ 1.793233] mmc0: SDHCI controller on fe2e0000.mmc [fe2e0000.mmc] using ADMA [ 1.892860] mmc0: new HS400 Enhanced strobe MMC card at address 0001 [ 1.893418] mmcblk0: mmc0:0001 A3A444 230 GiB [ 1.900752] mmcblk0: p1 [ 1.901187] mmcblk0boot0: mmc0:0001 A3A444 4.00 MiB [ 1.902094] mmcblk0boot1: mmc0:0001 A3A444 4.00 MiB [ 1.903152] mmcblk0rpmb: mmc0:0001 A3A444 4.00 MiB, chardev (243:0) [ 2.015519] dwmmc_rockchip fe2c0000.mmc: IDMAC supports 32-bit address mode. [ 2.015588] dwmmc_rockchip fe2c0000.mmc: Using internal DMA controller. [ 2.015603] dwmmc_rockchip fe2c0000.mmc: Version ID is 270a [ 2.015721] dwmmc_rockchip fe2c0000.mmc: DW MMC controller at irq 98,32 bit host data width,256 deep fifo [ 2.016264] dwmmc_rockchip fe2c0000.mmc: Got CD GPIO [ 2.029321] mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [ 2.270630] mmc_host mmc1: Bus speed (slot 0) = 198000000Hz (slot req 200000000Hz, actual 198000000HZ div = 0) [ 2.473628] dwmmc_rockchip fe2c0000.mmc: Successfully tuned phase to 247 [ 2.477145] mmc1: new UHS-I speed SDR104 SDXC card at address 544c [ 2.478144] mmcblk1: mmc1:544c LX64G 58.9 GiB [ 2.483356] mmcblk1: p1 [ 3.176039] EXT4-fs (mmcblk1p1): mounted filesystem 3aa41aca-1f77-4222-b253-8d444c3dfca5 ro with writeback data mode. Quota mode: none. [ 8.484634] EXT4-fs (mmcblk1p1): re-mounted 3aa41aca-1f77-4222-b253-8d444c3dfca5 r/w. Quota mode: none. root@t6-2:~# uname -a Linux t6-2.superkali.lan 6.14.4-edge-rockchip64 #1 SMP PREEMPT Fri Apr 25 08:51:21 UTC 2025 aarch64 GNU/Linux root@nanopct6-lts:~# dmesg | grep mmc [ 4.386835] dwmmc_rockchip fe2c0000.mmc: No normal pinctrl state [ 4.386849] dwmmc_rockchip fe2c0000.mmc: No idle pinctrl state [ 4.386921] dwmmc_rockchip fe2c0000.mmc: IDMAC supports 32-bit address mode. [ 4.386972] dwmmc_rockchip fe2c0000.mmc: Using internal DMA controller. [ 4.386986] dwmmc_rockchip fe2c0000.mmc: Version ID is 270a [ 4.387034] dwmmc_rockchip fe2c0000.mmc: DW MMC controller at irq 157,32 bit host data width,256 deep fifo [ 4.387131] dwmmc_rockchip fe2c0000.mmc: Looking up vmmc-supply from device tree [ 4.387431] dwmmc_rockchip fe2c0000.mmc: Looking up vqmmc-supply from device tree [ 4.403026] mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [ 4.495259] mmc0: Command Queue Engine enabled [ 4.495299] mmc0: new HS400 Enhanced strobe MMC card at address 0001 [ 4.496710] mmcblk0: mmc0:0001 A3A561 57.6 GiB [ 4.505219] mmcblk0: p1 [ 4.505766] mmcblk0boot0: mmc0:0001 A3A561 4.00 MiB [ 4.506882] mmcblk0boot1: mmc0:0001 A3A561 4.00 MiB [ 4.507923] mmcblk0rpmb: mmc0:0001 A3A561 16.0 MiB, chardev (234:0) root@nanopct6-lts:~# uname -a Linux nanopct6-lts 6.1.84-vendor-rk35xx #1 SMP Wed Dec 18 05:56:40 UTC 2024 aarch64 GNU/Linux root@nanopct6-lts:~# The first two are the variants with 256GB of eMMC, therefore non-LTS, while the last one is the LTS variant with 64GB of eMMC. From my tests with both the edge version and the vendor kernel, both negotiate in HS400 without any problems: A test carried out by T6-2: /dev/mmcblk0p1: Timing cached reads: 7686 MB in 2.00 seconds = 3845.97 MB/sec Timing buffered disk reads: 854 MB in 3.00 seconds = 284.38 MB/sec I don't see your errors, so I think there might be something strange with your board. Can you try the edge kernel and tell me if you have the same problems, or the vendor kernel?

Hey @amazingfate, I have an issue with the build-in IR receiver on my OPI5+: ##O#O## OS: Armbian 25.8.1 noble aarch64 ####### Host: Orange Pi 5 Plus ########### Kernel: 6.1.115-vendor-rk35xx ############# Uptime: 2 mins ############### Packages: 1934 (dpkg), 5 (snap) ################ Shell: bash 5.2.21 ################# Resolution: 3840x2160 ##################### DE: GNOME 46.0 ##################### WM: Mutter ################# WM Theme: Adwaita Theme: Adwaita [GTK2/3] Icons: Adwaita [GTK2/3] Terminal: x-terminal-emul CPU: (8) @ 1.800GHz Memory: 2585MiB / 15957MiB After a reboot it works just fine, but once I suspend/resume it stops working. Logs look clear of errors. I have tried to troubleshoot with ChatGPT but goin' in circles and gave up. Lastly ended up with some speculations from it like: static int rockchip_pwm_remotectl_resume(struct device *dev) { struct remotectl_dev *rc_dev = dev_get_drvdata(dev); // Re-init or restart the device if (rc_dev && rc_dev->restart) rc_dev->restart(rc_dev); return 0; } static const struct dev_pm_ops rockchip_pwm_remotectl_pm_ops = { .resume = rockchip_pwm_remotectl_resume, }; static struct platform_driver rockchip_pwm_remotectl_driver = { .probe = rockchip_pwm_remotectl_probe, .driver = { .name = "rockchip_pwm_remotectl", .pm = &rockchip_pwm_remotectl_pm_ops, }, }; Do you think this is the problem, or if not can I share some details so you can try to find it?

hi guys, yesterdays announcement of Qualcomm Arduino UNO Q on some Dragonwing SoC ... but heard anybody about it already? how it can be open? some questions ... P.

moved

moved

Not an Armbian image. If you want to use this one, try to get support from where you got the image from.

Hi @Hqnicolas first of all, thanks for all yours and other efforts on this project. I had an eye on it a few months back but only this week did I dig out my two boxes.. A few questions for you if you don't mind answering? I have two boxes, 2GB version I was using for development (Android image) and then full fledged 8GB version. Now, because the boxes were in storage for a year or two I thought I had the 4GB and 8GB version, do you happen to have somewhere the Bootloader image for the 2GB model? I've done a google but can only find the 4 and 8GB version. I was experimenting with Armbian and kinda bloated the image so I'll start from scratch. I went ahead and flashed Armbian on both now without issues, however, I've noticed the Wifi is quite slow on it - around 120-240KB/s download and ping to `1.1.1.1` gives around 30 - 300ms, I've had `top` going at the same time and don't see any high CPU utilization. The Wifi driver is something like `bcmrfm` or alike. Is this normal? I've got my 2GB version hooked up to serial out. I do remember seeing an output in plain English however I can't remember the settings, would you be able to tell me? I've tried the common baud rates with Minicom but no matter what I do I just get a garbled output. The link from previous messages for the SDCard holder is now invalid, could you point me to one that will fit nicely on the board? Finally, from your last post, I see you got the front display displaying data, could you point me in the right direction to code for this? Either C++ or Python will do. I do plan on a monitor for eth, wifi and with time + load + temp possibly. Thanks, Robert.

That's already a topic (with a solution): https://forum.armbian.com/topic/55129-trixie-apt-warning-policy-will-reject-signature-within-a-year/

@werner, thanks for the information and the clarification on my concern in the documentation. This sounds like an interesting project, I do believe I'll give it a try. Again, thank you for the encouragement and the pointers.

same problem， and 25.11.0-trunk.129 img dont work

Hi, I have the same TV Box and would like to install Armbian Linux. Could someone tell me which version to install and how?

I have a TV box with 1.5 GB lpddr3 that has been running Manjaro Arm without any problems for a long time. I used this TV box to add lpddr3 support to the dram driver many years ago. You can get the latest patch for 6GBIT lpddr3 support here: https://github.com/iuncuim/manjaro-h616/blob/main/uboot-t98-h2b-lp3/0007-shrink-ram.patch

From the Circuit Schematic it looks like the Radxa Rock 5B+ RK3588 GPIO0-C0 is the fan I/O, GPIO pin 24, if thats correct. I will verify I can access this on the Armbian distro.

Hello, I have two Orange Pi Zero 2 for two years, I didn't know what to do with it. Yesterday I have installed Armbian_25.5.1_Orangepizero2_noble_current_6.12.23. The serial was a bit buggy during installation (display + key press), I have used option -L with screen: screen -L /dev/ttyUSB0 115200 Thank you for your great work !

Orange pi 5 wifi now supports injection mode using nexmon. Kali distro available from setup menu.

where exactly does this error show up? while downloading with your browser? while writing to the sdcard? while booting? Please elaborate. debug boot issues: https://debug.armbian.de

Hi @loeriver, Yes, it depends a bit on what brand/type and how you connect the USB to serial converter. The ones i use to monitor the serial console on all my SBCs have these spurious events as well, even when I do not connect the +5Vdc on the serial/UART end. For me they are sometimes preventing a full board shutdown as they seem to leach power to the SBC (not sure how this is happening electrically, perhaps some pull-ups allowing current to flow from RX into the Vcc of the board?). You could try to remove the dongle from the system to see if that has any effect to rule this out completely. Groetjes,

@oscylator678 I used this PPA https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco Mesa 23.0, PanVk has already Vulkan 1.4.

@Fredrik thank you for testing.

It seems like there is a mix-up between specs for the framework and for the OS. A lightweight desktop can run on 512MB, yes but probably not much fun, depending on applications. Won't recommend running a web browser. I'd probably get some existing cheap sbcs with similar specs and play with them to elaborate if the performance is sufficient.

Thank you very much. I will try it. Thank you very much. I will try it.

I can confirm that my changes have now been merged into the upstream linux_openfd repo, so I have deleted my fork. Unfortunately I am unable to edit my instructions, but hopefully it should be clear from the instructions that if my fork is unavailable, then the original repo should be used (alternatively, if a mod could edit the post to remove the reference to my fork, to make the instructions clearer, that would also be appreciated).