CNCJIM

I was considering rebuilding the initrd image for orange pi 5 as I think there was an issue in what was put on the image file. But now I have an a system settup with 6.1.115 - I should be good.

Thanks for the background information. I installed the orange pi 5 - 6.1.115 release with XFCE desktop. I edited the armbianEnv.txt to set up the pointer to the orange pi pro dtb entry. and booted it up just fine. With this, most things work well, To run the OS on the nvme M.2 drive, you cannot boot up from the nvme m.2 drive. Through some mistake that was made by the designers, you must always boot from an SD card for the initramfs to work enough to find the nvme m.2 drive. I made a copy - of the SD card to a second SD card on a separate system. Used this SD card to restart the Orange Pi 5 pro. Then changed the UUID of the /dev/nvme0n1p1 partition. (tune2fs -U) updated the armbianEnv.txt file on the boot SD card and the nvme0n1p1 drive. and rebooted - Now root is mounted to /dev/nvme0n1p1 partition. I have to leave the SD card in the slot to boot the system. but I am running off the NVME drive - Gen3 x 4 which should run at roughly 800-1000 MB/s on average according to Tom's hardware. That is probably 10x most SD cards transfer rate. Bottom line - I have a working Orange Pi 5 pro running on an NVMe M.2 drive - with the ability to get 10x throughput over using an SD card and up to 8TB of storage . Now it wasn't simple to actually set it up. It took some research and a learning curve. So I am not too happy about the lack of upfront information about getting this to work. But it is working. I had tried too build a real time kernel for this system. I did rebuild a kernel, but when I set the RT config up - I didn't have list of configuration question answers ready - Needed more information. The general idea was to get a fast multicore system with huge storage capacity and use this to run robotic systems. I am missing the real time kernel, I will run some latency tests to check the worst case jitter and look for a config setup. I see that there is now a Raspberry Pi 4 and Raspberry P5 real time kernel on a debian 12 release. I will see if I can get any build information for the real time kernel build. Thanks for the feedback. I will start looking for a different sbc model - among the platinum supported group.

I am downloading three different builds from 6.12 for orange pi 5. I have an orange pi 5 pro but since there is not dtb entry in 6.12 for that sbc in the Armbian 25.8.1 6.12.28 dtb file I used the orange pi 5b.dtb entry which works with the Armbian 25.8.1 6.1.115 images. The result is that the initramfs cant find a root disk - and when checking for drives in initramfs - there are none ls /dev/disks/by-uuid. So the initramfs file isn't running correctly as its not finding drives. I went back and loaded Armbian_24.8.1_Rock-5c-trixid_current_6.12.42_minimal.image and that boots up to root login. However if I change the card type to orangepi-5b. I cannot boot - in exactly the same manner - no drives found by initramfs. I have decided to go back to Armbian_25.8.1_Orangepi5-trixie_vendor_6.1.115_xfce_desktop.img - flash that and change the armbianEnv.txt to use the orangepi-5-pro setting. At 6.1.115, the image dtb/rockchip directory still has an entry for the orangepi-5-pro. - the new one doesn't. I am curious if I am just out of luck getting updates for orange pi 5 pro? will orange pi 5b be supported in the future? I have working images for debian 13 - and 6.1.115 versions, so my orange pi 5 is useable as is. I bought this sbc as I could get a useable NVME M.2 drive. I see that all new Orange pi sbc's are using the RK3588 chipset not the RK3588s variant. Opinions - there are new Orange Pi 5 variants - Ultra, Max, Plus etc. I dont need tons of HDMI, I want an NVME M.2 slot or two to run the OS on fast drives. -Or should I abandon Orange Pi and look elsewhere.

CONFIG_PREEMPT_RT=y. I was hoping to use the OrangePi5 Pro - with Linuxcnc - for machine controls - This would require predictable response times for precision cutting routines. The kernel build settings in the current release do not include the Setting for PREEMPTIVE_RT. Debian for X86 defaults to having it setup to support a Fully Preemptive mode. I am wondering why this hasn't trickled down to SBC builds. Byte2bot sells a shield card for converting the Pi 20 pin header to a Parallel port for connecting to CNC motion control cards - roughly $50 without having any manual wiring. Really slick - but at the moment - its would be good for Raspberry pi 4 and 5 as they have the Realtime kernel build available. I have a Tower PC with PCIe parallel on debian bookwork setup for machine control for a milling machine. So the Orange_Pi_5 is a much better solution . Please let me know how if I am on the correct track. I will copy the config file to the .config file in the kernel build directory -- This should be found in the /boot directory or the /proc directory - and add in the PREEMPT commands for fully PREEMTIVE that I found listed in the Kconfig file. Then I have to figure out where to place the orangepi5pro.csc file you pointed me to. At that point I should try to find some reference material about the Preemption settings the make process is going to ask me about. make should complete, and then "make module_install" - Then "make modules" At that point - the build is done. I will have to sort out how the /boot files need to be modified. Sorry for all the questions - If there is some reference material - that is clear about the Image Uinitram the Armbian Environment - and other boot related topics please point them out.

Werner - thanks - I did check the community and only found builds for 6.1 -- I did a build and had added three lines in the .conf file CONFIG_ PREEMPTICE_RT=y CONFIG_PREEMPTION=y and CONFIG_PREEMPT=y as I recall. did the "make" "make modules_install" and then the "make module" and there were a string of questions - during the make about some of the pre-emption options, which I was unprepared to answer. Not worried about those. I was concerned that the modules_install and the module make commands were installing the necessary routines. I do not understand how the orangepi5pro.csc file gets incorporated into the build process. I was on an Orangepi os to run the krtnrl build. Now moving back to Armbian 6.1.115. I am downloading a Armbian community supported 6.1.115 download for orange pi pro. I will then download the rockchip-rk3588.conf file - and the orangepi5pro.csc file - not sure where the board config file goes and how it ties into the kernel build process - might need a pointer for that Jim

I have questions about 1 building a full image that supports the Orange Pi 5 Pro. From my understanding of building the kernel - the supported modules for the chipset need to be built for the specific SBC card. I can easily access the correct kernel I would like. What I am lacking is an understanding of what source images to install on my build platform for the modules and what the the configuration settings specific to the SBC. Can someone clue me in? I haven't built a kernel in 20 years. I can try to make a case for Armbian to support the OPI 5 Pro or Max. But this isn't the right forum for that, I prefer the Pro or Max over the Plus as I do not need all those HDMI ports. My goal is to build two kernels - one on SMB Pre-emptive and one RT PREEMPTIVE - specifically for the Orange Pi 5 PRO and two images with all the I/O functional. Evidently the Armbian official builds are for the Orange Pi 5B and the Plus. I haven't exhaustively gone through all of the community supported offerings.

I have an Orange Pi 5 pro - with a 256GB M.2 SSD drive - I have kernel 6.115 running . Booting from SD - root is mounted on nvme0n1p1 (the SSD). Armbian 25.8.0-trunk53.-bookworm. I have three issues with this - 1:- no audio out of the 3.5 inch jack. 2: No internal Bluetooth 3. Have to use the SD card for initial boot. PCI is working on that version. I would like to use the RT-Pre-emptive kernel. It doesn't seem to be available. And the 6.1.2 kernel images do not find the SSD drive at all on orange pi 5 pro.