Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Orange Pi RV2

Featured Replies

Solved by sven-ola

Not sure why, but i had to add the pcie_aspm=off to my /boot/extlinux.conf to get the newest build to see my nvme drive, this has never happened on previous builds, and  the only options i turn on from the default config being fetched is enabling graphics drivers. very strange. 

took me a long time to figure out why, my nvme drive would show under lspci, and it would see the controller but id never get anything under lsblk. still not sure what changed but if anyone else runs into similar problem thats how i fixed it. 

so im not exactly sure why, but now i am getting an error building the most recent images in debian 13 under  virtualbox. 
 

[🔨]     INSTALL /home/vm/armbian/build/.tmp/work-7197f8ae-9b85-4959-9885-0c198551c928/kernel_dest_install_dir-wUSTJ/libc_headers/include
[🔨]   /bin/sh: 1: rsync: not found
[🔨]   make[2]: *** [Makefile:1416: headers_install] Error 127
[🔨]   make[1]: *** [/home/vm/armbian/build/cache/sources/linux-kernel-worktree/6.18__spacemit__riscv64/Makefile:380: __build_one_by_one] Error 2
[🔨]   make: *** [Makefile:248: __sub-make] Error 2
[🌱] Ccache result [ hit=0 miss=0 (0%) ]
[💥] Error 2 occurred in main shell [ at /home/vm/armbian/build/lib/functions/compilation/kernel.sh:264
                   kernel_build() --> lib/functions/compilation/kernel.sh:264                                                                                                                                     
                  do_with_hooks() --> lib/functions/general/extensions.sh:618                                                                                                                                     
                do_with_logging() --> lib/functions/logging/section-logging.sh:81                                                                                                                                 
   kernel_prepare_build_and_package() --> lib/functions/compilation/kernel.sh:166                                                                                                                                 
                 compile_kernel() --> lib/functions/compilation/kernel.sh:99                                                                                                                                      
   artifact_kernel_build_from_sources() --> lib/functions/artifacts/artifact-kernel.sh:310                                                                                                                        
    artifact_build_from_sources() --> lib/functions/artifacts/artifacts-obtain.sh:34                                                                                                                              
       obtain_complete_artifact() --> lib/functions/artifacts/artifacts-obtain.sh:280                                                                                                                             
       build_artifact_for_image() --> lib/functions/artifacts/artifacts-obtain.sh:394                                                                                                                             
    main_default_build_packages() --> lib/functions/main/build-packages.sh:97                                                                                                                                     
   full_build_packages_rootfs_and_image() --> lib/functions/main/default-build.sh:31                                                                                                                              
          do_with_default_build() --> lib/functions/main/default-build.sh:42                                                                                                                                      
         cli_standard_build_run() --> lib/functions/cli/cli-build.sh:25                                                                                                                                           
        armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:136                                                                                                                                          
                 cli_entrypoint() --> lib/functions/cli/entrypoint.sh:216                                                                                                                                         
                           main() --> compile.sh:50                                                                                                                                                               
 ]                                                                                                                                                                                                                
[💥] Cleaning up [ please wait for cleanups to finish ]
[✨] Repeat Build Options [ ./compile.sh build BOARD=orangepirv2 BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no INSTALL_HEADERS=yes KERNEL_CONFIGURE=yes KERNEL_GIT=Full RELEASE=trixie ]

Hello. Finally, I have built an image on my Orange Pi 5B for the Orange Pi RV2 and launched it from a TF card. Currently, I have two RV2 boards with 8 GB of RAM and plan to maximize these devices by contributing to Armbian specifically for this device. Well, so far I have only successfully launched the system, and it will take a few days to figure out its capabilities and errors. So far I can only work with TF cards, but after a while I will add m.2 drives. It is not very clear what about working with USB. I am interested not only in the successful work of the server build but also in the effective work of the graphical desktop environment. In a few days I will write about the test results.

IMG_20260905_053018_391.jpg

Hi. Following up on the previous post: I used the built image to compile HestiaCP and set up a web hosting server, successfully launching a PHP site. I also ran several Go applications, which proved stable without requiring any "quick-and-dirty" workarounds. My next step is to perform load testing on the web server—specifically, testing how it handles a significant number of connections and streams multimedia and data via WebSockets. I plan to deploy this same image on another board and attempt to install a graphical environment. I’m not moving very fast, but I’m glad the server is up and running stably; this allows me to start planning for its deployment in a production environment.

Hello! I would like to get Trixie with a desktop working on my board. I currently use "armbian-unofficial_26.02.0-*-6.18.18_gnome_desktop" and it actually works well. It worked better and had less stuttering before i upgraded and got "6.18.44-current-spacemit", but it's still usable for light browsing, "RDP"ing into my main machine with Remmina (currently doing that to write this comment!) and even gaming: "The Question" demo renpy game from repos works well and I'm curious how something bigger like "Everlasting Summer" is going to work on that board, but for that I need renpy 8.3.4 and noble is at 8.1.3, so that's why I want to get Trixie working: it has the exact version I need.
Should I try to compile the image with BUILD_DESKTOP set? Does the unofficial image contain some additional fixes for graphics drivers?

Edited by VBB

I have build Trixie with gnome desktop. Then ran the `spacemit-gpu-addon.sh` script and hw acceleration appears to be working. vkcube fails with this error:
```
Selected WSI platform: xcb
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
vkcube: ./cube/cube.c:4228: demo_select_physical_device: Assertion `demo->gpu_number >= 0' failed.
```
Then I tried to launch gnome system monitor with vulkan renderer (GSK_RENDERER=vulkan gnome-system-monitor) and, besides some bugs with icons, it does work, inspector show that vulkan gsk renderer is used.
I was able to successfully launch Everlasting Summer (copied it from stream from renpy8 branch) with the 7dl mod (must be ported to python3 and renpy8, luckily sources are available). Very much playable. I have used renpy from distro repos and removed splash screen pictures, because the game crashes after being unable to create a window for that splash screen. `RENPY_LESS_UPDATES=1` can be used too, but it also reduces animations in the game itself.
Wi-Fi doesn't work, but it's not a big deal for me, since I use Ethernet. Bluetooth works.
Boot time is veeery long. 3 mins for kernel.
```
systemd-analyze             
Startup finished in 3min 15.784s (kernel) + 31.495s (userspace) = 3min 47.280s 
graphical.target reached after 31.491s in userspace.
```

Hey. I've installed the image to my Orangepi RV2. I experience some weird delay on boot: i see a black screen (hdmi) for 3 minutes and then the mini pc shows the terminal and I can log in. I used another image (kernel 6.6), and such an issue didn't exist there. Can you help me solve this issue, pls?

On 11/6/2026 at 1:47 PM, c0rnelius said:

This PR should resolve the issue; https://github.com/armbian/build/pull/11035

Try updating the kernel.

The issue still exists. I tested using the last version (the image from Nov 3 + all the updates). Each time I power on Orangepi RV2, i have to wait ~3 mins. I also tested Armbian Debian image several months ago. I had the same issue. I decided to continue using Orangepirv2_1.0.0_debian_trixie_minimal_linux6.6.63-v3.img because of that issue. Recently, a critical velnerability was discovered in Linux kernel (in TCP). I can't use 6.6.63 anymore because of it.

I am not sure if I would experience the delay if I used an NVME SSD. I think booting from a fast MicroSD card should not be a problem. I don't know how I can troubleshoot this issue because it happens on an early stage, i.e. before Systemd starts services. I tried disconnecting all the USB devices and HDMI monitor. I does not help to fix the delay.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.