That's what I have been doing. I guess "full shutdown" probably doesn't mean much, but I almost always shutdown the computer completely. I learned early on that reboots don't do anything. -- Jonathan Martin www.niblet.us
>>Unfortunately, none of that worked. When this has happened in the past, >>the only thing that will correct it is moving it to another pci slot and >>trying again. > > which involves a full power off and time to let the caps die. Just > power down and unplug it for a minute or so and then restart it. > >>-- >>Jonathan Martin >>www.niblet.us >> >>> Jonathan Martin wrote: >>>> My remote will not respond now after several reboots and full >>>> shutdowns. >>>> Not sure what the problem is. The /dev/lirc0 device is present. >>>> dmesg >>>> gives the following: >>>> >>>> lirc_i2c: chip found @ 0x71 (Hauppauge IR (PVR150)) >>>> ivtv: i2c attach [client=Hauppauge IR (PVR150),ok] >>>> lirc_dev: lirc_register_plugin: sample_rate: 10 >>>> >>> OK, that means it found the hardware so everything should be ok. Next >>> step is to check that lircd is running, check the lircd logfile >>> (/var/log/lircd) and then try irw. If you are having trouble with >>> that >>> lot it would be something like: >>> >>> # start lirc >>> lircd --device=/dev/lirc0 --output=/dev/lircd >>> --pidfile=/var/run/lircd.pid >>> >>> # check for lirc* >>> ls -l /dev/lirc* >>> >>> # check logfile >>> less /var/log/lircd >>> >>> # try irw >>> irw >>> >>> press buttons, get output >>> >>>> I've had this before, but for some reason it seems the more I used >>>> mythtv >>>> the worse the situation gets. It works great for about 3 days after >>>> a >>>> fresh install, then slowly it gets worse. >>> Make sure mythtv is not running when you carry out the above tests, it >>> will only confuse the issue. >>> >>> >>> ------------------------------------------------------- >>> 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 >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/ivtv-devel >>> >> >> >> >> >>------------------------------------------------------- >>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 >>[email protected] >>https://lists.sourceforge.net/lists/listinfo/ivtv-devel > > > > > ------------------------------------------------------- > 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 > [email protected] > https://lists.sourceforge.net/lists/listinfo/ivtv-devel > ------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
