greenais

Yes, but since this created device isn't mounted anywhere it makes no sense - no service or whatever could use it anyway, what definitely turns this creature into just waste of RAM for nothing, am I wrong?

You are completely right - at least 50MB one is there /dev/zram1 on /var/log type ext4 (rw,nosuid,nodev,noexec,relatime,discard) But big 987MB /dev/zram0 isn't at all - so it looks like it's useless and could be removed from zram config, right? Both mystic /dev/mmcblk2bootX are still in question

In fact in image's default fstab they aren't mounted so those probably could be assumed as a kind of waste of RAM this way? Or there is chance that they actually mounted somewhere else but fstab? root@heaven:~# cat /etc/fstab # <file system> <mount point> <type> <options> <dump> <pass> tmpfs /tmp tmpfs defaults,nosuid 00 UUID=fb077685-a428-49f2-b013-287dc5fc9672 / ext4 defaults,noatime,commit=120,errors=remount-ro,x-gvfs-hide 0 1 Thank you for tip regarding /var/log, I was suspecting that it should be there as soon as device created. Do you mean to inspect with binwalk/strngs those devices in hope to find out what is there? I'd gave a try - there is nothing: root@heaven:~# binwalk /dev/mmcblk2boot0 DECIMAL HEXADECIMAL DESCRIPTION -------------------------------------------------------------------------------- root@heaven:~# binwalk /dev/mmcblk2boot1 DECIMAL HEXADECIMAL DESCRIPTION -------------------------------------------------------------------------------- root@heaven:~# strings /dev/mmcblk2boot0 root@heaven:~# They also can't be mounted - dmesg excerpt: [390869.014377] F2FS-fs (mmcblk2boot0): Magic Mismatch, valid(0xf2f52010) - read(0x0) [390869.014508] F2FS-fs (mmcblk2boot0): Can't find valid F2FS filesystem in 1th superblock Magic mismatch - mystic things unsolved)

Please give me a tip - what is purpose of /dev/mmcblk2boot block devices created? Quite small size - 4MB - ones, do they serve to something u-boot needs at boot time? There are no records for them in fstab so I assume they are created by zram, but what happens to them after boot when they aren't needed anymore? Board Orangepi 3LTS with bookworm minimal Also as a matter of wondering - why there are two zram devices: one of 1/2 of RAM (as usual) and another of quite small 50MB only, what is it for? root@heaven:~# fdisk -l <redacted> Disk /dev/mmcblk2boot0: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mmcblk2boot1: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes <redacted> Disk /dev/zram0: 987,53 MiB, 1035497472 bytes, 252807 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/zram1: 50 MiB, 52428800 bytes, 12800 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Any chance to get this new and great version on Oragepi3LTS working? I've got armbian-config.sources identical to what is described in user documentation above but still get probably old script version installed - with no additional menu items and, particularly, different name of Disable upgrades as follows: which, in turn, doesn't work for me anymore - nothing changes after I choose "Yes" at question "Disable?" and system has (according to apt-mark showhold) quite old kernel images holded while new updates keep coming and install... Thank you in advance for any suggestions. I know it's community-maintained image for Oragepi3LTS but hope there is some workaround for armbian-config

Thank you, first of all! So you mean that even in vendor's preinstalled Android they don't use GPU for that? I installed there VLC + couple of players from vanilla stores - all of them have no issues with HW decoding at all... According to their status Cedrus could be much easier way - VLC stated there as supported already

Definitely I will - that's why we all are here.

I clearly understand (almost) all you've written above - that's why there is "I'm ready to invest my time" instead of "shut up and give me everything for free, I said - NOW!" "Talk is cheap, send patches." - really good point, sure, my support. Probably something to support their own statements "On Debian 11 and newer, you're required to use the free and open-source Panfrost/Lima drivers" - in terms of just very basic AV HWA, not all the 3D HW shining peaks whistles?)

Have you solved the issue? I bumped into same thing and my findings made me think of this approach. Didn't you try it yet? Originally I've got direction from this old post here.

Hi @jernej could you elaborate perhaps what have been done on LibreELEC side to get hardware acceleration work on OPi3-LTS? Is it somehow related to v4l2_request module for VA drivers which was mentioned in several other treads elsewhere? For my tasks LibreELEC is little bit too much narrow in terms of multi-purpose usage of such a quite powerful SBC. I was really hoping to get much more out of this board when suddenly bumped into lack of quite basic functionality in modern Armbian... To stay on vendor's HWA-enabled Android isn't option for me, so I'm ready to invest my time in order to get even basic HWA working in Armbian. To my point there is quite little we can expect here from Debian Panfrost guys, they clearly stated that HW acceleration is out of their focus at all (yet? for years already)

@balbes150 leaving is surely a big loss for all TV-boxers... Could you please elaborate - is requirement form "Getting started" regarding install " NAND: kernel 3.4.x and NAND storage " applied to his builds too? Years ago I successfully installed Armbian to NAND of MXQ 805 box (with nand-sata-install these days, I guess), and it worked like a charm, but now I can't find any s805 image with kernel 3.4, the earliest ones are 3.10 already. Thank you in advance if you could give a tip.