Search the Community

Hey there! I've just bought a used Orange Pi 5, according to the owner he never managed too boot up the first time, because he said it was bricked, for the price he offered for the device and accessories I thought I'd give it a go.. and yeah, I tried to install on different microSD cards, Armbian, OrangePi Os, Android 12 for Orange Pi, many tries but none of them booted or did anything after waiting even 15min. If I set the device into maskrom mode it enters the mode but it gives error to anything I try. I read on a post that using this firmware fixed someones board: https://dl.radxa.com/rock5/sw/images/loader/rock-5b/release/ I tried and I get the following: Download Boot Start, Download Boot Success, Wait for Maskrom Start and Success and then on Test Device Start, I get Test Device Fail , Note: Comunication issues, Certainly please check usb, Completed... If I go to the advanced function tab, Test Device fails, Get ChipInfo fails, ReadFlashInfo Fails too Flash ID... all of them,... IDK if I'm missing something or this one is really dead and there is nothing I can do. If someone has any idea of what could I try to do to get it working it would be nice! Thank you!

The latest version of RKNPU Driver is 0.9.8, 0.9.7 version doesn't works with rknn-llm or other projects.

Has anyone seen this? The claims there is a Vulkan driver now: https://github.com/Bleach665/Mali610Vulkan Can't confirm.

Hi all, Testing this OP5, got a standard M2 NVMe SSD (this works on my OP5Plus) I have formatted to exFAT with windows, inserted on the OP5, loaded ArmbianOS on MicroSD, it boots fine but I cant get it to show the nvme drive using fdisk -l or lsblk It seem like its not detecting the m2 nvme ssd at all.. little help please ?

Is anyone using the current Kodi Flatpak, Omega? I'm having issues viewing videos that have pixel format of yuv420p10le with the current apt repository Kodi Nexus. I thought to try Kodi Flatpak and it worked and I was able to view those yuv420p10le videos without issue. However, it was choppy and had high CPU usage...around 80% on many of the CPUs. I'm trying to figure that out. It's happening on all types of videos. All is played using software decoding. I've never gotten hardware decoding working. In the Kodi Nexus version I'm using it also software decoding but very low CPU usage. In any case, just want to see what experiences others are having.

All images have build dates 1 month back. Several images seem to be based on "vendor kernel". What is happening? G

Hi, after upgrading to Armbian 24.11.3 noble with 6.1 Kernel I have this problem that every time I turn off my TV that is connected to OPI with HDMI, then turning it back on again it will never have a HDMI signal. Same thing happens when I unplug the HDMI cable and plug it back in. I can reproduce it every single time - not just occasionally. It is not a hardware or cable problem, the exact same setup has worked flawlessly for long time with older Armbian and 5.1 kernel. I tried disabling all of the KDE power saving settings, also totally disabled kpowerdevil - with no change. SSH still works fine, the OS has not crashed. No new messages come to "dmesg" after tuning the TV off and on. Only thing that appear is in /var/log/syslog is when I turn the tv back ON again. Turning it off does not add any messages. 2025-02-06T13:21:23.984567+02:00 loovsys DiscoverNotifier[1979]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:21:23.984940+02:00 loovsys kded6[1877]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:21:23.985204+02:00 loovsys polkit-kde-authentication-agent-1[1929]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:21:23.985425+02:00 loovsys plasmashell[1897]: kde.plasmashell: requesting unexisting screen available rect -1 2025-02-06T13:21:23.985562+02:00 loovsys plasmashell[1897]: message repeated 3 times: [ kde.plasmashell: requesting unexisting screen available rect -1] 2025-02-06T13:21:23.986668+02:00 loovsys kalendarac[1985]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:21:23.986910+02:00 loovsys kactivitymanagerd[1904]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:21:23.987124+02:00 loovsys xdg-desktop-portal-kde[1930]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:21:23.991124+02:00 loovsys plasmashell[1897]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:21:23.991328+02:00 loovsys plasmashell[1897]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken. Or another time pretty similar 2025-02-06T13:26:53.652232+02:00 loovsys kactivitymanagerd[1880]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:26:53.653516+02:00 loovsys kalendarac[1964]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:26:53.654495+02:00 loovsys kded6[1852]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:26:53.655328+02:00 loovsys DiscoverNotifier[1957]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:26:53.656229+02:00 loovsys xdg-desktop-portal-kde[1905]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:26:53.657111+02:00 loovsys plasmashell[1868]: kde.plasmashell: requesting unexisting screen available rect -1 2025-02-06T13:26:53.657645+02:00 loovsys plasmashell[1868]: message repeated 3 times: [ kde.plasmashell: requesting unexisting screen available rect -1] 2025-02-06T13:26:53.658397+02:00 loovsys polkit-kde-authentication-agent-1[1904]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:26:53.665372+02:00 loovsys plasmashell[1868]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:26:53.665685+02:00 loovsys plasmashell[1868]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken. 2025-02-06T13:26:53.807759+02:00 loovsys plasmashell[1868]: message repeated 3 times: [ kf.plasma.quick: Exposed with no visual parent. Window positioning broken.] When plugging the HDMI cable back in: 2025-02-06T13:30:00.668173+02:00 loovsys kalendarac[1948]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:30:00.669049+02:00 loovsys DiscoverNotifier[1946]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:30:00.669745+02:00 loovsys kactivitymanagerd[1869]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:30:00.670412+02:00 loovsys kded6[1839]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:30:00.671016+02:00 loovsys xdg-desktop-portal-kde[1889]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:30:00.671596+02:00 loovsys polkit-kde-authentication-agent-1[1888]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:30:00.672173+02:00 loovsys plasmashell[1858]: kde.plasmashell: requesting unexisting screen available rect -1 2025-02-06T13:30:00.672548+02:00 loovsys plasmashell[1858]: message repeated 3 times: [ kde.plasmashell: requesting unexisting screen available rect -1] 2025-02-06T13:30:00.672946+02:00 loovsys plasmashell[1858]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:30:00.688381+02:00 loovsys plasmashell[1858]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken. 2025-02-06T13:30:00.705197+02:00 loovsys plasmashell[1858]: message repeated 2 times: [ kf.plasma.quick: Exposed with no visual parent. Window positioning broken.] 2025-02-06T13:30:01.892282+02:00 loovsys CRON[6339]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs) 2025-02-06T13:30:01.895234+02:00 loovsys CRON[6338]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi) 2025-02-06T13:30:02.361046+02:00 loovsys chronyd[1553]: Selected source 212.7.1.131 (0.ubuntu.pool.ntp.org) 2025-02-06T13:30:05.222767+02:00 loovsys plasmashell[1858]: The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. I also tried to switch between graphical and multi-user targets. (This works fine when the TV is never turned off - i can get the console and switch back to grapgical UI) systemctl isolate multi-user.target systemctl isolate graphical.target Issuing a reboot command will bring the display back. I do not have to power cycle the entire device to get the display back. I can also get back the display after I have lost signal by switching to the multi-user.target, unplugging and plugging back in the cable. After that i can also switch back to graphical.target and everything works. Only switching between graphical and multi-user afer losing the signal will not bring back the display. If I first switch to multi-user.target and then turn off the tv, then turning it back on the display works. I can also enable the graphical target again without problems. Then the following messages appear in syslog 2025-02-06T13:37:21.290588+02:00 loovsys kernel: rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_disable] Crtc atomic disable vp0 2025-02-06T13:37:24.167556+02:00 loovsys kernel: rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] Update mode to 3840x2160p60, type: 11(if:HDMI0, flag:0x0) for vp0 dclk: 594000000 2025-02-06T13:37:24.167664+02:00 loovsys kernel: rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx_ropll_cmn_config bus_width:5aa320 rate:5940000 2025-02-06T13:37:24.167680+02:00 loovsys kernel: rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy pll locked! 2025-02-06T13:37:24.167693+02:00 loovsys kernel: rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] dclk_out0 div: 0 dclk_core0 div: 2 2025-02-06T13:37:24.167706+02:00 loovsys kernel: rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] set dclk_vop0 to 594000000, get 594000000 2025-02-06T13:37:24.167719+02:00 loovsys kernel: dwhdmi-rockchip fde80000.hdmi: final tmdsclk = 594000000 2025-02-06T13:37:24.280906+02:00 loovsys kernel: dwhdmi-rockchip fde80000.hdmi: don't use dsc mode 2025-02-06T13:37:24.280986+02:00 loovsys kernel: dwhdmi-rockchip fde80000.hdmi: dw hdmi qp use tmds mode 2025-02-06T13:37:24.281000+02:00 loovsys kernel: rockchip-hdptx-phy-hdmi fed60000.hdmiphy: bus_width:0x5aa320,bit_rate:5940000 2025-02-06T13:37:24.281011+02:00 loovsys kernel: rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy lane locked! Also in the dmesg the following appears [ 293.342367] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_disable] Crtc atomic disable vp0 [ 296.325415] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] Update mode to 3840x2160p60, type: 11(if:HDMI0, flag:0x0) for vp0 dclk: 594000000 [ 296.326327] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx_ropll_cmn_config bus_width:5aa320 rate:5940000 [ 296.326706] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy pll locked! [ 296.327137] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] dclk_out0 div: 0 dclk_core0 div: 2 [ 296.327226] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] set dclk_vop0 to 594000000, get 594000000 [ 296.327422] dwhdmi-rockchip fde80000.hdmi: final tmdsclk = 594000000 [ 296.438292] dwhdmi-rockchip fde80000.hdmi: don't use dsc mode [ 296.438342] dwhdmi-rockchip fde80000.hdmi: dw hdmi qp use tmds mode [ 296.438380] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: bus_width:0x5aa320,bit_rate:5940000 [ 296.438665] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy lane locked! As soon as I use the graphical target, then dmesg shows nothing and syslog only the messages I showed before. root@loovsys:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Armbian 24.11.3 noble Release: 24.04 Codename: noble root@loovsys:~# uname -a Linux loovsys.eu 6.1.84-vendor-rk35xx #1 SMP Thu Jan 9 02:09:01 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux Anyone experiencing similar issues or has any idea what could be the reason for it? Otherwise t

Hi all, I am trying to recover after a failed NVMe install. I have a working install on an SDCard, but I think my board no longer boots to SDCard, since I flashed the bootloader via armbian-install. I am not sure if my NVMe install is good or not, and I can't currently reflash it. So I think my best bet is to wipe the SPI, which I hope means the board will go back to booting from SDCard. That's question 1 - is that actually a valid solution? If I wipe the SPI will I be able to again boot to SDCard? I am able to get the board into Maskrom mode, and I can see it using the Windows tool. However, I believe that I need a "loader image" that I "download" into the tool before I can wipe the bootloader. The Rock5 SPI wipe guide posted elsewhere in this forum refers to rk3588_spl_loader_v1.08.111.bin, which I don't have, and I'm not sure that's the right loader for the OPi5. That's question 2 - is there a loader for the OPi5 and/or can the Rock5 loader be used here? The OPi5 Manual is very sparse about Maskrom info, it says how to get into that mode, but only gives instructions for flashing the board to Android. The Android download is not working right now (Google Drive quota) so I am not able to get that package, in case it happens to have a suitable loader image. Thanks for any replies in advance.

Hi I want to work with g_audio drivers on the usb type c otg port. When I build the image with current kernel, by applying the following overlay (I only change dr_mode to peripheral) i am able to convert the usb port in peripheral mode and successfully load the g_audio drivers and audio interfaces also come up. /dts-v1/; /plugin/; / { compatible = "rockchip,rk3588s"; fragment@0 { target = <&usb_host0_xhci>; // This matches the label in the device tree __overlay__ { dr_mode = "peripheral"; }; }; }; But when i want to do similar with the vendor kernel, which has different device tree, changing dr_mode doesn't work. /dts-v1/; /plugin/; / { compatible = "rockchip,rk3588s"; fragment@0 { target = <&usbdrd3_0>; // Target the usbdrd3_0 node __overlay__ { usb@fc000000 { dr_mode = "peripheral"; // Change dr_mode to peripheral }; }; }; }; The device trees for usb type c port for both kernels are as below - //***This node is of current kernel*** usb@fc000000 { power-domains = <0x21 0x1f>; snps,dis-u1-entry-quirk; snps,dis_enblslpm_quirk; phy-names = "usb2-phy\0usb3-phy"; clock-names = "ref_clk\0suspend_clk\0bus_clk"; snps,dis-u2-freeclk-exists-quirk; usb-role-switch; phy_type = "utmi_wide"; resets = <0x1f 0x152>; interrupts = <0x00 0xdc 0x04 0x00>; clocks = <0x1f 0x194 0x1f 0x193 0x1f 0x192>; snps,dis-u2-entry-quirk; compatible = "rockchip,rk3588-dwc3\0snps,dwc3"; snps,dis-del-phy-power-chg-quirk; status = "okay"; phys = <0x23 0x24 0x04>; reg = <0x00 0xfc000000 0x00 0x400000>; phandle = <0x116>; dr_mode = "peripheral"; snps,dis-tx-ipgap-linecheck-quirk; port { endpoint { remote-endpoint = <0x25>; phandle = <0xeb>; }; }; }; ------------ dmesg output [ 15.417624] i2c 6-0022: deferred probe pending: typec_fusb302: cannot register tcpm port [ 600.475296] g_audio gadget.0: Linux USB Audio Gadget, version: Feb 2, 2012 [ 600.475317] g_audio gadget.0: g_audio ready Vendor Kernel //***This node is of vendor kernel usbdrd3_0 { #address-cells = <0x02>; clock-names = "ref\0suspend\0bus"; clocks = <0x02 0x1a3 0x02 0x1a2 0x02 0x1a1>; #size-cells = <0x02>; compatible = "rockchip,rk3588-dwc3\0rockchip,rk3399-dwc3"; ranges; status = "okay"; phandle = <0x22b>; usb@fc000000 { power-domains = <0x06 0x1f>; snps,dis-u1-entry-quirk; snps,dis_enblslpm_quirk; phy-names = "usb2-phy\0usb3-phy"; snps,dis-u2-freeclk-exists-quirk; usb-role-switch; phy_type = "utmi_wide"; quirk-skip-phy-init; resets = <0x02 0x2a4>; interrupts = <0x00 0xdc 0x04>; snps,dis-u2-entry-quirk; compatible = "snps,dwc3"; snps,parkmode-disable-hs-quirk; snps,dis-del-phy-power-chg-quirk; status = "okay"; snps,parkmode-disable-ss-quirk; phys = <0x74 0x75>; reg = <0x00 0xfc000000 0x00 0x400000>; phandle = <0x22c>; dr_mode = "otg"; reset-names = "usb3-otg"; snps,dis-tx-ipgap-linecheck-quirk; port { #address-cells = <0x01>; #size-cells = <0x00>; endpoint@0 { remote-endpoint = <0x76>; reg = <0x00>; phandle = <0x183>; }; }; }; }; //dmesg output [ 41.238153] [GTP-ERR][__do_register_ext_module:79] Module [goodix-fwu] timeout [ 243.574594] g_audio gadget.0: Hardware params: access 3, format 2, channels 2, rate 48000 [ 243.574756] g_audio gadget.0: Linux USB Audio Gadget, version: Feb 2, 2012 [ 243.574773] g_audio gadget.0: g_audio ready [ 243.578558] typec_fusb302 6-0022: Looking up vbus-supply from device tree [ 243.581576] dwc3 fcd00000.usb: device reset Can some one help me what kind of overlay should i make to convert the port to peripheral mode.

System Information: https://paste.armbian.com/mozehisomu When i am trying to setup many vlan interfacces i have whis dmesg message: rk_gmac-dwmac fe1c0000.ethernet eth0: MAC_VLAN_Tag_Filter full (size: 4) interface info: ethtool -i eth0 driver: st_gmac version: Jan_2016 firmware-version: expansion-rom-version: bus-info: supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: yes supports-priv-flags: no I need about 20-30 vlan interfaces

Hi everybody, I installed Deb 12 Cinnamon Armbian flavor. This: dl.armbian.com/orangepi5-plus/Bookworm_current_cinnamon-backported-mesa When I open system setup there is no Idiom/Language Icon. So all apps remains in English. Even if I run "sudo dpkg-reconfigure keyboard-configuration" and "sudo dpkg-reconfigure locales" I found an issue running "armbian-config"/localization/change Keyboard layout, on console this msg "setupcon: We are not on the console, the console is left unconfigured." But if I run "sudo dpkg-reconfigure keyboard-configuration" from a terminal window no error. Thanks, Cury

Hello ! I've bought a Orange Pi 5 PRO board about 2 months ago . I've tryed all images (Linux and Android) from the official Orange Pi site . Later I tryed Armbian . In the end I've concluded that the best choice is Armbian 24.5.2 Noble Gnome ( Armbian_24.5.2_Orangepi5pro_noble_vendor_6.1.43_gnome-oibaf_desktop.img ). Using Armbian 24.5.2 Noble Gnome I got the best (the smoothest) video playback, both in video players and online (youtube) content . And it' s very responsive in operation, generally . I have one single issue : My MCE remote is not detected properly - the Play, Pause, Next, Previous, Forward, Rewind buttons did't perform any actions when I used Kodi video player . When I press any of these buttons I get a 🚫 (no entry) sign on the bottom of the screen . Only the following buttons are performing correctly : Power, Ok, Left, Right, Up, Down, back, and numeric keys . If I'm using other video players, like Celluloid, Vlc,Haruna, Smplayer, all the remote control's buttons performs as it should . The remote control's model number is HP TSGH-2401 with RF USB dongle . I tryed the remote and Kodi on different Linux images, even on Armbian_24.5.2_Orangepi5pro_noble_vendor_6.1.43_xfce-oibaf_desktop.img - it perform as it should, but all these Linux images have video playback issues (or maybe i'm too picky) . The problem with the remote control is present only on Armbian 24.5.2 Noble Gnome (which I preffered for it's video performance) . I tryed to fix the problem using inputlirc package, but with limited success . I also tried "Keymap editor " add-on for Kodi, but with almost none positive results . I attached 2 screenshoots with the the screen when I get a 🚫 (no entry) sign on the bottom of the screen . Please help me with some suggestions . Thank you in advance !

Happy New Year for all, My old Samsung Monitor stopped working some days ago, and I dont know if it will be fixed, so I decided to buy a new LG 27'' Monitor. My Zorin OS and Windows on X64, Raspbian and Ubuntu On Raspberry PIs are working properly. But booting Armbian - Ubuntu 24.04 (Noble) on "Orange PI 5" and "Orange PI 5 Plus" My New monitor refuses to show any image (only black screen). "Orange PI OS XFCE" on "Orange PI 5" is OK on my new monitor. I took a litle look at boot files but I didn't find anything to fix this problem. Any idea to solve this problem??? Thanks, Cury

I don't know why, I think after doing "sudo apt update/upgrade" (but I'm not sure), the wiringOP library on "orange pi 5" with Armbian 23.02.2 doesn't work anymore. If I run the command "sudo gpio readall" I get the following output: Oops: Unable to determine board revision from /proc/device-tree/system/linux,revision or from /proc/cpuinfo -> No "Hardware" line -> You'd best google the error to find out why. Can anyone help me solve this problem?

Was using my Orange Pi 5 and it rebooted on it's own. After that, it continually reboots. Been running fine for months. Tried restarting a few times. Tried swapping SD cards. It looks like the power supply is OK, although I'll try swapping with another. I had just backed up the SD Card too. I'll try re-imaging an SD card, but I'm thinking the SD card may not be the issue. I hooked up my UART and captured output. At the end of each loop, it looks like it's saying "Starting Kernel" and then restarting. Captured output follows. Any ideas, suggestions or comments on what's happening. I'm thinking it's probably a hardware issue. I purchased on Amazon. Can't find out how long the warranty/if it's still under warranty. DDR V1.11 f1474cf52f cym 23/05/09-11:02:36 LPDDR4X, 2112MHz CH2 RX Vref:27.5%, TX Vref:19.8%,20.8% CH3 RX Vref:30.1%, TX change to F1: 528MHz change to F2: 1068MHz change to F3: 156out U-Boot SPL board init U-Boot SPL 2017.09 (Jun 30 2023 - 19unknown raw ID 0 0 0 unrecognized JEDEC id bytes: 00, 00, 00 TTrying fit image at 0x4000 sector ## Verified-boot: 0 ## Check## Checking uboot 0x00200000 ... sha256(bab9643a63...) + OK ## atf-3 0x000f0000 ... sha256(da90adf3a4...) + OK Jumping to U-B.622 ms INFO: Preloader serial: 2 NOTICE: BL31: v2.3():vrt detected. INFO: ARM GICv3 driver initialized in EL3 INFOams[0].freq_mhz= 2112MHz INFO: dfs DDR fsp_params[1].freq_mhz= 528MHz INFO: dfs DDR fsp_params[2].freq_mhz= 1068MHz INFINFO: BL31: Initialising Exception Handling Framework INFO: initializing runtime service opteed_fast INFO: BL31: Prepar 0x200000 INFO: SPSR = 0x3c9 U-Boot 2017.09 (Jun 30 202CR: M/C/I Using default environment mmc@fe2c0000: 0, mmc@fe2Bootdev(atags): mmc 0 MMC0: Legacy, 52Mhz PartType: EFI DM: vCLK: (sync kernel. arm: enter 1008000 KHz, init 1008000 KHz, kerpll 1188000 KHz npll 24000 KHz ppll 1100000 KHz aclk_ceer_root 396000 KHz aclk_center_low_root 500000 KHz aclk_toot 396000 KHz Net: No ethernet found. Hit key to stop autobo-Boot script /boot.scr reading /boot.scr 3476 bytes read in 1 ded from mmc 0 reading /armbianEnv.txt 212 bytes read in 2 ms 15248365 bytes read in 1223 ms (11.9 MiB/s) reading /Image 34638336 bytes read in 2777 ms (11.9 MiB/s) reading /dtb/rockch234611 bytes read in 30 ms (7.5 MiB/s) ** Unable to read file /OK ## Flattened Device Tree blob at 0x0a100000 Booting usin000000000a1a1fff Adding bank: 0x00200000 - 0xf0000000 (size: 0xize: 0x03a00000) Adding bank: 0x4f0000000 - 0x500000000 (size: Total: 4379.611 ms Starting kernel ... DDR V1.11 f1474cf52f cym 23/05/09-11:02:36 LPDDR4X, 2112MHz cher ID:0x6 CH0 RX Vref:28.5%, TX Vref:20.8%,20.8% CH1 RX Vref:2 CH2 RX Vref:27.5%, TX Vref:20.8%,19.8% CH3 RX Vref:29.3%, TX change to F1: 528MHz change to F2: 1068MHz change to F3: 156out U-Boot SPL board init U-Boot SPL 2017.09 (Jun 30 2023 - 19Trying fit image at 0x4000 sector ## Verified-boot: 0 ## Check## Checking uboot 0x00200000 ... sha256(bab9643a63...) + OK ## .902 ms INFO: Preloader serial: 2 NOTICE: BL31: v2.3():vINFO: ddr: stride-en 4CH INFO: GICv3 without legacy suppo: system boots from cpu-hwid-0 INFO: idle_st=0x21fff, pd_ams[0].freq_mhz= 2112MHz INFO: dfs DDR fsp_params[1].freq_mhINFO: BL31: Initialising Exception Handling Framework INFO: U-Boot 2017.09 (Jun 30 2023 - 19:08:39 +0200) Model: OranCR: M/C/I Using default environment mmc@fe2c0000: 0, mmc@fe2Bootdev(atags): mmc 0 MMC0: Legacy, 52Mhz PartType: EFI DM: vCLK: (sync kernel. arm: enter 1008000 KHz, init 1008000 KHz, kerot 396000 KHz Net: No ethernet found. Hit key to stop autoboms (3.3 MiB/s) ## Executing script at 00500000 Boot script loa15248365 bytes read in 1223 ms (11.9 MiB/s) reading /Image 34638336 bytes read in 2776 ms (11.9 MiB/s) reading /dtb/rockch234611 bytes read in 29 ms (7.7 MiB/s) ** Unable to read file /p compressed) Data Size: 15248301 Bytes = 14.5 MiB LoOK ## Flattened Device Tree blob at 0x0a100000 Booting usinefe00000) Adding bank: 0x100000000 - 0x3fc000000 (size: 0x2fc00ize: 0x03a00000) Adding bank: 0x4f0000000 - 0x500000000 (size: Total: 4378.924 ms Starting kernel ...

Hello all. Trying to get PCIe/NVMe working (even to show on microSD boot, let alone boot NVMe) on a custom compile on my Orange Pi 5 SBC version 1.3.2, because the official images aren't working either for me. No idea where to go from here and need some assistance as NVMe is required for my purpose. Here is what I did during compile.sh > Show kernel config > Board: orangepi5 > Kernel: current > Target: jammy > Image with desktop > Gnome desktop > Base configuration > Tick: Browsers > Device Drivers > PCI support > (default values) > Device Drivers > NVME Support > (default values) I used "SHARE_LOG=yes" but got below error at the end so I'm guessing it did not upload. I'm attaching it instead. SHARE_LOG=yes, uploading log [ uploading logs ] Log uploaded, share URL: [ <!DOCTYPE html> <html lang=en> <head> <meta charset=utf-8> <title>Error</title> </head> <body> <pre>Cannot POST /log</pre> </body> </html> ] Repeat build options Repeat Build Options [ ./compile.sh build BOARD=orangepi5 BRANCH=current BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED=browsers DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base KERNEL_CONFIGURE=yes RELEASE=jammy SHARE_LOG=yes ] Side notes: I've tested with Joshua-Riek's ubuntu-rockchip builds here https://github.com/Joshua-Riek/ubuntu-rockchip/releases After writing the 22.04 version 3 to the microSD card, then boot to the microSD card on the SBC, doing lsblk lists the NVMe drive just fine. I use the tools this provides to copy the current configuration to the NVMe, update the bootloader, shutdown and only attempt to boot from NVMe and it does not work. So that is working a bit more than Armbian, but still not dedicated NVMe boot. I found this issue that talked about some Armbian changes to the DTS files for the arm64 boot on linux-rockchip, that seems to be the NVMe is not enabled? Here is that link: https://github.com/Joshua-Riek/ubuntu-rockchip/issues/709 One person was able to re-compile the DTS to DTB and manually update and dmesg output seems to work. This is where I'm lost as I've never compiled the device tree before. Assistance is greatly appreciated! Thanks! log-build-7d071dfd-1b54-45cf-8488-2bc8b5e62079.zip

Before writing I searched the forum a bit but couldn't find any recent posts about it. I have an OPI5 board and on NVME I would like to install armbian. I downloaded the image to micro sd and it boots fine. At this point I don't know what to do because I had to waste a lot of time on it some time ago and I don't remember the steps. With the armbian-config utility is it possible to clone the armbian release I am using on the micro sd? I remember that this wasn't possible some time ago. I would like to know specifically the steps to take and whether it is advisable to delete any old partitions on nvme. Thank you

I tried installing the OS using SD card and EMMC, but both failed. Orange Pi OS (Arch) on the official website ran normally. However, I installed focal_desktop_xfce or jammy_desktop_gnome from Ubuntu Image, but they all failed. After inserting the image into the SD card, the symptom is a black screen and no booting. Does it only support SSD? Because it is entered through a translator, there may be unnatural sentences. If you reply about that, I will get back to you.

Hey folks, im trying to compile a realtime kernel for mt orange pi 5. I plan to use it for djing. A fully preemptive kernel delivers better performance for this, as less xruns appear. I am following the official dev instructions and am using the docker method, Compiling only the kernel, not the entire armbian OS. I copied a realtime patch (actually I tried several sub versions of 5.10) from the kernel.org realtime project site into the userpatches directory (I looked up the correct orange pi 5 subfolder name but forgot it rn) but compiling throws me some errors. Has anyone succeeded in creating a kernel like this for the orange pi 5 and/or could give me any advice for doing so? I actually dont care much about the kernel version, I just need it to be fully preemptive .. Help is much apprecieated! Kenny

I have an Armbian installation on the NVMe drive and I'm trying to switch back to boot from SD card. In `armbian-config` I messed up the boot settings by leaving the root fs type unchanged, (SD card is in fat32 but NVMe partition is ext4). Now the board boots into initramfs prompt. Here's what I've already tried based on search and ChatGPT: Mount the NVMe partition to `/mnt` then chroot to it, this did work but the `/boot` partition was not mounted inside of the chroot so I can't fix boot env. I also tried `switch_root` but it's not available in the initramfs prompt. Update `/proc/cmdline` to change the root fs back to the Armbian partition, but `echo ... > /proc/cmdline` doesn't really do anything. Any ideas?

Hello everyone, I recently purchased an ili9488 touch screen for use with my Orange Pi 5, but I'm having trouble getting it to work. I've tried several solutions that I found online, but so far nothing has worked. Specifically, the screen isn't displaying any output when I connect it to my Orange Pi 5, and I'm not sure what steps to take next. https://a.aliexpress.com/_EQaN4gj - That is the screen I bought. For context,I have the latest version of the Armbian operating system installed. I've followed the instructions that came with the touch screen, and I've also tried several different solutions that I found online (including using the fbset command to adjust the display resolution, and updating the device tree overlay file). If anyone has any suggestions or advice for how I can troubleshoot this issue, I would be extremely grateful. I'm open to any possible solutions, and I'm willing to try anything to get this screen up and running. Thank you in advance for your help!

Please advise on how to fix this, thanks: Setting up rockchip-multimedia-config (1.0.2+jammy) ... dpkg-query: error: --listfiles needs at least one package name argument Use --help for help about querying packages. dpkg: error processing package rockchip-multimedia-config (--configure): installed rockchip-multimedia-config package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: rockchip-multimedia-config E: Sub-process /usr/bin/dpkg returned an error code (1)

Hello, I installed lm-sensors on my Opi5 and I'm able to check temperatures, however I don't know how to make the little fan spin when the temperature rise. I know the temperature is not going to rise till critical levels, but I live in very hot country and I just don't want my device to become too hot. And do you know how to make the fan start at certain temperature rise? Also I'm not sure which pins I should connect the fan to.. One pin should be the 3.3V to get the power, what about the other one? I'm running Armbian 23.02.2 with kernel 5.10.110-rockchip-rk3588 Thanks in advance

flashed to m2 mvme, board attempts to boot , then after armbian logo it falls into busybox command prompt (

Couldn't booti from NVME with armbian-config or armbian-install, finally I could do it, a dirty easy and convoluted following way. No details about burning stuff This is what I did 1) boot system from fresh downloaded SD (Armbian Jammy Desktop) 2) NVME setup (sudo gparted) - if empty create a partition table (GPT) if not delete all partitions - create 256MB FAT16 partition (nvme0n1p1) - create EXT4 partition (nvme0n1p2) - optionally create more partitions (system recovery, backups ...) - format partitions nvme0n1p1 -> FAT16 - format partitions nvme0n1p2 -> EXT4 - check partitions (if old NVME) - label nvme0n1p1 as armbi_boot - label nvme0n1p2 as armbi_root 3) run sudo armbian-install - option 7 to flash mtdblock0 (bootloader install) - option 4 (to install system and boot from mtdblock0) choose nvme0n1p2 partition to install system don't POWEROFF, just EXIT 4) copy SD boot partition to nvme0n1p1 - sudo dd if=/dev/mmcblk1p1 of=/dev/nvme0n1p1 bs=1M status=progress - sudo sync 5) armbianExt.txt setup on NMVE - sudo mount /dev/nvme0n1p1 /mnt - check boot files/directories are already copied (ls -l /mnt) - blkid - copy (CTL_INS -> new UUID) of nvme0n1p2 UUID (without "") with your favourite editor: - sudo vi armbianExt.txt - replace rootdev=UUID=with new UUID (SHIFT-INS) - save (ESC :x) 6) - sudo poweroff - remove SD - press power button to restart Maybe this cam help someone