going

It is Allwinner H618, Quad-core ARM Cortex™-A53 processor. I meant which Eth chip is used in your case Bananapi-m4-berry: h618 ==> Eth chip rtl8211f ==> connecting socket Bananapi-m4-zero: h618 ==> Eth chip ???? ==> connecting socket As far as I understand, this is some kind of expansion card for the 26 pin connector. Can you post a diagram of this expansion board here. The brand of the Ethernet chip matters.

> sunxi-gmac 5030000.ethernet end0: No PHY found! The first question. What brand of chip is used in your case? The second question. Is this an external device? [ 341.101053] usb 2-1: new high-speed USB device number 2 using ehci-platform [ 341.257994] usb 2-1: New USB device found, idVendor=0b95, idProduct=772b, bcdDevice= 0.01 [ 341.258024] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 341.258033] usb 2-1: Product: AX88772B [ 341.258039] usb 2-1: Manufacturer: ASIX Elec. Corp. [ 341.258045] usb 2-1: SerialNumber: E5A1DD [ 341.902647] asix 2-1:1.0 (unnamed net_device) (uninitialized): PHY [usb-002:002:10] driver [Asix Electronics AX88772C] (irq=POLL) [ 341.905987] Asix Electronics AX88772C usb-002:002:10: attached PHY driver (mii_bus:phy_addr=usb-002:002:10, irq=POLL) In order for the ethernet-phy to work, it is necessary to turn on the PWM on the internal pin of the processor. As example see: arch/arm64/boot/dts/allwinner/sun50i-h618-orangepi-zero2w.dts and arch/arm64/boot/dts/allwinner/sun50i-h618-orangepi-zero2w.dts#L521-L539

This will be fixed soon.

It appears that the fsck file check reports a clean system then continues to boot? From the above log of the UART console, I see that uboot found the SD card partition and loaded the kernel from it. The kernel saw the root partition of the SD card, but after checking fsck.ext4 -a -C0 /dev/mmcblk0p1, for some reason, it cannot mount it. When you have written the image to the SD card, try to mount it in your running OS and fix it in the file /boot/armbianEnv.txt verbosity=7. After that, boot up and watch the UART. This may provide additional clues.

Alternatively, you can try disabling this file system verification service by connecting the SD card to a virtual machine and fixing the appropriate scripts.

What have you been updating? Only system files?

The analog audio output to the connector that is soldered to the board does not work for some reason. Although there is a code in the core, there is also a node in the DTS.

Audio output via HDMI should work on all H616-H618 devices. This was tested on the bananapi-m4-berry board for current and edge kernels. In the pulseaudio settings applet, you need to make several switches back and forth (turn on/off) for the sound to appear. Tested on gnome, ubuntu.

All the kernel panic options that you have shown here occur on v6.12.23. It all happens randomly. I suspect that this may be due to the presence of broken (faulty) blocks on the memory device. It's easy to check this.If you connect the SD card via an adapter to a Linux computer: sudo fsck.ext4 /dev/sdX1

When you have started the device on a new operating system image, does the kernel panic appear? After what action does the core panic?

Sparking between the wires on the poles produces high-frequency pulses of high power and transmits them through the wires to consumers of electricity. Household consumers such as a TV, vacuum cleaner, refrigerator do not have a built-in high-frequency protection filter and very often fail. As for the orange, it is not protected at all. My orange was just lying on the table and was connected by an Ethernet cable to the router. Both were not power up. Lightning struck a nearby building. The Ethernet cable caught an electromagnetic pulse. The orange burned down completely and the router has only 1 port damaged. You can draw your own conclusions.

Ok! Are you ready to test it?

No. Yes. This is the most stable and well-developed kernel.

Please throw away this 6.6.75 core. It is no longer supported. Or fix the regressions yourself.

The kernel headers that you have installed are quite enough to build the kernel module, the source codes of which you have. If the source codes are already in the kernel, then you just need to configure the kernel before compiling. launch: After you finish the configuration, the build system saves your configuration file (it will tell you where it did it). Save it under the name ./config/kernel/linux-sunxi64-current.config It is assumed that you are in the armbian/build directory. launch: ./compile.sh BOARD=orangepizero2 BRANCH=current kernel

Try some of these images. https://github.com/armbian/os/releases/tag/25.5.0-trunk.507 And please post here what doesn't work with the download link to the image.

Today 6.12 is the current kernel.

1) Play (decode) video audio 2) Read the status of multiple sensors at regular intervals 3) Generate pulses on GPIO 4) Transmit the packet at the right time over Ethernet, UART ... 5) .......? diff -u config/kernel/linux-sunxi64-edge.config userpatches/linux-sunxi64-edge.config

Have you tried applying this to the 6.12 kernel?

What is the purpose of using this core? Several people have already tried to build a real-time kernel here on the forum. They all face some challenges. Perhaps, if the tasks that such a core should perform are of a general nature, we can provide a configuration for its assembly. You built it yourself. Can you provide a difference in the configuration file for the same kernel version? As diff -u command.

A little clarification. Just install the EDGE core. The version must be 6.13.11 or higher.

kernel version? uname -r

This means that the missing pins should be written something like this: fragment@0 { target = <&spi1>; __overlay__ { status = "okay"; #address-cells = <1>; #size-cells = <0>; pinctrl-names = "default"; pinctrl-0 = <&spi1_pins>, <&spi1_cs0_pin>, <&spi1_cs1_pin>;

Try adding this line compatible = "armbian,spi-dev"; /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h616"; fragment@0 { target = <&spi1>; __overlay__ { status = "okay"; compatible = "armbian,spi-dev"; cs-gpios = <&pio 7 9 0>,<&pio 2 15 0>; // PH9=CS0 for lcd, PC15=CS1 for touch panel: panel@0 { compatible = "panel-mipi-dbi-spi"; reg = <0>; ................ P.S. I doubt that I am giving you the right advice.

Yes, please post it here. There may be several suggestions (explanations) as a short instruction for use.