LCD-show
LCD-show copied to clipboard
LCD 3.5" screen keep showing boot log
Hi, i have an issue with the 3.5" screen, i've installed everything correctly on the last version of raspbian, after doing ./LCD35-show the board reboot, the console boot is running on the screen but when everything is done the log stays on the screen. But when i click on something, it appears that the desktop is behind and i can see it briefly before the log comes back...
I have this problem too, dont know how to solve this issue.
Try removing the following line from /etc/rc.local
fbcp &
What is this doing? When using a 3.5" TFT the raspberry creates two framebuffers (memory where the picture that is displayed on a screen is stored), one for the HDMI output and the other for the TFT. fbcp is a tool that constantly copies the data from the HDMI buffer to the TFT buffer to increase display performance. In my case this was constantly overwriting the content for the TFT with the console and not what I wanted. Removing those lines fixed the issue.
Try removing the following line from /etc/rc.local
fbcp &What is this doing? When using a 3.5" TFT the raspberry creates two framebuffers (memory where the picture that is displayed on a screen is stored), one for the HDMI output and the other for the TFT. fbcp is a tool that constantly copies the data from the HDMI buffer to the TFT buffer to increase display performance. In my case this was constantly overwriting the content for the TFT with the console and not what I wanted. Removing those lines fixed the issue.
I have this problem too, but there is no fbcp & in the file you said....
Then you probably have a different problem, what does your rc.local file say?
I have this problem too
try install again? 2019-06-29
goodtft
发件人:sceic [email protected] 发送时间:2019-06-26 20:07 主题:Re: [goodtft/LCD-show] LCD 3.5" screen keep showing boot log (#107) 收件人:"goodtft/LCD-show"[email protected] 抄送:"Subscribed"[email protected]
I have this problem too — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
Try removing the following line from /etc/rc.local
fbcp &What is this doing? When using a 3.5" TFT the raspberry creates two framebuffers (memory where the picture that is displayed on a screen is stored), one for the HDMI output and the other for the TFT. fbcp is a tool that constantly copies the data from the HDMI buffer to the TFT buffer to increase display performance. In my case this was constantly overwriting the content for the TFT with the console and not what I wanted. Removing those lines fixed the issue.
This solved the issue for me. Thanks!
Commenting out fbcp & from /etc/rc.local also resolved this for me!
Commenting out fbcp also (effectively) disables _rotate... directives in config.txt.
You'll need to update the dtoverlay to reflect desired rotation if the default isn't what you need.
Another vote for commenting out fbcp & from /etc/rc.local 👍 This solved my issue ! Thanks!
- H/W: BCM2835, Rev: 9000c1, Model: Raspberry Pi Zero W Rev 1.1
- OS: Raspbian Buster Lite (2019-07-10-raspbian-buster-lite.zip), No X-Window installed
- Display: MHS35, 3.5'' LCD Display, TS11-JP
- Driver: Installed. (
clonethe repo ->cd LCD-show->sudo ./MHS35-show. Though it gave me errors ofxserver-xorg-input-evdevbut after the reboot LCD started to display the boot log) - Issue: The boot log on the LCD get stuck as below:
... [6.464968] systemd[1]: Created slice system-systemd\x2dfsck.slice. [6.518587] systemd[1]: Created slice syste-serial\x2dgetty.slice. [6.568936] systemd[1]: Created slice system-getty.slice. - Solution: Even the console log on LCD gets stuck, it is accessible to RPi-Zero W via SSH. So I commented out as suggested and rebooted, then it fixed my problem. TTY1 works as usual.
- Note: I'm not using GUI (Raspbian Desktop) but CUI only (Raspbian Lite with no X). So don't know if the touch sensor work.
Try removing the following line from /etc/rc.local
fbcp &What is this doing? When using a 3.5" TFT the raspberry creates two framebuffers (memory where the picture that is displayed on a screen is stored), one for the HDMI output and the other for the TFT. fbcp is a tool that constantly copies the data from the HDMI buffer to the TFT buffer to increase display performance. In my case this was constantly overwriting the content for the TFT with the console and not what I wanted. Removing those lines fixed the issue.
This did it for me! I was using the script from the similar Waveshare repository BTW. The screen kept blanking out and only showed when there was keyboard input.