Orange Pi 4 Pro - Usb 3.0 Not detected

Creating a bug report/issue

I have searched the existing open and closed issues

Required Information

  • DietPi version | cat /boot/dietpi/.version
  • G_DIETPI_VERSION_CORE=10
    G_DIETPI_VERSION_SUB=0
    G_DIETPI_VERSION_RC=1
    G_GITBRANCH=‘master’
    G_GITOWNER=‘MichaIng’
  • Distro version | echo $G_DISTRO_NAME $G_RASPBIAN
  • bookworm
  • Kernel version | uname --all
  • Linux DietPi 5.15.147-sun60iw2 #1.0.4 SMP PREEMPT Thu Oct 30 10:16:47 UTC 2025 aarch64 GNU/Linux
  • Architecture | dpkg --print-architecture
  • arm64
  • SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)
  • Generic Device (aarch64)
  • Power supply used | (EG: 5V 1A RAVpower)
  • 5v 3A
  • Using Emmc

Additional Information (if applicable)

  • Software title | (EG: Nextcloud)
  • Was the software title installed freshly or updated/migrated?
  • fresh install
  • Can this issue be replicated on a fresh installation of DietPi?
    ← If you sent a “dietpi-bugreport”, please paste the ID here →
  • Bug report ID | echo $G_HW_UUID

Steps to reproduce

  1. Plug USB SDD or HD on USB 3.0 port not detected on lsblk or dietpi drive manager
  2. If plugged on USB 2.0 both disks are detected and i can mount them

Expected behaviour

  • Detect SDD and HD on USB 3.0 port

Actual behaviour

  • Both SDD and HD leds are ON but they are not detected

Extra details

PS: I got the official Orange Pi 4 Pro debian image and run the diet-pi script on it

I don’t think the SBC is officially supported. Will be hard to get someone who has is running. You can try to open an issue at GitHub asking for support. Which will be the closed way to @MichaIng who is our developer.

it’s not officialy supported that’s why i run the script. I can do the “tests” on it since i have that SBC, i only need to know what to do/test since i’m new in linux.

Thank you all by the help.

We have 2 of them now, see also: Orange pi 4 pro

It is a very new SoC (Allwinner 733) without mainline Linux or U-Boot support yet. Allwinner’s vendor kernel sources are Linux 5.15 and U-Boot 2018.05 :see_no_evil_monkey:. At Armbian, someone tried to implement support for some Radxa SBCs with the same SoC (based on these vendor sources), but it was too much custom hassle for them: sun60iw2: add `vendor` kernel support for radxa cubie a7a/a7z by EvilOlaf · Pull Request #9145 · armbian/build · GitHub

The sources from Xunolng/Orange Pi:

Of course dietpi-installer should work somewhat. Since Xunlong uses an Armbian fork for their image builds, kernel and bootloader are somewhat consistently packaged. But for a proper support our end, it will take a bit longer. Orange Pi 4A is first on my list.

Linking our GitHub issues/requests:

FYI

Somebody managed to create a armbian mainline build with kernel 6.19
https://github.com/jonas5/orangepi-4pro-armbian

I also saw that Xunlong created a Linux 6.6 branch for that kernel. I hope this also means they updated their bootloader source, or there is a mainline-based U-Boot source.

The source you linked does not include a bootloader at all, hence seems to work with the present SPI bootloader only, and the SPI storage is optional on that board, AFAIK. The README mentioned a U-Boot patch dir which does not exist :thinking:. Anyway, a better starting point.

I will play with it this weekend.

I asked OPi a while ago (On Amazon BTW :sweat_smile:, but the Answer of this Question is not available anymore on the product page for some reason) about the SPI storage because some of their documents are a bit misleading (Some say “Optional 128/256MB SPI”), but the stated that there is always at least 128MB SPI storage, the 256MB are an optional variation.

Ah good to know. So maybe the idea was similar like our StarFive JH7110 images.

Here is the Xunlong Linux 6.6 sources: GitHub - orangepi-xunlong/linux-orangepi at orange-pi-6.6-sun60iw2 · GitHub

Main issue remains U-Boot: GitHub - orangepi-xunlong/u-boot-orangepi at v2018.05-sun60iw2 · GitHub
As said, this basically compiles a 32-bit U-Boot without booti command support, hence it can only load legacy uImage and uInitrd images. Too much work to implement into Armbian, way too much special-handling.

Mainline U-Boot has started to implement support for the SoC, but there seems to be more missing than just a defconf and device tree: Merge branch 'master' of https://source.denx.de/u-boot/custodians/u-b… · u-boot/u-boot@c08da5d · GitHub