lcd4linux-users

[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] 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.

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] init.d problem

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

Hi Petri,

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

> I tried to track this down and put debug messages in the source. It dies in 
> line 458 in drv_USBLCD.c on sleep(3); This sound very strange to me. But I 
> did put debug messages before and after and only got the message before. Also 
> when commenting this line or running with -q works. And this happens only 
> when booted, not if I use this same init.d script afterwards. Strange...

Why the heck should it hang on a sleep????

could you cut the sleep(3) into threee pieces of sleep(1), each followed
by a debug statement? Sounds crazy, but this *is* crazy....

better ideas anyone?

bye, Michael

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