Devuan bug report logs -
#311
Device Tree Overlays Do Not Work
Reply or subscribe to this bug.
Toggle useless messages
Report forwarded to devuan-bugs@lists.dyne.org, owner@bugs.devuan.org
:
bug#311
; Package arm64_raspi3
.
(full text, mbox, link).
Acknowledgement sent to Paul Bryan Roberts <paul.bryan.roberts@the-custards.uk>
:
New bug report received and forwarded. Copy sent to owner@bugs.devuan.org
.
(full text, mbox, link).
Message #5 received at submit@bugs.devuan.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
Package: arm64_raspi3
Version: ascii_2.0.0
* Details of the configuration of the program with the problem.
Include the complete text of its configuration files.
I was using devuan_ascii_2.0.0_arm64_raspi3.img.xz downloaded on January
19th 2019 at around 18:00 UTC.
* A description of the incorrect behaviour: exactly what behaviour you
were expecting, and what you observed. A transcript of an example
session is a good way of showing this.
This image comes with a /boot/overlays directory containing a large
number Device Tree Overlay files and a /boot/config.txt that contain at
least one dtoverlay= directive.
So it seems reasonable to suppose that this Devuan image is supposed to
be Device Tree Overlay capable. It appears not to be.
* The /exact/ and /complete/ text of any error messages printed or
logged. This is very important!
It appears DT overlays are not loaded. There are no error messages
printed or logged: such failures are silent.
There is a tool named vcdbg that can be used to extract the Device Tree
load time logs but this is closed source and, as yet, there is no arm64
binary. I did get the following using a different tool:
pi@devuan:~$ dtmerge /boot/bcm2710-rpi-3-b-plus.dtb merge.dtbo
/boot/overlays/tft35a.dtbo
DTOVERLAY[error]: No symbols found
* Exiting with error code 1
Without symbols you can't overlay. Sadly the tool dtmerge is not
available for Devuan. You can build it from source or pinch an arm64
binary from the Ubuntu ubuntu-raspi2 PPA.
* Exactly what you typed or did to demonstrate the problem.
What you can do under Devuan is confirm that Device Tree Blob is missing
symbols. Install the device-tree-compiler-package first.
pi@devuan:~$ fdtdump /boot/overlays/tft35a.dtbo | fgrep '__ {'
__overlay__ {
__overlay__ {
__overlay__ {
__overrides__ {
__symbols__ {
__fixups__ {
__local_fixups__ {
pi@devuan:~$ fdtdump /boot/bcm2710-rpi-3-b-plus.dtb | fgrep '__ {'
__overrides__{
This confirms that the symbols are missing from the Devuan DT Blob, not
my DT Overlay.
* A description of the incorrect behaviour: exactly what behaviour you
were expecting, and what you observed. A transcript of an example
session is a good way of showing this.
The DT Overlay describes my device. When applied, the kernel will load
the appropriate modules (ads7846 and fb_ili9486). The modules should
appear in the dmesg output and also the output of lsmod.
Under Devuan, they do not. The current versions of these modules do not
take parameters but expect to extract them from the Device Tree so
manual loading of these has no effect.
My device is unusable.
* A suggested fix, or even a patch, if you have one.
A quick work around is to take the equivalent Device Tree Blob from
Raspian. It contains symbols, the kernel loads the modules, the device
springs into life and everyone lives happily ever after.
A more sensible approach might be to upgrade the device tree compiler to
a version that is symbol capable, build the Device Tree Blobs passing
the -@ option to the device tree compiler and reissue the SD image(s).
[Message part 2 (text/html, inline)]
bug reassigned from package 'arm64_raspi3' to 'arm-sdk'.
Request was from Mark Hindley <mark@hindley.org.uk>
to control@bugs.devuan.org
.
(Sun, 26 Jan 2020 15:33:02 GMT) (full text, mbox, link).
Send a report that this bug log contains spam.