I am using the stock init-LCDd.rpm script on my CentOS 7 machine. I copied the init.LCDd.rpm file into my /etc/init.d/ directory, and renamed it "LCDd". The next step was to make the script executable by doing "chmod 755 /etc/init.d/LCDd", followed by "chkconfig LCDd --add" and "chkconfig LCDd on".
On reboot, my welcome message is displayed as expected, but then the display starts sending streams of garbage characters across the screen. LCDd does start as intended, so the script seems to be fine. However, it starts sending random characters across the screen after a couple of seconds. This situation seems similar to an improper baud rate, but because I am using a USB MtxOrb display model, I believe the baud rate should be irrelevant or fixed at 19200.
My immediate guess is that my machine is sending some data on startup that the display cannot parse, but am a little stuck as to how to fix this issue. I can provide my LCDd.conf if necessary.
My picoglcd has the same issue as yours, it displays some initial startup screen on boot because kernel recognized it and assign it as an frame buffer display.
I tried to blacklist the module for my glcd and it worked. GLCD displays nothing until LCDd started.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I am using the stock init-LCDd.rpm script on my CentOS 7 machine. I copied the init.LCDd.rpm file into my /etc/init.d/ directory, and renamed it "LCDd". The next step was to make the script executable by doing "chmod 755 /etc/init.d/LCDd", followed by "chkconfig LCDd --add" and "chkconfig LCDd on".
On reboot, my welcome message is displayed as expected, but then the display starts sending streams of garbage characters across the screen. LCDd does start as intended, so the script seems to be fine. However, it starts sending random characters across the screen after a couple of seconds. This situation seems similar to an improper baud rate, but because I am using a USB MtxOrb display model, I believe the baud rate should be irrelevant or fixed at 19200.
My immediate guess is that my machine is sending some data on startup that the display cannot parse, but am a little stuck as to how to fix this issue. I can provide my LCDd.conf if necessary.
Thanks in advance,
--Jeff
Last edit: Jeffrey Han 2015-08-27
My picoglcd has the same issue as yours, it displays some initial startup screen on boot because kernel recognized it and assign it as an frame buffer display.
I tried to blacklist the module for my glcd and it worked. GLCD displays nothing until LCDd started.