Jump to content

going

Members
  • Posts

    818
  • Joined

  • Last visited

Other groups

Contributor/Maintainer

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Each attached memory disk must have its own unique UUID. This is its essence. This depends on the platform (BROM bootloader flashed into the chip) and possibly the switch soldered to the board.
  2. There are three ways to do this. The first simplest is to assemble a binary debian package using the Armbiyan assembly system and then convert it to a rpm package directly in a running OpenSuse OS. The second way is more complicated but it is more correct. You can take patches directly from the build system and apply them to OpenSuse kernel sources in the sequence in which the build system does this while running. Next, build the kernel package using rpmbuild. The third way is the same as the second but use OBS. This will allow you to have your own repository of signed packages and install them using zypper. You can find like-minded people anywhere on our planet, including this place. Hope this helps you.
  3. This is similar to physical damage to the SD card
  4. Please read the documentation on the manufacturer's website (radxa). It really works.
  5. If you want to find a request, please publish the UART log. maybe after that we can say recommendations.
  6. ./compile.sh And choose this:
  7. UART console log? In fact, only the u-boot version and the kernel version are interested. On my devices with rk3588 (s) chips, old versions of u-boot were originally installed and they did not allow loading Armbian images. I used the instructions from the manufacturer's official website and recorded the bootloader provided by Armbian on the SPI chip using special software. In other words, Armbian delivers his images from u-boot v2025.XX but my orangepi5plus was loaded using u-boot v2019 recorded on an SPI chip. And that may be the problem. After overwriting the new version, my device loads any images and PCI (NVME) devices register correctly. I checked several of these from different manufacturers. Hope this information helps with your problem.
  8. Today it is EDGE v6.15 no v6.16.
  9. Recommended to upgrade U-Boot to version v2025.07 This version has big changes for allwinner (sunxi) chips. This concerns the initialization of a non-standard size of RAM (1.5; 2.5 GB), downloads from eMMC.....
  10. Yes, that's right. This is relevant to the issue under discussion.
  11. v5.1-rc5 v6.12.35 Please use the current documentation for the CURRENT kernel. sun4i-a10-video-engine.yaml sun8i-h3-deinterlace.yaml Documentation/arch/arm/sunxi.rst arch/arm/boot/dts/allwinner/sun8i-h3-nanopi-duo2.dts arch/arm/boot/dts/allwinner/sun8i-h3.dtsi P.S. Please read this. repository-for-v4l2request-hardware-video-decoding-rockchip-allwinner
  12. 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.
  13. > 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
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines