Jim Reith wrote: >> Daniel and Mary-Beth Sherwood wrote: >> >>> Hi >>> >>> I have had a PVR150 system working for a while now and >>> use an ATI Remote Wonder as the remote control. Recently howvere I >>> have seen e-mails on this list >>> regarding getting the PVR150 IR Blaster working. >>> >>> This would be a good feature fo me to have so I can >>> control the SKY satellite box so I thought I'd have a >>> go at installing it following Mark's instructions. >>> >>> However when I run modprobe lirc_i2c, the /dev/lirc >>> device fails to appear. Looking at the kernel log >>> below, I can see that this is because the lirc_i2c >>> driver fails to find the device on the I2C bus. Ive >>> tried this on the patched version supplied by Mark and >>> the 0.7.2 release of LIRC. >>> >>> Any thoughts on this, and yes I do hae a non-MCE card >>> with a IR Blaster cable. >>> >> Given I have the exact same model of card (x2 in fact) this ought to >> work. Can you try powering the machine off and then on again and >> reloading the module? During testing I've managed to get the IR >> chip into a state where I had to do this in order to get it to start >> responding again (a soft reboot didn't clear the issue, presumably >> as the chip wasn't actually powered off). >> >> I can't think of anything else that might cause this -- at the very >> least the remote ought to work with the release version of LIRC. > > > I have a problem with this also. I'm still running with 3.6y as I > haven't had time to upgrade but when I fresh boot the remote works > but after a short time of recording or watching Live TV it goes > unresponsive. Bryan Mayland (if I recall correctly) said he thought > he had seen it before and I passed him some register values but > nothing popped out at him. Haven't heard anything since and haven't > had time to play with it further. Maybe my problem is different as > mine works for a while and then dies but it does initially work. > > > Use ivtvctl --reset-ir to get the remote back. To keep my remote going, > I have to > run this from /etc/crontab every minute. A kludge, but it works. > > Daniel Hyams
I tried running the above command last night through crontab and my remote still went out twice. I then tried through the command line to ensure it wasn't a crontab thing, but the remote never came back. Is there a log file to find out what might be causing the remote to stop listening? -- Jonathan Martin www.niblet.us ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
