lcd4linux-users

[lcd4linux] Problem with lcd4linux 0.10.0 / framebuffer

[Julien B. <Dha...@ho...>]

Hi,

I recently installed lcd4linux on my clarkconnect box (ver3.2) to interface
with a matrix orbital GKL1223-25 display. I modified lcd4linux.conf as
explained in the doc. The startup message "LCD4Linux 0.10.0" appears on
screen, I can modify the contrast and turn on/off the backlight. However,
nothing else seems to go through as if the "Layout" part of the config file
wasn't read. lcd4linux -Fvv returns:

Version 0.10.0 starting
plugin_cfg.c: Variable minute = '60' (60)
plugin_cfg.c: Variable tack = '10' (10)
plugin_cfg.c: Variable tick = '50' (50)
lcd4linux.c: initializing driver MatrixOrbital
MatrixOrbital: using model 'GLK12232-25'
MatrixOrbital: using port '/dev/ttyS0' at 19200 baud
removing stale lockfile /var/lock/LCK..ttyS0
MatrixOrbital: framebuffer could not be allocated: malloc() failed

Anyone has an idea how to solve this?

Thanks very much,

Julien

Re: [lcd4linux] Problem with lcd4linux 0.10.0 / framebuffer

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

Hi Julien,

> I recently installed lcd4linux on my clarkconnect box (ver3.2) to interface
> with a matrix orbital GKL1223-25 display. I modified lcd4linux.conf as
> explained in the doc. The startup message "LCD4Linux 0.10.0" appears on
> screen, I can modify the contrast and turn on/off the backlight. However,
> nothing else seems to go through as if the "Layout" part of the config file
> wasn't read. lcd4linux -Fvv returns:
> 
> MatrixOrbital: framebuffer could not be allocated: malloc() failed

Well, the reason for malloc() failing is simle: looks like I've been too
lazy to enter all display sizes :-)

Take a look into drv_MatrixOrbital and look for your model name
(GKL1223-25). There you will find:

    {0x0f, "VK204-25", 4, 20, 0, 1, 1},
    {0x10, "GLC12232", -1, -1, 0, 1, 1},
    {0x13, "GLC24064", -1, -1, 0, 1, 1},
    {0x15, "GLK24064-25", -1, -1, 0, 1, 1},
    {0x22, "GLK12232-25", -1, -1, 0, 1, 1},
    {0x31, "LK404-AT", 4, 40, 8, 8, 2},

As you can see, all the GLC- and GLK-models have an unknown size. Enter
the correct size here, and you should be done.

And, *please*, return your corrections as a patch so others can benefit,
too.



TIA, Michael

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

Re: [lcd4linux] Problem with lcd4linux 0.10.0 / framebuffer

[Julien B. <Dha...@ho...>]

Hi Michael,

Never mind my last e-mail, I fond the file and modified it. Sorry about
that.
The GKL still doesn't work. Get the same error message. However, setting it
up as an LCD4041 seems to work.
One last question: I think the "clear" function does not work. I will
attempt to fix it but I must tell you that my knowledge of C is like
vaporware LOL

drv_generic_serial_write("\376\130", 2); --> the \376\130 these are decimal
number equivalent to ascii characters you send to the LCD right? Sequence
"command + command number".

Thanks for your patience,

Julien



On 1/30/06 11:36 PM, "Michael Reinelt" <re...@eu...> wrote:

> Hi Julien,
> 
>> I recently installed lcd4linux on my clarkconnect box (ver3.2) to interface
>> with a matrix orbital GKL1223-25 display. I modified lcd4linux.conf as
>> explained in the doc. The startup message "LCD4Linux 0.10.0" appears on
>> screen, I can modify the contrast and turn on/off the backlight. However,
>> nothing else seems to go through as if the "Layout" part of the config file
>> wasn't read. lcd4linux -Fvv returns:
>> 
>> MatrixOrbital: framebuffer could not be allocated: malloc() failed
> 
> Well, the reason for malloc() failing is simle: looks like I've been too
> lazy to enter all display sizes :-)
> 
> Take a look into drv_MatrixOrbital and look for your model name
> (GKL1223-25). There you will find:
> 
>   {0x0f, "VK204-25", 4, 20, 0, 1, 1},
>   {0x10, "GLC12232", -1, -1, 0, 1, 1},
>   {0x13, "GLC24064", -1, -1, 0, 1, 1},
>   {0x15, "GLK24064-25", -1, -1, 0, 1, 1},
>   {0x22, "GLK12232-25", -1, -1, 0, 1, 1},
>   {0x31, "LK404-AT", 4, 40, 8, 8, 2},
> 
> As you can see, all the GLC- and GLK-models have an unknown size. Enter
> the correct size here, and you should be done.
> 
> And, *please*, return your corrections as a patch so others can benefit,
> too.
> 
> 
> 
> TIA, Michael

Re: [lcd4linux] Problem with lcd4linux 0.10.0 / framebuffer

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

Hi Julien,


> Never mind my last e-mail, I fond the file and modified it. Sorry about
> that.
> The GKL still doesn't work. Get the same error message. 
You did compile it afterwards?

> However, setting it
> up as an LCD4041 seems to work.
Fine. But I'd like to get it to work the "correct" way, too....

> One last question: I think the "clear" function does not work. I will
> attempt to fix it but I must tell you that my knowledge of C is like
> vaporware LOL
> 
> drv_generic_serial_write("\376\130", 2); --> the \376\130 these are decimal
> number equivalent to ascii characters you send to the LCD right? Sequence
> "command + command number".

No, it's not decimal, but octal.
\376 (octal) is 254(decimal) or 0xfe (hex)
\130 (octal) is  88(decimal) or 0x58 (hex)

look at 'man ascii'


bye, Michael

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