From: Scarfboy <sca...@ya...> - 2002-01-27 22:22:36
|
On Sunday 27 January 2002 04:18, Marius Kjeldahl wrote: > Hi, I'm trying to track down a bug with lirc and/or the Pinnacle driver. > The symptom is that suddenly the remote stops working. I've enabled logs > and this _always_ happens after the following is output in the lircd > log file (from hw_pinsys.c): > > Jan 27 03:29:02 james.kjeldahl.net lircd-0.6.5: timeout reading byte 1 > > After this happens (which it does sooner or later when I use my TV > remote control, i.e. a remote control that is not Pinnacle), the select > statement in lircd.c in waitfordata in the following section: > > if(timerisset(&tv) || reconnect) > { > ret=select(maxfd+1,&fds,NULL,NULL,&tv); > } > else > { > THIS ONE NEVER RETURNS => ret=select(maxfd+1,&fds,NULL,NULL,NULL); > } > > I've tried putting a timeout on that select, but that does not fix it > either, so I am suspecting that something is happening with the file > descriptor. > > Hopefully, somebody with more clues than me can help track this down. I suspect this is some driver issue. (Possibly some lirc code that has recently changed, i wouldn't know.) That timeout is `perfectly' normal, in fact a too-fast timeout in the first version of the driver made it say that all the time. (most of the time it just means an incomplete code, or some other infrared signal that the receiver doesn't see as three bytes, made it to the receiver. Actually, even with the current version i occasionaly get a timeout on byte 1 error) What i'm tryting to way is that the timeuot is unlikely to have something to do with your problem. --Bart (PS. Thought - is the device (/dev/lirc i believe, though it's ttyS{whatever} that counts) on a nonstandard filysystem?) |