Search the Community

Please, I need an img of Armbian compatible with the following: RK3399T and with HDMI. I have tried all versions of Armbian and they do not work. Some do, but the problem is that it does not display an image. I believe it could be the HDMI. The most preferable versions for me are Armbian Noble or Bookworm. The problem also occurs during updates. After updating, the wireless does not work. If there is a version with this fixed, I would be grateful if someone could post a version for me, as up-to-date as possible. My Radxa is a Rock Pi 4Plus v1.73. With a 256GB microSD, I need an img of Armbian that is compatible with wireless and HDMI. If anyone can send me the link, I would be grateful!

Hello I want to disable console on /dev/ttyS2 on a Radxa ROCK 4C+ running rock@rockpi-4cplus:/boot$ cat /etc/os-release | grep -v URL PRETTY_NAME="Armbian 25.5.0-trunk.40 noble" NAME="Ubuntu" VERSION_ID="24.04" VERSION="24.04 LTS (Noble Numbat)" VERSION_CODENAME=noble ID=ubuntu ID_LIKE=debian UBUNTU_CODENAME=noble LOGO="armbian-logo" ARMBIAN_PRETTY_NAME="Armbian 25.5.0-trunk.40 noble" There are posts and other information out there. For instance: https://docs.armbian.com/User-Guide_Fine-Tuning/#how-to-toggle-boot-output which leads to http://redsymbol.net/linux-kernel-boot-parameters/ rock@rockpi-4cplus:/boot$ grep console armbianEnv.txt console=both The information found so far, implies there are options like: none, serial, both, and another But what is the another option? So that I can disable console on /dev/ttyS2 and use that for other purposes. Without compromising the Docs reccomandation: To disable console entirely (not recommended) set console to none

Hello everyone, I’m trying also to connect the RTC ds1307 in RockPi4C+, but it isn’t detecting by I2C. Informations: RTC ds1307 used: https://www.seeedstudio.com/Pi-RTC-DS1307.html Armbian OS version: 25.2 Kernel version: 6.12.10-current-rockchip64 i2c-7 enabled on armbian-config (> System > Kernel > SY210 > rockchip-rk3399-i2c7) When I run the command: sudo i2cdetect -y 7 shows the error Error: Could not open file /dev/i2c-7' or /dev/i2c/7’: No such file or directory When I run the command: sudo i2cdetect -l shows: i2c-0 i2c rk3x-i2c I2C adapter i2c-3 i2c rk3x-i2c I2C adapter Is someone can help to solve this problem? Thanks

I have a RockPi 4c plus v1.41 with the Armbian Community version Armbian_community_24.11.0-trunk.202_Rockpi-4cplus_bookworm_current_6.6.53_minimal. Everything is okay, till i attach a dougther board (https://z-wave.me/products/razberry-old/) to the Rockpi. Normaly it boots fine from SDcard, but after attaching the that dougther board it won't boot anymore. It seems to stuck in uboot. I have done some boot logs, but everything before line 110 is identical WithDB.txt WithoutDB.txt

I have encountered an issue on my Rock Pi 4C+ where a USB 3.0 drive plugged into the lower USB 3.0 port is recognized as USB 2.0 speed if inserted before boot. However, if I hot-plug the drive after boot, it switches to USB 3.0 speed as expected. Tested Images: Community Images: Armbian_community_24.11.0-trunk.202_Rockpi-4cplus_noble_current_6.6.53_gnome-kisak_desktop.img.xz Armbian_community_24.11.0-trunk.167_Rockpi-4cplus_noble_current_6.6.52_gnome-kisak_desktop.img Official Image (No Issue): Armbian_23.11.1_Rockpi-4cplus_bookworm_current_6.1.63.img Has anyone else experienced this, or found a workaround for the community versions? Thank you! dmesg [ 2.819924] usb 1-1: new high-speed USB device number 2 using xhci-hcd [ 72.804089] usb 2-1: new SuperSpeed USB device number 2 using xhci-hcd root@rockpi:~# dmesg | grep -i usb [ 0.000000] Kernel command line: root=UUID=8015785f-e8cd-4061-9e51-bab0f82d6f6b rootwait rootfstype=ext4 splash plymouth.ignore-serial-consoles console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart=dfeec6ee-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory [ 0.708079] usbcore: registered new interface driver usbfs [ 0.708124] usbcore: registered new interface driver hub [ 0.708168] usbcore: registered new device driver usb [ 0.850637] usbcore: registered new interface driver usb-storage [ 0.919948] usbcore: registered new interface driver usbhid [ 0.919957] usbhid: USB HID core driver [ 2.558303] xhci-hcd xhci-hcd.9.auto: new USB bus registered, assigned bus number 1 [ 2.558846] xhci-hcd xhci-hcd.9.auto: new USB bus registered, assigned bus number 2 [ 2.558868] xhci-hcd xhci-hcd.9.auto: Host supports USB 3.0 SuperSpeed [ 2.559390] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06 [ 2.559413] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.559429] usb usb1: Product: xHCI Host Controller [ 2.559443] usb usb1: Manufacturer: Linux 6.6.52-current-rockchip64 xhci-hcd [ 2.559456] usb usb1: SerialNumber: xhci-hcd.9.auto [ 2.560867] hub 1-0:1.0: USB hub found [ 2.561911] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. [ 2.562226] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.06 [ 2.562248] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.562264] usb usb2: Product: xHCI Host Controller [ 2.562278] usb usb2: Manufacturer: Linux 6.6.52-current-rockchip64 xhci-hcd [ 2.562291] usb usb2: SerialNumber: xhci-hcd.9.auto [ 2.563037] hub 2-0:1.0: USB hub found [ 2.567689] ehci-platform fe380000.usb: EHCI Host Controller [ 2.567745] ehci-platform fe380000.usb: new USB bus registered, assigned bus number 3 [ 2.567851] ohci-platform fe3a0000.usb: Generic Platform OHCI controller [ 2.567894] ohci-platform fe3a0000.usb: new USB bus registered, assigned bus number 4 [ 2.567952] ehci-platform fe380000.usb: irq 86, io mem 0xfe380000 [ 2.568062] ohci-platform fe3a0000.usb: irq 88, io mem 0xfe3a0000 [ 2.568300] ehci-platform fe3c0000.usb: EHCI Host Controller [ 2.568338] ehci-platform fe3c0000.usb: new USB bus registered, assigned bus number 5 [ 2.568413] ohci-platform fe3e0000.usb: Generic Platform OHCI controller [ 2.568450] ohci-platform fe3e0000.usb: new USB bus registered, assigned bus number 6 [ 2.568482] ehci-platform fe3c0000.usb: irq 87, io mem 0xfe3c0000 [ 2.568572] ohci-platform fe3e0000.usb: irq 89, io mem 0xfe3e0000 [ 2.583871] ehci-platform fe380000.usb: USB 2.0 started, EHCI 1.00 [ 2.584328] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06 [ 2.584351] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.584364] usb usb3: Product: EHCI Host Controller [ 2.584376] usb usb3: Manufacturer: Linux 6.6.52-current-rockchip64 ehci_hcd [ 2.584385] usb usb3: SerialNumber: fe380000.usb [ 2.585353] hub 3-0:1.0: USB hub found [ 2.599915] ehci-platform fe3c0000.usb: USB 2.0 started, EHCI 1.00 [ 2.600995] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06 [ 2.601019] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.601036] usb usb5: Product: EHCI Host Controller [ 2.601050] usb usb5: Manufacturer: Linux 6.6.52-current-rockchip64 ehci_hcd [ 2.601063] usb usb5: SerialNumber: fe3c0000.usb [ 2.602091] hub 5-0:1.0: USB hub found [ 2.632922] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.06 [ 2.632962] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.632978] usb usb4: Product: Generic Platform OHCI controller [ 2.632992] usb usb4: Manufacturer: Linux 6.6.52-current-rockchip64 ohci_hcd [ 2.633006] usb usb4: SerialNumber: fe3a0000.usb [ 2.634138] hub 4-0:1.0: USB hub found [ 2.635277] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.06 [ 2.635301] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.635314] usb usb6: Product: Generic Platform OHCI controller [ 2.635325] usb usb6: Manufacturer: Linux 6.6.52-current-rockchip64 ohci_hcd [ 2.635335] usb usb6: SerialNumber: fe3e0000.usb [ 2.636362] hub 6-0:1.0: USB hub found [ 2.819924] usb 1-1: new high-speed USB device number 2 using xhci-hcd [ 2.971325] usb 1-1: New USB device found, idVendor=21c4, idProduct=0cd1, bcdDevice= 2.00 [ 2.971370] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2.971387] usb 1-1: Product: USB3.2 Gen1 [ 2.971400] usb 1-1: Manufacturer: JZAO [ 2.971412] usb 1-1: SerialNumber: 54163167782522DF [ 2.973188] usb-storage 1-1:1.0: USB Mass Storage device detected [ 2.974535] scsi host0: usb-storage 1-1:1.0 [ 3.034825] usbcore: registered new interface driver uas [ 4.001023] scsi 0:0:0:0: Direct-Access JZAO USB3.2 Gen1 3.00 PQ: 0 ANSI: 4 [ 7.802249] systemd[1]: Hostname set to <teslausb-ModelY>. [ 10.521682] systemd[1]: Reached target usb-gadget.target - Hardware activated USB gadget. [ 10.648372] systemd[1]: Found device dev-disk-by\x2dlabel-mutable.device - USB3.2_Gen1 mutable. [ 10.651731] usbcore: registered new interface driver brcmfmac [ 69.019098] usb 1-1: USB disconnect, device number 2 [ 72.804089] usb 2-1: new SuperSpeed USB device number 2 using xhci-hcd [ 72.825156] usb 2-1: LPM exit latency is zeroed, disabling LPM. [ 72.826001] usb 2-1: New USB device found, idVendor=21c4, idProduct=0cd1, bcdDevice= 2.00 [ 72.826036] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 72.826061] usb 2-1: Product: USB3.2 Gen1 [ 72.826080] usb 2-1: Manufacturer: JZAO [ 72.826099] usb 2-1: SerialNumber: 54163167782522DF [ 72.828074] usb-storage 2-1:1.0: USB Mass Storage device detected [ 72.834789] scsi host0: usb-storage 2-1:1.0 [ 73.858883] scsi 0:0:0:0: Direct-Access JZAO USB3.2 Gen1 3.00 PQ: 0 ANSI: 4

Hi all, new Rock Pi and as well new armbian user. After reading forum threads on the Rock Pi official forum, it seems possible to get the OS to run around 2W idle. I have installed cpufrequtils without getting any success, still sucks around 4W. Any help to tweak kernel or other activities to get Armbian to get into lower power mode would be appreciated. /Daniel

The mainline 5.11 patch "phy: rockchip: set pulldown for strobe line in dts" https://github.com/torvalds/linux/commit/8b5c2b45b8f0a11c9072da0f7baf9ee986d3151e (not backported to 5.10.y) seems to have broken most if not all rockchip board EMMC HS400 enhanced strobe support. This probably affects supported rockchip boards (at least rk3399 ones, but probably most). That is boards exhibit: [ 18.985162] mmc1: running CQE recovery [ 18.988056] ------------[ cut here ]------------ [ 18.988500] mmc1: cqhci: spurious TCN for tag 12 and the filesystem ends up corrupted on write attempt. Note that another bug about regulator core DEFERRED support (which might have produced the same issue hardware wise) was introduced in 5.10.43 (I had bisected it to https://github.com/torvalds/linux/commit/98e48cd9283dbac0e1445ee780889f10b3d1db6a "regulator: core: resolve supply for boot-on/always-on regulators"). But I was confident that it to be fixed in at least 6.1 by https://github.com/torvalds/linux/commit/8a866d527ac0441c0eb14a991fa11358b476b11d "regulator: core: Resolve supply name earlier to prevent double-init" (introduced in 6.1), still EMMC was still failing on me. Thanks to @RussianNeuroMancer telling me that not all rk339 boards had EMMC HS400es broken, I found that nanopc-t4 had https://github.com/torvalds/linux/commit/463be3cb357dab7d7e4d8dcc7c15c642e10c5bef arm64: dts: rockchip: add enable-strobe-pulldown to emmc phy on nanopi4 So the current way, from this nanopc-t4 commit, to fix EMMC HS400 on most rockchip is to add "rockchip,enable-strobe-pulldown;" to the "emmc_phy" node (at least this node alias for rk3399). &emmc_phy { + rockchip,enable-strobe-pulldown; status = "okay"; }; With this patch I can renable hs400es for rk3399 emmc on helios64 (it is already set for nanopc-t4 in mainline). Details in: I believe the https://github.com/torvalds/linux/commit/8b5c2b45b8f0a11c9072da0f7baf9ee986d3151e mainline commit was wrong in that it probably should have done the opposite (that is enable the pulldown) as most boards were hardwired so. As was done for rk3588 boards: "arm64: dts: rockchip: Fix eMMC Data Strobe PD on rk3588" https://github.com/torvalds/linux/commit/37f3d6108730713c411827ab4af764909f4dfc78 " JEDEC standard JESD84-B51 defines the eMMC Data Strobe line, which is currently used only in HS400 mode, as a device->host clock signal that "is used only in read operation. The Data Strobe is always High-Z (not driven by the device and pulled down by RDS) or Driven Low in write operation, except during CRC status response." RDS is a pull-down resistor specified in the 10K-100K ohm range. Thus per the standard, the Data Strobe is always pulled to ground (by the eMMC and/or RDS) during write operations. Evidently, the eMMC host controller in the RK3588 considers an active voltage on the eMMC-DS line during a write to be an error. The default (i.e. hardware reset, and Rockchip BSP) behavior for the RK3588 is to activate the eMMC-DS pin's builtin pull-down. As a result, many RK3588 board designers do not bother adding a dedicated RDS resistor, instead relying on the RK3588's internal bias. The current devicetree, however, disables this bias (`pcfg_pull_none`), breaking HS400-mode writes for boards without a dedicated RDS, but with an eMMC chip that chooses to High-Z (instead of drive-low) the eMMC-DS line. (The Turing RK1 is one such board.) Fix this by changing the bias in the (common) emmc_data_strobe case to reflect the expected hardware/BSP behavior. This is unlikely to cause regressions elsewhere: the pull-down is only relevant for High-Z eMMCs, and if this is redundant with a (dedicated) RDS resistor, the effective result is only a lower resistance to ground -- where the range of tolerance is quite high. If it does, it's better fixed in the specific devicetrees. Maybe one can confirm this is the case not only for rk5588 but for other rockchip boards? (about the default for hardware reset and rockchip BSP with regards to active that eMMC-DS pin's builtin pulldown if any, and board designers for other boards than rk5588 also not bothering to add a dedicated RDS resistor, instead relying on the rockchip internal bias, also if any on non rk5588) At least two other boards disabled hs400es in mainline probbaly due to this patch disabling the internal pulldown by default "phy: rockchip: set pulldown for strobe line in dts" https://github.com/torvalds/linux/commit/8b5c2b45b8f0a11c9072da0f7baf9ee986d3151e in 2023 in vanilla Linux: Rock 4C+ https://github.com/torvalds/linux/commit/2bd1d2dd808c60532283e9cf05110bf1bf2f9079 Rock Pi 4 https://github.com/torvalds/linux/commit/cee572756aa2cb46e959e9797ad4b730b78a050b

Hello everyone, I seem to have a problem with not knowing how to change the top usb3 port of my Rock pi 4+ to host mode from otg mode, I just got it and installed armbian on it and open media vault, only to notice that I couldn't connect anything to the top usb 3 port and have it show up in open media vault, the other ports work fine and looking at the internet seems to have found that the answer is that the port is in OTG mode and on the official website they do have a way to change it to host mode, but not in armbian and I'm not skilled enough in linux to find where the file I need to change is. I'm running this build "Armbian_v22.05.2_Rockpi-4cplus_bullseye_current_6.1.33.img.xz" downloaded from the armbian website. Thanks in advance for the help :)

I have been using a Rock Pi 4C Plus (v1.2) with M.2 slot with Armbian for some time. I boot from eMMC, but have a 500GB NVME device Cannot recall the original version of firmware installed, but it was originally a Debian bullseye image and I re-installed when a bookworm image became available. I regularly use "apt update" followed by "apt upgrade" to keep the software up to date. After a recent update the system went into a boot loop. I attempted to recover by creating an SD card with the latest Armbian image. When trying to debug the issue I noticed that the NVME in the M.2 slot is no longer recognized. Reverting to previously available 23.11 image and the NVME device is again available. I'll need to dig further to discover what exactly changed between 23.11 and 24.2, but this is definitely a regression for anyone with the earlier version of the 4C Plus using the M.2 slot. So, fair warning anyone using the M.2 slot on a RockPi 4C Plus should avoid updating!

The most resent build 24.5.0-trunk.93 does not have comedi drivers included. I tried to build them with the armbian build system, but it is exclude there. How I can change that so that I can include these drivers. I have a bunch of data aquisition system relying on this drivers that I ran with a rockpi 4c+ Any hint appreciate, Thomas

Hi, I want to use a mcp2515 can controller over spi1 or 2. I read about internal flash is blocking the spi1. Can I use another Chipselect pin to use the spi1 with GPIO? Can you please give some advice where to start my research about overlays? What else do I need to activate? (core moduls, driver…)

Hello, I tried to use the power button on my Rock 4 C+ running Armbian 23.02.2 Bullseye with Linux 5.15.93-rockchip64. It is able to power off. But I can't boot up the controller. When I use the debian based radxa image the button works like expected. I found this at the rk3399-rock-4c-plus.dts of the radxa kernel. &rockchip_suspend { status = "okay"; rockchip,sleep-debug-en = <1>; rockchip,sleep-mode-config = < (0 | RKPM_SLP_ARMPD | RKPM_SLP_PERILPPD | RKPM_SLP_DDR_RET | RKPM_SLP_PLLPD | RKPM_SLP_CENTER_PD ) >; rockchip,wakeup-config = < (0 | RKPM_GPIO_WKUP_EN | RKPM_PWM_WKUP_EN | RKPM_USB_WKUP_EN | RKPM_USB_LINESTATE_WKUP_EN ) >; rockchip,pwm-regulator-config = < (0 | PWM2_REGULATOR_EN ) >; rockchip,power-ctrl = <&gpio1 17 GPIO_ACTIVE_HIGH>, <&gpio1 14 GPIO_ACTIVE_HIGH>, <&gpio0 3 GPIO_ACTIVE_HIGH>; }; I would test the overlay with current armbian build, but I doesn't know where to place it. Maybe someone can help me here?