Search the Community

I have setup the hardware acceleration as explained in the posts, but within Kodi, every now and then I can see the image with "pixelising", and looking in the syslog when this just happened, I can read: Feb 15 16:54:17 orangepi5 kernel: [ 1267.908544] mpp_rkvdec2 fdc48100.rkvdec-core: reset done Feb 15 16:54:17 orangepi5 kernel: [ 1267.908549] mpp_rkvdec2 fdc38100.rkvdec-core: resetting... Feb 15 16:54:17 orangepi5 kernel: [ 1267.908670] mpp_rkvdec2 fdc38100.rkvdec-core: reset done Feb 15 16:54:17 orangepi5 kernel: [ 1268.316705] mpp_rkvdec2 fdc48100.rkvdec-core: resetting... Feb 15 16:54:17 orangepi5 kernel: [ 1268.316855] mpp_rkvdec2 fdc48100.rkvdec-core: reset done Feb 15 16:54:17 orangepi5 kernel: [ 1268.316860] mpp_rkvdec2 fdc38100.rkvdec-core: resetting... Feb 15 16:54:17 orangepi5 kernel: [ 1268.316930] mpp_rkvdec2 fdc38100.rkvdec-core: reset done Any idea what could be wrong? Thanks.

Hi, I've trouble getting 3840x2160 resolution to work. When I try to switch to that resolution the monitor says resolution is 3848x2160 and display is all garbled. 2560x1440 works fine. Also, If I try to login to Gnome (Wayland) I get blank screen and I'm back at the login screen. X11 lets me login to the system. uname -a: Linux lindon 5.10.110-rockchip-rk3588 #trunk.0184 SMP Fri Jan 20 18:24:04 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux I've fetched the latest updates (apt update && apt upgrade) and I've just ran firmware update using armbian-config. Edit: display is connected via usb-c - - > displayport cable.

I want to install the usb wifi/bluetooth card drivers but I keep getting an error during compilation. What to do? below code: DKMS make.log for rtl8812au-5.13.6 for kernel 5.10.110-rockchip-rk3588 (aarch64) Tue Jan 10 08:48:19 PM CET 2023 make ARCH=arm64 CROSS_COMPILE= -C /lib/modules/5.10.110-rockchip-rk3588/build M=/var/lib/dkms/rtl8812au/5.13.6/build modules make[1]: Entering directory '/usr/src/linux-headers-5.10.110-rockchip-rk3588' CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_cmd.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_security.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_debug.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_io.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_ioctl_query.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_ioctl_set.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_ieee80211.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_mlme.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_mlme_ext.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_mi.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_wlan_util.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_vht.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_pwrctrl.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_rf.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_chplan.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/monitor/rtw_radiotap.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_recv.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_sta_mgt.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_ap.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/wds/rtw_wds.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/mesh/rtw_mesh.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/mesh/rtw_mesh_pathtbl.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/mesh/rtw_mesh_hwmp.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_xmit.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_p2p.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_rson.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_tdls.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_br_ext.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_iol.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_sreset.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_btcoex_wifionly.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_btcoex.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_beamforming.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_odm.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_rm.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_rm_fsm.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_ft.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_wnm.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_mbo.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_rm_util.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/efuse/rtw_efuse.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_roch.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/aes-internal.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/aes-internal-enc.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/aes-gcm.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/aes-ccm.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/aes-omac1.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/ccmp.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/gcmp.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/aes-siv.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/aes-ctr.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/sha256-internal.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/sha256.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/sha256-prf.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/rtw_crypto_wrap.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_swcrypto.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/osdep_service.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/os_intfs.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/usb_intf.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/usb_ops_linux.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/ioctl_linux.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/xmit_linux.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/mlme_linux.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/recv_linux.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/ioctl_cfg80211.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/rtw_cfgvendor.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/wifi_regd.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/rtw_android.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/rtw_proc.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/nlrtw.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/rtw_rhashtable.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/hal_intf.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/hal_com.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/hal_com_phycfg.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/hal_phy.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/hal_dm.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/hal_dm_acs.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/hal_btcoex_wifionly.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/hal_btcoex.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/hal_mp.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/hal_mcc.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/hal_hci/hal_usb.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/led/hal_led.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/led/hal_usb_led.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/HalPwrSeqCmd.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/Hal8812PwrSeq.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/Hal8821APwrSeq.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/rtl8812a_xmit.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/rtl8812a_sreset.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/rtl8812a_hal_init.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/rtl8812a_phycfg.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/rtl8812a_rf6052.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/rtl8812a_dm.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/rtl8812a_rxdesc.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/rtl8812a_cmd.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/usb/usb_halinit.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/usb/rtl8812au_led.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/usb/rtl8812au_xmit.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/usb/rtl8812au_recv.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/usb/usb_ops_linux.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/efuse/rtl8812a/HalEfuseMask8812A_USB.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/hal8812a_fw.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_debug.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_antdiv.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_soml.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_smt_ant.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_antdect.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_interface.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_phystatus.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_hwconfig.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_dig.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_pathdiv.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_rainfo.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_dynamictxpower.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_adaptivity.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_cfotracking.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_noisemonitor.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_beamforming.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_direct_bf.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_dfs.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/txbf/halcomtxbf.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/txbf/haltxbfinterface.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/txbf/phydm_hal_txbf_api.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_adc_sampling.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_ccx.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_psd.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_primary_cca.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_cck_pd.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_rssi_monitor.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_auto_dbg.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_math_lib.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_api.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_pow_train.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_lna_sat.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_pmac_tx_setting.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_mp.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_cck_rx_pathdiv.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/halrf/halrf.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/halrf/halrf_debug.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/halrf/halphyrf_ce.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/halrf/halrf_powertracking_ce.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/halrf/halrf_powertracking.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/halrf/halrf_kfree.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/halrf/halrf_psd.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/rtl8812a/halhwimg8812a_mac.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/rtl8812a/halhwimg8812a_bb.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/rtl8812a/halhwimg8812a_rf.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/halrf/rtl8812a/halrf_8812a_ce.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/rtl8812a/phydm_regconfig8812a.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/rtl8812a/phydm_rtl8812a.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/txbf/haltxbfjaguar.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/platform/platform_ops.o LD [M] /var/lib/dkms/rtl8812au/5.13.6/build/8812au.o MODPOST /var/lib/dkms/rtl8812au/5.13.6/build/Module.symvers ERROR: modpost: module 8812au uses symbol kernel_write from namespace VFS_internal_I_am_really_a_filesystem_and_am_NOT_a_driver, but does not import it. ERROR: modpost: module 8812au uses symbol kernel_read from namespace VFS_internal_I_am_really_a_filesystem_and_am_NOT_a_driver, but does not import it. ERROR: modpost: module 8812au uses symbol filp_open from namespace VFS_internal_I_am_really_a_filesystem_and_am_NOT_a_driver, but does not import it. make[2]: *** [scripts/Makefile.modpost:169: /var/lib/dkms/rtl8812au/5.13.6/build/Module.symvers] Error 1 make[2]: *** Deleting file '/var/lib/dkms/rtl8812au/5.13.6/build/Module.symvers' make[1]: *** [Makefile:1822: modules] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.10.110-rockchip-rk3588' make: *** [Makefile:2504: modules] Error 2

I just installed the most recent nightly image - this one looks like a major update but it broke armbian on my opi 5 1. I had to re-install the mali firmware to get x11/wayland to start - not sure why the update deleted the file 2. I had to re-install the mali-g610-firmware rockchip-multimedia-config packages 3. VLC cannot start the h264 decoder anymore [0000005583627590] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface. Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. [00000055836b79e0] main playlist: playlist is empty [h264_rkmpp @ 0x7f4cc37630] Failed to initialize MPP context (code = -1). [h264_rkmpp @ 0x7f4cc37630] Failed to initialize RKMPP decoder. [0000007f4cc18690] avcodec decoder error: cannot start codec (h264_rkmpp) [0000007f4cc18690] main decoder error: Codec `h264' (H264 - MPEG-4 AVC (part 10)) is not supported. [00000055836e1790] main audio output error: too low audio sample frequency (0) [0000007f4cc18690] main decoder error: failed to create audio output [00000055836e1790] vlcpulse audio output error: digital pass-through stream connection failure: Not supported [00000055836e1790] main audio output error: module not functional [0000007f4cc18690] main decoder error: failed to create audio output QObject::~QObject: Timers cannot be stopped from another thread Any suggestions to fix the video decoding?

I've been trying to implement traffic shaping using tc. But it seems that ingress is not working. I am running Armbian Minimal Server on Orange Pi 5. Running this command: tc qdisc add dev eth0 ingress Will throw an error: Error: Specified qdisc kind is unknown. This has been working for orange pi pc/one armbian. Does the ingress module missing from this build? Can anyone point me to the right direction. Thanks.

So recently I flashed Orange Pi OS to SD card, booted from there, updated system, firmware and flashed bootloader to SPI flash. I already had an external HDD with Armbian flashed, and tried to boot from there, but no luck. Afterwards, I tried to boot Armbian from SD card, but I can't boot any system that is not Orange Pi OS (and especifically, it needs to be from SD card, can't also boot from USB even in OPi OS). Tried with different SD cards and USB devices, no luck I believe I need to erase SPI flash in order to boot from SD again, but, how can I do it? Used latest OrangePi OS and Armbian Jammy CLI from 23/01 (stable release)

I finally found an official source code on the download page of OrangePI that has a version of wiring pi with support for the Orange PI 5 - unfortunately that code is not on the github of orangepi yet. What would be the best way to get this code and the gpio tool into armbian? Build a PPA and package for that one? I don't mind forking their repo and adding the mods but I'm not familiar with generating debian packages.

After upgrading today with "apt update && apt upgrade" I was no longer able to watch videos. mpv player would Segfault, also tried vlc - not working either. Gnome desktop with wayland itself works, only video playback seems to be affected. After rolling back the following packages in liujianfeng1994 repo it started to work again: librockchip-mpp1:arm64 OLD: 1.5.0-1+git221020.d63affb~jammy NEW, causes segfault: 1.5.0-1+git230210.c145c84~jammy The repository no longer has the old version, but I managed to get it back to 1.5.0-1+git221020.d63affb~jammy like this #Find the deb file from cache find /var/cache/apt -name '*librockchip-mpp1*' #Install it using dpkg, your version might differ dpkg -i /var/cache/apt/archives/librockchip-mpp1_1.5.0-1+git221020.d63affb~jammy_arm64.deb Syslog lines that appear when launching mpv and it sefaults(video will not play): Feb 10 21:13:09 loovsys mpp[69636]: mpp_info: mpp version: unknown mpp version for missing VCS info Feb 10 21:13:09 loovsys mpp[69636]: mpp_dma_heap: Assertion fd > 0 failed at heap_fd_open:136 Feb 10 21:13:09 loovsys mpp[69636]: mpp_dma_heap: os_allocator_dma_heap_open open dma heap type 0 failed! Feb 10 21:13:09 loovsys mpp[69636]: mpp_allocator: mpp_allocator_get type 1 failed Feb 10 21:13:09 loovsys mpp[69636]: mpp_dma_heap: Assertion fd > 0 failed at heap_fd_open:136 Feb 10 21:13:09 loovsys mpp[69636]: mpp_dma_heap: os_allocator_dma_heap_open open dma heap type 0 failed! Feb 10 21:13:09 loovsys mpp[69636]: mpp_allocator: mpp_allocator_get type 3 failed Feb 10 21:13:09 loovsys mpp[69636]: mpp_dma_heap: Assertion fd > 0 failed at heap_fd_open:136 Feb 10 21:13:09 loovsys mpp[69636]: mpp_dma_heap: os_allocator_dma_heap_open open dma heap type 0 failed! Feb 10 21:13:09 loovsys mpp[69636]: mpp_allocator: mpp_allocator_get type 4 failed Feb 10 21:13:09 loovsys mpp[69636]: mpp_buffer: Assertion p->allocator failed at get_group:902 Feb 10 21:13:09 loovsys mpp[69636]: mpp_buffer: Assertion p->alloc_api failed at get_group:903 Feb 10 21:13:09 loovsys mpp[69636]: mpp_buffer: Assertion p->allocator failed at get_group:902 Feb 10 21:13:09 loovsys mpp[69636]: mpp_buffer: Assertion p->alloc_api failed at get_group:903 Syslog lines that appear after rolling back the package and video plays again: Feb 10 21:14:02 loovsys mpp[69759]: mpp_info: mpp version: unknown mpp version for missing VCS info Feb 10 21:14:02 loovsys mpp[69759]: hal_h264d_vdpu34x: control info: fmt 0, w 800, h 600 Feb 10 21:14:02 loovsys mpp[69759]: mpp_buf_slot: set frame info: w 800 h 600 hor 800 ver 608 Feb 10 21:14:02 loovsys mpp[69759]: mpp_dec: setting default w 800 h 600 h_str 800 v_str 608 All packages that I upgraded during the upgrade. #Not relevant at all docker-compose-plugin:arm64 (2.15.1-1~ubuntu.22.04~jammy, 2.16.0-1~ubuntu.22.04~jammy), libpam-runtime:arm64 (1.4.0-11ubuntu2.1, 1.4.0-11ubuntu2.3), docker-ce-cli:arm64 (5:23.0.0-1~ubuntu.22.04~jammy, 5:23.0.1-1~ubuntu.22.04~jammy), armbian-config:arm64 (23.02.0-trunk.0232, 23.02.0-trunk.0250), less:arm64 (590-1build1, 590-1ubuntu0.22.04.1), docker-ce:arm64 (5:23.0.0-1~ubuntu.22.04~jammy, 5:23.0.1-1~ubuntu.22.04~jammy), firefox:arm64 (109.0.1+build1-0ubuntu0.22.04.1~mt1, 110.0+build1-0ubuntu0.22.04.1~mt1), libssl3:arm64 (3.0.2-0ubuntu1.7, 3.0.2-0ubuntu1.8), libpam-modules:arm64 (1.4.0-11ubuntu2.1, 1.4.0-11ubuntu2.3), openssl:arm64 (3.0.2-0ubuntu1.7, 3.0.2-0ubuntu1.8), armbian-plymouth-theme:arm64 (23.02.0-trunk.0232, 23.02.0-trunk.0250), libssl-dev:arm64 (3.0.2-0ubuntu1.7, 3.0.2-0ubuntu1.8), #Might be relevant xserver-xorg-core:arm64 (2:21.1.3-2ubuntu2.5, 2:21.1.3-2ubuntu2.7), librockchip-mpp1:arm64 (1.5.0-1+git221020.d63affb~jammy, 1.5.0-1+git230210.c145c84~jammy), xserver-common:arm64 (2:21.1.3-2ubuntu2.5, 2:21.1.3-2ubuntu2.7), xwayland:arm64 (2:22.1.1-1ubuntu0.4, 2:22.1.1-1ubuntu0.5), libpam-modules-bin:arm64 (1.4.0-11ubuntu2.1, 1.4.0-11ubuntu2.3), libpam0g:arm64 (1.4.0-11ubuntu2.1, 1.4.0-11ubuntu2.3), linux-dtb-legacy-rockchip-rk3588:arm64 (23.02.0-trunk.0232, 23.02.0-trunk.0248), linux-headers-legacy-rockchip-rk3588:arm64 (23.02.0-trunk.0232, 23.02.0-trunk.0248), armbian-bsp-cli-orangepi5:arm64 (23.02.0-trunk.0232, 23.02.0-trunk.0250), linux-image-legacy-rockchip-rk3588:arm64 (23.02.0-trunk.0232, 23.02.0-trunk.0248), linux-u-boot-orangepi5-legacy:arm64 (23.02.0-trunk.0232, 23.02.0-trunk.0250), armbian-firmware:arm64 (23.02.0-trunk.0232, 23.02.0-trunk.0250), linux-libc-dev:arm64 (23.02.0-trunk.0232, 23.02.0-trunk.0250), #Probably not relevant libavdevice58:arm64 (7:4.4.2-0ubuntu0.22.04.1+rkmpp20221203, 7:4.4.2-0ubuntu0.22.04.1+rkmpp20230207), libpostproc55:arm64 (7:4.4.2-0ubuntu0.22.04.1+rkmpp20221203, 7:4.4.2-0ubuntu0.22.04.1+rkmpp20230207), libavcodec58:arm64 (7:4.4.2-0ubuntu0.22.04.1+rkmpp20221203, 7:4.4.2-0ubuntu0.22.04.1+rkmpp20230207), libavutil56:arm64 (7:4.4.2-0ubuntu0.22.04.1+rkmpp20221203, 7:4.4.2-0ubuntu0.22.04.1+rkmpp20230207), libswscale5:arm64 (7:4.4.2-0ubuntu0.22.04.1+rkmpp20221203, 7:4.4.2-0ubuntu0.22.04.1+rkmpp20230207), libavutil-dev:arm64 (7:4.4.2-0ubuntu0.22.04.1+rkmpp20221203, 7:4.4.2-0ubuntu0.22.04.1+rkmpp20230207), libswresample3:arm64 (7:4.4.2-0ubuntu0.22.04.1+rkmpp20221203, 7:4.4.2-0ubuntu0.22.04.1+rkmpp20230207), libavformat58:arm64 (7:4.4.2-0ubuntu0.22.04.1+rkmpp20221203, 7:4.4.2-0ubuntu0.22.04.1+rkmpp20230207), libavformat-dev:arm64 (7:4.4.2-0ubuntu0.22.04.1+rkmpp20221203, 7:4.4.2-0ubuntu0.22.04.1+rkmpp20230207), libavcodec-dev:arm64 (7:4.4.2-0ubuntu0.22.04.1+rkmpp20221203, 7:4.4.2-0ubuntu0.22.04.1+rkmpp20230207), libswresample-dev:arm64 (7:4.4.2-0ubuntu0.22.04.1+rkmpp20221203, 7:4.4.2-0ubuntu0.22.04.1+rkmpp20230207), libavfilter7:arm64 (7:4.4.2-0ubuntu0.22.04.1+rkmpp20221203, 7:4.4.2-0ubuntu0.22.04.1+rkmpp20230207)

Only sharing what I managed to make working on the Orange Pi5: a Tvheadend server with satellite cards TBS 5527 and TBS 5520se. The rough path I followed: - recompiled the kernel in order to have "Linux tv" as a module (CCONFIG_DVB_CORE=m). This will be replaced by the tbs driver in next steps. - installed TVheadend from the armbian-config - compiled tbs drivers by following standards instructions....but: - had to add a CFGLAGS += -w to avoid some warning stopping the build (Makefile in the v4l directory) - had to disable the creation of the mc.ko (MEDIA_CONTROL) to avoid conflict with kernel built-in module (not sure why, but trying to rebuild the kernel with "Media support" as a module was causing some compilation errors dealing with a samsung chip in the RK5588s). That is it, hope it will helps the ones wondering like myself whether it would work or not.

Just interested if anyway has being able to set this up in Armbian yet? I had a brief look this morning but couldn't get it to work.

Processing triggers for initramfs-tools (0.140ubuntu13.1) ... ln: failed to create hard link '/boot/initrd.img-5.10.110-rockchip-rk3588.dpkg-bak' => '/boot/initrd.img-5.10.110-rockchip-rk3588': Operation not permitted update-initramfs: Generating /boot/initrd.img-5.10.110-rockchip-rk3588 update-initramfs: Converting to u-boot format I am getting this error every time I do an apt upgarde. I am running on a 256Gb NVME drive and booting off of it with no problems. So does this error mean it's not actually updating /boot/initrd.img-5.10.110-rockchip-rk3588 ? The third line there makes me think that it just fails with the hard link and then generates the file instead. My google searching only led to instances where it couldn't do this because of partition format issues but that does not seem to be the case here. Is this a permissions issue? Is this even something that needs to be fixed for proper operation or can it be safely ignored. Thanks in advance for any help and thanks to the devs for their continued great work!

Hello, I have a problem with mounting a USB HD via fstab. If I enter the HD in the fstab, the system hangs when booting. The problem, USB is not activated yet and will be loaded later. If I remove the HD from fstab, it is automatically mounted under /run/media/USER. However, this must not be mounted under a user, but should be mounted as root. What can I do. Thanks very much

I am trying to build the kernel with the standards scripts, but directly on my orange pi 5. The build is stopping at some point because of a Warning issued by the compiler (this is the default behaviour for the compiler who does not tolerate any warning by default). (Some functions in the C code are depreciated, thus a warning is issue) How can I set the CFLAGS so that the kernel build takes it into account during compilation? Thanks.

I have an Orange Pi 5 (16GB RAM) running Armbian Jammy with the latest updates installed. I am booting from NVMe and when it boots successfully it runs flawlessly without issue. The problem occurs when I reboot -- the majority of the time it does not boot up successfully. Sometimes when it boots I only see the red light (and no green light), and other times I will see the green light flash like normal, yet the external hard drive does not spin up or mount properly. This results in me needing to power down the Orange Pi 5 and try again. Eventually it will boot up successfully (along with the external HDD) and then everything is good; that is, until the next time I have to reboot. A few details that might be helpful to know: I ordered the Orange Pi5 from Amazon and I'm using 5V4A Type C Power Supply that came with my device My os-release reports as: Armbian 23.02.0-trunk.0112 Jammy I'm booting from NVMe. (Samsung SSD 256GB PM991 M.2 2242 42mm PCIe 3.0 x4 NVMe MZALQ256HAJD MZ-ALQ2560 Solid State Drive) I have an external hard drive configured to automount to "/mnt/hdd" in fstab. I do not believe fstab is mis-configured because I've been using this same HDD with the same fstab entry for my old Raspberry Pi 4 and never had this issue. The Hard drive is a WD Elements 25A3 which has its own AC adapter Any ideas of what could be the culprit? I've looked in dmesg (from the successful boot) and dmesg.0 (from the previous unsuccessful boot) and did not see any glaring issues between the two.

I am trying to compile the Kernel on my PC with the Ubuntu recommended version. I get the error below: arch/arm/dts/rk3128-evb.dtb: Warning (avoid_default_addr_size): Relying on default #address-cells value for /syscon@20008000/usb2-phy@17c arch/arm/dts/rk3128-evb.dtb: Warning (avoid_default_addr_size): Relying on default #size-cells value for /syscon@20008000/usb2-phy@17c FATAL ERROR: Couldn't open "./u-boot.dtb": No such file or directory ./tools/mkimage: Can't read u-boot.itb.tmp: Invalid argument make: *** [Makefile:1053: u-boot.itb] Error 255 Any idea what this could be? It is the first time I am running ./.compile.sh potential-paths.log Thank you. == u-boot make orangepi_5_defconfig == arch/../configs/orangepi_5_defconfig:245:warning: override: reassigning to symbol CMD_SETEXPR == u-boot make BL31=/home/eric/installed/build/cache/sources/rkbin-tools/rk35/rk3588_bl31_v1.28.elf tpl/u-boot-tpl.bin spl/u-boot-spl.bin u-boot.itb BL31=/home/eric/installed/build/cache/sources/rkbin-tools/rk35/rk3588_bl31_v1.28.elf spl/u-boot-spl.bin u-boot.dtb u-boot.itb == .config:1667:warning: override: reassigning to symbol BOOTDELAY tools/rockchip/boot_merger.c: In function ‘mergeBoot’: tools/rockchip/boot_merger.c:700:43: warning: ‘%s’ directive output may be truncated writing up to 813 bytes into a region of size 5 [-Wformat-truncation=] 700 | snprintf(buffer, sizeof(buffer), "%s", chip); | ^~ ...... 742 | chipType = convertChipType(chip + 2); | ~~~~~~~~~~~~~~~~~~~~~~~~~ In file included from /usr/include/stdio.h:894, from ././include/compiler.h:25, from <command-line>: /usr/include/x86_64-linux-gnu/bits/stdio2.h:71:10: note: ‘__builtin_snprintf’ output between 1 and 814 bytes into a destination of size 5 71 | return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 72 | __glibc_objsize (__s), __fmt, | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 73 | __va_arg_pack ()); | ~~~~~~~~~~~~~~~~~ tools/rockchip/boot_merger.c: In function ‘main’: tools/rockchip/boot_merger.c:895:18: warning: array subscript 20 is outside array bounds of ‘char[20]’ [-Warray-bounds] 895 | str[len] = 0; | ~~~~~~~~~^~~ tools/rockchip/boot_merger.c:933:14: note: while referencing ‘name’ 933 | char name[MAX_NAME_LEN]; | ^~~~ tools/rockchip/bmp2gray16.c: In function ‘usage’: tools/rockchip/bmp2gray16.c:121:25: warning: ‘%s’ directive argument is not a nul-terminated string [-Wformat-overflow=] 121 | printf("Version %s (zwp@rock-chips.com)\n", version); | ^~ ~~~~~~~ tools/rockchip/bmp2gray16.c:109:19: note: referenced argument declared here 109 | static const char version[4] = "1.00"; | ^~~~~~~ arch/arm/dts/rk3126-evb.dtb: Warning (reg_format): "reg" property in /syscon@20008000/usb2-phy@17c has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1) arch/arm/dts/rk3126-evb.dtb: Warning (avoid_default_addr_size): Relying on default #address-cells value for /syscon@20008000/usb2-phy@17c arch/arm/dts/rk3126-evb.dtb: Warning (avoid_default_addr_size): Relying on default #size-cells value for /syscon@20008000/usb2-phy@17c arch/arm/dts/rk3128-evb.dtb: Warning (reg_format): "reg" property in /syscon@20008000/usb2-phy@17c has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1) arch/arm/dts/rk3128-evb.dtb: Warning (avoid_default_addr_size): Relying on default #address-cells value for /syscon@20008000/usb2-phy@17c arch/arm/dts/rk3128-evb.dtb: Warning (avoid_default_addr_size): Relying on default #size-cells value for /syscon@20008000/usb2-phy@17c FATAL ERROR: Couldn't open "./u-boot.dtb": No such file or directory ./tools/mkimage: Can't read u-boot.itb.tmp: Invalid argument make: *** [Makefile:1053: u-boot.itb] Error 255 make: *** Waiting for unfinished jobs....

I'm trying to setup LIRC on my OPI5 but I can't find any details on how that would be possible. I checked the kernel configuration and I cannot see any references to LIRC either. The module list has nothing obvious - is this feature completely disabled? Any suggested alternatives?

Hello All, Do you also have this kind of messages in syslog ? [ 1601.687044] ------------[ cut here ]------------ [ 1601.687070] WARNING: CPU: 2 PID: 112 at drivers/gpu/drm/rockchip/rockchip_drm_vop2.c:2986 vop2_crtc_load_lut+0x54/0x310 [ 1601.687075] Modules linked in: bnep zstd joydev sch_fq_codel fuse ip_tables ipv6 r8152 panfrost gpu_sched [ 1601.687114] CPU: 2 PID: 112 Comm: kworker/u16:1 Tainted: G W 5.10.110-rockchip-rk3588 #trunk.0184 [ 1601.687117] Hardware name: Orange Pi 5 (DT) [ 1601.687127] Workqueue: events_unbound commit_work [ 1601.687134] pstate: 40c00009 (nZcv daif +PAN +UAO -TCO BTYPE=--) [ 1601.687138] pc : vop2_crtc_load_lut+0x54/0x310 [ 1601.687142] lr : vop2_crtc_load_lut+0x4c/0x310 [ 1601.687145] sp : ffffffc012d0bbd0 [ 1601.687148] x29: ffffffc012d0bbd0 x28: ffffff812bbbc000 [ 1601.687155] x27: ffffffc01113d020 x26: ffffff821141aa00 [ 1601.687162] x25: ffffff82108a0058 x24: ffffff81053b2080 [ 1601.687168] x23: 0000000000000400 x22: ffffffc011598cf8 [ 1601.687175] x21: ffffff81053b0080 x20: ffffff81053b0080 [ 1601.687182] x19: ffffff81053b00f8 x18: 0000000000000000 [ 1601.687189] x17: 0000000000000000 x16: 0000000000000000 [ 1601.687195] x15: 0000000000000010 x14: 0000000034325258 [ 1601.687202] x13: ffffffc012d0bb98 x12: ffffffffffffffff [ 1601.687208] x11: 0000000000000040 x10: 00000000fffffffe [ 1601.687214] x9 : ffffffc0107e6030 x8 : 0000000000000000 [ 1601.687221] x7 : ffffff81053d0080 x6 : 00000000000003ff [ 1601.687227] x5 : 0000000000000400 x4 : 00000000000003ff [ 1601.687233] x3 : 000000003fffffff x2 : 00000000000003ff [ 1601.687240] x1 : ffffffc012d05000 x0 : 0000000000000000 [ 1601.687247] Call trace: [ 1601.687253] vop2_crtc_load_lut+0x54/0x310 [ 1601.687258] vop2_crtc_atomic_flush+0x948/0xc18 [ 1601.687262] drm_atomic_helper_commit_planes+0x1c0/0x1c8 [ 1601.687269] rockchip_drm_atomic_helper_commit_tail_rpm+0xa4/0x144 [ 1601.687273] commit_tail+0x80/0x108 [ 1601.687277] commit_work+0x1c/0x28 [ 1601.687283] process_one_work+0x1d8/0x290 [ 1601.687287] worker_thread+0x1e0/0x270 [ 1601.687293] kthread+0xf4/0x104 [ 1601.687299] ret_from_fork+0x10/0x30 [ 1601.687302] ... followed by large dump in hex I really don't have any clue of where it may come from. I'm using the Armbian 22.11 Jammy Gnome Release date: Jan 23, 2023, and I unfreeze nighlies to have latest kernel updates/testings : Linux orangepi5 5.10.110-rockchip-rk3588 #trunk.0220 SMP Tue Jan 31 16:58:49 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux All seems to be working just fine. I would just like to report. thanks !

There is no Orange Pi 5 results yet, but we can see already results of RK3588S. https://github.com/ThomasKaiser/sbc-bench/blob/master/results/Sorted-Results.md

Hello, finally I have time to play with my OPI5, first thing I tried is to install on USB-C, but the port doesn't seem to work. Then I tried to install using USB3 port, on a ssd drive. The armbian-install utility seems to do the job and after installing the bootloader on mtdblock0 I powered off. At reboot everything is like before: if I remove the sd card the systen won't boot. If I boot with the sd card inserted the root partition is on /dev/mmcblk0p2 First thing that came into my mind is to mount SPI and check if bootloader is ok, but I'm unable to mount it: ~# mount /dev/mtdblock0 /mnt/spi mount: /mnt/spi: wrong fs type, bad option, bad superblock on /dev/mtdblock0, missing codepage or helper program, or other error. How can I debug the whole process?

I want to install Armbian on Nvme SSD. How do I install on SSD?

I know this driver should be part of the recent kernel releases (and definitely avail for 5.10) but I am not sure how/why/where this driver would be in the armbian release. I also did install the firmware files but I don't see the module in the /usr/lib/module section. Any suggestions to build or enable this driver? Thanks

Hi there, Just got Orange Pi 5 8GB and have no idea where to begin. I have a microSD card available, but no writer. I had the idea to boot from USB thumbstick and then write the SD card using the port on the Orange Pi 5, then I can boot from SD card. Is this possible? What image and method do I need to follow in order to boot from a simple 32GB USB Sandisk thumbstick? Thank you!

I saw that you now have a stable release of armbian for opi5. I installed Armbian 23.02.0-trunk.0112 Bullseye a week ago. Now I'm wondering if it is possible to switch back to the stable version without reinstalling the system. The OPI is now running in production and I have several containers running on it. This is what I tried -> armbian-config -> system -> nightly after that back to stable -> armbian-config -> system -> stable ->armbian-config -> system -> other -> linux-image-legacy-rockchip-rk3588=22.11.4 But after login I always see: Welcome to Armbian 23.02.0-trunk.0112 Bullseye with Linux 5.10.110-rockchip-rk3588 No end-user support: work in progress Is something bad about this? Do I receive updates with this settings? Thank you, Nico

I did a bit of reading - to prevent ubuntu packages to update the rockchip optimized packages, you need to pin the packages. There is a simple way to do that. 1. Create a file called rockchip-multimedia-ppu in /etc/apt/preferences.d with Package: * Pin: release o=LP-PPA-liujianfeng1994-rockchip-multimedia Pin-Priority: 600 2. Create a file called panfork-mesa-ppu in /etc/apt/preferences.d with Package: * Pin: release o=LP-PPA-liujianfeng1994-liujianfeng1994-panfork-mesa Pin-Priority: 600 You can verify that the apt configuration is working correctly with sudo apt policy chromium-browser which should return chromium-browser: Installed: 1:105.0.5195.125-0ubuntu1~jammy~rkmpp20221209 Candidate: 1:107.0.5304.62-0ubuntu1~ppa1~22.04.1 Version table: 1:107.0.5304.62-0ubuntu1~ppa1~22.04.1 500 500 http://apt.armbian.com jammy/jammy-desktop arm64 Packages 500 http://ppa.launchpadcontent.net/saiarcot895/chromium-beta/ubuntu jammy/main arm64 Packages *** 1:105.0.5195.125-0ubuntu1~jammy~rkmpp20221209 400 400 https://ppa.launchpadcontent.net/liujianfeng1994/rockchip-multimedia/ubuntu jammy/main arm64 Packages 100 /var/lib/dpkg/status 1:85.0.4183.83-0ubuntu2 500 500 http://ports.ubuntu.com jammy/universe arm64 Packages

Has anyone tried GPIO access on the latest armbian? I noticed that the custom wiringPi https://github.com/orangepi-xunlong/wiringOP.git doesn't compile on armbian. It is missing GPIO constants.