reimaged my reTerminal with SEEED image: “2022-06-19-Raspian-reTerminal.img” (32bit)
includes “bullseye”
sudo apt update
sudo apt upgrade
sudo apt install git {success}
Then
git clone GitHub - Seeed-Studio/seeed-linux-dtoverlays: Device Tree Overlays for Seeed boards
cd seeed-linux-dtoverlays
sudo ./scripts/reTerminal.sh
…
Building module:
cleaning build area…(bad exit status: 2)
make -j4 KERNELRELEASE=6.1.21-v7l+ all KVERSION=6.1.21-v7l+…(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.1.21-v7l+ (aarch64)
Consult /var/lib/dkms/mipi_dsi/0.1/build/make.log for more information.
Can’t compile with this kernel, aborting
lease try to compile with the option --compat-kernel
DKMS make.log for mipi_dsi-0.1 for kernel 6.1.21-v7l+ (aarch64)
Sat 20 May 2023 01:15:43 PM PDT
make -C /lib/modules/6.1.21-v7l+/build M=/var/lib/dkms/mipi_dsi/0.1/build modules
make[1]: Entering directory ‘/usr/src/linux-headers-6.1.21-v7l+’
CC [M] /var/lib/dkms/mipi_dsi/0.1/build/mipi_dsi_drv.o
CC [M] /var/lib/dkms/mipi_dsi/0.1/build/touch_panel.o
CC [M] /var/lib/dkms/mipi_dsi/0.1/build/panel-ili9881d.o
In file included from ./include/linux/types.h:6,
from ./include/linux/limits.h:6,
from ./include/linux/kernel.h:16,
from ./include/linux/interrupt.h:6,
from /var/lib/dkms/mipi_dsi/0.1/build/mipi_dsi.h:15,
from /var/lib/dkms/mipi_dsi/0.1/build/touch_panel.c:1:
./include/uapi/linux/types.h:5:10: fatal error: asm/types.h: No such file or directory
5 | #include <asm/types.h>
| ^~~~~~~~~~~~~
In file included from ./include/linux/types.h:6,
from ./include/linux/limits.h:6,
from ./include/linux/kernel.h:16,
from ./include/linux/interrupt.h:6,
from /var/lib/dkms/mipi_dsi/0.1/build/mipi_dsi.h:15,
from /var/lib/dkms/mipi_dsi/0.1/build/panel-ili9881d.c:8:
./include/uapi/linux/types.h:5:10: fatal error: asm/types.h: No such file or directory
5 | #include <asm/types.h>
| ^~~~~~~~~~~~~
In file included from ./include/linux/types.h:6,
from ./include/linux/limits.h:6,
from ./include/linux/kernel.h:16,
from ./include/linux/interrupt.h:6,
from /var/lib/dkms/mipi_dsi/0.1/build/mipi_dsi.h:15,
from /var/lib/dkms/mipi_dsi/0.1/build/mipi_dsi_drv.c:11:
./include/uapi/linux/types.h:5:10: fatal error: asm/types.h: No such file or directory
5 | #include <asm/types.h>
| ^~~~~~~~~~~~~
compilation terminated.
compilation terminated.
compilation terminated.
make[2]: *** [scripts/Makefile.build:250: /var/lib/dkms/mipi_dsi/0.1/build/mipi_dsi_drv.o] Error 1
make[2]: *** Waiting for unfinished jobs…
make[2]: *** [scripts/Makefile.build:250: /var/lib/dkms/mipi_dsi/0.1/build/touch_panel.o] Error 1
make[2]: *** [scripts/Makefile.build:250: /var/lib/dkms/mipi_dsi/0.1/build/panel-ili9881d.o] Error 1
make[1]: *** [Makefile:2012: /var/lib/dkms/mipi_dsi/0.1/build] Error 2
make[1]: Leaving directory ‘/usr/src/linux-headers-6.1.21-v7l+’
make: *** [Makefile:15: all] Error 2
just to check as the next step (was successful!)
raspberry@reTerminal01:~/seeed-linux-dtoverlays $ ls /boot/overlays/reTerminal-bridge.dtbo
/boot/overlays/reTerminal-bridge.dtbo
raspberry@reTerminal01:~/seeed-linux-dtoverlays $
Why am I getting all the erros above?
i noticed the kernel issue and checked which one was on my reTerminal:
raspberry@reTerminal01:~/seeed-linux-dtoverlays $ uname -a
Linux reTerminal01 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
raspberry@reTerminal01:~/seeed-linux-dtoverlays $
If I remember from another reImage the next step was ::sudo apt update
sudo apt upgrade
Maybe that was not a good idea??
I tried with my newest reTerminal which apparently was not full-upgrade as it was Buster and Linux 5.10.60-v71+ #1449 SMP
However, it did appear to improve. What stood out:
run-parts: executing /etc/kernel/header_postinst.d/dkms 5.10.103-v8+
Error! echo
Your kernel headers for kernel 5.10.103-v8+ cannot be found at
/lib/modules/5.10.103-v8+/build or /lib/modules/5.10.103-v8+/source.
W: --force-yes is deprecated, use one of the options starting with --allow instead.
KBUILD: /lib/modules/5.10.103-v7l+/build
…
Building module:
cleaning build area…(bad exit status: 2)
make -j4 KERNELRELEASE=5.10.103-v7l+ all KVERSION=5.10.103-v7l+…(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.10.103-v7l+ (armv7l)
Consult /var/lib/dkms/mipi_dsi/0.1/build/make.log for more information.
Can’t compile with this kernel, aborting
…
/var/lib/dkms/mipi_dsi/0.1/build/mipi_dsi_drv.c:435:12: error: initialization of ‘int (*)(struct i2c_client )’ from incompatible pointer type ‘void ()(struct i2c_client *)’ [-Werror=incompatible-pointer-types]
.remove = i2c_md_remove,
^~~~~~~~~~~~~
/var/lib/dkms/mipi_dsi/0.1/build/mipi_dsi_drv.c:435:12: note: (near initialization for ‘i2c_md_driver.remove’)
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:280: /var/lib/dkms/mipi_dsi/0.1/build/mipi_dsi_drv.o] Error 1
make[2]: *** Waiting for unfinished jobs…
make[1]: *** [Makefile:1825: /var/lib/dkms/mipi_dsi/0.1/build] Error 2
make[1]: Leaving directory ‘/usr/src/linux-headers-5.10.103-v7l+’
make: *** [Makefile:15: all] Error 2
pi@reTerminal01:~/seeed-linux-dtoverlays $
At least with “Bullseye” the
ls /boot/overlays/reTerminal-bridge.dtbo
/boot/overlays/reTerminal-bridge.dtbo existed. With Buster No such file or directory
Obviously the “Bullseye” reTerminal-bridge.dtbo exists but what about all the errors?
Help!
The problem may be due to the 32-bit system updating behavior while downloading the driver, causing the whole device to mess up.
You can try re-burning the original 32 - bit image. Once the system is installed, type in the terminal:
echo arm_64bit=0 | sudo tee -a /boot/config.txt
Then go back to the Wiki steps.
I’m sorry to have kept you waiting so long. I hope this helps you!
Thank you. I will try it today. I really appreciate your support!
Another problem which occurs at a "?random " time and remains “broken” is connecting an external HDMI display to the reTerminal. The first time occurred after connecting my reTerminal to my TV and Changing the resolution. Could never change it back as it was never an option. When I disconnected from my TV the reTerminal’s display no longer worked. Only choice was connecting to any external HDMI display.
This happened recently with my second reTerminal after connecting it again to an external display. The reTerminal 's display is no longer accessible!
In both cases, I had successfully connected both reTerminals to an external monitor and both the external monitor and internal reTerminal display were both visible at the same time. What caused this to happen, apparently, at a “random” time?
I have a suggestion regarding the overlays required for the E10-1 (bridge). Provide the SEEED supplied reTerminal Image without the E10-1 overlays or the image WITH the E10-1 overlays (each image will contain the required reTerminal overlays). If the customer never plans to add the E10-1, they can choose the image without the Bridge overlays. In addition, provide an explanation as to what fixes or updates are in each image and which Linux Kernel/ Raspberry OS and Python versions the image is compatible with.
