going

@belegdol Are you interested in how to do this in your local assembly? Or is it a problem with updates, when a new kernel with a lower version should be updated by apt to the old kernel from the armbian repository but with a higher version? I want to understand the essence of the problem in a broader sense. And information for everyone. I am continuing to develop the master branch. At home locally. And knowing, understanding what the user wants is very important for all of us.

@lissizza It seems to me that I have reviewed all the links on the Internet, but I have not found any information about the chip with the letters that you published. Can we try to get information from the other side? For example, show what is written directly on the printed circuit board: the name of the device and its version. For example, I have: Orange PI PC v1.1 And please give me a link to download the schematic diagram for the version of this device.

Please check the correct operation usb_modeswitch

I do not promise a quick result. Thanks for the dts file. Very timely, I am currently fixing it for the 6.2 kernel. Unfortunately, I am not an advisor on displays and their resolutions. I work with headless devices. Wait, someone will help.

And can you see 2GB of memory? Just attach this file to your message

Maybe the android version will work. I only need a dtb blob from the working version. These chips, according to the data that I found, can work with a voltage of a little more or less. The question is the exact figure. If we have any working image. I'll pull the information out of it and assemble a working kernel for you.

@lissizza Which image is currently running on your device. Why am I asking? Whether some other was downloaded, for example from the manufacturer's website or another Armbian edition.

Different series of the same chip. It is sad. I'll think about what can be done.

These inscriptions on this chip? Do I understand correctly?

I sincerely wish you gentlemen good luck.

I think the best option is to take a fresh image for your device

Here I just want to change the core. I think it's clear what needs to be done.

In order to disable the patch, it is enough to put a minus sign at the beginning of the line with this patch in the "series.conf" file. These patches exist, but they don't apply.

It has no functionality for processor frequency @ALIGMSTEN Alistair, can you add patches that you have running on the 5.19 kernel for the 6.1 kernel?

htop --version on bullseye ?

Tested: Armbian_23.02.1_Bananapim64_jammy_current_5.15.93_minimal.img The first start, boot, reboot is normal. Found not included in the fix for "armbianmonitor" for one cluster. Corrections here

I am collecting packages in a virtual machine. The virtual machine and the running device are on a local network. I have ssh access to both. mc

You have to transfer two files (linux-dtb*linux-image*) to the system on the device. It can be mc & ssh or just write them to the home directory on the sd card from which the device is loaded. Sorry. I didn't see that build directly on the device. If the build was done using the scripts of the Armbian build system, then just install two packages using the "dpkg -i linux-dtb-*.deb linux-image-*.deb " command.

@Hasan Ali The bootloader and kernel versions in your original firmware and what is going to Armbian are most likely different. You must convert the original dtb into a text file of the dts and create your own for your device and in accordance with the requirements and capabilities of the new kernel and u-boot versions. Add compilation capability to Makefile. Make these changes in the form of patches and add them to the appropriate directories in the userpatches/patch directory. Currently: cache/sources/linux-mainline/6.1> ls arch/arm64/boot/dts/allwinner/*h616* arch/arm64/boot/dts/allwinner/sun50i-h616.dtsi arch/arm64/boot/dts/allwinner/sun50i-h616-orangepi-zero2.dts arch/arm64/boot/dts/allwinner/sun50i-h616-x96-mate.dts u-boot> ls arch/arm/dts/*h616* arch/arm/dts/sun50i-h616.dtsi arch/arm/dts/sun50i-h616-orangepi-zero2.dts arch/arm/dts/sun50i-h616-x96-mate.dts

First, find the documentation for this device. Processor, memory chips, wifi\Ethernet chips. Read the documentation about the capabilities of the sunxi-tools utility. Build and install this program on your external Linux computer. Try to connect from this computer to the device that you are breaking. Try to read and save all the files that you managed to take. Of particular value is *.dtb. If there is a USB port on the device and it is possible to boot from it and luck to read and save a binary dtb file, then no special problems are expected. If there is no USB connector, then you will have to disassemble the device and pick up a soldering iron. Are you ready for such a development? I'm not an Android expert. I can only give advice on how to assemble an image using the armbian assembly system. Good luck. Write if something starts to work out there are people who have done hacking of such devices. You can search for them on the forum.

Sunxi-tools See custom-u-boot-configuration-howto

@rodw Why are you asking these questions about the real-time operation of the kernel here on this site? Here we can discuss the Armbian assembly system itself. Here we can discuss working on the devices of images that have been provided for download. If you use the Armbian build system and want it to be able to assemble a number of interdependent packages in a complex, then ask. I can direct you right now and I can provide my development branch for this. But it is best to discuss the source code of the kernel and linuxcnc on the linuxcnc forum.

Xenomai or rt-preempt today is a simple application of patches to the kernel source code. This process will not cause difficulties. But then we will need to build\rebuild several additional libraries and kernel modules and the application that uses these libraries loads and unloads modules. Obviously, it is necessary to prescribe dependencies correctly in this entire chain.