lcd4linux-users — lcd4linux users

[lcd4linux] Crystalfontz 635

[Michael R. <re...@eu...>]

Hi there,

anybody out there with such a display? LCD4Linux does not know them by
now, but the driver should be easyly adapted. Probably just a new entry
in the Model[] table should do the job.

TIA, Michael

-- 
Michael Reinelt <re...@eu...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

[lcd4linux] Re: lcd4linux 0.10

[Michael R. <re...@eu...>]

Hi all,

>>>   I'm having problems showing graphics characters with the Crystalfontz
>>>driver (631). Do you know any issue?
>>>    
>>>
>>No, I don't. But I must say that I didn't try CF displays lately.
>>
>>What exactly are your Problems? Bars? Icons?
>>
>     Whenever I use an icon, the screen get corrupted and the others
> layout are not rendered correctly (they disappear).

Should be fixed in CVS. I reworked the whole CrystalFontz stuff, and now
we're waiting for every command ACK packet from the display. This slows
down things a bit, but it works...

Could you please test it? If you need assistance with CVS, let me know
(or take a look at the wiki)


bye, Michael

-- 
Michael Reinelt <re...@eu...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

[lcd4linux] Re: LCD screen

[Michael R. <re...@eu...>]

Hi Juliano,

> I use your program and I'm having problems with the informations that
> are displayed in the lcd.
> 
> I can't clear the lcd screen and send another information to the lcd.
> 
> I use the  Crystalfontz LCD and your site doesn't say much about my doubt.

I'm sorry but I'm not sure what exactly is your problem. Could you
please try again to explain what does not work, or what you want to achieve?


bye, Michael

-- 
Michael Reinelt <re...@eu...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [lcd4linux] bugreport on HD44780 driver for 0.10.0

[Michael R. <re...@eu...>]

Hi Johan

> -       drv_generic_text_greet("goodbye!", NULL);
> +       drv_generic_text_greet("goodbye", NULL);

> Indeed, I only removed the exclamation mark in the final splash screen.
> Everything works as it should. ["goodbye! dude" also worked, it seems the
> exclamation mark is the cullprit]

Well, I tend to not to believe you :-)

> I know my patch only solved a symptom. The real problem (why can't I
> show an exclamation mark) is still there. I hope one of the developpers
> is able to find this real problem.

I have absolutely no idea. Maybe your display interprets the ! as some
sort of control sequence...

could you try if you can use a exclamation mark somewhere in the layout
(just use a stativc text or so) without problems?

bye, Michael

-- 
Michael Reinelt <re...@eu...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [lcd4linux] init.d problem

[Michael R. <re...@eu...>]

Hi Petri,

sorry for the delay....

> I run lcd4linux from init.d script. When computer is booted lcd4linux doesn't 
> start. If I run '/etc/init.d/lcd4linux restart' afterwards it works fine. 
> When I put -vv in init.d script and get... 

> on boot:
> Jul 21 13:03:51 wood LCD4Linux[13299]: USBLCD: found USBLCD V01.12 on bus 003 
> device 004

> on restart:
> Jul 21 13:10:55 wood LCD4Linux[14461]: USBLCD: found USBLCD V01.12 on bus 003 
> device 004
> Jul 21 13:10:58 wood LCD4Linux[14461]: initializing layout 'damu'

> I'm running Gentoo Linux on AMD64. Any idea what could be wrong?

Looks like something inside the USB initialization hangs. You could add
a lot of debug statements to the code, to see where it stops.


bye, Michael

-- 
Michael Reinelt <re...@eu...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [lcd4linux] Printserver

[Michael R. <re...@eu...>]

Hi Joanand,

> I have some printserver (Intel NetExpress Pro/100 with 1 printerport,
> Netgear PS110 with 2 printerport and Target N7667 with 3 printerport)
> and I would like to attach each port a LCD-display and controll it with
> a server. By doing so, I can position LCD-display across the whole
> house, only with a RJ45 cable or even nothing (wlan, current-ethernet)

This is for sure a great idea. But it will be not that easy. I don't say
it's impossible but...

> CUPS uses "socket://ipaddr:portaddr" to send printer information, so
> what I am asking you is, is there any possiblity to realise what I am
> thinking?
The problem is that these printer servers contain a microprocessor,
translating between a special lp/ipp protocol on the ethernet side, and
a printer protocol on the parallel port.

For lcd4linux and for most of the parallel displays, you need to control
every control and data signal of the parport individually. If you can
find a way of doing so, you will for sure run into timing problems. If
you can solve these, too, your patch will be very welcome :-)

bye, Michael

-- 
Michael Reinelt <re...@eu...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

[lcd4linux] Printserver

[Joanand K. <joa...@mg...>]

Hi,
I have some printserver (Intel NetExpress Pro/100 with 1 printerport,
Netgear PS110 with 2 printerport and Target N7667 with 3 printerport)
and I would like to attach each port a LCD-display and controll it with
a server. By doing so, I can position LCD-display across the whole
house, only with a RJ45 cable or even nothing (wlan, current-ethernet)

I would like to use the first printerport to controll a LCD (2x20 or
4x20) and the other one (if there is one and is bidirectional) controll
the server with a keypad.

CUPS uses "socket://ipaddr:portaddr" to send printer information, so
what I am asking you is, is there any possiblity to realise what I am
thinking?

Thanks.
Sincerely your
Joanandk

Re: [lcd4linux] lcd4linux on LEAF Bering-uclibc - PPP data updates too quickly (want time averaged data instead)

[Martin H. <ma...@he...>]

Hi Kevin,

> I'd love to update to version 0.10 but the bering-uclibc package
> hasn't been updated yet - perhaps someone who reads this mailing list
> knows if/when that will be done and if it's in the works?
Sorry about that - that was oversight on my part. The setup building
0.10.0 for Bering uClibc has been in CVS since mid-June - I just forgot
to upload the package too...
The package is already in CVS - it should be visible on
http://cvs.sourceforge.net/viewcvs.py/leaf/bin/packages/uclibc-0.9/20/lcd4linx.lrp?rev=HEAD&view=log
within the next 4 or so hours (you want revision 1.5 of the package).
I'll also update the packages page as soon as it's visible on viewcvs
(and as soon as I can find my login info to actually modify the leaf
pages :-))

Martin

[lcd4linux] lcd4linux on LEAF Bering-uclibc - PPP data updates too quickly (want time averaged data instead)

[Kevin K. <sup...@gm...>]

Greetings.

lcd4linux 0.9.11 rev3 package on bering-uclibc firewall (LEAF).

I'm using the following format to display PPP data from my firewall
onto the LCD:

Row1 PPP %ti $R8ti+to %to

Works fine, but the data updates too quickly and isn't time averaged -
so the output isn't really all that useful (it jumps all over the
map).

Could someone tell me if/how I could adjust this so that the output is
time averaged or made to be more useful in some other way?  Not sure
how that works in this 'token' system of calling data.

I'd love to update to version 0.10 but the bering-uclibc package
hasn't been updated yet - perhaps someone who reads this mailing list
knows if/when that will be done and if it's in the works?

Any help would be appreciated.

[lcd4linux] bugreport on HD44780 driver for 0.10.0

[Johan S. <Joh...@xs...>]

Hello,

I have a hd44780 which worked very well yesterday evening and stopped 
working this morning. Yesterday evening I used the options -Fvvq when 
testing, today I only remembered the -Fvv part. I found that indeed the 
splashscreen is the troublemaker. Unformatunately I do not understand why.

Here are the details:

processor AMD 1400 Mhz Athlon
kernel    2.4.31
version   lcd4linux-0.10.0
driver    HD44780
size      20x4

part of the verbose output
HD44780: using ppdev /dev/parport0
HD44780: wiring: [DISPLAY:RS]<==>[PARPORT:AUTOFD (Pin 14)]
HD44780: wiring: [DISPLAY:RW]<==>[PARPORT:GND]
HD44780: wiring: [DISPLAY:ENABLE]<==>[PARPORT:STROBE (Pin 1)]
HD44780: wiring: [DISPLAY:ENABLE2]<==>[PARPORT:GND]
HD44780: wiring: [DISPLAY:ENABLE3]<==>[PARPORT:GND]
HD44780: wiring: [DISPLAY:ENABLE4]<==>[PARPORT:GND]
HD44780: wiring: [DISPLAY:BACKLIGHT]<==>[PARPORT:GND]
HD44780: wiring: [DISPLAY:GPO]<==>[PARPORT:GND]
HD44780: not using busy-flag checking


mode 1
Not using splash screen, everything works as it should.


mode 2
Using a splash screen with patched drv_HD44780.c

--- lcd4linux-0.10.0/drv_HD44780.c      2005-06-09 19:41:47.000000000 +0200
+++ /home/johan/work/lcd4linux-0.10.0/drv_HD44780.c  2005-08-09 
15:04:47.0000000
00 +0200
@@ -1489,7 +1489,7 @@

      /* say goodbye... */
      if (!quiet) {
-       drv_generic_text_greet("goodbye!", NULL);
+       drv_generic_text_greet("goodbye", NULL);
      }

      drv_HD_stop();

Indeed, I only removed the exclamation mark in the final splash screen. 
Everything works as it should. ["goodbye! dude" also worked, it seems the
exclamation mark is the cullprit]


mode 3
With the splash screen, starting lcd4linux is ok; stopping lcd4linux is 
ok; restarting results in a messed up display:
- the display only shows line 1 and line 3. Line 1 also shows content of 
line 2 and 4. The initial splash screen now looks like:


      2 4 6 8 0 2 4 6 8 0
    +--------------------+
  1 |orgCD4Linux 0.10.0 *|
  2 |                    |
  3 |    HD44780 20x4    |
  4 |                    |
    +--------------------+

- the contrast has changed such that the background of line 1 and 3 are 
      nearly black. The contrast can be changed by the potmeter I 
connected to my LCD-display.
But this does not give me line 2 and 4.


The final splash screen from mode 2 (that is with my "patch") manages to 
recover the display from being messed up.


I know my patch only solved a symptom. The real problem (why can't I 
show an exclamation mark) is still there. I hope one of the developpers 
is able to find this real problem.


Regards, Johan Swenker

Re: [lcd4linux] T6963 / corrupted output

[Christoph H. <e05...@st...>]

> When does this abort happen? When you stop it?
Output of "time lcd4linux -F -vvv" is
real    0m3.187s
user    0m0.110s
sys     0m0.075s
> Are you shure that serdisplib uses the same wiring than lcd4linux? 
Yes, double (and triple) checked that.
> Are you familiar with gdb?
Nope, but I _will_ soon be familiar with it, if that's the only
way to go.
;)
BTW: The Layouts L8x2, L16x2 and L20x2 all work okay - actually
the output is still corrupted, but lcd4linux doesn't abort and
I see something which looks like heavily distorted moving bars.
It's interesting that these layouts also show the glibc free()
error message - after I kill lcd4linux with CTRL+C.
Furthermore I found out in which cases lcd4linux aborts; it only
happens when the content of the selected layout is bigger than
the lcd size (21x8 char).
Two logs attached: First one shows lcd4linux "crashing" with the
"Default" Layout, second one shows lcd4linux _not_ "crashing"
with modified "Default" Layout (DiskBar and Eth0Bar length
reduced to 11).

===log1===
host:/usr/src/lcd4linux# lcd4linux -F -vvv
Version 0.10.1-CVS starting
plugin_cfg.c: Variable minute = '60000' (60000)
plugin_cfg.c: Variable tack = '100' (100)
plugin_cfg.c: Variable tick = '500' (500)
lcd4linux.c: initializing driver T6963
T6963: using model 'generic'
drv_T6963.c: malloc buffer 2 (21*64)=1344
udelay: CPU supports Time Stamp Counter
udelay: CPU runs at 1208.796000 MHz
udelay: using TSC delay loop, 1209 ticks per microsecond
T6963: using ppdev /dev/parports/0
T6963: wiring: DISPLAY:CE        - PARPORT:AUTOFD (Pin 14)
T6963: wiring: DISPLAY:CD        - PARPORT:INIT   (Pin 16)
T6963: wiring: DISPLAY:RD        - PARPORT:SLCTIN (Pin 17)
T6963: wiring: DISPLAY:WR        - PARPORT:STROBE (Pin  1)
initializing layout 'Default'
lcd4linux.c: starting main loop
*** glibc detected *** free(): invalid next size (fast): 0x0807e0e8 ***
Aborted
===end===

===log2===
host:/usr/src/lcd4linux# lcd4linux -F -vvv
Version 0.10.1-CVS starting
plugin_cfg.c: Variable minute = '60000' (60000)
plugin_cfg.c: Variable tack = '100' (100)
plugin_cfg.c: Variable tick = '500' (500)
lcd4linux.c: initializing driver T6963
T6963: using model 'generic'
drv_T6963.c: malloc buffer 2 (21*64)=1344
udelay: CPU supports Time Stamp Counter
udelay: CPU runs at 1208.796000 MHz
udelay: using TSC delay loop, 1209 ticks per microsecond
T6963: using ppdev /dev/parports/0
T6963: wiring: DISPLAY:CE        - PARPORT:AUTOFD (Pin 14)
T6963: wiring: DISPLAY:CD        - PARPORT:INIT   (Pin 16)
T6963: wiring: DISPLAY:RD        - PARPORT:SLCTIN (Pin 17)
T6963: wiring: DISPLAY:WR        - PARPORT:STROBE (Pin  1)
initializing layout 'Default'
lcd4linux.c: starting main loop
lcd4linux.c: got signal 2
lcd4linux.c: leaving main loop
T6963: shutting down.
*** glibc detected *** free(): invalid next size (fast): 0x0807e0e8 ***
Aborted
===end===

Greetings,
Christoph Haderer

[lcd4linux] Re: Optrex LCD display..

[Michael R. <re...@eu...>]

Hi Francisco,

sorry for the late answer. I'm very short on time at the moment.

>  Do you know if there is a way to drive this Optrex LCD 
>  display?

I've never seen this display before. From what I can read from the data
sheet, it doesn't use any of the standard LCD controllers (HD44780,
T6963, ...)

But of course it would be possible to write a driver for it.

Is the display a graphical one? If so, maybe it would be better to write
a serdisplib driver (so it would be useful for other applications too,
not only for lcd4linux). But if you want to give it a try to write a
lcd4linux driver, surely I will help you.

>  Any, really any advice would be usefull.. I could also contribute to 
>  modify or write a driver for linux but I really am clueless about the
>  power source circuit of this lcd..
I've never seen such a contrast circuit. But using a negative contrast
voltage is quite common (T6963 does so).


bye, Michael

-- 
Michael Reinelt <re...@eu...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

[lcd4linux] Re: lcd4linux 0.10

[Michael R. <re...@eu...>]

Hi there,

sorry for the delay, I'm very busy at the moment...

>    I'm having problems showing graphics characters with the Crystalfontz
> driver (631). Do you know any issue?

No, I don't. But I must say that I didn't try CF displays lately.

What exactly are your Problems? Bars? Icons?

bye, Michael

-- 
Michael Reinelt <re...@eu...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [lcd4linux] Syntax similar to "du"?

[Michael R. <re...@eu...>]

Hi Thomas,

> If there is the Statfs command which is similar to "df" (disk free) so
> I was wondering if there is a similar command to the "du" syntax?

No, I'm afraid there is no such plugin at the moment. And it would be
not trivial to write one: As you'd have to scan recursively through the
whole directory tree, this could take some time; therefore the plugin
should be asynchronous, using a seperate thread.

But it's not impossible. Volunteers are welcome :-)

HTH, Michael

-- 
Michael Reinelt <re...@eu...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [lcd4linux] T6963 / corrupted output

[Michael R. <re...@eu...>]

Hi Christoph,

> initializing layout 'Default'
> lcd4linux.c: starting main loop
> *** glibc detected *** free(): invalid next size (fast): 0x0807e0d8 ***
> Aborted

This is NotGood (TM)

When does this abort happen? When you stop it?

Are you shure that serdisplib uses the same wiring than lcd4linux? (but
I suppose if you'd use the wrong wiring, there would be no output at all)

Are you familiar with gdb? which a debugging session we could get an
idea what causes the above error.

TIA, Michael

-- 
Michael Reinelt <re...@eu...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

[lcd4linux] T6963 / corrupted output

[Christoph H. <e05...@st...>]

Hi all!
I recently bought a 128*64px t6963c based LCD. It works fine with the vendor
supplied Test program (Delphi source included in
http://www.pollin.de/shop/downloads/D120291S.ZIP) as well as with serdisplib
1.95 (so it works with lcd4linux if I use the serdisplib driver), but with
lcd4linux (CVS from 06.08.2005) and the T6963 driver I get only corrupted
output and a glibc free error message. Attached is the output of lcd4linux -F
-vvv :

===serdisplib (works), canceled with CTRL+C===
Version 0.10.1-CVS starting
plugin_cfg.c: Variable minute = '60000' (60000)
plugin_cfg.c: Variable tack = '500' (500)
plugin_cfg.c: Variable tick = '1000' (1000)
lcd4linux.c: initializing driver serdisplib
serdisplib: header  version 1.95
serdisplib: library version 1.95
serdisplib: using model 'T6963'
serdisplib: using options 'WIDTH=128;HEIGHT=64;FONTWIDTH=6;CHECK=1'
serdisplib: display size 128x64
initializing layout 'Default'
lcd4linux.c: starting main loop
lcd4linux.c: got signal 2
lcd4linux.c: leaving main loop
serdisplib: shutting down.
===end===

===T6963 (doesn't work), aborts===
Version 0.10.1-CVS starting
plugin_cfg.c: Variable minute = '60000' (60000)
plugin_cfg.c: Variable tack = '500' (500)
plugin_cfg.c: Variable tick = '1000' (1000)
lcd4linux.c: initializing driver T6963
T6963: using model 'generic'
drv_T6963.c: malloc buffer 2 (21*64)=1344
udelay: CPU supports Time Stamp Counter
udelay: CPU runs at 1209.185000 MHz
udelay: using TSC delay loop, 1210 ticks per microsecond
T6963: using ppdev /dev/parports/0
T6963: wiring: DISPLAY:CE        - PARPORT:AUTOFD (Pin 14)
T6963: wiring: DISPLAY:CD        - PARPORT:INIT   (Pin 16)
T6963: wiring: DISPLAY:RD        - PARPORT:SLCTIN (Pin 17)
T6963: wiring: DISPLAY:WR        - PARPORT:STROBE (Pin  1)

initializing layout 'Default'
lcd4linux.c: starting main loop
*** glibc detected *** free(): invalid next size (fast): 0x0807e0d8 ***
Aborted
===end===

Pictures of the right/corrupted greeting msg/default layout output are
available at http://stud3.tuwien.ac.at/~e0525270/lcd4linux/ .
I would be thankful for any comment/attempt to solve this problem.

Regards,
Christoph Haderer

[lcd4linux] Syntax similar to "du"?

[Thomas S. <se...@gm...>]

Hi,

I hope someone can help me: 

If there is the Statfs command which is similar to "df" (disk free) so
I was wondering if there is a similar command to the "du" syntax?

Thank you in advance

Greetings Thomas

Re: [lcd4linux] bulix.org down?

[Maxime P. <max...@bu...>]

Hi,

> is lcd4linux.bulix.org down? I can=B4t
> reach the online manuals.

I'm truly sorry for the downtime today, a power failure made all my
servers to go down :/ I jumped into the first train to get them back
online as soon as possible.

Everything should be Ok by now (and since 00:30 am).

Sorry again,
- Sam

--=20
Maxime Petazzoni (http://www.bulix.org)
 -- gone crazy, back soon. leave message.

[lcd4linux] bulix.org down?

[Thomas S. <se...@gm...>]

Heyho,

is lcd4linux.bulix.org down? I can=B4t
reach the online manuals.

And the second question: can anyone tell me
how the correct syntax for the calculation
of the used ram status might be?
(something like mem total - MemFree)

Greetings
Thomas

Re: [lcd4linux] Problem with colums and rows - Display 320*240

[Michael R. <re...@eu...>]

Hi Thomas,

> I am new to lcd4linux and I have a problem to get
> the right amount of colums and rows from a LC Display
> with 320*240 dots.

Well, I'd say that it has 320 columns and 240 rows :-)

If you're talking about *Text* rows/cols, just divide it by the font size.

bye, Michael

-- 
Michael Reinelt <re...@eu...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

[lcd4linux] Problem with colums and rows - Display 320*240

[MMC G. - S. <t.s...@mm...>]

Hi,
 
I am new to lcd4linux and I have a problem to get
the right amount of colums and rows from a LC Display
with 320*240 dots.
 
Can you help me please?
 
Thank you very much.
Thomas
 
se...@gm...

[lcd4linux] Re: init.d problem

[Petri D. <pet...@ik...>]

>Where"s the problem ? You did not even tell us if the LCD was working
>as expected after that.

As i said in the beginning of the mail when computer boots lcd4linux won't=
=20
start, well starts but gives only welcome message and dies. As the messages=
=20
in log shows it dies before 'initializing layout' should come. It works=20
perfectly if I start it after computer is fully booted using the same init.=
d=20
script.

Petri

Re: [lcd4linux] init.d problem

[Maxime P. <max...@bu...>]

Hi,

> I run lcd4linux from init.d script. When computer is booted
> lcd4linux doesn't start. If I run '/etc/init.d/lcd4linux restart'
> afterwards it works fine.  When I put -vv in init.d script and
> get...
> 
> on boot:

--snip--

> I'm running Gentoo Linux on AMD64. Any idea what could be wrong?


I don't see any error here. You increase verbosity by adding -vv, and
you comply about lcd4linux being verbose ?

Where's the problem ? You did not even tell us if the LCD was working
as expected after that.

- Sam

-- 
Maxime Petazzoni (http://www.bulix.org)
 -- gone crazy, back soon. leave message.

[lcd4linux] init.d problem

[Petri D. <pet...@ik...>]

Hi,

I run lcd4linux from init.d script. When computer is booted lcd4linux doesn=
't=20
start. If I run '/etc/init.d/lcd4linux restart' afterwards it works fine.=20
When I put -vv in init.d script and get...=20

on boot:
Jul 21 13:03:51 wood LCD4Linux[13183]: Version 0.10.1-CVS starting
Jul 21 13:03:51 wood LCD4Linux[13183]: plugin_cfg.c: Variable mail =3D=20
'300000' (300000)
Jul 21 13:03:51 wood LCD4Linux[13183]: plugin_cfg.c: Variable minute =3D=20
'60000' (60000)
Jul 21 13:03:51 wood LCD4Linux[13183]: plugin_cfg.c: Variable tack =3D=20
'100' (100)
Jul 21 13:03:51 wood LCD4Linux[13183]: plugin_cfg.c: Variable tick =3D=20
'500' (500)
Jul 21 13:03:51 wood LCD4Linux[13183]: lcd4linux.c: going background...
Jul 21 13:03:51 wood LCD4Linux[13299]: lcd4linux.c: initializing driver USB=
LCD
Jul 21 13:03:51 wood LCD4Linux[13299]: drv_USBLCD.c: using libusb
Jul 21 13:03:51 wood LCD4Linux[13299]: USBLCD: scanning for USBLCD...
Jul 21 13:03:51 wood LCD4Linux[13299]: USBLCD: found USBLCD V01.12 on bus 0=
03=20
device 004

on restart:
Jul 21 13:10:55 wood LCD4Linux[14460]: Version 0.10.1-CVS starting
Jul 21 13:10:55 wood LCD4Linux[14460]: plugin_cfg.c: Variable mail =3D=20
'300000' (300000)
Jul 21 13:10:55 wood LCD4Linux[14460]: plugin_cfg.c: Variable minute =3D=20
'60000' (60000)
Jul 21 13:10:55 wood LCD4Linux[14460]: plugin_cfg.c: Variable tack =3D=20
'100' (100)
Jul 21 13:10:55 wood LCD4Linux[14460]: plugin_cfg.c: Variable tick =3D=20
'500' (500)
Jul 21 13:10:55 wood LCD4Linux[14460]: lcd4linux.c: going background...
Jul 21 13:10:55 wood LCD4Linux[14461]: lcd4linux.c: initializing driver USB=
LCD
Jul 21 13:10:55 wood LCD4Linux[14461]: drv_USBLCD.c: using libusb
Jul 21 13:10:55 wood LCD4Linux[14461]: USBLCD: scanning for USBLCD...
Jul 21 13:10:55 wood LCD4Linux[14461]: USBLCD: found USBLCD V01.12 on bus 0=
03=20
device 004
Jul 21 13:10:58 wood LCD4Linux[14461]: initializing layout 'damu'
Jul 21 13:10:58 wood LCD4Linux[14461]: lcd4linux.c: starting main loop
Jul 21 13:10:58 wood LCD4Linux[14461]: plugin_i2c_sensors.c: using i2c sens=
ors=20
at (null) (from /etc/lcd4linux/lcd4linux.conf)
Jul 21 13:10:58 wood LCD4Linux[14461]: [POP3] No 'Plugin:POP3.server3' entr=
y=20
from /etc/lcd4linux/lcd4linux.conf, disabling POP3 account #3
Jul 21 13:10:58 wood LCD4Linux[14461]: [POP3] 2 POP3 accounts have been=20
succesfully defined

I'm running Gentoo Linux on AMD64. Any idea what could be wrong?

Petri

Re: [lcd4linux] serial HD44780

[paul k. <pau...@xs...>]

Ognjen Bezanov wrote:

>But will serial connections be supported in future?
>
>  
>
Only if someone finds the need for it, and does all the work. Just like 
Luis and I need the I2C support, so we did the work for it.

>What exactly is I2C, I know it is a serial bus, but where is it? Is
>there a I2C connector on my motherboard? or does it work using the
>serial/parallel ports. Where can I find more information regarding how
>to connect LCD displays
>to the I2C bus.
>
>  
>
I doubt if there is een i2c connector on your mainboard. I have a VIA 
EPIA mainboard, which has one. But most mainstream PC mainboards don't 
have one.
I2C is a 2-wire (clock and data line) serial bus. Mainly intended to 
interface with peripheral devices (NVRAM, digital potmeters etc.)
In 99-100% of the cases, to interface with user hardware (like an lcd 
display) a PCF8574 chip is used. This is a I2C to 8-bit IO expander.
datasheet can be found here:
http://www.semiconductors.philips.com/cgi-bin/pldb/pip/pcf8574p

I know there is kernel support to emulate i2c over the parallel port. 
But I am not sure if it is supported to do the same thing over serial 
port. (theoretically it is possible)

Good luck,

Paul