Rockchip

Hey guys, So I wanted to update the OS on my NAS to patch the Copy Fail vulnerability today. I installed everything, I also did an apt-upgrade (not a full one) to make sure my kernel was as up to date as I could get it, and I also updated the initramfs, too. Now when I boot up the Kobol, I can hear the disks spinning up after a few seconds upon powering up, they make an odd noise and then just stop. The LEDs on the front panel also no longer show blue anymore, and `fdisk -l` no longer shows anything. I know for a fact these HDDs are not dead. They have worked perfectly fine before the upgrade, and the SATA pins look perfectly clean. I e…

Hi, I am trying out Armbian 26.2.0-trunk.592 nightly (trixie) on a Radxa Rock PI 4b+ The community supported image boots fine and it is no problem to install Armbian on the on-board eMMC flash, but the installed NVMe SSD on PCIi is no recognised. It looks like the whole PCIe bus is not initialised properly during boot. in the kernel log I see: [ 0.062396] /pcie@f8000000: Fixed dependency cycle(s) with /pcie@f8000000/interrupt-controller [ 2.160749] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges: [ 2.160771] rockchip-pcie f8000000.pcie: MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000 [ 2.160779] rockchip-…

I get static noise on the analog audio out when no sound is playing (I use alsa). I tried to add a configuration file in /etc/modprobe.d which disables power saving (as this appears to be the usual reason for static noise), but this does not work. Does anyone know how to resolve this?

Are there no more update coming for the armsom-w3? I was planning to put the new ubuntu with KDE that showed up one month ago, and since a few days, it is not available anymore, there is only the trixie minimal. I was just wondering if it was normal or if the support was dropped for the armsom-w3 board.

I'm trying to enable UART6, UART7, and UART10 via overlays on a sige5 board. UART6 AND UART7 are working fine but I'm not seeing UART10 in the /dev directory. Could someone help me debug this?

Hi all, I want to try the new Armbian, but before I do, I need to get this Orange Pi 5 Max updated with whatever UEFI project is still maintained and supports it. The UEFI I have installed right now is a hacked relic from a now abandoned ARM distro that was given to me -- I assume surely this has been superceded by a more legitimate source? Thanks kindly for any updates, looking forward to rejoining the Armbian family soon as my UEFI is updated

I have a question. Why isnt all the rockchip information including forward mainline all in one space for all to see and collaborate/advance? That question is the right one to ask at the end of this particular week — because you've now personally visited every scattered fragment: English docs in one repo, Chinese docs in another, the mainline truth in Collabora's private notes file, the seek-handling wisdom buried in nyanmisaka's ffmpeg fork, the SoC-capability gotcha in a Jellyfin support thread, the 10-bit format law in a kernel patch, and the B-frame fix in nobody's space until Tuesday. Here's why it's like this — the honest anatomy: 1. Rockchip itself …

Board: Orange Pi 5 Pro (RK3588S) OS: Armbian, kernel 6.1.115-vendor-rk35xx Display: Generic 7" HDMI panel, 1024x600 native (SKU MPI7002, "7inch HDMI Display-C") Symptom HDMI0 (the HDMI 2.1 port, using the new hdptx combo PHY via dwhdmi-rockchip) reliably fails to link-train at this panel's native timing (1024x600@59.82Hz, pixel clock 50.25MHz): dwhdmi-rockchip fde80000.hdmi: use tmds mode rockchip-vop2: Update mode to 1024x600p60 ... dclk: 50250000 rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy pll locked! rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy lane can't ready! phy phy-fed60000.hdmiphy.7: phy poweron faile…

Per the title, I was able to extract an ftb file and convert it to dtb and dts file. I would like to use the community build framework and build Armbian for SV06 Ace. The initial plan was to base the new board/*csc files on other rk3308b boards; sakurapi and rock-s0 and then pull configuration values from the OEM dts file. I'm confused about the dts structure in Community builds and the proper locations for defconfig, dts and dtsi files. I've worked with the files in OpenWRT where they are rigidly structured - something that would be a monumental task for Armbian community builds. The OEM dts file does not use any includes/dtsi fi…

I flashed a home built nanpim4v2 image to two brand new Silicon Power 32GB sdcards and they wont boot whereas SanDisk 32GB boot OK can anyone explain why ?

Orange Pi 5 Ultra HDMI RX no video when connecting Walksnail VTX Ascent. When I connect Walksnail Ascent VRX, the picture is fine, but when I connect VTX Ascent to VRX, the system doesn't see the HDMI RX. Specifically, it sees the source but can't lock it. The settings are set to 1080p60. I've tried different kernel and OS builds, but the result remains the same. What are the ways to solve this problem at the software level, since I specifically chose the Orange Pi 5 Ultra because of its built-in HDMI IN. [ 41.859256] fdee0000.hdmirx-controller: Vertical Sync threshold reached interrupt 0x2 [ 42.371741] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_delayed…

Hi everyone, I'm looking for help troubleshooting a boot issue with my Orange Pi 5 Pro (RK3588S). The board previously booted successfully with multiple operating systems, including: Armbian Ubuntu by Joshua Riek Android 12 However, after leaving the board unused for several months, I tried using it again and found that it could no longer boot properly. Current symptoms I'm connecting to the board through its serial console at 1,500,000 baud using picocom. With Armbian Debian Trixie Minimal, using the current kernel (6.18.55), the boot process stops after: picocom v3.1 port is : /dev/ttyACM2 flowcontrol…

If anyone is still interested, I have a Helios 64 that I assembled, looked at, but never got around to using for more than a couple hours. Works fine, does not yet have the 2.5GB fix but I have the instructions for same. No idea what to ask for it but it certainly isn't doing me any good sitting on my shelf. Have the manual, SATA drive bay adapters for 2.5" drives and the like. Make me an offer and pay shipping from Oregon. Let's talk!

Hi there!!! LTNS. Not pretending to ask for a solution. Just curious, what am I doing wrong, after a decade with Armbian. ;) A new Chinese board with RK3567, quite similar to kickPi. Boots up to "INFO: BL31: Initializing BL32" then hangs. Changing DTB in armbianEnv.txt does nothing, same is for verbosity. I guess there's some pre-DTB in uboot, as I recall, this is common with RK chips. And it seems to not match my hardware. Any reasonable way to fix, before i rebuild the whole image? Thanks in advance!

Hello, I'm running Armbian Community 26.8.0 / kernel 6.18.35-current-rockchip64 CPU is quite hot, 56-60 C even when idling; it used to be around 43-45 C on the BSP image. I have a passive cooler mounted. So I added a fan and connected to the FAN header, but it does not spin. I seem to remember a "fan control" overlay within armbian-config for other boards, but it's not present here. Any suggestion? It's a nice board but it's too hot with Armbian 😕 Thanks!

my rock64 sometimes hangs with unknow reason. Enabling/testing watchdog did not help. Does hardware watchdog is working at all ? some outputs: # dmesg | grep -i watchd [ 0.838922] dw_wdt ff1a0000.watchdog: No valid TOPs array specified [ 0.928770] rk_gmac-dwmac ff540000.ethernet: Enable RX Mitigation via HW Watchdog Timer [ 3.920201] systemd[1]: Using hardware watchdog 'Synopsys DesignWare Watchdog', version 0, device /dev/watchdog0 [ 3.921218] systemd[1]: Watchdog running with a hardware timeout of 28s. # wdctl Device: /dev/watchdog0 Identity: Synopsys DesignWare Watchdog [version 0] Timeout: 28 seconds Timeleft: 18 seconds Pre…

The same problem on the Pi 5 Ultra, has anyone managed to solve this problem? Or is this a global bug for all Orange devices?

) my Setup is : **Board**: Helios64 (RK3399) - **Kernel**: `6.18.44-current-rockchip64` - **Armbian**: 26.8.3 (upgraded from 25.11.2 via apt) - **Boot**: currently booting from SD card (rootfs on mmcblk0); b) symptoms : After upgrading to 26.8.3, my drives are no longer detected — but only on a "warm reboot": - ASM1061 PCIe-SATA controller (bays 1-2) completely missing from `lspci` - JMS561 USB-SATA bridges (bays 3-5) missing from `lsusb` - Other USB devices (VIA hubs, Realtek USB NIC) enumerate fine - No `sdX` block devices at all in `lsblk` The only fix is a "cold boot": `poweroff`, unplug the power cable, wait 1-2 minutes, power back …

I want to share a solution to a problem that I had: Problem: The problem was that no HDDs nor JMB585 were being detected. If I run the `lspci -nn`, it would show no devices: # lspci -nn And there were some `PCIe link training gen1 timeout` in the kernel messages. root@helios64:/home/amreo# dmesg | grep -Ei 'sata|ahci|scsi|ata|sas|sd[a-z]|helios' [ 0.000000] Machine model: Kobol Helios64 [ 0.000000] NODE_DATA(0) allocated [mem 0xf77c6800-0xf77c8fbf] [ 0.000000] printk: log buffer data + meta data: 262144 + 917504 = 1179648 bytes [ 0.016416] CPU features: detected: ARM errata 1165522, 1319367, or 1530923 [ 0.022065] Memory: 3778312K/4061184…

I have an AD-Z33 V1.2 which has the same rockchip as the xt-q8l-v10 but I cannot get it to start in Maskrom mode for eemc/bootloader flashing. Can anyone shed some light on how I can do this?

Filed this as armbian/build#10551 and was (reasonably) pointed here instead, since it's a kernel-code observation rather than a build-framework bug. Posting for the record — this is a question about the code, not a bug report. Where: drivers/gpu/drm/rockchip/rockchip_drm_vop2.c — identical across Rockchip BSP 6.1, ubuntu-rockchip, and Armbian rk35xx-vendor-6.1 (carried unpatched). rk3568_vop2_cfg_done() waits for the layer-select latch to take effect when it changes: old_layer_sel_val = vop2_readl(vop2, layer_sel_offset); cfg_layer_sel_val = vop2->regsbak[layer_sel_offset >> 2]; ... vop2_writel(vop2, 0, val); /* Make sure the layer sel is take…

Hi all, I've been running the official Orange Pi 1.0.2 Jammy image (grabbed from their drive) since 2023, and I just realized I'm stuck on a 5.10.110 kernel with no real update path. Joshua-Riek/ubuntu-rockchip looked like a great alternative, but it's archived now, so Armbian is my default plan. I've browsed a bunch of threads here about eMMC installs on the 5B being finicky, so before I dive in I'd rather ask around first. Questions: Which Armbian image/branch/version do you run day to day on a 5B, and would you recommend it for a server? Is there a complete, up-to-date install guide for eMMC on the 5B specifically? Do I need t…

Hello, ARMBIAN Ubuntu image looks not driving drive FAN_CTL_H pin ( GPIO3_D1) that control GND of fan connector, even if lm-senors report FAN PWM to with changin PWM value PWM9_M2 ( GPIO3_D1) alternate function is not visible into kernel overlays. Any hints ? Regards

I know this is going into the wrong section of the Rockchip forum but I don't see a parent category for anything like "Rockchip - Other". I can outline the issue in this thread, but I would rather have this post get moderated and get directed into the right spot to ask about specifically the Turing RK-1 or more generally "weird boards that have RK3588s that aren't already listed".

Has anyone been able to get both of the HDMI output to work with newer kernels than 6.1.115? I have my TV connected to the second output and it works with the vendor kernel but not with 6.18.x. There's no output at all.

(Don't know if this is the right place for this, but the Github-Issue link lead me to here, so... here it goes) Like the title states, the checksum of the downloaded Armbian 26.8.0 minimal image for the NanoPi NEO3 and the expected checksum for said image differ. I don't know if this is by accident, but I thought I'd report it before this goes unnoticed. I've tried downloading the image from the Armbian NEO3 page (https://armbian.com/boards/nanopineo3) as well as through the Armbian installer, both resulting in an image with a non-matching checksum (imager log: https://paste.armbian.com/mabojoqoja). - the SHA256-checksum of the image accordin…

Please tell me how to build the current bootloader for Rock Pi 4A for booting from SPI?

Hi, after doing an "apt upgrade" on my Luckfox Lyra Zero W running "Armbian 26.11.0 Minimal (Trixie)" on kernel 6.1.115-vendor-rockchip, I got an error mid-upgrade: The aic8800-usb driver did not recompile for the new kernel version: Setting up linux-image-vendor-rockchip (26.11.0-trunk.37) ... Armbian 'linux-image-vendor-rockchip' for '6.1.172-vendor-rockchip': 'postinst' starting. The kernel is built without module signing facility, modules won't be signed Autoinstall of module aic8800-usb/5.0+git20260123.5f7be68d-8 for kernel 6.1.172-vendor-rockchip (armv7l) Building module(s)....................(bad exit status: 2) Failed command: make -j3 KERNELRELEASE=6.1…

Just got an ODroid M1S (8GB), tried current community build, and found it wasn't working (Armbian_community_26.11.0-trunk.120_Odroidm1s_resolute_current_6.18.60_minimal.img.xz). So, a thread while I'm debugging if anyone's interested. Lets see how far I get. boot_fail.txt

Hi everyone, I have physical access to an Orange Pi 5 Ultra with 16 GB RAM and would like to help with testing and maintenance of this board. Here is my first round of hardware testing on the current/mainline image. I am posting the working features, reproducible problems and remaining gaps separately. This is an initial test report, not a release sign-off. Image and test environmentBoard: Orange Pi 5 Ultra, RK3588, 16 GB RAM. Image: Armbian community 26.11.0-trunk.120, Ubuntu 26.04 Resolute, GNOME/Wayland, booted from microSD. Kernel: 6.18.60-current-rockchip64. Image build commit: c24ea08f8759a37aaa83a101774582c37c18eda6. Kernel, DTB and BSP packages: 26.11.0-trunk.120.…

Board: HINLINK H68K (community-maintained) Image: Armbian_community_26.11.0-trunk.108_Hinlink-h68k_trixie_current_6.18.57_minimal (kernel 6.18.57-current-rockchip64) What happened? 1. The port labelled eth0 never works. At boot its link LED blinks once and stays dark. mii-tool end1 reports "No MII transceiver present!" and bringing it up logs "Failed to reset the dma". I observed the problem on two separate H68K units. Once that was resolved, I further noticed that... 2. With a good cable, eth0 and eth1 link at 1000 Mbit/s but can't receive. Received frames land in mmc_rx_crc_error (on eth1, all of them), so DHCP never completes. With a cable that negotiates 100 Mbit/…