From: Paul M. <pmi...@us...> - 2005-04-18 04:45:23
|
So when both mythtv and irw are connected, both clients will lockup or just mythtv? And you haven't been able to irw to lockup alone? It sounds like mythtv is doing something strange with lircd. How are you using mythtv with lirc? IIRC, there are two popular methods -- native lirc support and irxevent. Perhaps mythtv is stalling and causing lircd to lockup... -Paul On Sunday 17 April 2005 3:08 pm, you wrote: > Hi Paul, > > I haven't been able to duplicate it outside of mythtv yet -- is > that significant? I'm going to keep trying though, I'm attempting > to roughly duplicate what I do in mythtv. > > I ran irw in addition to mythtv, and when it locked up, the last > two lines in irw were normal: > > 00000014f7220000 00 down SAPPHIRE_ATIUSB_5000023600 > 00000014f7220000 01 down SAPPHIRE_ATIUSB_5000023600 > > and in /var/log/messages it was just: > > Apr 17 15:04:07 cochrane kernel: lirc_atiusb[2]: data received 14 > e7 22 f0 (ep=0x81 length=4) > > but nothing else. > > Anything else I can do in the meantime besides just trying to lock > it up while running just irw? > > Moses > > On Sun, 17 Apr 2005, Paul Miller wrote: > > Try reproducing it using another program, such as irw. Send any > > debugging output to me. > > > > Thanks, > > -Paul > > > > On Sunday 17 April 2005 11:05 am, Moses Leslie wrote: > > > [apologies if this is duplicated, sent from the wrong address > > > the first time] > > > > > > Hello, > > > > > > I'm using an ATI remote wonder I with a CVS version of lirc > > > from a couple days ago with a 2.4.30 kernel. > > > > > > Everything works great for a little while, but after a number > > > of button presses (seems to be a random number) the kernel > > > module no longer recognizes the remote signals. The thing that > > > seems to cause it more often is editing commercial flagging in > > > mythtv, I assume because it's a bunch of keypresses in a row. > > > > > > I did: > > > > > > modprobe lirc_atiusb debug=1 > > > > > > and it spit out a bunch more information while running, but > > > when it gets to the point that it stalls out, there's nothing > > > printed by the kernel when I press buttons (which leads me to > > > believe that it's the module rather than lircd). > > > > > > I can fix it by killing mythfrontend and lircd, rmmod'ing the > > > module and re-modprobing it, so it's not actually completely > > > stuck. > > > > > > Is there anything else I can do to help track this down? > > > > > > Thanks! > > > > > > Moses > > > > > > > > > ------------------------------------------------------- > > > SF email is sponsored by - The IT Product Guide > > > Read honest & candid reviews on hundreds of IT Products from > > > real users. Discover which products truly live up to the hype. > > > Start reading now. > > > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > > > > ------------------------------------------------------- > > SF email is sponsored by - The IT Product Guide > > Read honest & candid reviews on hundreds of IT Products from real > > users. Discover which products truly live up to the hype. Start > > reading now. > > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click |