Tryng to understand device tree overlays

1st Official Post

    I'm trying to make sense of the boot process on a CM3588. Specifically where to modify the device tree overlay. I have a CM3588 that came pre-installed with OMV 7 OS on the eMMC and I think it has an older device tree overlay. I'm trying to update it, but can't find the /boot. This really blows my mind.


    Firstly, am I in the wrong forum? Does the OMV group build these images? My understanding is that this is an OMV OS versus OMV installed on Debian.


    Secondly, how do I read my current device tree overlay and how do I change it?


    I've been using Linux for a long time, but this little device has me a bit baffled.


    Any help will be greatly appreciated.

    root@openmediavault
    -------------------
    OS: Debian GNU/Linux 12 (bookworm) aarch64
    Host: FriendlyElec CM3588
    Kernel: 6.1.57
    Uptime: 2 days, 20 hours, 53 mins
    Packages: 1537 (dpkg)
    Shell: bash 5.2.15
    CPU: (8) @ 1.800GHz
    Memory: 2080MiB / 15948MiB

    • Official Post
    Quote from berapp

    Does the OMV group build these images?

    No, Friendly builds and maintains them.

    Quote from berapp

    My understanding is that this is an OMV OS versus OMV installed on Debian.

    There is no OMV OS. OMV is always installed on Debian. The OMV iso for amd64 does this automatically. The install script also does this. Friendly chose to create their own image.

    Quote from berapp

    how do I read my current device tree overlay and how do I change it?

    What do you mean by a device tree overlay?

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    The device tree information is available via /proc/device-tree.

    You change the device tree information by modifying the underlying *.DTS and/or *.DTSI source files and send them through the device tree compiler (dtc) to generate the DTB (device tree binary) file, which is read at boot time or part of the kernel image being loaded.

    • Official Post
    Quote from ananas

    The device tree information is available via /proc/device-tree.

    You change the device tree information by modifying the underlying *.DTS and/or *.DTSI source files and send them through the device tree compiler (dtc) to generate the DTB (device tree binary) file, which is read at boot time or part of the kernel image being loaded.

    I know what a device tree is but I wanted to clarify what the OP was referring to.

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    THANK YOU! I'm working on a reply. It will take a while for me to compose my thoughts.

    root@openmediavault
    -------------------
    OS: Debian GNU/Linux 12 (bookworm) aarch64
    Host: FriendlyElec CM3588
    Kernel: 6.1.57
    Uptime: 2 days, 20 hours, 53 mins
    Packages: 1537 (dpkg)
    Shell: bash 5.2.15
    CPU: (8) @ 1.800GHz
    Memory: 2080MiB / 15948MiB

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login