balbes150

I do not have such equipment, I do not know where the regression occurred and what is missing for its operation I have never been involved in overclocking, these devices are already very hot, so I don't see any use in this.

Everything necessary for CSC is already there and I can send PR to the general build system (I have all the necessary changes in the build system to get working images with the main kernel and the main u-boot for quartz64). I have not published these changes anywhere in the build system, only one ready-made test image to check how it works. My question was related to having a common position on supporting this model.

If I'm not confused, it's not a phone, it's a tablet If the other developers have no objections, I will create a PR Especially for this device, I have already put together a test version with the main kernel and the main u-boot.

A question about Quartz64. Can I create a PR for CSC or do we not support it in any form ?

I have never used this configuration and do not know what changes are needed for it.

The launch of the correction is a forced temporary measure, until the moment when a new version of the Initrd formation will be used. We discussed this with @rpardini on github. The problem there is that by default, little space is allocated to Initrd in u-boot, and if its size is larger than 14 MB, then the subsequent loading of the kernel file is superimposed on it and spoils it. It's strange, my UART output works without problems on all cores\images.

Yes, I plan to create a PR with a new set of images (targets.conf) and edit the download page and add information about the fix. Have you launched the u-boot fix (the order of which is described above) after upgrading u-boot to the latest official version?

there is a kernel config in the /boot directory that is used during the build, you can check it for the necessary options. You can also rebuild the kernel yourself on Jetson Nano itself (using the Armbian build system it's very easy) using your kernel config changes. maybe there are problems with your provider ?

Have you checked the setting of different output frequencies ? have you checked the legacy kernel version ? For the current and edge versions, all sound devices available in the USB core are included. Try the AltLinux versions (there is a link to the images above in the topic), it's interesting to fuck up the behavior with the screen flickering.

The procedure for updating (fixing) the latest version of u-boot for Jetson Nano. Fixes the system startup error when the Initrd size is more than 14 MB. 1. Download the boot.scr file from the link. 2. Prepare any clean media (you can use any media SD card or USB flash drive of any size). The media must be formatted in FAT32 or EXT2\3\4. 3. Write the boot.scr file to the media 4. Connect the media to the Jetson Nano and turn on the power. 5 Wait 3-4 Minutes and turn off the power, disconnect the media. This is a one-time procedure that automatically fixes an error in u-boot SPI. After that, you can use any systems from external media. https://disk.yandex.ru/d/p1uI2wyAfpoLRA

Yes, these are commands for the UART console. But in the near future I will publish another solution to this problem, which does not need a UART console. No. I'm only testing for 1080p try switching in the settings. in fact, 120 Hz is a useless trick of marketers \ manufacturers, which has nothing useful for the human eye.

I checked the latest test version and found a bug in u-boot that prevents the system from starting correctly. By default, too little space is allocated for Initrd when loading, so the kernel file (Image) is superimposed on the Initrd address range, which causes its destruction. A temporary solution. Open the UART console and run two commands that will fix the problem and they will allow you to run any system in the future.. setenv kernel_addr_r 0x85000000 saveenv

Yes I do not observe such a problem myself. Two different test TV and monitor are working correctly. What settings are you trying to use? Try using images from here. https://disk.yandex.ru/d/XBRXnig7F1M4rw At the moment, getting a working HDMI sound is not a top priority. I have not checked its operation, but I see that there are sound devices with a huge number of settings (it takes a lot of time to check them). If you find the correct parameters and provide the resulting settings file (/var/lib/alsa/asound.state), I will be able to include it in the resulting images.

What page are you writing about ? It is present in the 5.16 kernel, but it has not been tested in operation (it may not work or requires additional settings) It is not tested because there is no corresponding equipment. For legacy kernel work (As far as I remember) For kernel 5.x - no test. Write a script (steps) to check or check for yourself. No After burning an SD card or USB media (now direct system startup is supported immediately from USB without an SD card), nothing needs to be copied or changed. A prerequisite is updating u-boot to the latest version (this happens automatically when the official Ubuntu NVIDIA image is launched from the SD card once). Not tested.

This is a description of you, you're afraid to indicate your real nickname, under which you hang out in their community. I don't see any point in continuing to communicate with you, you're a banal troll.

Why on earth should I change my attitude towards those who are engaged in theft, piracy, spreading lies, impersonating others in order to compromise those they don't like. I will specifically emphasize that not everyone in their community is like that, most are normal and sane people, whom I treat with respect and we cooperate with some (not publicly). Especially for you, the AML BSP core is full of shit.

The fact that it works in their shit does not mean at all that if you add only DTB, then it will be able to work on the main core. @WernerThe piquancy of the situation is that the "customer" did not even specify the exact version of the kernel for which DTB is needed, and this is a key parameter that can dramatically change the price and amount of work. DTB and core are tightly linked. I have an opinion that the "customer" does not sufficiently understand the essence of the task that he wants to solve, he requests the creation of a DTB for the kernel and then writes about u-boot.

Without false modesty, I think there are few specialists who know Amlogic TV boxes + Linux (Armbian) better than me. Therefore, I know well what I am writing about. I have to upset you a lot, just the opposite, you will get the opposite result. Your system can be very easily stolen and used without spending a cent on updating the program and kernel and using the shittiest AML TV boxes. It's enough to take the shittiest and cheapest AML TV box and make a stupid copy of your system (buy one of your devices anonymously, run a full copy of eMMC on it with a banal DD command and then deploy it all to cheap shit TV boxes). If Wi-Fi \BT AV does not work, the simplest USB WiFi \ BT USB sound card with AV is bought for $ 1-2 and the issue is resolved. With SbS (especially with Rockchip or Aw), everything is not so simple - the system from them will not work on AML TV boxes, and TV boxes for RK and AW, on which it can work, will cost no less than SbS. Therefore, pirates will not benefit from theft. p.s. I don't want to waste time on empty conversations, it's your money and you decide where to spend

At the moment, so far only for Buster 4.4 there is a media package with KODI and mpv (HW) in network repo armbian. As soon as @JMCC releases and places in our repo a new version of the media package for the 5.15 kernel (I have already checked its test build of the package for Bulsey and it works well with full HW acceleration), I want to remove the old version (4.4) from subsequent builds and I will leave the version with the 4.4 kernel only in the archive for those who urgently need it.

Question to the user Station P\M. Which images should preferably be placed on the official Armbian download page. I assume such a set: stable versions Buster XFCE kernel-4.4 Bullseye CLI kernel current (5.15) Bullseye DE XFCE kernel current (5.15) Hirsute CLI kernel current (5.15) Hirsute DE XFCE kernel current (5.15) and one but nightly build of Jamm with edge kernel (5.16).

Pay attention to the information from Igor. He understood correctly what I am trying to explain to you. Even if create a DTB, it absolutely does not mean that your equipment will work. To do this, you need another "little thing" - the availability of support (drivers) for your hardware in the kernel itself (and firmware \ settings and other things in the system). And this is a completely different cost many, many, many times more than your budget. Therefore, I advise you to listen carefully to the advice - choose SUPPORTED equipment and throw this trash in the trash.

What does "current Armbian version" mean? There is no such thing for TV boxes. It follows from this that the hidden context of the task is to create for you a full-fledged system with a working core in which all the equipment for your device works. Yes, I can create such a DTB, but who will support all devices in the kernel itself, in the system.

No, I don't have them. No

Ver 20220108-edge kernel 5.16-rc8

Version 20220108-edge with kernel 5.16-rc8. Please note, kernel versions are changing. Now Current = 5.15 and EDGE = 5.16.