Jump to content

SteeMan

Moderators
  • Posts

    1840
  • Joined

  • Last visited

Posts posted by SteeMan

  1. On 12/13/2023 at 7:44 PM, SteeMan said:

    What dtb file did you use?

    Since this issue is well over a year old, I'm not sure where you stand with this.  Are you still looking to get a fix?  If so, answering all of the questions asked would be helpful.

    When you say "broke again" what do you mean by broke?  Apparently the box is running and you can update it as you continue to update it per the message above saying you have upgraded to 6.12.32.

    Have you tried a fresh image installed on a new SD card to see if that works (vs. your upgraded system)?

  2. 3 hours ago, salas said:

    @Efe ÇetinWhy DTB compiled for kernel 6.1 wont work in 6.10 kernel ? Should't that info about regulators, dt nodes , properties be the same?

    Second question: If I take DTS source for 6.1 and compile using dt compiler of 6.10, should it work ?

    Technically a DTS is specific to a kernel version.  As changes happen to the kernel apis, those need to be reflected in the DTS's.  So they DTB and kernel image are always built and shipped together.

     

    Now in practice changes that impact the DTS aren't common, so you can usually use DTS's accross kernel versions.

     

    However in this case, I'm assuming that when you refer to 6.1 that is a vendor kernel, and 6.10 or greater would be mainline kernel.  Now these are two very different code bases.  A vendor kernel is whatever the board/cpu vendor hacked together to get a kernel running on their hardware.  Often these are more android kernel based.  When features finally get rolled into mainline, their implementation is often completely different.  Thus one can't share a DTS between a vendor kernel and a mainline kernel.  But often you can use the vendor DTS to gather information about what needs to be implemented in the mainline DTS.

  3. @KrzyPacu  The Amlogic TV Box builds use extlinux.conf.  So you should add your overlay info in that file (/boot/extlinux/extlinux.conf).

    I believe the syntax for extlinux is:

    OVERLAYS /dtb/amlogic/overlay/...

    (I'd recommend placing it just below the FDT line)

    (Note: I've never tried to load an overlay through extlinux, but have been intending to try it some day.  Let us know how it goes)

  4. 3 hours ago, KrzyPacu said:

    Please provide a .dtb file with working SPDIF.

    TV boxes are Community supported.  That means they are not supported by Armbian.  It is up to community members like you to figure these things out and submit them back to the community through your contributions.

  5. Look at your board config file:  config/boards/orangepi5b.csc

    In there you will find the board family, which in your case is:

    BOARDFAMILY="rockchip-rk3588"

     

    Then look at the corresponding board family config file:

    config/sources/families/rockchip-rk3588.conf

     

    There you will find a section for each branch (i.e vendor, current, edge) that will specify which kernel source is used:

    For BRANCH=vendor that would currently be:

            KERNELSOURCE='https://github.com/armbian/linux-rockchip.git'
            KERNELBRANCH='branch:rk-6.1-rkr5.1'
            KERNELPATCHDIR='rk35xx-vendor-6.1'

     

     

     

     

  6. 8 minutes ago, dart wejder said:

    The only thing I wanted to clarify with you, just to understand how the boards are loaded from the sd card if there is no boot partition on it?

    That isn't as simple of a question as you may think it is.  It depends.  But since you are dealing with a TV box, that would be better asked in a question over in the TV box forums as it is off topic for this thread.

  7. @Antom  You are not using Armbian.  ophub is a fork of Armbian that uses the Armbian name without permission.  They do not contribute to Armbian development nor participate in these forums.  You need to direct your question to their forums, not here.

  8. On 5/26/2025 at 11:14 PM, nnq1612 said:

    U-Boot SPL board init
    U-Boot SPL 2017.09-orangepi (Jul 05 2024 - 20:18:28)
    Trying to boot from MMC1

    From your log, this is the uboot that is booting and it is trying and failing to boot from your mmc1.  I would expect your SD to be mmc0, so it doesn't look like it is even trying to boot from your SD card.  So you probably need to replace/update the onboard uboot or perhaps wipe the mmc1.  

    But I don't have this board and really am just guessing.  But these are directions you could look into.

  9. From the boot log, the uboot can't recognize the internal emmc.  It appears that the u-boot you are using is one based on u-boot 20-07.  I would recommend rebuilding the u-boot-s905x-s912 based on a more current u-boot source.  The instructions for doing this are in the readme.txt file in build-u-boot folder.  If this helps, then report back here and I can look at including a newer build in the distribution going forward.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines