ORANGE PI 3B

  • Good afternoon.

    Could someone create an image for this board for me? I've been using it for a while, just in case something comes out for it.

    I know no developer has it, but I'm sure someone is waiting to buy it. It's a good, very affordable board that could be put to good use with LibreElec.

    On the Internet, from the page http://www.orangepi.org/html/hardWare/…ange-Pi-3B.html you can see all its features.

    If someone helps me create it, I promise to perform any tests they need.

    Greetings

  • Needs https://github.com/LibreELEC/LibreELEC.tv/pull/7864 to be merged as a basic step. Also needs upstream kernel developers to finish writing all the drivers because AFAIK that SoC type is still missing a ton of things. If you've been using it for a while already I assume you are either using some kind of vendor kernel (which we won't use on principe) or it's a desktop distro release missing a bunch of media functionality.

  • Nothing... in the end, hard acceleration doesn't work with that file either, at least on the 3566. One curious thing I've noticed is that the motherboard behaves differently on different displays. On a 40 display, it's different than on a 24 or even a 50" display. It's weird...

  • In any case, I'm not worried about the hardware acceleration issue. I'll disable it and problem solved.
    What I would like is for Wi-Fi, Ethernet, and Bluetooth to work.



    Ethernet de 10/100/1000 Mbps (chip físico integrado: YT8531C-CA)

    Wi-Fi 5+BT 5.0, BLE (AP6256)

    Edited 2 times, last by deleonkikko: Merged a post created by deleonkikko into this post. (May 28, 2025 at 6:25 PM).

  • By mainline linux device tree, Orange Pi 3B has 2 HW revisions V1.1 and V2.1.

    I met the ethernet problem on my V2.1 revision device when V1.1 dtb file was used.
    But, it was able to use the ethernet when V2.1 dtb file is used.

    Please check your HW revision and your dtb file I hope.
    HW revision is printed in board.

  • To understand what might be happending we'll need to know what sources the image you're using is built from (as we didn't build or provide the image, and we're not mind readers) and to see UART logs showing u-boot and system output during boot.

    In the absence of that info .. /shrug