Leaderboard

first: -> TCRP ( same for ARPL ) Always use full size DSM PAT files when building loaders. For DS3622+ or DS918+, 7.1.1-42962 U1 (with update 1) Corresponds to the final version with full size. In particular, in the case of DS923+ / DS723+ / RS4021xs+, 7.1.1-42962 U5 exists in full size. If you go to the path below, PAT files that exceed approximately 300M are such files. https://archive.synology.com/download/Os/DSM After that, you need to additionally install the required SMALL Update version. After the Small Update version is installed, FRIEND proceeds with RD automatic patching. second: -> You don't have to use the UEFI version of IMG to boot into UEFI. Legacy versions are also compatible with UEFI. If you have problems with the legacy version of IMG, I know that the workaround is to use the UEFI version of IMG. This part borrows the image produced by pocopico as it is in M SHELL, so I don't know exactly how it works.

yes

Finally, I succeeded in creating bsp of SA6400 for TCRP. https://github.com/PeterSuh-Q3/redpill-load/tree/master/config/SA6400/7.1.1-42962 I've changed my mind a bit. To regenerate zImage, should I use the same version of the toolchain and Linux source as the kernel version of DSM? The bottom line was that it wasn't. It seems that the kernel version to be used for bsp generation does not have to be the same as the kernel version of DSM. https://github.com/PeterSuh-Q3/redpill-load/actions/runs/4902082033/workflow 7.1.1-42962 has been deployed to M SHELL for the SA6400 model. Loaderbuild and booting of the FRIEND kernel also work without problems. However, problems still remain. The /dev/synoboot device is not found normally. It doesn't discriminate between bare metal and VM. Although it was possible to force synoboot to be created, During the DSM installation process, I encounter a 55% file corruption message. I will focus on this matter from tomorrow. I'd love to have a solution for this part.

Мне пока хватает только распознавание пересечения барьера, но и эта функция, как я уже писал ранее, работает не идеально, иногда тупо не записывает и всё, хотя, xpenology фиксирует человека в это же время, это видно в другом пункте меню

Я не использую распознавание, по крайней мере пока не использую, у меня используется распознавание вторжения, ну т.е. пересечение линии

Распознавание лиц, распознавание номерных знаков и некоторые настройки обнаружения вторжений потребляют системные ресурсы, эквивалентные 2 задачам DVA. Одновременно может выполняться не более 6 таких задач. При записи в качестве 4K максимальное количество задач DVA ограничено 8 Это официальный комментарий от Synology