OttawaHacker

Did more reading and the docs mention that overlays are a WIP not available for all boards... Going to assume that overlays with this version do not exist? I was originally thinking of using armbian on all my boards but it looks like the rpi4 build might be behind features compared to official ubuntu - going to assume several features are missing since hardware menu is not there... Is that an actual fact?

The `hardware` menu is missing on the current build - so been trying to manually install spidev module. I did add the following lines to armbianEnv.txt but I don't see anything yet in /dev/spi* overlays=spi-spidev param_spidev_spi_bus=0

In the most recent builds, the kernel logs have been flood with Mar 02 21:31:38 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Unsupported format modifier 0x800000100000351 Mar 02 21:31:38 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Unsupported format modifier 0x800000100000351 Mar 02 21:31:38 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Unsupported format modifier 0x800000100000351 Mar 02 21:31:38 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Unsupported format modifier 0x800000100000351 Mar 02 21:31:38 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Unsupported format modifier 0x800000100000351 Mar 02 21:31:38 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Unsupported format modifier 0x800000100000351 Mar 02 21:31:38 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Unsupported format modifier 0x800000100000351 Mar 02 21:31:38 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Unsupported format modifier 0x800000100000351 Mar 02 21:31:38 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Unsupported format modifier 0x800000100000351 Mar 02 21:31:38 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Unsupported format modifier 0x800000100000351 Mar 02 21:31:38 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Unsupported format modifier 0x800000100000351 Mar 02 21:31:38 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Unsupported format modifier 0x800000100000351 Mar 02 21:31:38 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Unsupported format modifier 0x800000100000351 Mar 02 21:31:38 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Unsupported format modifier 0x800000100000351 Mar 02 21:31:38 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Unsupported format modifier 0x800000100000351 Mar 02 21:31:38 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Unsupported format modifier 0x800000100000351 Mar 02 21:31:38 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Unsupported format modifier 0x800000100000351 there are no issues with the opi itself beside these log messages... any way to remove them?

Figured it out - the permissions/groups changed somehow. Also the update brings its own udev - the udev rules is not necessary anymore. Neither is the device creation... That's a solid release! sudo usermod -a -G video <username> - fixed the h264 mpp service sudo usermod -a -G netdev <username> - prevents popup for wifi sudo usermod -a -G bluetooth <username>

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?

Haven't found any threads here for setting up libwidevine on armbian. Has anyone had any luck setting it up on armbian 64 bit? I've seen sone snaps and on the raspberry pi OS, they have a package for chromium 32 bit (since there is no libwidevine 64bit yet). Any suggestions?

Btw the library above is the same as the RPI4 one... All the GPIO tools seem to be forks of the rpi ones.

This repo is missing the support for OPI 5. You have to download the code from the link I posted above to get the GPIO working. I started working on a ppa repo and cloning their repo but did not finish that stuff yet... not too familiar with the debian packaging system

In that case, I'd recommend a raspberry pi board or arduino for getting familiar with GPIO - the Orange Pi 5 is pretty much bleeding edge, and all the GPIO stuff is rather experimental. Probably going to be different in few months but right now the GPIO support is quite limited. Also most of the GPIO tools were designed originally for the RPi board.

All you need to do is unfreeze and enable nightly in armbian-config. Enable nightly will run all the apt updates for you. This should update you to 5.10.110-rockchip-rk3588 #trunk.0211 SMP Sat Jan 28 03:01:04 UTC 2023 aarch64 aarch64 aarch64 GNU/Linu which has a bunch of USB modules enabled

You'll find them on this link Official Tool - Google Drive - this link is in the section "Official tools" from the orangepi.org / Download I'm would like to make them a package so that they can be installed more easily.

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.

Do you guys know how reliable the chrome://gpu is? Mine says that hardware video decoding is enabled - I don't get the great 14% cpu usage that @royk gets but the machine plays 4k videos without any hickup with ~ 60% cpu which is imo already fast.

After following all the threads - the panfork drivers, there is somekind of back story with the author of the drivers... I can understand that the armbian community wants to separate themselves, but I'm not sure how much practical difference there would be if the software menu had a clear option to install the panfork drivers (at your own risk and put more context) vs advertising the ppa repo in the landing. Sadly I'm not sure end users have options for mesa drivers right now. For the multimedia ppa - these packages originate from an engineer from rockchip - my understanding is that it is a different story. Is there any specific reason for that PPA? IMO the multimedia one should be optional since it has a modified version of chromium, there could be legitimate security reasons someone doesn't want to install that (esp since that chromium is going to stay behind in versions).

Wow that ansible collection is amazing - any chances some of these features could be contributed into the current armbian-config features? Would be nice for inexperienced users to have a simple "Install hardware acceleration and optimized Chromium browser" in software category

I might have this one figured out... @royk do you mind confirming *which* tool you used to monitor the CPU when you play videos in Chromium? One thing I just realized is that every linux tool has a different opinion - I've been using the antique top tool but that one is only scaled to *one* core (aka CPU utilization can reach 400%) where as other system tools do account for cores... So the whole time - my videos have been consuming only 30% of one core. Even my 4k test video does 30% of one core - no matter which player I use... So either the hardware encoding is working or this board is insanely fast (both are possible).

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

Hold on want to make sure I understand - are you referring to the branch armbian-next in the git repo? That branch is quite a bit behind the master branch - or what is that 'next' you are referring to?

Forgot to mention these - I have all of that as well. I have all package from both ppas installed.

I'm really struggling to get chromium to work correctly with hardware acceleration. 1) I have custom kernel image from master branch last week. Which maybe could cause some issues? 2) I added the two repos (panfork and mesa) sudo add-apt-repository ppa:liujianfeng1994/panfork-mesa sudo add-apt-repository ppa:liujianfeng1994/rockchip-multimedia 3) I've ran all the updates 4) I installed ubuntu desktop to enable Wayland which is working nicely 5) I've added the HDMI audio output 6) My default chromium configuration does already have the egl enabled. When I start Chromium, I get the following errors 39610:39643:0125/091804.694008:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/portal /desktop: org.freedesktop.DBus.Error.InvalidArgs: No such interface “org.freedesktop.portal.FileChooser” [39610:39643:0125/091804.694207:ERROR:select_file_dialog_linux_portal.cc(242)] Failed to read portal version property libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) [39655:39655:0125/091804.826811:ERROR:gpu_init.cc(537)] Passthrough is not supported, GL is egl, ANGLE is [39655:39655:0125/091804.829891:ERROR:gl_display.cc(508)] EGL Driver message (Error) eglQueryDeviceAttribEXT: eglQueryDeviceAttribEXT [39655:39655:0125/091804.830069:ERROR:gl_angle_util_vulkan.cc(189)] Failed to retrieve vkGetInstanceProcAddr [39655:39655:0125/091804.830187:ERROR:vulkan_instance.cc(91)] Failed to get vkGetInstanceProcAddr pointer from ANGLE. [39655:39655:0125/091807.500915:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times! [39655:39655:0125/091809.004733:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times! [39655:39655:0125/091829.513030:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times! I cannot figure out the "Passthrough" error. Sounds like egl should be enabled... What am I missing? libva error - this is usually because there is no LIB_VA - but from what I've seen there is no lib va available for Orange PI 5. Correct or am I missing something?

I did compile the master branch. I suspect the GPIO constants come from additional custom files from OrangePI custom kernel... I haven't figured out where they have their source code but was going to dig more into the issue. Is there any repo I could just pull the most recent kernel packages from CI pipeline?

I think you are going the complex route. The armbian build system is incredible, all you need is setup a VM with ubuntu and the build system will generate a custom image with your kernel customizations. Please submit a PR if you can validate the build and hardware - this distribution needs more modules. I recently submitted a PR that got accepted for MediaTek USB devices.

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.

I am not sure there is a vlc version in the panfork driver repo. I have the default VLC media player 3.0.16 Vetinari (revision 3.0.13-8-g41878ff4f2) installed - that one is actually complaining about Wayland support but even after installing the required qt stuff, there is no difference. For Chrome, I was missing the version from the ppu however even after that, I am not having any luck getting video accelleration there. After installing the panfork version, I am not getting green screens anymore for youtube, the videos play smoothly but cpu is skyrocketing. Wondering what I might be missing from your setup. I followed all your other steps. To note, Wayland makes a huge difference on this box. It is surprising how snappy the UI becomes after installing the ubuntu desktop compared to the default cinnamon one. This ubuntu desktop should be a default.

I found this amazing page https://linux-sunxi.org/Sunxi-Cedrus#VLC that explains alot on VLC and hardware accelleration but I cannot clearly figure out if my playback is using hardware acceleration. I did follow all the steps to optimize chromium with the ppu sources - chromium doesn't work well yet for me - so not sure if that install worked as expected. My playback of h264 in VLC is super smooth but I have around 20-35% cpu usage (1080p videos) - I know h264 is more demanding than AV1 but someone reported AV1 with 15% CPU usage and 4k. Is there anything I can do to make sure the hardware acceleration is working (aka the VA-API is used)?