-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enabling display leads to stuck Raspberry Pi4 #112
Comments
Hi @HayleySummer, thanks for submitting this issue! The procedure has been tested with the following display: http://www.miuzeipro.com/product/miuzei-raspberry-pi-4-touch-screen-with-case-fan-4-inch-ips-full-angle-game-display-800x480-pixel-support-hdmi-input-with-touch-pen-4-pcs-heatsinks-support-raspbian-kali-by-miuzei/ (which is also available at Amazon in several countries, and several other shops) The core code for configuration of the display is in the following script: bin/rq_enable_touch.sh Not sure if it needs to be modified for the Waveshare LCD 4'' you are using. |
Hi Jan,
|
Thank you, @HayleySummer ! With the Miuzei display attached it looks like this:
|
Hi,
I followed the setup instructions with my Raspberry Pi 4. Everything worked smothly until I tried to execute "S2 – Enable 4’’ Display " via the RasQberry Configuration Tool. This caused my display (Waveshare LCD 4'') to get stuck, showing only two white stripes at the bottom of the screen and nothing else. After several minutes I forced the Raspberry to reboot (via Control+alt+F1 and terminal).
I wiped the OS and started again from scratch, this time skipping the touchscreen enablement, but I had the same issue with "S0 – Bloch Autostart" which requires enabling the touch screen.
Is there a known workaround to solve this issue? Or is enabling the display configuration only suitable for some displays?
If you have any questions on this, don't hesistate to get in touch with me. Thank you and kind regards
The text was updated successfully, but these errors were encountered: