MichaIng

@SteveJohnsson Thanks for your report. Yeah indeed the script is out of style, but this is no big issue, it is small enough to easily allow an overview. The problem...

@SteveJohnsson Ah one more thing, since this is no HDMI display? I don't know too much about this, but do you know if the display uses I2C, SPI and/or UART...

@SteveJohnsson Thanks for feedback. Did you check which interface is actually required, I²C, SPI and/or UART? I reopen this issue as a request to add this LCD to our dietpi-config...

@SteveJohnsson If you want you can test it: ``` sed -i '/dtparam=i2c_arm=/d' /boot/config.txt sed -i '/enable_uart=/d' /boot/config.txt ``` Then reboot and see if the display still works.

@rzmichel I just updated my steps above by going through the script again which contains some changes: https://github.com/goodtft/LCD-show/blob/master/LCD35-show - Somehow it contains now enabling everything: SPI, I2C, forced HDMI, UART...

@rzmichel If I get it right, `99-calibration.conf` is for the touchscreen: https://github.com/goodtft/LCD-show/blob/master/usr/99-calibration.conf-32-90 `Option "Calibration" "3700 115 155 3865" `+ `"SwapAxes"` is what you need to play around to have the...

@rzmichel Thanks for your comparison details. From `cmdline.txt` and `99-calibration.conf` content it looks like you used a slightly different script than I used as basis. Which script did you run?...

@rzmichel Glad it finally worked. Note that you currently have two conflicting xorg sections in theory: ``` Identifier "Allwinner A10/A13/A20 FBDEV" Driver "fbturbo" Option "fbdev" "/dev/fb1" ``` and ``` Identifier...

@rzmichel Okay thanks for testing. Commenting the "uga" device of course causes an error since this is used by the "Screen" section 😉. However good to know that the fbturbo...

Thanks for the offer. Yes generally those install scripts work on DietPi as well, but they are extremely intrusive, override large parts of boot configuration which is not required and...