[lcdproc] Problem with Crystalfontz display
Sat, 8 Sep 2001 16:13:03 -0500 (EST)
On Sat, 8 Sep 2001 firstname.lastname@example.org wrote:
> > I'm not sure. I don't remember seeing a speed setting in the BIOS or the
> > kernel. How can I check it? (When I do 'cat /dev/lcd' as root, the LCD
> > shows a blinking cursor, but that's not really doing anything.)
> /dev/lcd is just a symlink to one of your serial ports. Besides, doing a
> "cat /dev/lcd" just tries to read the device (read *from* whatever's
> attached to the display) ... not what we want in this case.
> You need to dig up the manual for your display and find out what it's set
> to expect. I think CrystalFontz does up to 9,600 baud, but it's worth
> checking. Pass a "--speed 9600" to the driver to set the speed to 9,600:
> # LCDd -d CFontz "--speed 9600"
> Use --speed 1200 or --speed 2400 if that's what your display expects.
The manual says 19200, 9600, 4800, and 2400 are supported. And, according
to /proc/tty/driver/serial, ttyS0 is set to 9600 baud. (It still
amazes me what I can find in the proc filesystem if I just root around
for a bit.) But, the LCD showed garbage even when I gave the driver the
What should the behavior be after I start LCDd but before I start lcdproc?
> I mean "it should absolutely never hold on to the TCP port when it exits."
> If it's not closing the port immediately on shutdown (even if a signal
> kills it (except kill -9 :) it should still catch that and shutdown
> gracefully), we've got a bug.
I just took out the call to setsockopt, and the server restarted
immediately, so I guess it wasn't necessary. Oh well. I only thought
of it because I had to do the setsockopt() thing in a webserver I wrote
for my networking class.
Computer Science, Purdue University
"The two most common things in the Universe are Hydrogen and Stupidity."
To unsubscribe from this list send a blank message to