lcd4linux-users — lcd4linux users

Re: [lcd4linux] AC_PYTHON_DEVEL

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

Hi Paul,

> Ok, did some further checking and searching. Turns out that I swig
> (www.swig.org) installed on my system as part of a dependency to another
> package. I assume that swig installed a file swig.m4 in the
> /usr/share/aclocal/
> This file contains a macro PYTHON_DEVEL which in turn requires
> AM_PATH_PYTHON

Good investigations, paul!

I can confirm the problem here. As soon as I install the swig.m4 file to
/usr/share/aclocal, I get the same error.

"I've seen all the things in Heaven and Earth"
"I've seen many things in Hell"

The problem is that swig uses a macro called PYTHON_DEVEL, while
lcd4linux uses one called AC_PYTHON_DEVEL (or MY_PYTHON_DEVEL). Somehow
aclocal ignores the AM_ or MY_ prefix, and executes the swig.m4, where I
found a reference to AM_PATH_PYTHON.

I renamed the AC_PYTH_PYTHON to AC_PATH__PYTHON (note the double
underscore), now it works here.

please test!


bye, Michael

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

Re: [lcd4linux] Newbie - confusing .conf file...

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

Hi there,

> I did just check, I don't have a /dev/parport0 on my system either. So
> this deveice specification wouldn't work for me either.
> I do have a dev/lp0 and a dev/par0 on my system, but I am not sure if it
> would mean the same device.

The device lcd4linux needs is the "ppdev" device, it is very important
not to confuse it with the lp device.

Normally you have to load the ppdev module (unless it's compiled into
the kernel, which would be unusual. So the first step is always a
'modprobe ppdev'.

You can verify that the driver is loaded by looking for a line in
/proc/devices which reads ' 99 ppdev' (the major number of the character
device is 99)

If you can't find the corresponding device file in /dev, try this:

find /dev -type c -major 99

well, at least I thought so :-) unfortunately there is no -major option
to 'find'.

unless you can locate the correct device file yourself, just create one:
'mknod /dev/parport0 c 99 0'


HTH, Michael

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

Re: [lcd4linux] Newbie - confusing .conf file...

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

Ok,

As far  as I can tell, the i2c sensors thing is not the source of your 
problem.

Second, now I am getting a bit confused too. :-)
I am using a display connect to an i2c bus, not a parallel port.
I did just check, I don't have a /dev/parport0 on my system either. So 
this deveice specification wouldn't work for me either.
I do have a dev/lp0 and a dev/par0 on my system, but I am not sure if it 
would mean the same device.

Since you are using FC3, I found this.
http://forums.fedoraforum.org/archive/index.php/t-49358.html
There is an entry from Terry Polzin in there. maybe that could solve it.

This one could also help

https://www.redhat.com/archives/fedora-test-list/2004-October/msg00251.html

Let me know if you have any luck.

regards,

Paul

I did notice that on of the other displays actually identifies the 
device as /dev/parports/0 (maybe that could work for you)

Kenneth Solberg wrote:

> Sorry Paul, I seem to have installed to different versions. I tried 
> again and this is what came up:
>
> [root@localhost bin]# lcd4linux -vv -F -f /etc/lcd4linux.conf
> Version 0.10.0-RC1 starting
> cfg.c: Warning: key <Row2>: value <Load%l1%L$r14l1> overwritten with 
> <%p CPU  %r MB RAM>
> cfg.c: Warning: key <Row1>: value <Busy %cb%% $r14cs+cb> overwritten 
> with <Load%l1%L$r10cs+cb>
> cfg.c: Warning: key <Row2>: value <%p CPU  %r MB RAM> overwritten with 
> <Disk%dm$R10dr+dw>
> i2c_sensors: unable to autodetect i2c sensors!
> [POP3] No 'Plugin:POP3.server1' entry from /etc/lcd4linux.conf, 
> disabling POP3 account #1
> [POP3] No 'Plugin:POP3.server2' entry from /etc/lcd4linux.conf, 
> disabling POP3 account #2
> [POP3] No 'Plugin:POP3.server3' entry from /etc/lcd4linux.conf, 
> disabling POP3 account #3
> lcd4linux.c: initializing driver HD44780
> HD44780: using model 'generic'
> HD44780: using parallel port
> HD44780: using 1 controller(s)
> HD44780: using 8 bit mode
> udelay: The file 'include/asm/msr.h' was missing at compile time.
> udelay: Even if your CPU supports TSC, it will not be used!
> udelay: You *really* should install msr.h and recompile LCD4linux!
> udelay: using gettimeofday() delay loop
> HD44780: using ppdev /dev/parport0
> HD44780: ioctl(/dev/parport0, PPCLAIM) failed: 6 No such device or address
> HD44780: could not initialize parallel port!
> HD44780: start display failed!
>
>
> I'm really getting confused now
>
> Kenneth

Re: [lcd4linux] Newbie - confusing .conf file...

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

Hi Kenneth,

For some reason I can't read your config file. It appears emtpy.

Could you try starting lcd4linux using:

lcd4linux -vv -F -f /etc/lcd4linux.conf

This will start lcd4linux in the forground with verbose output.

One more thing, what version of lcd4linux are you using?

Cheers,

Paul

Kenneth Solberg wrote:

> Hello Paul, I'm sorry to bother you with these newbiw questions...
>
> I edited my lcd4linux.conf the way you suggested, now I get this error 
> message when trying to run lcd4linux:
>
> [root@localhost bin]# lcd4linux -f /etc/lcd4linux.conf
> i2c_sensors: unable to autodetect i2c sensors!
> [root@localhost bin]#
>
> I have a pretty old motherboard (some Compaq model with a PIII 930MHz 
> processor) and I don't think it has got any temperature sensors on it. 
> (At least Motherboard Monitor didn't show any when I was running 
> Windows on it)
>
> Is there a way to disable lcd4linux temp probinf (i2c)?
>
> I have attached my lcd4linux.conf.
>
> Greatful for any help you are able to provide.
>
> Kenneth
>
> On 6/2/05, *Paul Kamphuis* <pau...@xs... 
> <mailto:pau...@xs...>> wrote:
>
>     Hi Kenneth,
>
>     I did a quick check, your wiring seems to be nearly similar to the
>     winamp wiring.
>     Only exception could be the RW signal. Not sure if it could be the
>     problem. But you could try to
>     specify it as GND.
>     check the WIKI page for the winamp wiring description:
>     https://ssl.bulix.org/projects/lcd4linux/wiki/HD44780
>
>     something like this.
>
>     # generic HD44780 display (WinAmp wiring)
>     Display HD44780-winamp {
>         Driver 'HD44780'
>         Model 'generic'
>         UseBusy 1
>         Port '/dev/parport0'
>         Size '20x4'
>         Wire {
>             RW      'GND'
>             RS      'INIT'
>             ENABLE  'STROBE'
>             ENABLE2 'GND'
>             GPO     'GND'
>         }
>     }
>
>     Are you sure you have set the correct display and layout to be used?
>     (near the end of the config sample file)
>
>     Display 'HD44780-winamp'
>     Layout 'L20x4'
>
>     Both of these entries are not in the default sample conf file.
>
>     If you stay having problems, please send me your config file
>
>     kind regards,
>
>     Paul
>
>
>
>     Kenneth Solberg wrote:
>
>     > Hello all!
>     >
>     > I have a 20x4 HD44780-compatible parallel LCD-display which I would
>     > like to use with my Fedora (Core 3) home webserver.
>     >
>     > The display works fine in Windows (Smartie53) thus it is not a
>     > hw-problem, but I can't get it to work with lcd4linux...
>     >
>     > The display is wired like this:
>     >
>     > LCD Pin - Symbol - Parallell pin
>     > 1               Vss            GND
>     > 2               Vdd            +5V
>     > 3                Vo            GND
>     > 4                RS        Parallelpin 16
>     > 5               R/W          GND
>     > 6                E           Parallelpin 1
>     > 7             DB0         Parallelpin 2
>     > 8              DB1      Parallelpin 3
>     > 9              DB2       Parallelpin 4
>     > 10            DB3       Parallelpin 5
>     > 11             DB4    Parallelpin 6
>     > 12             DB5    Parallelpin 7
>     > 13             DB6    Parallelpin 8
>     > 14             DB7  Parallelpin 9
>     > 15            A            +5V
>     > 16            K            GND
>     >
>     > Is this a predefined wiring (like 8-bit, winamp and so on)?
>     >
>     > Anyone who can help with a lcd4linux.conf? I suspect it to be a
>     driver
>     > problem, as long as the Driver section of the .conf is ok, I will
>     > probably be able to configure the rest myself...
>     >
>     > Thankful for all help...
>     >
>     > Ken
>     >
>
>
>
>

Re: [lcd4linux] AC_PYTHON_DEVEL

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

Hi Michael,

Maybe. I renamed the twy python macros to MY_... to ensure they don't

>collide with somnething else.
>
>I just checked in. Could you please try again with "--with-python"?
>
>
>bye, Michael
>
>  
>
I just got the latest version from CVS.
running ./bootstrap
directly produces this error
tux lcd4linux # ./bootstrap
aclocal: macro `AM_PATH_PYTHON' required but not defined

./configure seems to work ok.

But make still gives the same problem

tux lcd4linux # make
cd . && aclocal-1.4
aclocal: macro `AM_PATH_PYTHON' required but not defined
make: *** [aclocal.m4] Error 1
tux lcd4linux #

As you can see I am not even using the --with-python option at moment

So I still do have a problem, and it is even worse then I thought. I am 
not able to build the CVS version directly. :-(

Ok, did some further checking and searching. Turns out that I swig 
(www.swig.org) installed on my system as part of a dependency to another 
package. I assume that swig installed a file swig.m4 in the 
/usr/share/aclocal/
This file contains a macro PYTHON_DEVEL which in turn requires 
AM_PATH_PYTHON

I still can't understand how this can affect the lcd4linux build, but 
removing the swig.m4 file solved the build process.
Attached is this swig.m4 file, so if anyone cares to have a look at it. 
Feel free.
Question remains, do we have a problem or does swig have a problem.

cheers,

Paul

Re: [lcd4linux] AC_PYTHON_DEVEL (was: release lcd4linux-0.10.0 this weekend, wishlist)

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

Hi Paul,

>>> But I do want to remind you, that I still have a problem with that
>>> AC_PYTHON_PATH macro.
>>> If I leave the AC_PYTHON_DEVEL macro call in the configure.in file, and
>>> trigger a recreate of make and configure files. The whole thing blows
>>> up. =-O

>> Really? AC_PYTHON_DEVEL should not be called unless you specify
>> "--with-python".... that's why I added thsi switch. Don't tell me that
>> this didn't help :-)

> Mea culpa. I didn't test this changes yet. But anyway, if I do want
> python (and I *do* have python installed) I still would have the
> problem. right?

Maybe. I renamed the twy python macros to MY_... to ensure they don't
collide with somnething else.

I just checked in. Could you please try again with "--with-python"?


bye, Michael

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

Re: [lcd4linux] release lcd4linux-0.10.0 this weekend, wishlist

[Paul K. <pau...@xs...>]

Michael Reinelt wrote:

>Hi Paul,
>
>  
>
>>But I do want to remind you, that I still have a problem with that
>>AC_PYTHON_PATH macro.
>>If I leave the AC_PYTHON_DEVEL macro call in the configure.in file, and
>>trigger a recreate of make and configure files. The whole thing blows
>>up. =-O
>>    
>>
>
>Really? AC_PYTHON_DEVEL should not be called unless you specify
>"--with-python".... that's why I added thsi switch. Don't tell me that
>this didn't help :-)
>
>
>bye, Michael
>
>  
>
Mea culpa. I didn't test this changes yet. But anyway, if I do want 
python (and I *do* have python installed) I still would have the 
problem. right?

Paul

Re: [lcd4linux] release lcd4linux-0.10.0 this weekend, wishlist

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

Hi Paul,

> But I do want to remind you, that I still have a problem with that
> AC_PYTHON_PATH macro.
> If I leave the AC_PYTHON_DEVEL macro call in the configure.in file, and
> trigger a recreate of make and configure files. The whole thing blows
> up. =-O

Really? AC_PYTHON_DEVEL should not be called unless you specify
"--with-python".... that's why I added thsi switch. Don't tell me that
this didn't help :-)


bye, Michael

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

Re: [lcd4linux] release lcd4linux-0.10.0 this weekend, wishlist

[Paul K. <pau...@xs...>]

Hi Michael,

Good to hear we are now very close to an official release. :-)
But I do want to remind you, that I still have a problem with that 
AC_PYTHON_PATH macro.
If I leave the AC_PYTHON_DEVEL macro call in the configure.in file, and 
trigger a recreate of make and configure files. The whole thing blows 
up. =-O
I guess it wouldn't effect 'normal' users who only build the standard 
set of code. But someone doing a modification could end up in trouble.

cheers,

Paul

Michael Reinelt wrote:

>Hi all,
>
>looks like we solved the two outstanding issues 'compile i2c support'
>and 'compile without python', so version 0.10.0 of lcd4linux could be
>released this weekend.
>
>It would be great if if some people could do final tests with the latest
>code from CVS. It should
>
>- compile cleanly (without any warnings) without the need of specifying
>special options to 'configure'
>
>- work :-)
>
>Any feedback (positive and negative) would be very appreciated!
>
>
>As soon as 0.10.0 is released, there are lots of things I want to start
>with (keypad support, GPO's, events, timers, ...), and there sould be a
>*much* shorter release cycle in the future.
>
>To allow us to discuss and design some of the new features, I added a
>new area to the wiki called "Wish List", and added one entry as a
>starting point. I will glance over the tickets in the next days, and add
>my own ideas there. Please have a look, and contribute!
>
>
>bye, Michael
>
>  
>

[lcd4linux] release lcd4linux-0.10.0 this weekend, wishlist

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

Hi all,

looks like we solved the two outstanding issues 'compile i2c support'
and 'compile without python', so version 0.10.0 of lcd4linux could be
released this weekend.

It would be great if if some people could do final tests with the latest
code from CVS. It should

- compile cleanly (without any warnings) without the need of specifying
special options to 'configure'

- work :-)

Any feedback (positive and negative) would be very appreciated!


As soon as 0.10.0 is released, there are lots of things I want to start
with (keypad support, GPO's, events, timers, ...), and there sould be a
*much* shorter release cycle in the future.

To allow us to discuss and design some of the new features, I added a
new area to the wiki called "Wish List", and added one entry as a
starting point. I will glance over the tickets in the next days, and add
my own ideas there. Please have a look, and contribute!


bye, Michael

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

Re: [lcd4linux] Newbie - confusing .conf file...

[Paul K. <pau...@xs...>]

Hi Kenneth,

I did a quick check, your wiring seems to be nearly similar to the 
winamp wiring.
Only exception could be the RW signal. Not sure if it could be the 
problem. But you could try to
specify it as GND.
check the WIKI page for the winamp wiring description: 
https://ssl.bulix.org/projects/lcd4linux/wiki/HD44780

something like this.

# generic HD44780 display (WinAmp wiring)
Display HD44780-winamp {
    Driver 'HD44780'
    Model 'generic'
    UseBusy 1
    Port '/dev/parport0'
    Size '20x4'
    Wire {
        RW      'GND'
        RS      'INIT'
        ENABLE  'STROBE'
        ENABLE2 'GND'
        GPO     'GND'
    }
}

Are you sure you have set the correct display and layout to be used? 
(near the end of the config sample file)

Display 'HD44780-winamp'
Layout 'L20x4'

Both of these entries are not in the default sample conf file.

If you stay having problems, please send me your config file

kind regards,

Paul



Kenneth Solberg wrote:

> Hello all!
>  
> I have a 20x4 HD44780-compatible parallel LCD-display which I would 
> like to use with my Fedora (Core 3) home webserver.
>
> The display works fine in Windows (Smartie53) thus it is not a 
> hw-problem, but I can't get it to work with lcd4linux...
>
> The display is wired like this:
>
> LCD Pin - Symbol - Parallell pin
> 1               Vss            GND
> 2               Vdd            +5V
> 3                Vo            GND
> 4                RS        Parallelpin 16
> 5               R/W          GND
> 6                E           Parallelpin 1
> 7             DB0         Parallelpin 2
> 8              DB1      Parallelpin 3
> 9              DB2       Parallelpin 4
> 10            DB3       Parallelpin 5
> 11             DB4    Parallelpin 6
> 12             DB5    Parallelpin 7
> 13             DB6    Parallelpin 8
> 14             DB7  Parallelpin 9
> 15            A            +5V
> 16            K            GND
>  
> Is this a predefined wiring (like 8-bit, winamp and so on)?
>
> Anyone who can help with a lcd4linux.conf? I suspect it to be a driver 
> problem, as long as the Driver section of the .conf is ok, I will 
> probably be able to configure the rest myself...
>
> Thankful for all help...
>  
> Ken
>  

[lcd4linux] Newbie - confusing .conf file...

[Kenneth S. <ke...@gm...>]

Hello all!=20
 I have a 20x4 HD44780-compatible parallel LCD-display which I would like t=
o=20
use with my Fedora (Core 3) home webserver.

The display works fine in Windows (Smartie53) thus it is not a hw-problem,=
=20
but I can't get it to work with lcd4linux...=20

The display is wired like this:

LCD Pin - Symbol - Parallell pin
1 Vss GND
2 Vdd +5V=20
3 Vo GND
4 RS Parallelpin 16=20
5 R/W GND
6 E Parallelpin 1=20
7 DB0 Parallelpin 2=20
8 DB1 Parallelpin 3=20
9 DB2 Parallelpin 4=20
10 DB3 Parallelpin 5=20
11 DB4 Parallelpin 6=20
12 DB5 Parallelpin 7=20
13 DB6 Parallelpin 8=20
14 DB7 Parallelpin 9=20
15 A +5V=20
16 K GND
 Is this a predefined wiring (like 8-bit, winamp and so on)?

Anyone who can help with a lcd4linux.conf? I suspect it to be a driver=20
problem, as long as the Driver section of the .conf is ok, I will probably=
=20
be able to configure the rest myself...

Thankful for all help...
 Ken

Re: [lcd4linux] Way to readout SMART-values

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

Hi Andreas,

> Is there a way to printout any SMART-values 
> (the harddisc-temperature as example) to 
> display ?
> 
> I havent found anything in the Documentation,
> so i think its impossible at the moment?

There is no plugin for SMART or HD temperature at the moment. You could
try to use smartctl or hddtemp with the exec plugin.

smartctl may be hard to use because it prints out a lot of junk. Maybe
its possible to force it to just print the value yu're interested in.

with hddtemp it's easy: It has an option '-n' which prints only the
temperature. So

exec('/usr/sbin/hddtemp -n /dev/hda',1000)

should do the trick.


HTH, Michael

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

[lcd4linux] Way to readout SMART-values

[Andreas W. <An...@t-...>]

Hello List !

Is there a way to printout any SMART-values 
(the harddisc-temperature as example) to 
display ?

I havent found anything in the Documentation,
so i think its impossible at the moment?

Thanks for help,

Andreas

Re: [lcd4linux] Support for Sharp Graphic LCD?

[Ognjen B. <og...@ma...>]

Michael Reinelt wrote:

>Hi there,
>
>  
>
Heya!

>>I just found a graphic display (320x240) which I want to use with lcd4linux,
>>    
>>
>320x240 would be cool! Where have you got the display from?
>
>  
>
I havent got It yet, its selling on ebay and I wanted to check if its
supported before I bid.

>>Now It says that the display uses 4-bit mode and two drivers, as stated:
>>
>>Segment driver: LH1560F3*2 (SHARP)
>>Common driver: LH1562F4*1 (SHARP)
>>
>>Is this Graphic LCD display supported?
>>    
>>
>I'm afraid it is not, at least not at the moment.
>
>  
>
Shame... It would have been cool

>>I dont know whether the sharp
>>drivers are the same as the toshiba ones,
>>    
>>
>If you mean the T6963 by "Toshiba", I'm quite sure they're not.
>
>  
>
Yeah, thats what I meant

>>Here is a link to the datasheet if you need more info:
>>http://www.farnell.com/datasheets/39211.pdf
>>    
>>
>Well, this is probably the funniest data sheet I've ever seen: It
>contains a process diagram of their quality assurance department, but no
>real technical description of the display.
>
>  
>
perhaps that why the product failed ;)  The farnell page states that the
product is no longer sold.

The product can be seen here:

http://uk.farnell.com/jsp/endecaSearch/partDetail.jsp?SKU=4135090&N=401

>At the moment the farnell page is down (at least I cannot reach them),
>but yesterday I did a bit googeling on the "PG320240" IIRC, and found
>some pages about VDR's graphlcd-plugin... I read something about SED1330...
>
>  
>
the auction states that its made by a company called Powertip. And I
know about the existence of the SED display controllers so hopefullly it
is of a more well known design.

>If you can provide any additional info about this display, I'm shure we
>can write a driver together.
>
>  
>
Well, I havent got the display yet, we will see how much it goes for. If
lucky and I get it I wouldnt mind helping you (after all I do want it to
work with linux :) ).

As long as I dont have to do any coding, becuase I havent got a clue
about C programming (still learning python :P ) .

>bye, Michael
>
>  
>
320x240, thats big... 8)

Re: [lcd4linux] Support for Sharp Graphic LCD?

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

Hi there,

> I just found a graphic display (320x240) which I want to use with lcd4linux,
320x240 would be cool! Where have you got the display from?

> Now It says that the display uses 4-bit mode and two drivers, as stated:
> 
> Segment driver: LH1560F3*2 (SHARP)
> Common driver: LH1562F4*1 (SHARP)
> 
> Is this Graphic LCD display supported?
I'm afraid it is not, at least not at the moment.

> I dont know whether the sharp
> drivers are the same as the toshiba ones,
If you mean the T6963 by "Toshiba", I'm quite sure they're not.

> Here is a link to the datasheet if you need more info:
> http://www.farnell.com/datasheets/39211.pdf
Well, this is probably the funniest data sheet I've ever seen: It
contains a process diagram of their quality assurance department, but no
real technical description of the display.

At the moment the farnell page is down (at least I cannot reach them),
but yesterday I did a bit googeling on the "PG320240" IIRC, and found
some pages about VDR's graphlcd-plugin... I read something about SED1330...

If you can provide any additional info about this display, I'm shure we
can write a driver together.


bye, Michael

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

[lcd4linux] Cool Stuff

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

Hi there,

I just added a "Cool Stuff" section to the lcd4linux wiki. You all are
invited to add some sexy photos of lcd4linux there!

@geronet: please add the image you sent me lately in ICQ!


Thanks, Michael

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

[lcd4linux] Support for Sharp Graphic LCD?

[Ognjen B. <og...@ma...>]

I all,

I just found a graphic display (320x240) which I want to use with lcd4linux,

Now It says that the display uses 4-bit mode and two drivers, as stated:

Segment driver: LH1560F3*2 (SHARP)
Common driver: LH1562F4*1 (SHARP)

Is this Graphic LCD display supported? I dont know whether the sharp
drivers are the same as the toshiba ones,

Here is a link to the datasheet if you need more info:

http://www.farnell.com/datasheets/39211.pdf

[lcd4linux] Gouranga

[Neateye <nit...@ao...>]

Call out Gouranga be happy!!!
Gouranga Gouranga Gouranga ....
That which brings the highest happiness!!

Re: [lcd4linux] write on differnt lines of the display

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

Hi Alejandro,

> i continue testing my display. I=B4m working with pyserial, writing to
> /dev/ttyUSB0. Maybe you could help me with this question.

I'm afraid I can't. I don't know nothing about pyserial.

> Can you help me or recommend me some web where i could find
> information about it?

You should have a look at the data sheets Cwlinux provides. There are
some control codes that are necessary to do cursor positioning.


bye, Michael

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

[lcd4linux] write on differnt lines of the display

[<al3...@gm...>]

Hello again,

i continue testing my display. I=B4m working with pyserial, writing to
/dev/ttyUSB0. Maybe you could help me with this question.

The problem is that i send messages to the device but all the
characters are sended to the las line of the display. I=B4ve been trying
to write on the first line (or any other) without luck. I sended \n
character. I also tryied to send enough characters to overflow the
lines, but then, wen it arrives to the end of the display it starts
again on the first column, on the same line.

Can you help me or recommend me some web where i could find
information about it?

Thanks a lot.

Re: (SOLVED) Re: [lcd4linux] device or resource busy

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

Hi Alejandro,

> ok, i finally get it working. I don=B4t really understand how it does,
> but it does. I compiled once and again my kernel and in the last
> configuration i inserted all the usb modules which i founded. Really
> weird solution, but it works. I=B4ll have time to clean my kernel later=
.

Fine!

Your problem was that you've tried to handle the display with the usblcd
module, which is for a completely different display.

You neet the usbserial and pl2303 modules for Cwlinux LCD's /The pl2303
is a simple USB-to-serial converter).


Have Fun!
           Michael

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

(SOLVED) Re: [lcd4linux] device or resource busy

[<al3...@gm...>]

ok, i finally get it working. I don=B4t really understand how it does,
but it does. I compiled once and again my kernel and in the last
configuration i inserted all the usb modules which i founded. Really
weird solution, but it works. I=B4ll have time to clean my kernel later.

Thanks a lot for you help and your time.


On 4/19/05, Alejandro Moreno L=F3pez <al3...@gm...> wrote:
> im yet here, i=B4m sorry :-(. No good news by now.
>=20
> Compiling in the kernel statically doesn=B4t seems to help. How can i
> guess where is it now the display (if it is in any place)?
>=20
> this is what dmesg says me (if it helps):
>=20
> hub.c: new USB device 00:05.2-1, assigned address 3
> usb.c: kmalloc IF c55158a0, numif 1
> usb.c: new device strings: Mfr=3D0, Product=3D0, SerialNumber=3D0
> usb.c: unhandled interfaces on device
> usb.c: USB device 3 (vend/prod 0x67b/0x2303) is not claimed by any
> active driver.
>   Length              =3D 18
>   DescriptorType      =3D 01
>   USB version         =3D 1.10
>   Vendor:Product      =3D 067b:2303
>   MaxPacketSize0      =3D 8
>   NumConfigurations   =3D 1
>   Device version      =3D 2.02
>   Device Class:SubClass:Protocol =3D 00:00:00
>     Per-interface classes
> Configuration:
>   bLength             =3D    9
>   bDescriptorType     =3D   02
>   wTotalLength        =3D 0027
>   bNumInterfaces      =3D   01
>   bConfigurationValue =3D   01
>   iConfiguration      =3D   00
>   bmAttributes        =3D   a0
>   MaxPower            =3D  100mA
>=20
>   Interface: 0
>   Alternate Setting:  0
>     bLength             =3D    9
>     bDescriptorType     =3D   04
>     bInterfaceNumber    =3D   00
>     bAlternateSetting   =3D   00
>     bNumEndpoints       =3D   03
>     bInterface Class:SubClass:Protocol =3D   ff:00:00
>     iInterface          =3D   00
>     Endpoint:
>       bLength             =3D    7
>       bDescriptorType     =3D   05
>       bEndpointAddress    =3D   81 (in)
>       bmAttributes        =3D   03 (Interrupt)
>       wMaxPacketSize      =3D 000a
>       bInterval           =3D   01
>     Endpoint:
>       bLength             =3D    7
>       bDescriptorType     =3D   05
>       bEndpointAddress    =3D   02 (out)
>       bmAttributes        =3D   02 (Bulk)
>       wMaxPacketSize      =3D 0040
>       bInterval           =3D   00
>     Endpoint:
>       bLength             =3D    7
>       bDescriptorType     =3D   05
>       bEndpointAddress    =3D   83 (in)
>       bmAttributes        =3D   02 (Bulk)
>       wMaxPacketSize      =3D 0040
>       bInterval           =3D   00
> usb.c: kusbd: /sbin/hotplug add 3
> hub.c: port 2, portstatus 100, change 0, 12 Mb/s
> hub.c: port 1, portstatus 103, change 0, 12 Mb/s
> hub.c: port 2, portstatus 100, change 0, 12 Mb/s
> howap:~#
>=20
>=20
> On 4/19/05, Alejandro Moreno L=F3pez <al3...@gm...> wrote:
> > ok, just was i was thinking:
> >
> > howap:~# lcd4linux -Fvv
> > Version 0.10.0-RC2 starting
> > plugin_cfg.c: Variable minute =3D '60000' (60000)
> > plugin_cfg.c: Variable tack =3D '100' (100)
> > plugin_cfg.c: Variable tick =3D '500' (500)
> > lcd4linux.c: initializing driver Cwlinux
> > Cwlinux: using model 'CW12232'
> > Cwlinux: using port '/dev/tts/USB0' at 19200 baud
> > Cwlinux: open(/dev/tts/USB0) failed: No such file or directory
> >
> > but using usb/lcd didn=B4t help:
> >
> > howap:~# lcd4linux -Fvv
> > Version 0.10.0-RC2 starting
> > plugin_cfg.c: Variable minute =3D '60000' (60000)
> > plugin_cfg.c: Variable tack =3D '100' (100)
> > plugin_cfg.c: Variable tick =3D '500' (500)
> > lcd4linux.c: initializing driver Cwlinux
> > Cwlinux: using model 'CW12232'
> > Cwlinux: using port '/dev/usb/lcd' at 19200 baud
> > Cwlinux: open(/dev/usb/lcd) failed: Device or resource busy
> > howap:~#
> >
> > What i=B4ve just seen is that when i plug in the display i get:
> >
> > [....]
> > usb.c: USB device 2 (vend/proc .....) is not claimed by any active driv=
er
> > [....]
> >
> > not claimed by any active driver? is that ok?
> >
> > On 4/19/05, Alejandro Moreno L=F3pez <al3...@gm...> wrote:
> > > I=B4m using the module which comes with the kernel. It=B4s just the s=
ame
> > > driver, but i had problems when i tryed to compile it on my machine s=
o
> > > i tried compiling directly as a kernel module.
> > >
> > > Just now i=B4m compiling again but i wonder that the dev '/dev/tts/US=
B0'
> > > doesn=B4t exist... i mean that the kernel installs the device on
> > > /dev/usb/lcd. Or at least seems that. Ok, anyway, i=B4m going to try =
two
> > > different changes and i submit you my problems or (hopefully) success=
.
> > > I really need it working as soon as possible.
> > >
> > > Thanks a lot for your help.
> > >
> > > On 4/19/05, Michael Reinelt <re...@eu...> wrote:
> > > > Hi,
> > > >
> > > > > i=B4ve tried this
> > > > >
> > > > > Display LCDTerm {
> > > > >     Driver 'CW12232'
> > > > >     Port 'USB serial port'
> > > > >     Speed 19200
> > > > >     Size '20x4'
> > > > >     Icons 1
> > > > > }
> > > > >
> > > >
> > > > > howap:~/lcd/cvs/lcd4linux# lcd4linux -Fvv
> > > > > lcd4linux.c: initializing driver CW12232
> > > > > drv_init(CW12232) failed: no such driver
> > > >
> > > > Well, LCD4Linux is right here: There is no driver called "CW12232".
> > > > There is a driver called "Cwlinux", which supports a model called "=
CW12232".
> > > >
> > > > And even though it makes no difference, I have no clue why you're
> > > > calling your display section "LCDTerm".
> > > >
> > > > And what the heck do you think should lcd4linux do with "USB serial
> > > > port"? I'm working on the AI plugin, but it's not finished yet.
> > > >
> > > > Maybe you want to try this configuration:
> > > >
> > > > Display CW12232 {
> > > >     Driver 'Cwlinux'
> > > >     Model 'CW12232'
> > > >     Port '/dev/tts/USB0'
> > > >     Speed 19200
> > > >     Brightness 2
> > > >     Icons 1
> > > > }
> > > >
> > > > I just added this one as an "Example" to the wiki.
> > > >
> > > > I'm afraid I've to provide examples for every display.
> > > >
> > > > @all: someone out there who wants to write a graphically configurat=
ion
> > > > program? I have the dim feeling that we're in the need for it :-)
> > > >
> > > > bye, Michael
> > > >
> > > > sorry for being a bit rude. I've got a cold.
> > > >
> > > > --
> > > > Michael Reinelt <re...@eu...>
> > > > http://home.pages.at/reinelt
> > > > GPG-Key 0xDF13BA50
> > > > ICQ #288386781
> > > >
> > >
> >
>

Re: [lcd4linux] device or resource busy

[<al3...@gm...>]

im yet here, i=B4m sorry :-(. No good news by now.

Compiling in the kernel statically doesn=B4t seems to help. How can i
guess where is it now the display (if it is in any place)?

this is what dmesg says me (if it helps):

hub.c: new USB device 00:05.2-1, assigned address 3
usb.c: kmalloc IF c55158a0, numif 1
usb.c: new device strings: Mfr=3D0, Product=3D0, SerialNumber=3D0
usb.c: unhandled interfaces on device
usb.c: USB device 3 (vend/prod 0x67b/0x2303) is not claimed by any
active driver.
  Length              =3D 18
  DescriptorType      =3D 01
  USB version         =3D 1.10
  Vendor:Product      =3D 067b:2303
  MaxPacketSize0      =3D 8
  NumConfigurations   =3D 1
  Device version      =3D 2.02
  Device Class:SubClass:Protocol =3D 00:00:00
    Per-interface classes
Configuration:
  bLength             =3D    9
  bDescriptorType     =3D   02
  wTotalLength        =3D 0027
  bNumInterfaces      =3D   01
  bConfigurationValue =3D   01
  iConfiguration      =3D   00
  bmAttributes        =3D   a0
  MaxPower            =3D  100mA

  Interface: 0
  Alternate Setting:  0
    bLength             =3D    9
    bDescriptorType     =3D   04
    bInterfaceNumber    =3D   00
    bAlternateSetting   =3D   00
    bNumEndpoints       =3D   03
    bInterface Class:SubClass:Protocol =3D   ff:00:00
    iInterface          =3D   00
    Endpoint:
      bLength             =3D    7
      bDescriptorType     =3D   05
      bEndpointAddress    =3D   81 (in)
      bmAttributes        =3D   03 (Interrupt)
      wMaxPacketSize      =3D 000a
      bInterval           =3D   01
    Endpoint:
      bLength             =3D    7
      bDescriptorType     =3D   05
      bEndpointAddress    =3D   02 (out)
      bmAttributes        =3D   02 (Bulk)
      wMaxPacketSize      =3D 0040
      bInterval           =3D   00
    Endpoint:
      bLength             =3D    7
      bDescriptorType     =3D   05
      bEndpointAddress    =3D   83 (in)
      bmAttributes        =3D   02 (Bulk)
      wMaxPacketSize      =3D 0040
      bInterval           =3D   00
usb.c: kusbd: /sbin/hotplug add 3
hub.c: port 2, portstatus 100, change 0, 12 Mb/s
hub.c: port 1, portstatus 103, change 0, 12 Mb/s
hub.c: port 2, portstatus 100, change 0, 12 Mb/s
howap:~# =20



On 4/19/05, Alejandro Moreno L=F3pez <al3...@gm...> wrote:
> ok, just was i was thinking:
>=20
> howap:~# lcd4linux -Fvv
> Version 0.10.0-RC2 starting
> plugin_cfg.c: Variable minute =3D '60000' (60000)
> plugin_cfg.c: Variable tack =3D '100' (100)
> plugin_cfg.c: Variable tick =3D '500' (500)
> lcd4linux.c: initializing driver Cwlinux
> Cwlinux: using model 'CW12232'
> Cwlinux: using port '/dev/tts/USB0' at 19200 baud
> Cwlinux: open(/dev/tts/USB0) failed: No such file or directory
>=20
> but using usb/lcd didn=B4t help:
>=20
> howap:~# lcd4linux -Fvv
> Version 0.10.0-RC2 starting
> plugin_cfg.c: Variable minute =3D '60000' (60000)
> plugin_cfg.c: Variable tack =3D '100' (100)
> plugin_cfg.c: Variable tick =3D '500' (500)
> lcd4linux.c: initializing driver Cwlinux
> Cwlinux: using model 'CW12232'
> Cwlinux: using port '/dev/usb/lcd' at 19200 baud
> Cwlinux: open(/dev/usb/lcd) failed: Device or resource busy
> howap:~#
>=20
> What i=B4ve just seen is that when i plug in the display i get:
>=20
> [....]
> usb.c: USB device 2 (vend/proc .....) is not claimed by any active driver
> [....]
>=20
> not claimed by any active driver? is that ok?
>=20
> On 4/19/05, Alejandro Moreno L=F3pez <al3...@gm...> wrote:
> > I=B4m using the module which comes with the kernel. It=B4s just the sam=
e
> > driver, but i had problems when i tryed to compile it on my machine so
> > i tried compiling directly as a kernel module.
> >
> > Just now i=B4m compiling again but i wonder that the dev '/dev/tts/USB0=
'
> > doesn=B4t exist... i mean that the kernel installs the device on
> > /dev/usb/lcd. Or at least seems that. Ok, anyway, i=B4m going to try tw=
o
> > different changes and i submit you my problems or (hopefully) success.
> > I really need it working as soon as possible.
> >
> > Thanks a lot for your help.
> >
> > On 4/19/05, Michael Reinelt <re...@eu...> wrote:
> > > Hi,
> > >
> > > > i=B4ve tried this
> > > >
> > > > Display LCDTerm {
> > > >     Driver 'CW12232'
> > > >     Port 'USB serial port'
> > > >     Speed 19200
> > > >     Size '20x4'
> > > >     Icons 1
> > > > }
> > > >
> > >
> > > > howap:~/lcd/cvs/lcd4linux# lcd4linux -Fvv
> > > > lcd4linux.c: initializing driver CW12232
> > > > drv_init(CW12232) failed: no such driver
> > >
> > > Well, LCD4Linux is right here: There is no driver called "CW12232".
> > > There is a driver called "Cwlinux", which supports a model called "CW=
12232".
> > >
> > > And even though it makes no difference, I have no clue why you're
> > > calling your display section "LCDTerm".
> > >
> > > And what the heck do you think should lcd4linux do with "USB serial
> > > port"? I'm working on the AI plugin, but it's not finished yet.
> > >
> > > Maybe you want to try this configuration:
> > >
> > > Display CW12232 {
> > >     Driver 'Cwlinux'
> > >     Model 'CW12232'
> > >     Port '/dev/tts/USB0'
> > >     Speed 19200
> > >     Brightness 2
> > >     Icons 1
> > > }
> > >
> > > I just added this one as an "Example" to the wiki.
> > >
> > > I'm afraid I've to provide examples for every display.
> > >
> > > @all: someone out there who wants to write a graphically configuratio=
n
> > > program? I have the dim feeling that we're in the need for it :-)
> > >
> > > bye, Michael
> > >
> > > sorry for being a bit rude. I've got a cold.
> > >
> > > --
> > > Michael Reinelt <re...@eu...>
> > > http://home.pages.at/reinelt
> > > GPG-Key 0xDF13BA50
> > > ICQ #288386781
> > >
> >
>

Re: [lcd4linux] device or resource busy

[<al3...@gm...>]

ok, just was i was thinking:

howap:~# lcd4linux -Fvv
Version 0.10.0-RC2 starting
plugin_cfg.c: Variable minute =3D '60000' (60000)
plugin_cfg.c: Variable tack =3D '100' (100)
plugin_cfg.c: Variable tick =3D '500' (500)
lcd4linux.c: initializing driver Cwlinux
Cwlinux: using model 'CW12232'
Cwlinux: using port '/dev/tts/USB0' at 19200 baud
Cwlinux: open(/dev/tts/USB0) failed: No such file or directory

but using usb/lcd didn=B4t help:

howap:~# lcd4linux -Fvv
Version 0.10.0-RC2 starting
plugin_cfg.c: Variable minute =3D '60000' (60000)
plugin_cfg.c: Variable tack =3D '100' (100)
plugin_cfg.c: Variable tick =3D '500' (500)
lcd4linux.c: initializing driver Cwlinux
Cwlinux: using model 'CW12232'
Cwlinux: using port '/dev/usb/lcd' at 19200 baud
Cwlinux: open(/dev/usb/lcd) failed: Device or resource busy
howap:~#=20

What i=B4ve just seen is that when i plug in the display i get:

[....]
usb.c: USB device 2 (vend/proc .....) is not claimed by any active driver
[....]

not claimed by any active driver? is that ok?

On 4/19/05, Alejandro Moreno L=F3pez <al3...@gm...> wrote:
> I=B4m using the module which comes with the kernel. It=B4s just the same
> driver, but i had problems when i tryed to compile it on my machine so
> i tried compiling directly as a kernel module.
>=20
> Just now i=B4m compiling again but i wonder that the dev '/dev/tts/USB0'
> doesn=B4t exist... i mean that the kernel installs the device on
> /dev/usb/lcd. Or at least seems that. Ok, anyway, i=B4m going to try two
> different changes and i submit you my problems or (hopefully) success.
> I really need it working as soon as possible.
>=20
> Thanks a lot for your help.
>=20
> On 4/19/05, Michael Reinelt <re...@eu...> wrote:
> > Hi,
> >
> > > i=B4ve tried this
> > >
> > > Display LCDTerm {
> > >     Driver 'CW12232'
> > >     Port 'USB serial port'
> > >     Speed 19200
> > >     Size '20x4'
> > >     Icons 1
> > > }
> > >
> >
> > > howap:~/lcd/cvs/lcd4linux# lcd4linux -Fvv
> > > lcd4linux.c: initializing driver CW12232
> > > drv_init(CW12232) failed: no such driver
> >
> > Well, LCD4Linux is right here: There is no driver called "CW12232".
> > There is a driver called "Cwlinux", which supports a model called "CW12=
232".
> >
> > And even though it makes no difference, I have no clue why you're
> > calling your display section "LCDTerm".
> >
> > And what the heck do you think should lcd4linux do with "USB serial
> > port"? I'm working on the AI plugin, but it's not finished yet.
> >
> > Maybe you want to try this configuration:
> >
> > Display CW12232 {
> >     Driver 'Cwlinux'
> >     Model 'CW12232'
> >     Port '/dev/tts/USB0'
> >     Speed 19200
> >     Brightness 2
> >     Icons 1
> > }
> >
> > I just added this one as an "Example" to the wiki.
> >
> > I'm afraid I've to provide examples for every display.
> >
> > @all: someone out there who wants to write a graphically configuration
> > program? I have the dim feeling that we're in the need for it :-)
> >
> > bye, Michael
> >
> > sorry for being a bit rude. I've got a cold.
> >
> > --
> > Michael Reinelt <re...@eu...>
> > http://home.pages.at/reinelt
> > GPG-Key 0xDF13BA50
> > ICQ #288386781
> >
>