I have just built a Klipper image using KIAUH on Raspberry Pi OS Lite (32 bit) Bookworm. I installed Klipper, Moonraker, Mainsail, and KlipperScreen (in that order). Klipper and Mainsail are working. During the boot process the console messages show on the display, and then the display goes blank and periodically shows a “No Signal” message. KlipperScreen was installed using the Wayland option instead of Xserve.
The display I am using is a Waveshare 5 inch LCD HDMI capacitive touchscreen. The HDMI is connected to the micro HDMI port closest to the USB-C power connector of the Raspberry Pi 4B. The power and touchscreen interface are provided by a USB2 port.
KlipperScreen is running and a copy of the KlipperScreen.log is provided below. At this point I have no idea what to try to get KlipperScreen to display.
This is mainly a question of correctly setting up the Linux OS level and is highly individual for the different displays, Linux version and type of SBC. Typically Waveshare and KlipperScreen are offering good guidance, e.g.
Sineos - thanks for the reply. I have looked at both the resources you noted, but it is not clear how to use the information. The Waveshare documentation discusses configuration using /boot/config.txt, but that method does not apply to Bookworm. I tried the troubleshooting steps from the KlipperScreen site, but there is nothing there that matches my configuration and observations. The display works during boot, but displays “No Signal” afterward.
What is frustrating to me is that there does not appear to be much in the way of useful documentation of how to configure video in Bookworm. What I have found (including on the Raspberry Pi site) seems incomplete.
My system is usable without the touchscreen display, but I would like to have it working again. It still works on my old Buster/Python 3.7 system, just not on any of the new images I have created.
Unfortunately, I cannot offer much more guidance. As stated, it is a goofy combination from:
Display and the used driver chip on it
Linux distribution and the way it loads the required device tree overlays and their options, e.g. the Raspberries have just deprecated some legacy ways and are using different drivers, e.g. vc4-fkms-v3d versus vc4-kms-v3d
Wayland versus X11 as the window system protocol and architecture
Probably some quantum flux interference from the 9th dimension
Thanks anyway Sineos. I found something that seems to work. While experimenting with one of my Bullseye OctoPrint images I uncommented the hdmi_force_hotplug=1 line in the /boot/config.txt file and I was able to get OctoDash to work.
Since my Mainsail image is Bookworm, not Bullseye, that solution will not work. I was able to find something that is roughly equivalent. Add video=HDMI-A-1:e to the end of the /boot/firmware/cmdline.txt file. This apparently forces the HDMI to be enabled, and allowed KlipperScreen to show.