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. 

@cal5582 Seems like lots of NVME needs to disable ASPM. For my Samsung 9b1 NVME, I solved this with a kernel patch, see https://github.com/armbian/build/blob/main/patch/kernel/archive/spacemit-6.18/013-Disable-ASPM-L0-for-Samsung-PM9B1-NVME.patch HTH // Sven-Ola

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 ]

Missing rsync somehow?

 

[🔨]   /bin/sh: 1: rsync: not found

not sure how i missed that. thanks1

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.

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.