All Activity

Thank you.

Hi there, I'm currently working on installing armbian onto my h96 max tv box (labelled as an rk3318 externally and in software, but the internal board is marked as an rk3328), and like many others here, I am having difficulty getting hdmi to work using the rk3318 build found at https://github.com/armbian/community/releases. I can access and control the box over ssh either over ethernet or wifi once configured, however I definitely need functional hdmi output for the use case of this device. The hdmi output works perfectly fine in both the bootloader, the stock android OS, and the bootable multitool, but once armbian boots, I completely lose hdmi signal on a standard 1080p monitor. My linux experience is intermediate at best (I daily drive Mint and am not very familiar with in-depth hardware configuration like armbian requires), so I am looking for assistance with a few things: I'd like to confirm that I am indeed meant to use the rk3318 build and not the rk3328 one, as while both the device case and the output of cat /proc/cpuinfo claim that this device has an rk3318, the marking on the board states it is an rk3328. I would rather not remove the heatsink to check the chip's markings directly, as I doubt that I have the means to reattach the heatsink once it is removed. If there is another recommended build that has working hdmi for this device or would perform better, please let me know. When/if I am on the right image/build for this device, I unfortunately do not have much knowledge on how hdmi would be enabled/initialised. I have seen others in this thread mentioning doing so, but i cannot find any mention of how this is done. Assuming hdmi is eventually functional, I did have a look through the different options in rk3318-config and armbian-config, but I am unsure how to best use the information printed on the board to select the optimal options in these tools for my system. The wifi did work without needing to select anything special, which is good. I did not test bluetooth or notice the front LED panel working at all, though. Thank you in advance for any help you can provide, and thanks to Jock for porting this neat little distro to this hardware. It's been fun to tinker around with so far. Attached are images of the board and label, and I can provide any other images or output of commands if further information is needed.

@psygnosis Can you run "armbianmonitor -m" (as root) to see what the processor speed and system load is when you are experiencing the high temperature. I found an old distro and loaded it on my test system and the temperature did not change: Welcome to Armbian 22.11.1 Bullseye with Linux 5.15.80-sunxi System load: 10% Up time: 5 min Memory usage: 14% of 491M IP: 192.168.1.69 CPU temp: 49°C Usage of /: 1% of 109G sysadmin@orangepione:~$ sudo armbianmonitor -m Stop monitoring using [ctrl]-[c] Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St. 16:09:02: 816MHz 0.18 15% 3% 7% 0% 3% 0% 49.9 °C 0/4 16:09:07: 816MHz 0.16 1% 1% 0% 0% 0% 0% 45.6 °C 0/4 16:09:12: 648MHz 0.15 1% 0% 0% 0% 0% 0% 46.0 °C 0/4 16:09:17: 648MHz 0.14 1% 0% 0% 0% 0% 0% 45.6 °C 0/4 16:09:22: 648MHz 0.12 1% 0% 0% 0% 0% 0% 45.6 °C 0/4 16:09:27: 816MHz 0.11 1% 0% 0% 0% 0% 0% 45.8 °C 0/4

Hi @coroner21, Can you share some pics of the Helios4 you have? Thanks, Groetjes,

Any way to use this to set up HW-ACC in jellyfin? I would like ti be able to perform audio transcode/remux

It looks like my test system just runs a little hotter, probably because it is in a case. I took the SD card out of the test (hot) system and put it in the operational system and the operational system still ran cool. So it is not the os. Changing to noble from bookworm made no difference in the running temperature.

@ScoreABSM https://github.com/pyavitz/binary/releases/download/images/Armbian-unofficial_25.08.0-trunk_Bananapim4zero_trixie_current_6.12.35.img.xz

Confirming that reversing the USB-C connector fixed the issue for me too. On official firmware it wasn’t needed, but on Armbian 25.8.0-trunk.322 (6.1.115-vendor-rk35xx), the device was only detected as USB 2.0 until I flipped it.

Arm Neon is quite a thing, SIMD https://developer.arm.com/documentation/102159/latest/ https://github.com/thenifty/neon-guide and accordingly aarch64 (e.g. Cortex A53, A55, A72, A75, A76 etc etc i.e. arm V8a onwards have them) https://developer.arm.com/documentation/102474/0100/Fundamentals-of-Armv8-Neon-technology the H618 is an A53 and hence should have it. it is a good 'replacement' for proprietary hardware etc as this like Intel's sse, avx , simd are defiined and standardized by Arm. Hence, they'd work if programs are coded and compiled to use them. Accordiingly, the pripietary video hardware is still undocumented (at least not publicly accessible), and most of that works are reverse engineered and incomplete. apps written to use Neon SIMD would however 'just works' and accelerated by virtue that it is SIMD.

Hi @c0rnelius, Sorry I was not clear enough, could you share with me an image to test including BT (the 2 patches removed and using your own defconfig)? Denis

Works with an apt update && upgrade. missing DTB is present, and boots ok. Thank you for the fast fix team.

Thank you for the solution!!! I struggled for days on this.

I finally got around to trying things out again. Here is the armbianmonitor -U (https://pastebin.com/7GUqZ2aP) before upgrading/updating on the 21.05.1 release. Setup a swap and going to try the upgrade now.

Just wondering if anyone would be interested in running a helios4 NAS still today? Or maybe you might need a spare board as a potential replacement? I have a decommissioned one at home that has been replaced with an x86 machine. The helios4 still works just fine and it would be quite a waste to just throw it away. It is the full kit: Case, board, cables and power adapter. Happy to send it (I am based in Germany) to whoever wants it as long as you cover the cost. Please send me a direct message if interested, thanks!

Thank you for replying. I run xscreensavers-gl in a window and it always gets 30FPS with <10% CPU in my opiz3, I even show 3D models in F3D... so I am getting 3D MESA acceleration in HDMI and SPI-LCD displays. If the video decoding in my opiz3 is using ARM NEON instructions, then I am fortunate I have that, at least (note: this is possible without needing ffmpeg-v4l2request) I will have to re-check how I was successful with 1080P H264 acceleration last year (I was even getting temporary glitches and pink hues sometimes).

Ok, I finally built armbian 25.5.1, to get Linux-edge 14.7 Bookworm + XFCE for my opiz3... and this time copy/pasted the whole build log to verify that: * the new patches mentioned in Pull Request 8086 were applied * the affected C files are compiled to .o files And then I tried the new ffmpeg-v4l2request with Bookworm's MPV, following the instructions in the original post.... I got the same result: 1080P plays smoothly, but with 100% CPU in all 4 cores. There's no error message of "unsupported hwdec=drm"... but there isn't any confirmation message from MPV either. (same behavior as with plain ffmpeg, from previous experiments)

Okay partially solved, its the Linux rockchip64 kernel version. On 6.12.32-current-rockchip64 the display is failing, 6.12.22-current-rockchip64, and 6.12.17-current-rockchip64 the display is working fine. 6.15.1-edge-rockchip64 is also working fine. 6.16.0-rc3-edge is not even booting, with BananaPi-M7. @amazingfate Would it be possible to look into this please.

Hi Guillame, unfortuantely there is a file size limit and my SD image breaks the upload limit. If you dm me your email address I can look to send you the image via wetransfer or something similar. Kind regards, Mark

If you plan to start from scratch and you don't want to wait hours until repository is updated, yes, rather download and use latest image. Upcoming fix will solve this problem for everyone that still use old image.

Or should I download a new .img image and re-flash ?

Ok, thanks all for your feedback. I will wait a few hours and try an apt update & apt upgrade, and let you know.

Packages are in the update process - few hours from now it will be ok.

Have the same issue, who has a ideas ?

You could attempt to recover ur current install by adding the required DTB to the SDCARD and see if the unit boots. Once booted, mount the eMMC and again copy the DTB to the required dir. DTB DIR: /boot/dtb/rockchip/ rk3566-nanopi-r3s-lts.dtb

According to ur log. It's pulling down an older kernel. This kernel does not have the DTB required so it's failing to boot. After purging the kernel on the current IMG available and installing the kernel from apt. https://paste.armbian.com/orokufexik The result is a missing DTB. root@nanopi-r3s-lts:~# ls /boot/dtb/rockchip/rk3566-nanopi-* /boot/dtb/rockchip/rk3566-nanopi-r3s.dtb