All Activity

TLDR; yes upping 75mV helps drastically, but is not enough at least for all frequencies. Indeed, before upping by 75mV I could not boot most of the time (only "emergency" mode boot was reliable, ie no raid10 and services off). But it seems 75mV is not enough to compensate for the issue at stake all the time. The thing is I don't know what the root issue upping 75mV workaround is. Could be 100mV is enough, but this is a value based on testing, not a theory that requires 75mV (could be the proper value is upper or could be upping the voltage only helps to cope with voltage drops, making them less frequently drop below a certain value where cpub crashes). The datasheet for the cpub regulator requires a bigger capacitor on voltage input than the helios64 one. But the weird thing is most rk3399 boards also use the same weak below-spec capacitor value at this place. At my level (without understanding the hardware interactions or barely) the next step would be to test if my test case also crashes these other boxes with the same vin too low capacitor ... if they crash we could guess that the design is bad and without a bigger capacitor the regulator cannot deliver the voltage for cpub reliably. Could be we could workaround this in software, but I am not qualified to tell that, at least at this point (I read about how these components work, but I am not an expert. Mind also I tested the board way less for the time to come as now that it is quite reliable I started using it again (been down for months, then I extracted the motherboard to test with the less complex setup possible, in emergency mode). NB: upping the voltage makes the CPU hotter, you might want to check the temperature values (with "sensors"). Mine were fine, way below the throttling temp of 80°C for the rk3399. Even with all opp3 and above at 1.2V. The issue seems mostly of keeping the power consumption low. But I wonder if it has a noticeable effect on helios64 power consumption.

Also Runing android APK's on H96 Max with this waydroid image: https://forum.armbian.com/topic/38184-waydroid-for-rk3588-with-armbian-edge-panthor-kernel-68/#comment-188934 No Vaapi on android video players.... Next try: Wine + Vulkan https://www.cnx-software.com/2021/03/29/panvk-panfrost-vulkan-driver/ https://archlinuxarm.org/packages/aarch64/vulkan-panfrost https://linuxconfig.org/improve-your-wine-gaming-on-linux-with-dxvk https://linuxhint.com/enable-vulkan-rendering-in-wine-games/ https://www.cnx-software.com/2023/07/21/arm-panfrost-is-now-the-gpu-driver-for-the-linux-community/

Testing this lineage on RK3566 h96 max No VAAPI No youtube

If the image would have been made by us its download would be either from armbian.com or https://github.com/armbian/community/ or https://github.com/armbian/os and not from some random baidu/google drive.

the question concerns the Armbian system. I don't know who made this image. Maybe one of you? I don't know.

I suggest to ask at the place where you got the image from. There no way we could tell in which way the source has been modified to create it.

Google Chrome and other Chromium-based web browsers now have VA-API support by default. However, it's not enabled by default. Verifying VA-API https://www.linuxuprising.com/2021/01/how-to-enable-hardware-accelerated.html https://www.linuxuprising.com/2018/08/how-to-enable-hardware-accelerated.html also https://wiki.archlinux.org/title/Chromium#Hardware_video_acceleration For browsers based on Google Chrome 90 and older: For browsers based on Google Chrome 91 and newer (there's no hardware-accelerated video decode any more, but we'll need to use a new command line flag - see step 4): ~/.config/chromium-flags.conf --disable-sync-preferences --no-startup-window --ozone-platform=wayland --ignore-gpu-blocklist --enable-zero-copy /etc/chromium-browser/customizations/92-vaapi-hardware-decoding https://www.linuxuprising.com/2019/01/ubuntu-testing-chromium-snap-with-vaapi.html sudo snap install --channel=candidate/vaapi chromium sudo snap install --channel=candidate/vaapi chromium chrome://media-internals Testing: https://mdn.github.io/dom-examples/webgl-examples/tutorial/sample4/ https://mdn.github.io/dom-examples/webgl-examples/tutorial/sample5/ https://mdn.github.io/dom-examples/webgl-examples/tutorial/sample6/ https://mdn.github.io/dom-examples/webgl-examples/tutorial/sample7/ https://mdn.github.io/dom-examples/webgl-examples/tutorial/sample8/

Hello RuDy_74 I try to do same (armbian on Bqeel K12pro S912) and thank you for yours posts. Some directory or links are deads. Can you resume whitch img and dbt files you used for working fine and install home assistant ? Thank you. PS: sorry for my poor english. brant : Bqeel model : K12 Pro CPU : Amlogic S912 Octa core ARM, Cortex-A53 64 bits – Maximum 2 Ghz GPU : Mali T820MP3 mother board : q201_9377 RAM 2 Go DDR3 ROM : 32 Go eMMC Ethernet Gigabit 100/1000M Wifi : b/g/n/ac – 2,4 & 5 Ghz Bluetooth : 4.1 Micro-SD : maximum 32 Go 2x USB 2.0 ports Android 6.0 (Marshmallow) mother board recto verso (left is left, top is bottom, right is right, bottom is top)

in this case, i think rk3528.dtb was on boot partition. Can you share the: $ lsblk $ df -h $ blkid

Hello I have got the LEMFO RBOX HK1RBOX with rk3528 (https://de.aliexpress.com/item/1005006654505780.html?spm=a2g0o.order_list.order_list_main.32.7cbf5c5fIj4Quv&gatewayAdapt=glo2deu) Is there any img and dtb, that works with this TV-Box. I tried Armbian_24.5.0_rockchip_h28k_jammy_5.10.160_server_2024.04.25.img.gz from ophub with rk3528-hlink-ht2.dtb, unfortunately the LAN did not work, even with all rk3528 dtb's I have tried the image recommended above https://github.com/armbian/community/releases/download/24.5.0-trunk.367/Armbian_community_24.5.0-trunk.367_Hinlink-ht2_bookworm_legacy_5.10.160_minimal.img.xz but I was lost, since the folder structure is different from the ones I am familiar with. I copied the rockchip folder to the boot folder and as well the a armbianEnv.txt adding dtfile=rockchip/rk3528-hlink-ht2.dtb. The original armbianEnv.txt was modified the same way. that did not work. Did you miss any other steps? I would appreciate any hint?

We dont know what resolution are you decoding but 1440p is something hantro cant do. Maybe 720p upscaled to 1440p. If that is the case you CPU usage is in concordante with VPU decoding.

Updated: The Armbian vendor kernel version now includes Panthor, and will soon be able to run it as well. Waydroid images: https://github.com/WillzenZou/armbian_fork_build/releases/download/willzen-armbian-24.5.0/2.waydroid-panthorv10-240416-v1.img.tar.gz Note: Waydroid needs to be run in the Wayland desktop environment. (Such as Gnome wayland, KDE wayland session) What's work: OpenGL ES is ok, I have tested some game: Mincecrat, gameSHINE, Monument Valley 2 What's not work: Vulkan. Video hardware decode and encode. How to use Waydroid 1. To install Waydroid, refer to the tutorial : https://docs.waydro.id/faq/using-custom-waydroid-images https://docs.waydro.id/usage/waydroid-command-line-options sudo apt install curl ca-certificates -y curl https://repo.waydro.id | sudo bash sudo apt install waydroid 2. Extract Waydroid system image waydroid-panthorv10-240416-v1.img.tar.gz to /usr/share/waydroid-extra/images and initialize it, there are system.img and vendor.img in it sudo waydroid init -f -i /usr/share/waydroid-extra/images 3. Other more useful parameters that need to be operated after waydroid session start Enable/disable multi-window: waydroid prop set persist.waydroid.multi_windows true waydroid prop set persist.waydroid.multi_windows false Install and start the app (also visible in the app menu after installation): waydroid app install com.app.apk waydroid app launch com.app List of apps: waydroid app list source code(needs morre work): https://github.com/WillzenZou/android_external_mesa3d

Hello I have installed this.: https://forum.banana-pi.org/t/banana-pi-bpi-m6-synaptics-vs680-sbc-new-image-fixed-voice-issue-when-play-video/17788 My question is .:what is the real cpu frequency? None of software show it. Cpu is very hot 70-80 celsius degree.

I have install armbian version 10 on this box. Did watch video for some time, no issues except remote who do not only mine box but satelite receiver also, and this do then crash. I have a new remote who can be adjusted on mucho boxes and dvd, tv enc. but did not manage to let it work on this RT box (mxq pro). Oke I did watch video and encode some in H265, but get not such small files als with H264 in handbrake, I do use hardware encoding with videocard, I need stil to install new computer board with a intel I7 but has not yet the time so I can try the intel hardware encoder who seems to be better... The video has much artifacts, special color screens and darknes, clouds. The videobox I have for years now the Elvira Xtreamer has not this artifacts on that same encoded H264 video while armbian has, The RT29** box do have a lot artfacts in dark scenes, sound do loud bang in the amplifier when boot, need to watch out with this, but that is not because of armbian but hardware of these cheap boxes.. Short, the H265 decoder on chip does a bad job, or the version of armbian has issues, and then I think special with the videoplayer, I can also just have 1280 x 720 max in armbian setup, or there is a software active who recode video on the fly for adjust screen dimensions?. I do not now. someone has experience with this?. regards

@Deoptim@maka I tried it your way and that is installing chromium via the snap - actually installed version 123 as it GitHub thread states that since version 121 all changes are mainstream. I also added these rules to 70-snap.chromium.rules: SUBSYSTEM=="video4linux", ATTR{name}=="rockchip,rk3568-vpu-dec", SYMLINK+="video-dec%n" SUBSYSTEM=="media", ATTR{model}=="hantro-vpu", SYMLINK+="media-dec%n" I tried to run chromium with a flag --disable_webgpu_shared_images=1 and the chrome://gpu still reports WebGPU and Vulkan as disabled. I am not completely sure if this is ok or not, but video playback was quite ok (once the page loads) and full-screen playback (1440p) is between 35-50% on all cores. To double check everything I only recently enabled the vpu node in the device tree and I did not spend any time investigating this at that time, is this enough for the mainline drivers or do we need to add different codecs as well? &vpu { status = "okay"; }; about-gpu-2024-04-27T12-05-58-533Z.txt

Seems that you want to try to use mpp with mainline kernel. That's not possible. The chromium PPA is for legacy kernel and dtb. In mainline kernel there is an VPU driver called hantro for rk3566 that works.

you want to add a 2 pin fan to opi5, unfortunitly, PWM port is IO port, it doesn't have enough power to driver your fan, thus would break the GPIO bank, and make whole bank unfunction. thus suggest to directly use 5V power pin. if you have 3 pin fan, you can use a PWM pin to control it speed. in this case, you need write dts code to enable it.

For chromium browser you need to create udev node: https://github.com/saiarcot895/chromium-ubuntu-build/issues/65#issuecomment-1793738401

Hi @SteeMan, is official support back for orange pi zero? Not long ago the releases page clearly indicated CSC support but now I read standard support. The kernel I had problems with was 6.6.16 and now I see 6.6.20 available, who knows if they have solved the temperature problem with the new kernel.

Thanks. Just to be clear, that's the rkvdec from staging drivers, right? It overrides hantro for H.264? Oh and I'm assuming the reason hantro H.264 is disabled is rkvdec offers better performance. Is that right?

Since userspace cannot sensibly select between two decoder instances of the same type, the H.264 hanto decoder is usually disabled for the rk3399 and the H.264 rkvdec is preferred. videoX-infos-nanopc-t4.log

Turns out it was a device tree problem. After updating the device tree, I can see the nodes set up by the mainline Rockchip hantro-vpu and rkvdec modules: /dev/video0: rockchip-rga /dev/video1: hantro-vpu (encoder) /dev/video2: hantro-vpu (decoder) /dev/video3: rkvdec

I tried the install package from this PPA , but it is a rather old version (114.x). As I can tell I think there is HW acceleration active. I am enclosing the whole dump of chrome://gpu. The system only reports that WebGPU and video_encode are disabled - the latter I think is clear as there is no DTB tree pointing to the hw codecs (yet). Lets see what you version will bring as you need to recompile the whole thing. I will try with firefox now. chromeReport.log

I'm using vl42-ctl to query the kernel directly through ioctls, so these decoders should show. The only other thing is no more than 2 nodes are created: /dev/video0 and /dev/video1. Could it be a udev thing?