All Activity

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

moved to tvboxes

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.

I've installed Armbian Ubuntu Nobble Cinnamon on sdcard with Polytron PDB F1 and it's chipset amlogic S912 After login with lightdm, my screen turn black, What I should do?

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 !

Hello. I have x96q DDR3 v5.1 box. I flashed vontar h618 image with patched dtb. Everything seems fine except extended file properties. Docker need these properties to operate normally. Can you suggest image with extended file properties support for my box with working ethernet?

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

You don't have to run on bare-metal. A proper VM will do too and is probably the better solution. Yes. Cross-compiling is used for everything that's not native. You're aware that the command in the docs is just an example, right?

Armbian does not come with some sort of admin console. Please elaborate. Try different patch cable. moved

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

@igor I think what you're suggesting is that I build my own Ubuntu 24.04 image using the info on the page; am I correct? I could be talked into this but first I would have to build a 24.04 system - my three desktops and one laptop are all running 25.04, soon to move to 25.10. I could sacrifice the "old beater"... Reading these instructions, I believe that running 24.04 on an X86/64 machine I could build an ARM system; does that make sense? This comment worries me though: I'm trying to create a minimal IOT image; is that a separate pathway? Thanks in advance, and as always thanks for Armbian!

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,

I have the default radxa image rock-5b-plus_bookworm_kde_b2 image with the fan working :- https://github.com/radxa-build/rock-5b-plus/releases/download/rsdk-b2/rock-5b-plus_bookworm_kde_b2.output.img.xz I/We need to try and find how this was built and the Linux DTD file the `uname -a` kernel reports as "Linux rock-5b-plus 6.1.84-1-rk2410" kernel. rsetup :- https://docs.radxa.com/en/rock5/rock5b/getting-started/interface-usage/fan https://github.com/radxa-pkg/rsetup

Right, that's the downside - anyone with a different eMMC chip will see a drop in performance. I've just given that overlay a try - thank you for suggesting it. I put it in to /boot/overlay-user, then edited /boot/armbianEnv.txt to include the line user_overlays=rk3588-nanopc-t6-emmc . Unfortunately, it then failed to boot. I had to put in an SD card, boot from that, mount the eMMC partition, and then remove the overload from armbianEnv.txt to get it to boot successfully from the eMMC again.

You will certainly gain many grateful users whose devices are not equipped with an affected eMMC, but who still have to suffer from the slowdown nonetheless. Does the attached overlay work for you?rk3588-nanopc-t6-emmc.dtbo

If I understood a bit better what the script is doing, i.e. this part: Then maybe I could help with updating it to work with the Radxa products.

Hi, I'm trying to download the image to add to my sd card, but all the images I tried downloading, either through direct link or torrent, give me this error: Internal error - code should not reach this point I couldn't find any information about this anywhere, and it is happening with all the images and versions. Can someone please help me download them? Thanks!

Raised up a PR with a patch. 🤞

at the first launch, I ran into the problem that the board cannot connect to the lan Internet via cable, it writes permanent connection and disconnection in the admin console. therefore, I cannot find out the ip address and understand what to connect to. Please help me if someone knows or has solved this problem.

I think i've managed to work around this, and set HS200 mode. I did this by decompiling /boot/dtb/rockchip/rk3588-nanopc-t6.dtb, modifying the mmc@fe2e0000 section to remove the mmc-hs400-1_8v; and mmc-hs400-enhanced-strobe; lines, adding a new mmc-hs200-1_8v; line and then recompiling it again. dtc -I dtb -O dts -f /boot/dtb/rockchip/rk3588-nanopc-t6.dtb -o rk3588-nanopc-t6.dts # Modify rk3588-nanopc-t6.dts here dtc -I dts -O dtb rk3588-nanopc-t6.dts -o /boot/dtb/rockchip/rk3588-nanopc-t6.dtb After rebooting, I confirmed that it was now running in HS200 mode: [ +0.010753] mmc0: SDHCI controller on fe2e0000.mmc [fe2e0000.mmc] using ADMA [ +0.034734] mmc0: new HS200 MMC card at address 0001 [ +0.000571] mmcblk0: mmc0:0001 A3A444 230 GiB I ran a heavy random read/write test, and observed no errors. However, I think this will be lost during a future update - so i'll see if I can figure out how to submit a patch!

Correct. Many Radxa SBC’s work this way. RockPi-S, RockPi-S0, RockPi-E, E20c, e25c, e52c, rock-pi-zero, etc.

Is this your SD card? This is your eMMC just 3.6G in size. This is the first time I have met this variant. We need to think about whether it is possible to add an exception for this case.

df -h Filesystem Size Used Avail Use% Mounted on udev 159M 0 159M 0% /dev tmpfs 47M 4.8M 42M 11% /run /dev/mmcblk1p1 58G 3.4G 53G 7% / tmpfs 234M 76K 233M 1% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 234M 4.0K 234M 1% /tmp /dev/zram1 47M 2.4M 42M 6% /var/log /dev/mmcblk0p1 3.4G 2.0G 1.3G 62% /media/emmc tmpfs 47M 0 47M 0% /run/user/0 lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mmcblk1 179:0 0 59.6G 0 disk └─mmcblk1p1 179:1 0 59G 0 part /var/log.hdd / mmcblk0 179:32 0 3.6G 0 disk └─mmcblk0p1 179:33 0 3.5G 0 part /media/emmc zram0 252:0 0 233.1M 0 disk [SWAP] zram1 252:1 0 50M 0 disk /var/log zram2 252:2 0 0B 0 disk lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Armbian 25.8.1 bookworm Release: 12 Codename: bookworm uname -r 6.12.44-current-rockchip64 I don't have an easy way to do the serial terminal thing to check U-Boot. I have updated it to the "latest" using armbian-install, however...

Was the auditd disabled ? Without it is difficult to see where the sysrq comes from. Re. monitoring ttyS1: you could try use screen: sudo screen /dev/ttyS1 9600 Replace 9500 if needed with the baud rate configured in the UPS

Hi, that's me again after a recent very bad sysrq incident on my system (I was away for a couple of days and the system went down for this time). I count > 5000 "sysrq: HELP" messages this time, 77 requests for loglevel changes (to 0, 4 or 8), 9 "show regs" requests, 1 "show state" and 4 "dump ftrace buffer" request. All this during 30 mins. The UART / USB converter was connected to ttyS0, but the PC on the other end was off. But I shall add that I also have connected the status output line of my UPS to ttyS1 (this is an "UPSPACK_V3" board that watches the 5V input and has a Li polymer battery connected). Could it also be that this system sends spurious BREAK commands that issue a SysRq event? And if yes: Is there a simple way to watch this interface? Maybe by temporarily logging the UPS board's UART Tx? Greetings.