balbes150

@IgorI fixed the Legacy kernel sources for Jetson-nano in GIT, now the Legacy kernel build on Hirsute is working. No patches are needed in the BUILD system, just the kernel build starts and works. (patches for Legacy that are currently needed in the build system)

Maybe it's not the same, but I'm currently working on simplifying the build process. Transferring most of the settings that are scattered in the build scripts (lib) to the BOARD.CONF settings files. This will significantly simplify the logic of the assembly scripts, they will not have confusing logical chains in which the assembly variables are reconfigured and redefined depending on the model. Yes, at the beginning this will increase the duplication of data (variables) in the board.config files, but then it is easily simplified by transferring the same settings to the group config for several devices. When the test sample is ready, I will try to create a separate branch for general analysis.

All versions of the group (Legacy or Current) use a single kernel. Look for the reason in your system settings.

Try installing the full firmware package or copying the FIRMWARE directory from NVIDIA image to the Armbian 4.9 and 5.10 system.

Do not mislead users. DTB from Android will never work directly on Armbian. These are completely different kernels, Android always has very old kernels that are not compatible with Armbian.

I don't have an M2 module for WiFi and I have no idea what it is missing. Have you checked the WiFi operation on a regular Ubuntu image from NVIDIA ?

Check how it works with kernel 4.9.

the formation of the core is laid down in the build patches and there is no change provided.

yes

The problem is that the system rigidly replaces the kernel, without giving the user the option to refuse to replace the kernel.

I suggest not to add separate versions of kernels, but to remove the very presence of a hard binding to some kernel.

Has this permission ever worked ?

@JMCCNow I tested the latest versions of Station-legacy P1\M1 with the installation of the media package. I get the same error - hard binding of the package to the rockchip64-legacy kernel. This creates a lot of problems. Back to the question, maybe you should remove the hard binding to the kernel ?

ver 20210614 kernel 4.9 and 5.10.43

ver 20210614 kernel 5.10.43 add image Hirsute

ver 20210614 kernel 5.10.43 the kernel config has changed significantly. the core is now common to all rk3399\rk3328\jetson-nano\h6

new version of Armbian 20210614 with core 5.10.43. Added support for analog audio and a standard remote control.

try versions with the Legacy kernel (4.4) or 5.10 with an extended WiFi list https://disk.yandex.ru/d/W9SHvYXAIpFEew

Module M2 E-key ?

what module are we talking about ?

info https://bbs.t-firefly.com/forum.php?mod=viewthread&tid=2948&extra=page%3D1

Perhaps someone will be interested in the new model, as long as there is a discount. https://www.firefly.store/goods.php?id=140

@IgorThere is no point in wasting time on characters who think only of themselves.

Version 20210513. Fixed startup with Legacy kernel, now these images work correctly.

Version 20210505. Added images with the Legacy 4.9 kernel.