Re: lirc 0.8.6 locks up with IMON USB device and PAD remote

[Johnny W. <joh...@gm...>]

My remote has not locked up (yet) but my LCD device has. It's usually
at about an hour. There's nothing in the logs about failed writes
unless I go to shut down the box. Then it logs these. I wonder if they
are related to the shutdown though and not the lock up that forced the
reboot.

And ideas?

On Wed, Nov 18, 2009 at 12:07 PM, Johnny Walker <joh...@gm...> wrote:
> Ok i've patched the lirc_imon driver out of cvs and replaced the following:
>
> /lib/modules/2.6.31-14-generic/kernel/ubuntu/lirc/lirc_dev/lirc_dev.ko
> /lib/modules/2.6.31-14-generic/kernel/ubuntu/lirc/lirc_imon/lirc_imon.ko
>
> there were also the new files already at:
>
> /lib/modules/2.6.31-14-generic/misc/
>
> I suppose now i just wait and see if the problem persists?
>
>
> On Tue, Nov 17, 2009 at 7:19 PM, Jarod Wilson <ja...@wi...> wrote:
>> On Nov 17, 2009, at 5:55 PM, Johnny Walker wrote:
>>
>>> using Mythbuntu 8.10 and lirc 0.8.6-0ubuntu2
>>> SilverStone LC11SM case with SoundGraph IMON USB device and PAD remote.
>>>
>>> This device locks up and stops responding after a time.
>>>
>>> The problem is that after about an hour maybe the device stops
>>> responding. It's almost exactly like the behavior described when on
>>> previous versions you were running only 1 lirc instance and not 2 tied
>>> together with a listen statement.
>>>
>>> When it locks up the LCD stops updating (it's not that good actually
>>> - I notice the LCD is not updating pretty often) The remote stops
>>> working altogether. I am unable to rmmod the lirc_imon module - it
>>> says it's in use.
>>>
>>> I've enable debug=1 in the modprobe.d/lirc.conf file but i'm not sure
>>> how to use this data.
>>>
>>> Is it possible that the '0.8.6-0ubuntu2' package of lirc still doesn't
>>> support this device correctly?
>>>
>>> What information do I need to contribute to help with this?
>>
>> Feedback when using your device with a test patch I posted two or three weeks back would be useful (you should be able to find it in the list archives, needs to be applied to the lirc_imon driver). Basically, so far as we can determine, some LCD/VFD can't keep up with constant writes to the display, so we hack in a delay before returning from any writes, hoping that with delay, the display can then keep up.
>>
>> However, it hasn't helped for at least one user, who has a display that locks up pretty much immediately. Most have manifested as periods of working, and an eventual lockup. The fun part in this is that neither my iMON LCD or VFD has any problems at all keeping up, even in a relatively fast machine constantly blasting data to it, so we need testing by folks such as yourself with problematic displays to figure out a fix. However, it does require patching, building and installing a kernel driver yourself.
>>
>> --
>> Jarod Wilson
>> ja...@wi...
>>
>>
>>
>>
>