balbes150

Support will be available only for Station P2\M2 models.

Only Station M2 P2 is discussed in this topic. If you want to have Armbian on rk35xx, use proven hardware. With your TV box, you need to contact the manufacturer or seller from whom you bought it.

in industrial design https://wiki.t-firefly.com/en/EC-R3566PC/started.html https://wiki.t-firefly.com/en/EC-A3568J/started.html

New version 20211017 kernel 5.10.73 and 5.14.12. A significant change is the transition to a new version of u-boot with support for running any system from USB to M1 (rk3328). Now you can run any test system from USB media. So far, only USB 2.0 is working.

s905x3 has never been supported and you can safely throw it in the trash, nothing will work.

I'm not sure if I can or not be at the meeting waiting for the results of covid-19 . But I will try to check the latest build-master data for all devices for which I have committed support, and I will try to send patches (if any).

ver 20211010 kernel 5.10.72 (current) and 5.14.11 (edge)

You have chosen a very bad equipment for a gift. Such equipment will do more harm than good.

yes the driver is responsible for this, it has nothing to do with the support of specific hardware. I didn't check, but I saw that to add the desired screen resolution, you can add it at the user settings level. try adding a parameter to extlinux.conf with your screen resolution drm.edid_firmware=edid/1920x1200.bin

New version 20211007-edge with 5.14.9 core. All equipment works, including analog sound and remote control. @JMCC I checked the operation of your KODI-18 packages on this kernel, KODI starts, but there is still an error and the video does not play, maybe I forgot some kernel options or a patch. I plan to check it again in the near future.

@JMCCWe kindly ask you not to add dependencies on specific kernels to future packages. New kernels with HW can be for RK \ AW and different versions of edge \ current.

@JMCC continuing testing I tested the new KODI on a Nanopc T4 + 4k TV with 4k resolution. Everything works fine. When playing test videos to the full screen, which works in 4k mode (desktop resolution 3840x2160), the load on the processor is minimal, here is a fragment of monitoring. For those who want to try a new version of KODI on Nanopc T4, there is a link to Bullseye test images with a new core. https://disk.yandex.ru/d/oUSTsAI_oRCGMA Time big.LITTLE load %cpu %sys %usr %nice %io %irq CPU C.St. 15:09:09: 408/1416MHz 1.43 8% 2% 3% 1% 0% 0% 50.6�°C 0/5 15:09:15: 600/ 600MHz 1.47 4% 1% 1% 0% 0% 0% 50.0�°C 0/5 15:09:20: 408/ 600MHz 1.44 5% 1% 1% 0% 0% 0% 50.0�°C 0/5 15:09:25: 600/ 408MHz 1.48 4% 1% 1% 0% 0% 0% 50.0�°C 0/5 15:09:30: 408/ 600MHz 1.44 4% 1% 1% 0% 0% 0% 50.0�°C 0/5 15:09:35: 408/ 408MHz 1.41 5% 1% 1% 0% 0% 1% 50.0�°C 0/5 15:09:40: 408/ 408MHz 1.45 5% 2% 1% 0% 0% 0% 50.0�°C 0/5 15:09:45: 408/ 600MHz 1.50 4% 2% 1% 0% 0% 0% 50.0�°C 0/5 15:09:51: 408/ 408MHz 1.54 4% 1% 1% 0% 0% 0% 50.0�°C 0/5 15:09:56: 408/ 408MHz 1.60 4% 1% 1% 0% 0% 0% 50.0�°C 0/5 15:10:01: 1800/ 600MHz 1.64 4% 2% 1% 0% 0% 0% 50.6�°C 0/5 15:10:06: 408/ 408MHz 1.66 4% 2% 1% 0% 0% 0% 50.0�°C 0/5 15:10:11: 1800/ 408MHz 1.61 4% 1% 1% 0% 0% 0% 50.0�°C 0/5

If you do not need maximum performance, I recommend paying attention to the new Station P2 and M2 models (these are full-fledged mini PCs). At the moment, there are systems with the Legacy core for them, but the development of support for the main core for the rk35x is very fast. And soon there should be a "monster" with very strong characteristics - RK3588. But if you need the most ready-made solution with the main core right now, I recommend P1\M1 . Just yesterday I tested the work of new versions of KODI with full HW support for playing full-screen video on P1\M1 on the main core (I pay attention not to the Legacy core, but the latest stable 5.10), everything works fine even with 4K. By the way, P1 (RK3399) copes with 720p full-screen video in the Chrome browser without problems , there are not big artifacts in 1080p mode, but with the release (I hope it will be in the coming months) of the new version of FFMPEG and adding its support to browsers, rk33xx (P1\M1) will easily cope with 4k in full-screen browsers.

@JMCC I checked your KODI-18 package on M1 (rk3328). Everything works fine, plays 4k video without any problems. The heating of the system is less than 50 degrees and KODI shows a load of less than 50%. Great job. It remains to add these packages to the Armbian network reps, so that users can easily install and use them.

by the way, I tried to install your packages in Hirsute, everything was installed, but there is not enough library when trying to launch it. I think it's not difficult to solve this by building a version for Ubuntu. Then we can assume that there is full support for KODI with HW on Ubuntu and Debian for Armbian at the same time.

Finally, I found the time and checked your version of KODI-18 for the main core. In short - all my test videos (including 4k) come with HW . When playing 4k, KODI shows a load of about 11% to Station p1. Great job. Can you build and upload new versions for the main core to the network reps ? It is interesting to try the new versions of KODI-19.

Added version 20210921-edge with the 5.15.0-rc2 kernel and with the new u-boot.

New version 20210920 with support for installation in eMMC\NVMe\SATA. For details of the use, see the corresponding topics. m2 https://bbs.stationpc.com/thread-211-2-1.html p2 https://bbs.stationpc.com/thread-209-1-1.html

New version of images 20210915-edge with 5.15.0-rc1 kernel. Please note, this version does not have an HDMI output, control is performed via SSH or UART. The wired network works, both LAN1 and LAN2 interfaces work on P2, M2 - LAN1. Please note that this is the primary test version and unpredictable behaviors are possible.

I connected the NVMe module to P2 , the system sees it and can work with it. Which image and which DTB are you using ? Here is the output of "fdisk -l", which clearly shows the presence of NVMe in the system. Disk /dev/nvme0n1: 119.24 GiB, 128035676160 bytes, 250069680 sectors Disk model: NE-128 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Armbian 21.11.0-trunk Hirsute ttyFIQ0 station-m2 login: root Password: ____ _ _ _ __ __ ____ / ___|| |_ __ _| |_(_) ___ _ __ | \/ |___ \ \___ \| __/ _` | __| |/ _ \| '_ \ | |\/| | __) | ___) | || (_| | |_| | (_) | | | | | | | |/ __/ |____/ \__\__,_|\__|_|\___/|_| |_| |_| |_|_____| Welcome to Armbian 21.11.0-trunk Hirsute with Linux 4.19.193 No end-user support: built from trunk System load: 62% Up time: 0 min Memory usage: 6% of 3.68G IP: 192.168.1.39 CPU temp: 30�°C Usage of /: 32% of 15G [ 2 security updates available, 7 updates total: apt upgrade ] Last check: 2021-09-08 14:13 Last login: Wed Sep 8 14:13:42 UTC 2021 on ttyFIQ0 root@station-m2:~# fdisk -l Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/mtdblock0: 32 MiB, 33554432 bytes, 65536 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/mmcblk0: 29.12 GiB, 31268536320 bytes, 61071360 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 Disklabel type: gpt Disk identifier: 1E020000-0000-406A-8000-113E00001CED Device Start End Sectors Size Type /dev/mmcblk0p1 16384 24575 8192 4M unknown /dev/mmcblk0p2 24576 32767 8192 4M unknown /dev/mmcblk0p3 32768 40959 8192 4M unknown /dev/mmcblk0p4 40960 49151 8192 4M unknown /dev/mmcblk0p5 49152 51199 2048 1M unknown /dev/mmcblk0p6 51200 116735 65536 32M unknown /dev/mmcblk0p7 116736 124927 8192 4M unknown /dev/mmcblk0p8 124928 321535 196608 96M unknown /dev/mmcblk0p9 321536 1107967 786432 384M unknown /dev/mmcblk0p10 1107968 1894399 786432 384M unknown /dev/mmcblk0p11 1894400 1927167 32768 16M unknown /dev/mmcblk0p12 1927168 8300543 6373376 3G unknown /dev/mmcblk0p13 8300544 9349119 1048576 512M unknown /dev/mmcblk0p14 9349120 61071326 51722207 24.7G unknown Disk /dev/mmcblk1: 14.87 GiB, 15962472448 bytes, 31176704 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 Disklabel type: gpt Disk identifier: BE4EF038-2CF8-46BD-8D6E-05E4769B6502 Device Start End Sectors Size Type /dev/mmcblk1p1 32768 65535 32768 16M Linux filesystem /dev/mmcblk1p2 65536 30834687 30769152 14.7G EFI System Disk /dev/nvme0n1: 119.24 GiB, 128035676160 bytes, 250069680 sectors Disk model: NE-128 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes root@station-m2:~#

ver 20210907 kernel 4.9.210 and 5.10.62

ver 20210907 kernel 5.10.62

ver 20210907 kernel 5.10.62

We are talking about the kernel Station-current (which now uses all the patches for LE).

I asked about this because I want to understand if it makes sense to support a new kernel now. If you have no plans to use it, I want to reduce the number of different cores and remove it from support (remove it from the official build system, so as not to produce unnecessary entities).