Fabricio Martínez Tamayo

I always use minimal CLI and deploy k3s. Might be the request amounts are too many or who knows. But the service hangs and stops working. Just my 2 cents.

Hi, No sure if this is the place to post this but here it goes. I use the Debian distro for my armbian deployments. Every time I deploy, and the system comes with systemd-resolved it gives me problems. I always have to remove it and use the /etc/resolv.conf file by it self. I would suggest removing this, it's not necessary or useful. -Cheers

Well don't know exactly how the board got bricked, but I would guess the armbian-config did not flash the SPI right and somehow my SD card got screwed too. armbian-install did it right. I was able to get it back by using the rkdeveloptool tool from my mac mini. For whoever runs into this problem this is what I had to do: Get a usb-c cable connected to the "DP Display Port" and connect to another machine to troubleshoot, disconnect the power source before you do this. Before you connect the cable, press the Maskrom button. This should allow you to access the SPI from your troubleshooting machine. I played around with the windows tool RKDevTool with no luck. I ended up compiling rkdeveloptool in my mac mini m4 and this one did work. Anywho, once you have the board hooked up and in Maskrom mode, you need to get your hands on the SPI Loader *.bin. It's somewhere in the resources page of radxa. The one I used is rk3588_spl_loader_v1.15.113.bin. After this you flash the board with the following commands: The following command should show you the board info and confirm it's connected in Maskrom mode. ./rkdeveloptool ld ./rkdeveloptool db rk3588_spl_loader_v1.15.113.bin ./rkdeveloptool ef ./rkdeveloptool rd This allowed me to boot again from SD, even though I had to reflash the SD because somehow it also went bad. Not sure if it was because of all the testing or armbian-config screwed it up. After all this, I was booting again, and I did an armbian-install to move again the content of the SD to the nvme. I again, did an install/update MTD flash and boot from MTD first and this time around it all worked. I'm able to boot from SD first and if not SD is present it boots from NVME.

Downloaded Debian 13 (Trixie)Minimal / IOT kernel 6.18 onto SD and had it working 24/7 for about 2-3 days with no problems. I selected the option to copy the content of the SD card to an NVME, updated the MTD flash and set it as first boot option and now the device wont boot from nvme, SD or USB. How can I recover the unit?

Hi, I have downloaded and tested the 6.12 kernel Minimal/IOT images and they are not booting. I downloaded trixie 6.1, booted, then manually installed latest 6.12 with armbian-config and the reboot failed. I re-flashed sd card with 6.1, installed edge 6.16.4 (latest) with armbian-config and it booted fine.

Hi, I can confirm I got a booting SD card with the suggested command. I ended up using the following: ./compile.sh BOARD=orangepi5pro BUILD_DESKTOP=no BRANCH=edge RELEASE=bookworm KERNEL_CONFIGURE=no BUILD_MINIMAL=yes SHARE_LOG=yes Thank you very much @laibsch. Cheers! P.S. I ended up buying a USB-UART adapter as you suggested in another thread to test another orange pi 5 board I have but it seems that one is dead.

Hi everyone, Sorry to bother you with what may be a basic question. I’m not very experienced with the Armbian build system, and it’s been a while since I last built and deployed my own kernels. I’ve been trying to compile both the current and edge branches without success. I did get vendor working. I came across this post but I’m still unclear on the exact steps. Could someone please give me a simplified explanation of: What needs to be done to successfully compile these branches? Where I can get the latest patches, and how to apply them? Whether I also need to rebuild U-Boot with the Armbian build system. Thanks a lot in advance for your help!

Hi, I have attempted to boot with edge and current branches with no success. I am now trying vendor since its what its running. My process is: ./compile.sh BOARD=orangepi5pro BRANCH=current kernel-config I enable tunneling GRE and some broadcom wifi drivers. ./compile.sh BOARD=orangepi5pro BRANCH=current kernel sudo dpkg -i output/debs/linux-image-*.deb sudo dpkg -i output/debs/linux-headers-*.deb sudo dpkg -i output/debs/linux-dtb-*.deb sudo reboot and after this the system does not boot or post through HDMI. I have to go back and erase /boot and restore a backup to be able to get it working again. What am I missing? P.S. I have /boot partition in SD card and the system partition is in an NVME drive.

I've tried installing k3s on my OP5Pro and it did not work out because I was missing a couple of things on the kernel. I read the docs on building a new kernel. Did that and was able to get a working 6.1.75 kernel. Even though i got some errors when installing the generated packages. What I did not find in the documents is how I can work on a new kernel. Say 6.11. Has anyone done this? Can you help me out? Thanks! P.D. On a side note. I built this kernel in the OP it self and it was kinda slow. What image can I load in vmware under a macbook air m3 to compile and build faster?

using the armbian-install configuration did not work well for me. I figured out that I had to dd an image to my nvme device then edit the orangepiEnv.txt file in the mmc (actual boot device) and add the UUID for the nvme partition under rootdev= Also, after this is done and you are booting, you need to edit your /etc/fstab to load the mmc boot partition. /dev/mmcblk1p1 /boot vfat defaults 0 2 That why if you want to install a new kernel, it installs it in the right place.

Where can i find this setting?

Hi, Just received this unit yesterday with my surprise and lack of reading, the unit does not include eMMC or SPI so I am unable to boot directly into nvme drive. Are there instructions somewhere on how to setup the device to boot from MicroSD but use nvme as main drive? Thank you.

Have an incident where I tried installing a newer kernel in an nvme working setup and the device wont post. My original installation flash card is working but is giving me problems. So I got 2 others and attempted to boot new version of the image and Im getting no post. I was able to solve my original problem by installing a legacy version in flash and copying /boot over to nvme. I also attempted rebuilding the mme partitions with no success. But it seems that there is something not working right with kernel 6.7.