<br><br><div><span class="gmail_quote">On 9/17/07, <b class="gmail_sendername">Brett Granger</b> <<a href="mailto:bdgranger@alum.mit.edu">bdgranger@alum.mit.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>Posting a follow-up, in case anyone else runs across this problem.<br><br>The SMK transceiver that came with the WinTV-PVR-USB2 MCE kit that I<br>recently purchased has a product Id that did not match either of the<br>
other 2 SMK products included in the list "known" to the mceusb2 driver.<br> Once I added an additional line with the correct product ID (0x0334)<br>to the appropriate entries in lirc_mceusb2.c and lirc_mceusb2.mod.c,
<br>recompiled, and reinstalled, all is working as it should.<br><br>As for the missing keys using the Streamzap remote, that was a case of<br>user error -- I did not restart lircd after putting the<br>streamzap-appropriate
lircd.conf in place...<br><br>Thanks to the users of this list, who gave me both hope and several<br>leads to chase down... Now I can use either remote on this system.<br><br>--Brett<br><br>Brett Granger wrote:<br>> Hi All,
<br>><br>> I have a problem somewhat similar to that described by Don Doumakes in<br>> posting <a href="http://mythtv.org/pipermail/mythtv-users/2007-September/193623.html">http://mythtv.org/pipermail/mythtv-users/2007-September/193623.html
</a><br>><br>> I have a new Ubuntu Feisty system, kernel 2.6.20-16 that I'm trying to<br>> bring up. Everything has been going great until trying to get lirc to work.<br>><br>> I have a Microsoft MCE remote that I got as part of the Hauppauge
<br>> WinTV-PVR-USB2 MCE kit. I've followed the instructions for downloading,<br>> compiling and installing the lirc_mceusb2 driver, using the 0.8.2 lirc<br>> tarball. Everything appears to compile fine, and I'm able to modprobe
<br>> the drivers.<br>><br>> However, when I actually attach the ir receiver and launch irw, it exits<br>> immediately and takes lircd down with it. In syslog, I see "could not<br>> open /dev/lirc; default_init(): No such device". It appears that when I
<br>> connect the ir receiver, the mceusb2 driver does not detect it and so<br>> does not actually create a device to go along with /dev/lirc? The<br>> device file is created as part of the "make install" step... When I
<br>> connect the receiver, I do get messages from the kernel acknowledging<br>> that a "new full speed USB device" is connected and that "configuration<br>> #1 chosen from 1 choice", so I think the USB part is fine.
<br>><br>> Any clues?<br>><br>> Additionally, I have a Streamzap remote on a different system (FC 6).<br>> When I compile the streamzap driver on the Ubuntu system, I at least see<br>> in syslog that the streamzap driver recognizes when the streamzap
<br>> receiver is attached and creates a corresponding /dev/lirc0 entry. irw<br>> doesn't exit immediately, but it does not report any keypresses (yes, I<br>> made sure to have the right lircd.conf file for the streamzap remote).
<br>> "mode2" does seem to detect pulses, so I think things are close there.<br>><br>> I'd rather use the MCE remote on this system and keep the streamzap on<br>> the other system, but will go with whatever works.
<br>><br>> Any thoughts would be greatly appreciated,<br>> --Brett Granger<br>></blockquote><div><br>Great, this means that now I have to buy the remote since it's $25 shipped :-)<br><br><a href="http://dealnews.com/deals/Windows-Vista-Media-Center-Remote-for-25-shipped/187605.html">
http://dealnews.com/deals/Windows-Vista-Media-Center-Remote-for-25-shipped/187605.html</a><br></div><br></div><br>