From: Joseph K. <jos...@gm...> - 2007-01-12 00:17:33
|
What does the mode2 command give you. Type: mode2, point and press buttons. On 1/9/07, Tim Burrell <tim...@gm...> wrote: > > Hi everyone, > > I got a Hauppauge wintv pvr-150 recently and it comes bundled with a new > style mceusb2 remote. I've compiled lirc (0.8.1) with mceusb2 support, > and modprobing the lirc_mceusb2 module results in the following dmesg > output: > > lirc_mceusb2[17]: SMK eHome Infrared Transceiver on usb1:17 > > However, catting the device node, irw, and irrecord do not create any > results. No data comes from the device node at all, irw does not detect > any events (when using the mceusb configuration file), and irrecord just > errors out after 10 seconds saying that it saw no data. > > The remote in question is different than the config file states... there > are no colored buttons. It enumerates itself in lsusb as: > > Bus 001 Device 017: ID 0609:031d SMK Manufacturing, Inc. > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 0 (Defined at Interface level) > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 16 > idVendor 0x0609 SMK Manufacturing, Inc. > idProduct 0x031d > bcdDevice 0.00 > iManufacturer 1 SMK > iProduct 2 eHome Infrared Transceiver > iSerial 3 SM006KuP > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 32 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0xa0 > Remote Wakeup > MaxPower 100mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 2 > bInterfaceClass 255 Vendor Specific Class > bInterfaceSubClass 255 Vendor Specific Subclass > bInterfaceProtocol 255 Vendor Specific Protocol > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x01 EP 1 OUT > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0010 1x 16 bytes > bInterval 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0010 1x 16 bytes > bInterval 0 > > Note that I can see the red light blinking on the IR receiver when I > press buttons on the remote. I also had a previous remote working with > lirc so I am fairly confident that it's not just user error (however I > am open to trying anything anyone can think of to get it to work). But > right now it seems as if the IR receiver is not supported correctly by > the mceusb2 module. I have seen other references on the interweb to > people running into the same problem with the new mceusb2 remote bundled > with the pvr-150. > > Any help or insight would be greatly appreciated! Also, if it is a case > that something has changed with the remote, and it's not supported, I > will gladly assist in any way I can to make it work. > > Thanks, > > Tim. > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > |