[mythtv-users] Troubles with Irtrans VFD

[tim dennis]

Another day, another test.

As a follow up to the VFD problems I have been having below, I decided to
check the response when  starting mythfrontend as per normal, then killing
the mythlcdserver pid, then starting mythlcdserver manually.

Basically the following:

1) Clean up:
$ pkill -HUP mythlcdserver (just to be sure to kill of any residuals before
test)

2) Start mythfrontend with verbose preferences:
$ mythfrontend -v all,nodatabase,nomedia

(Note: At this point mythfrontend has not connected to VFD display properly)

3) Find mythlcdserver PID:
$ ps ax | grep mythlcdserver

4) Kill mythlcdserver PID
$ sudo kill -9 3605

5) Manually start mythlcdserver with verbose preferences (within 10 seconds)
$ /usr/bin/mythlcdserver -v all -x 10


The result is that after killing mythlcdserver and restarting it manually it
connects perfectly and VFD starts displaying time and date, menu's work...
everything is good.

After this test I am now starting to believe that mythfrontend (as of 0.21)
is somehow responsible for the problem...

This afternoon I will start compiling and testing previous versions of
LCDproc (0.5.2, 0.5.1, 0.5.0... 0.4.3) just to be sure.



Tim



On Fri, Apr 18, 2008 at 7:41 AM, tim dennis <tdennis.sub at gmail.com> wrote:

> So I have compared the logs of Mythlcdserver fro the following three
> situations:
>
> A) Start mythfrontend (as normal)
> C) Start mythlcdserver then start mythfrontend
> D) Start mythlcdserver then start mythfrontend then "reload" frontend by
> running through the Setup/Appearances screens
>
> It looks like the following two lines do not appear when starting
> mythfrontend in all three situations.
>
> MythSocket(8bf7870:9): socket is readable
> MythSocket(8bf7870:9): cb->readyRead()
>
> For situation C: somehow when the frontend reloads after finishing the
> last Setup/Appearances page the first thing that happens is that the socket
> becomes readable and ready, thus enabling the VFD. It is almost as if
> mythfrontend is somehow initially blocking the socket. Perhaps this is
> timing related?
>
> Will do some further testing tonight... perhaps start mythfrontend as
> normal, kill mythlcdserver pid & start mythlcdserver again manually...see
> what happens.
>
> If anybody is having similar problems or has advise (or better yet a
> solution lol) please let me know.
>
> Tim
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20080420/57d56d6e/attachment.htm