From: Tomas D. <li...@to...> - 2006-09-01 20:18:57
|
hi everybody, i just got my remote, the shop where i bought it names it "Microsoft remote control x/Rcvr for MCE", so i hoped for support in usbmce/usbmce2. unfortunately it doesnt work. here's output from lsusb: Bus 003 Device 002: ID 1784:0001 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 16 idVendor 0x1784 idProduct 0x0001 bcdDevice 0.00 iManufacturer 1 Topseed iProduct 2 eHome Infrared Transceiver iSerial 3 TS00070X bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) 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 Device Status: 0x0001 Self Powered any idea which lirc module should work, or is this remote even supported? thanks T.D. |
From: Ian M. <ia...@ca...> - 2006-09-01 21:00:01
|
On Fri 01 Sep 2006 at 22:18:46 +0200, you wrote: > i just got my remote, the shop where i bought it names it "Microsoft > remote control x/Rcvr for MCE", so i hoped for support in > usbmce/usbmce2. unfortunately it doesnt work. > here's output from lsusb: > > any idea which lirc module should work, or is this remote even > supported? It's definitely supported. I'm using it. :-) lirc_mceusb2 is the module you want. You should see a line like this in your log when it's inserted: Sep 1 16:36:58 tourbillon kernel: lirc_mceusb2[4]: Philips eHome Infrared Trans ceiver on usb2:4 Do you see something like that? Otherwise, check that you have a valid /etc/lircd.conf in place for this remote control. Do you have ~/.lircrc in place? Is lircd running? Ian -- Ian Macdonald | Depart in pieces, i.e., split. ia...@ca... | http://www.caliban.org/ | | | |
From: Tomas D. <li...@to...> - 2006-09-01 21:27:28
|
On Fri, 1 Sep 2006 22:59:53 +0200 Ian Macdonald <ia...@ca...> wrote: > It's definitely supported. I'm using it. :-) > > lirc_mceusb2 is the module you want. You should see a line like this > in your log when it's inserted: thanks for reply, i'm afraid this is not the philips device, as lsusb says "topseed", or is this the same? i don't have /etc/lircd.conf because i cant even create one. when inserted, dmesg says (lirc_mceusb2 already modprobed): usb 3-2: new full speed USB device using uhci_hcd and address 3 usb 3-2: configuration #1 chosen from 1 choice irrecord then fails with: irrecord: could not init hardware (lircd running ? --> close it, check permissions) lircd is not running... > > Sep 1 16:36:58 tourbillon kernel: lirc_mceusb2[4]: Philips eHome > Infrared Trans ceiver on usb2:4 > > Do you see something like that? no, nothing like that. are you soure, that according to the lsusb output i sent, this is the philips device? if so, there's probably some error on my side and i'll keep debugging, just don't want to waste my time on mission impossible:-) > > Otherwise, check that you have a valid /etc/lircd.conf in place for > this remote control. Do you have ~/.lircrc in place? Is lircd running? > > Ian > -- > Ian Macdonald | Depart in pieces, i.e., split. > ia...@ca... | > http://www.caliban.org/ | > | > | |
From: Ian M. <ia...@ca...> - 2006-09-01 22:12:32
|
On Fri 01 Sep 2006 at 23:27:14 +0200, you wrote: > i'm afraid this is not the philips device, as lsusb says "topseed", or > is this the same? I don't know, but I should have read your lsusb output more closely and not just gone on what you were told the device was called at purchase time. > i don't have /etc/lircd.conf because i cant even create one. If it's compatible with the Philips device, you won't need to. The lirc distribution comes with an lircd.conf.mceusb file. Just rename that and try it out. > when inserted, dmesg says (lirc_mceusb2 already modprobed): > usb 3-2: new full speed USB device using uhci_hcd and address 3 > usb 3-2: configuration #1 chosen from 1 choice The fact it's trying to use lirc_mceusb2 sounds hopeful. Have you added anything to /etc/modprobe.conf to make it load lirc_mceusb2 or is it doing that on its own? Ian -- Ian Macdonald | Man who arrives at party two hours late ia...@ca... | will find he has been beaten to the punch. http://www.caliban.org/ | | | |
From: Tomas D. <li...@to...> - 2006-09-01 22:38:16
|
On Sat, 2 Sep 2006 00:12:24 +0200 Ian Macdonald <ia...@ca...> wrote: > On Fri 01 Sep 2006 at 23:27:14 +0200, you wrote: > > > i'm afraid this is not the philips device, as lsusb says "topseed", > > or is this the same? > > I don't know, but I should have read your lsusb output more closely > and not just gone on what you were told the device was called at > purchase time. > > > i don't have /etc/lircd.conf because i cant even create one. > > If it's compatible with the Philips device, you won't need to. The > lirc distribution comes with an lircd.conf.mceusb file. Just rename > that and try it out. hmm, tried it right now, lircd starts, but is not working.. > > > when inserted, dmesg says (lirc_mceusb2 already modprobed): > > usb 3-2: new full speed USB device using uhci_hcd and address 3 > > usb 3-2: configuration #1 chosen from 1 choice > > The fact it's trying to use lirc_mceusb2 sounds hopeful. Have you > added anything to /etc/modprobe.conf to make it load lirc_mceusb2 or > is it doing that on its own? no, it's not, i modprobed those manualy before connecting. connection of the device does not load any modules itself. > > Ian > -- > Ian Macdonald | Man who arrives at party two hours late > ia...@ca... | will find he has been beaten to the > punch. http://www.caliban.org/ | > | > | |
From: Ian M. <ia...@ca...> - 2006-09-01 22:06:49
|
On Fri 01 Sep 2006 at 22:18:46 +0200, you wrote: > i just got my remote, the shop where i bought it names it "Microsoft > remote control x/Rcvr for MCE", so i hoped for support in > usbmce/usbmce2. unfortunately it doesnt work. > here's output from lsusb: > > Bus 003 Device 002: ID 1784:0001 > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 0 (Defined at Interface level) > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 16 > idVendor 0x1784 > idProduct 0x0001 > bcdDevice 0.00 > iManufacturer 1 Topseed > iProduct 2 eHome Infrared Transceiver > iSerial 3 TS00070X > bNumConfigurations 1 Hmm, maybe Microsoft source these from various places. My unit, which is flat, black and has the Microsoft logo on it, identifies itself thus: Bus 002 Device 004: ID 0471:0815 Philips Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 16 idVendor 0x0471 Philips idProduct 0x0815 bcdDevice 0.00 iManufacturer 1 Philips iProduct 2 eHome Infrared Transceiver iSerial 3 PH00EK6O bNumConfigurations 1 So maybe the lirc_mceusb2 won't work for you; I don't know. Ian -- Ian Macdonald | Removing the straw that broke the camel's ia...@ca... | back does not necessarily allow the camel http://www.caliban.org/ | to walk again. | | |
From: Tomas D. <li...@to...> - 2006-09-01 22:13:37
|
On Sat, 2 Sep 2006 00:06:41 +0200 Ian Macdonald <ia...@ca...> wrote: > Hmm, maybe Microsoft source these from various places. > > My unit, which is flat, black and has the Microsoft logo on it, > identifies itself thus: yeah, flat, black, but no microsoft logo for me:-/ well, thanks anyway > > Bus 002 Device 004: ID 0471:0815 Philips > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 0 (Defined at Interface level) > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 16 > idVendor 0x0471 Philips > idProduct 0x0815 > bcdDevice 0.00 > iManufacturer 1 Philips > iProduct 2 eHome Infrared Transceiver > iSerial 3 PH00EK6O > bNumConfigurations 1 > > So maybe the lirc_mceusb2 won't work for you; I don't know. > > Ian > -- > Ian Macdonald | Removing the straw that broke the > camel's ia...@ca... | back does not necessarily allow > the camel http://www.caliban.org/ | to walk again. > | > | |
From: David K. <dcg...@dc...> - 2006-09-02 06:40:04
|
I'm pretty sure you will have to add the VID/PID values to the lirc_mceusb2 module. Near the top of lirc_mceusb2.c replace this: -- CODE -- #define VENDOR_PHILIPS 0x0471 #define VENDOR_SMK 0x0609 #define VENDOR_TATUNG 0x1460 static struct usb_device_id usb_remote_table [] = { { USB_DEVICE(VENDOR_PHILIPS, 0x0815) }, /* Philips eHome Infrared Transceiver */ { USB_DEVICE(VENDOR_SMK, 0x031d) }, /* SMK/Toshiba G83C0004D410 */ { USB_DEVICE(VENDOR_TATUNG, 0x9150) }, /* Tatung eHome Infrared Transceiver */ { } /* Terminating entry */ }; -- CODE -- With this: -- CODE -- #define VENDOR_PHILIPS 0x0471 #define VENDOR_SMK 0x0609 #define VENDOR_TATUNG 0x1460 #define VENDOR_TOPSEED 0x1784 static struct usb_device_id usb_remote_table [] = { { USB_DEVICE(VENDOR_PHILIPS, 0x0815) }, /* Philips eHome Infrared Transceiver */ { USB_DEVICE(VENDOR_SMK, 0x031d) }, /* SMK/Toshiba G83C0004D410 */ { USB_DEVICE(VENDOR_TATUNG, 0x9150) }, /* Tatung eHome Infrared Transceiver */ { USB_DEVICE(VENDOR_TOPSEED, 0x0001) }, /* Topseed eHome Infrared Transceiver */ { } /* Terminating entry */ }; -- CODE -- Recompile the module, and hope it works :) - David Tomas Dubec wrote: > On Sat, 2 Sep 2006 00:12:24 +0200 > Ian Macdonald <ia...@ca...> wrote: > >> On Fri 01 Sep 2006 at 23:27:14 +0200, you wrote: >> >>> i'm afraid this is not the philips device, as lsusb says "topseed", >>> or is this the same? >> I don't know, but I should have read your lsusb output more closely >> and not just gone on what you were told the device was called at >> purchase time. >> >>> i don't have /etc/lircd.conf because i cant even create one. >> If it's compatible with the Philips device, you won't need to. The >> lirc distribution comes with an lircd.conf.mceusb file. Just rename >> that and try it out. > > hmm, tried it right now, lircd starts, but is not working.. > >>> when inserted, dmesg says (lirc_mceusb2 already modprobed): >>> usb 3-2: new full speed USB device using uhci_hcd and address 3 >>> usb 3-2: configuration #1 chosen from 1 choice >> The fact it's trying to use lirc_mceusb2 sounds hopeful. Have you >> added anything to /etc/modprobe.conf to make it load lirc_mceusb2 or >> is it doing that on its own? > > no, it's not, i modprobed those manualy before connecting. connection > of the device does not load any modules itself. > |
From: Tomas D. <li...@to...> - 2006-09-02 07:55:13
|
On Sat, 02 Sep 2006 02:39:47 -0400 David Kuder <dcg...@dc...> wrote: > > I'm pretty sure you will have to add the VID/PID values to the > lirc_mceusb2 module. > Near the top of lirc_mceusb2.c replace this: > > -- CODE -- > #define VENDOR_PHILIPS 0x0471 > #define VENDOR_SMK 0x0609 > #define VENDOR_TATUNG 0x1460 > > static struct usb_device_id usb_remote_table [] = { > { USB_DEVICE(VENDOR_PHILIPS, 0x0815) }, > /* Philips eHome Infrared Transceiver */ > { USB_DEVICE(VENDOR_SMK, 0x031d) }, > /* SMK/Toshiba G83C0004D410 */ > { USB_DEVICE(VENDOR_TATUNG, 0x9150) }, > /* Tatung eHome Infrared Transceiver */ > { } /* Terminating entry */ > }; > -- CODE -- > > With this: > > -- CODE -- > #define VENDOR_PHILIPS 0x0471 > #define VENDOR_SMK 0x0609 > #define VENDOR_TATUNG 0x1460 > #define VENDOR_TOPSEED 0x1784 > > static struct usb_device_id usb_remote_table [] = { > { USB_DEVICE(VENDOR_PHILIPS, 0x0815) }, > /* Philips eHome Infrared Transceiver */ > { USB_DEVICE(VENDOR_SMK, 0x031d) }, > /* SMK/Toshiba G83C0004D410 */ > { USB_DEVICE(VENDOR_TATUNG, 0x9150) }, > /* Tatung eHome Infrared Transceiver */ > { USB_DEVICE(VENDOR_TOPSEED, 0x0001) }, > /* Topseed eHome Infrared Transceiver */ > { } /* Terminating entry */ > }; > -- CODE -- > > Recompile the module, and hope it works :) > > - David > YEAH! it does, thank you very very much! should i send a patch somewhere? |
From: muaddib <mua...@gm...> - 2006-11-21 18:31:06
|
I seem to have the same problem. I have a remote that sounds like the one you have from what seems to be the same company (www.jpcco.com). My lsusb output uses a different name though, and as I am very new to lirc and linux it would be very nice if you could send the patch at least here. Of course I would like my remote added aswell if it is not too much to ask. I guess it should be something like, #define VENDOR_JESSLINK 0x0766 ... { USB_DEVICE(VENDOR_TOPSEED, 0x0204) }, /* Jess-Link Products Co., Ltd */ Bus 001 Device 004: ID 0766:0204 Jess-Link Products Co., Ltd Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0766 Jess-Link Products Co., Ltd idProduct 0x0204 bcdDevice 0.01 iManufacturer 1 iProduct 2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 59 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 4 bmAttributes 0xa0 Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Devices bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 1 Keyboard iInterface 5 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.00 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 65 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Devices bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 6 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.00 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 244 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0005 1x 5 bytes bInterval 10 -- View this message in context: http://www.nabble.com/MCE-remote-tf2204637.html#a7476956 Sent from the LIRC mailing list archive at Nabble.com. |