From: Drew C. <li...@dr...> - 2005-07-29 17:43:31
|
Greetings all, I am in the final stages of converting my HTPC from WinMCE to MythTV (Gentoo based). The one piece of hardware that has caused me trouble is the aforementioned remote. I have searched the web, forums, and this list's archives and found information on this remote to be sparse at best. This remote is not the same as the Remote Wonder 2, as some have assumed. The following links offer some images and physical comparisons with the previous versions. http://ati.com/products/remotewonderplus/index.html http://www.hothardware.com/printarticle.cfm?articleid=650 (scroll down) http://remotew.free.fr/index.htm What I have been able to determine is that this remote uses X10 hardware like the original Remote Wonder rather than Philips (RW2), which explains why it's receiver is physically identical (externally, at least) to the RW1. Because of this, I hope support for this remote will not be terribly hard to acquire. I have installed lirc (0.7.1) with the atiusb driver. The remote is indeed detected by the driver and lircd loads with no errors. However, irw reports no input. When I try to create my own conf file using irrecord, it receives no signal as well (errors with: 'irrecord: gap not found, can't continue' when instructed to hold down a button). My experience with linux is respectable (mostly server oriented), but I am by no means qualified to be writing drivers. I have browsed through the atiusb source and noticed that the same vendor and product code is shared by a RW1. This would explain why it is detected by the driver. Aside from that, the code is rather greekish to me. The following is all the relevant information I could think to gather from my system. Please let me know where I should look or what else I can offer to help achieve support of this remote. I'd prefer to spend the necessary time to get this working rather than having to purchase another remote. Thanks. -Drew Conner #lsusb -vvv Bus 002 Device 003: ID 0bc7:0004 X10 Wireless Technology, Inc. X10 Receiver Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0bc7 X10 Wireless Technology, Inc. idProduct 0x0004 X10 Receiver bcdDevice 2.00 iManufacturer 1 X10 Wireless Technology Inc iProduct 2 USB Receiver iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 Remote Wakeup MaxPower 2mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 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 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 # usbmodules -d /proc/bus/usb/002/003 lirc_atiusb # dmesg | grep lirc lirc_dev: IR Remote Control driver registered, at major 61 lirc_atiusb: USB remote driver for LIRC v0.4 lirc_atiusb: Paul Miller <pmi...@us...> lirc_dev: lirc_register_plugin:sample_rate: 0 lirc_atiusb[3]: X10 Wireless Technology Inc USB Receiver on usb2:3 usbcore: registered new driver lirc_atiusb # cat /var/log/everything/current | grep lirc [kernel] lirc_dev: IR Remote Control driver registered, at major 61 [kernel] lirc_dev: lirc_register_plugin:sample_rate: 0 [kernel] lirc_atiusb[3]: X10 Wireless Technology Inc USB Receiver on usb2:3 [lircd 0.7.1] lircd(atiusb) ready |
From: Paul M. <pmi...@us...> - 2005-08-01 13:40:12
|
Your remote should be detected as a RW1. Could you load the driver with debug=1 and post all the debugging information? Thanks! -Paul On Friday 29 July 2005 10:43 am, Drew Conner wrote: > Greetings all, > I am in the final stages of converting my HTPC from WinMCE to > MythTV (Gentoo based). The one piece of hardware that has caused > me trouble is the aforementioned remote. I have searched the web, > forums, and this list's archives and found information on this > remote to be sparse at best. > > This remote is not the same as the Remote Wonder 2, as some have > assumed. The following links offer some images and physical > comparisons with the previous versions. > > http://ati.com/products/remotewonderplus/index.html > http://www.hothardware.com/printarticle.cfm?articleid=650 (scroll > down) http://remotew.free.fr/index.htm > > What I have been able to determine is that this remote uses X10 > hardware like the original Remote Wonder rather than Philips (RW2), > which explains why it's receiver is physically identical > (externally, at least) to the RW1. Because of this, I hope support > for this remote will not be terribly hard to acquire. > > I have installed lirc (0.7.1) with the atiusb driver. The remote > is indeed detected by the driver and lircd loads with no errors. > However, irw reports no input. When I try to create my own conf > file using irrecord, it receives no signal as well (errors with: > 'irrecord: gap not found, can't continue' when instructed to hold > down a button). > > My experience with linux is respectable (mostly server oriented), > but I am by no means qualified to be writing drivers. I have > browsed through the atiusb source and noticed that the same vendor > and product code is shared by a RW1. This would explain why it is > detected by the driver. Aside from that, the code is rather > greekish to me. > > The following is all the relevant information I could think to > gather from my system. Please let me know where I should look or > what else I can offer to help achieve support of this remote. I'd > prefer to spend the necessary time to get this working rather than > having to purchase another remote. Thanks. > > -Drew Conner > > > #lsusb -vvv > > Bus 002 Device 003: ID 0bc7:0004 X10 Wireless Technology, Inc. X10 > Receiver Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 0 (Defined at Interface level) > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 8 > idVendor 0x0bc7 X10 Wireless Technology, Inc. > idProduct 0x0004 X10 Receiver > bcdDevice 2.00 > iManufacturer 1 X10 Wireless Technology Inc > iProduct 2 USB Receiver > iSerial 0 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 32 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0xa0 > Remote Wakeup > MaxPower 2mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 2 > bInterfaceClass 255 Vendor Specific Class > bInterfaceSubClass 0 > bInterfaceProtocol 0 > iInterface 0 > 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 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x02 EP 2 OUT > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0008 1x 8 bytes > bInterval 10 > > > # usbmodules -d /proc/bus/usb/002/003 > > lirc_atiusb > > > # dmesg | grep lirc > > lirc_dev: IR Remote Control driver registered, at major 61 > lirc_atiusb: USB remote driver for LIRC v0.4 > lirc_atiusb: Paul Miller <pmi...@us...> > lirc_dev: lirc_register_plugin:sample_rate: 0 > lirc_atiusb[3]: X10 Wireless Technology Inc USB Receiver on usb2:3 > usbcore: registered new driver lirc_atiusb > > > # cat /var/log/everything/current | grep lirc > > [kernel] lirc_dev: IR Remote Control driver registered, at major 61 > [kernel] lirc_dev: lirc_register_plugin:sample_rate: 0 > [kernel] lirc_atiusb[3]: X10 Wireless Technology Inc USB Receiver > on usb2:3 [lircd 0.7.1] lircd(atiusb) ready > > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration > Strategies from IBM. Find simple to follow Roadmaps, > straightforward articles, informative Webcasts and more! Get > everything you need to get up to speed, fast. > http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click |
From: Drew C. <li...@dr...> - 2005-08-01 21:44:40
|
Here's the output when the driver is loaded with the debug option. Let me know if there's anything else I can post that would be useful. - Drew Conner #dmesg lirc_dev: IR Remote Control driver registered, at major 61 lirc_atiusb: USB remote driver for LIRC v0.4 lirc_atiusb: Paul Miller <pmi...@us...> lirc_atiusb: debug mode enabled: $Id: lirc_atiusb.c,v 1.49 2005/03/12 11:32:14 lirc Exp $ lirc_atiusb[3]: usb_remote_probe: dev:ffff81003a843000, intf:ffff8100389f1e00, id:ffffffff88413bd0) lirc_atiusb[3]: scanning remote_list... lirc_atiusb[3]: remote type = 0 lirc_atiusb[3]: adding remote to list lirc_atiusb[3]: processing endpoint 0 lirc_atiusb[3]: acceptable inbound endpoint (0x81) found (maxp=8 len=5) lirc_atiusb[3]: adding ep=0x81 to list lirc_atiusb[3]: processing endpoint 1 lirc_atiusb[3]: acceptable outbound endpoint (0x2) found lirc_dev: lirc_register_plugin: sample_rate: 0 lirc_atiusb[3]: X10 Wireless Technology Inc USB Receiver on usb2:3 lirc_atiusb[3]: usb_remote_probe: initializing outbound ep lirc_atiusb[3]: send called (0x8004) lirc_atiusb[3]: usb out called lirc_atiusb[3]: send complete (0x8004) lirc_atiusb[3]: send called (0x8007) lirc_atiusb[3]: usb out called lirc_atiusb[3]: send complete (0x8007) usbcore: registered new driver lirc_atiusb Quoting Paul Miller <pmi...@us...>: > Your remote should be detected as a RW1. Could you load the driver > with debug=1 and post all the debugging information? > > Thanks! > -Paul > > On Friday 29 July 2005 10:43 am, Drew Conner wrote: >> Greetings all, >> I am in the final stages of converting my HTPC from WinMCE to >> MythTV (Gentoo based). The one piece of hardware that has caused >> me trouble is the aforementioned remote. I have searched the web, >> forums, and this list's archives and found information on this >> remote to be sparse at best. >> >> This remote is not the same as the Remote Wonder 2, as some have >> assumed. The following links offer some images and physical >> comparisons with the previous versions. >> >> http://ati.com/products/remotewonderplus/index.html >> http://www.hothardware.com/printarticle.cfm?articleid=650 (scroll >> down) http://remotew.free.fr/index.htm >> >> What I have been able to determine is that this remote uses X10 >> hardware like the original Remote Wonder rather than Philips (RW2), >> which explains why it's receiver is physically identical >> (externally, at least) to the RW1. Because of this, I hope support >> for this remote will not be terribly hard to acquire. >> >> I have installed lirc (0.7.1) with the atiusb driver. The remote >> is indeed detected by the driver and lircd loads with no errors. >> However, irw reports no input. When I try to create my own conf >> file using irrecord, it receives no signal as well (errors with: >> 'irrecord: gap not found, can't continue' when instructed to hold >> down a button). >> >> My experience with linux is respectable (mostly server oriented), >> but I am by no means qualified to be writing drivers. I have >> browsed through the atiusb source and noticed that the same vendor >> and product code is shared by a RW1. This would explain why it is >> detected by the driver. Aside from that, the code is rather >> greekish to me. >> >> The following is all the relevant information I could think to >> gather from my system. Please let me know where I should look or >> what else I can offer to help achieve support of this remote. I'd >> prefer to spend the necessary time to get this working rather than >> having to purchase another remote. Thanks. >> >> -Drew Conner >> >> >> #lsusb -vvv >> >> Bus 002 Device 003: ID 0bc7:0004 X10 Wireless Technology, Inc. X10 >> Receiver Device Descriptor: >> bLength 18 >> bDescriptorType 1 >> bcdUSB 1.10 >> bDeviceClass 0 (Defined at Interface level) >> bDeviceSubClass 0 >> bDeviceProtocol 0 >> bMaxPacketSize0 8 >> idVendor 0x0bc7 X10 Wireless Technology, Inc. >> idProduct 0x0004 X10 Receiver >> bcdDevice 2.00 >> iManufacturer 1 X10 Wireless Technology Inc >> iProduct 2 USB Receiver >> iSerial 0 >> bNumConfigurations 1 >> Configuration Descriptor: >> bLength 9 >> bDescriptorType 2 >> wTotalLength 32 >> bNumInterfaces 1 >> bConfigurationValue 1 >> iConfiguration 0 >> bmAttributes 0xa0 >> Remote Wakeup >> MaxPower 2mA >> Interface Descriptor: >> bLength 9 >> bDescriptorType 4 >> bInterfaceNumber 0 >> bAlternateSetting 0 >> bNumEndpoints 2 >> bInterfaceClass 255 Vendor Specific Class >> bInterfaceSubClass 0 >> bInterfaceProtocol 0 >> iInterface 0 >> 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 >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x02 EP 2 OUT >> bmAttributes 3 >> Transfer Type Interrupt >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0008 1x 8 bytes >> bInterval 10 >> >> >> # usbmodules -d /proc/bus/usb/002/003 >> >> lirc_atiusb >> >> >> # dmesg | grep lirc >> >> lirc_dev: IR Remote Control driver registered, at major 61 >> lirc_atiusb: USB remote driver for LIRC v0.4 >> lirc_atiusb: Paul Miller <pmi...@us...> >> lirc_dev: lirc_register_plugin:sample_rate: 0 >> lirc_atiusb[3]: X10 Wireless Technology Inc USB Receiver on usb2:3 >> usbcore: registered new driver lirc_atiusb >> >> >> # cat /var/log/everything/current | grep lirc >> >> [kernel] lirc_dev: IR Remote Control driver registered, at major 61 >> [kernel] lirc_dev: lirc_register_plugin:sample_rate: 0 >> [kernel] lirc_atiusb[3]: X10 Wireless Technology Inc USB Receiver >> on usb2:3 [lircd 0.7.1] lircd(atiusb) ready >> >> >> >> >> ------------------------------------------------------- >> SF.Net email is sponsored by: Discover Easy Linux Migration >> Strategies from IBM. Find simple to follow Roadmaps, >> straightforward articles, informative Webcasts and more! Get >> everything you need to get up to speed, fast. >> http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > |
From: Paul M. <pmi...@us...> - 2005-08-02 00:01:37
|
Could you also run irrecord and see if it prints anything in the logs when you press different buttons? On Monday 01 August 2005 02:44 pm, Drew Conner wrote: > Here's the output when the driver is loaded with the debug option. > Let me know > if there's anything else I can post that would be useful. > > - Drew Conner > > #dmesg > > lirc_dev: IR Remote Control driver registered, at major 61 > > lirc_atiusb: USB remote driver for LIRC v0.4 > lirc_atiusb: Paul Miller <pmi...@us...> > lirc_atiusb: debug mode enabled: $Id: lirc_atiusb.c,v 1.49 > 2005/03/12 11:32:14 lirc Exp $ > lirc_atiusb[3]: usb_remote_probe: dev:ffff81003a843000, > intf:ffff8100389f1e00, id:ffffffff88413bd0) > lirc_atiusb[3]: scanning remote_list... > lirc_atiusb[3]: remote type = 0 > lirc_atiusb[3]: adding remote to list > lirc_atiusb[3]: processing endpoint 0 > lirc_atiusb[3]: acceptable inbound endpoint (0x81) found (maxp=8 > len=5) lirc_atiusb[3]: adding ep=0x81 to list > lirc_atiusb[3]: processing endpoint 1 > lirc_atiusb[3]: acceptable outbound endpoint (0x2) found > lirc_dev: lirc_register_plugin: sample_rate: 0 > lirc_atiusb[3]: X10 Wireless Technology Inc USB Receiver on usb2:3 > lirc_atiusb[3]: usb_remote_probe: initializing outbound ep > lirc_atiusb[3]: send called (0x8004) > lirc_atiusb[3]: usb out called > lirc_atiusb[3]: send complete (0x8004) > lirc_atiusb[3]: send called (0x8007) > lirc_atiusb[3]: usb out called > lirc_atiusb[3]: send complete (0x8007) > usbcore: registered new driver lirc_atiusb > > Quoting Paul Miller <pmi...@us...>: > > Your remote should be detected as a RW1. Could you load the > > driver with debug=1 and post all the debugging information? > > > > Thanks! > > -Paul > > > > On Friday 29 July 2005 10:43 am, Drew Conner wrote: > >> Greetings all, > >> I am in the final stages of converting my HTPC from WinMCE to > >> MythTV (Gentoo based). The one piece of hardware that has > >> caused me trouble is the aforementioned remote. I have searched > >> the web, forums, and this list's archives and found information > >> on this remote to be sparse at best. > >> > >> This remote is not the same as the Remote Wonder 2, as some have > >> assumed. The following links offer some images and physical > >> comparisons with the previous versions. > >> > >> http://ati.com/products/remotewonderplus/index.html > >> http://www.hothardware.com/printarticle.cfm?articleid=650 > >> (scroll down) http://remotew.free.fr/index.htm > >> > >> What I have been able to determine is that this remote uses X10 > >> hardware like the original Remote Wonder rather than Philips > >> (RW2), which explains why it's receiver is physically identical > >> (externally, at least) to the RW1. Because of this, I hope > >> support for this remote will not be terribly hard to acquire. > >> > >> I have installed lirc (0.7.1) with the atiusb driver. The > >> remote is indeed detected by the driver and lircd loads with no > >> errors. However, irw reports no input. When I try to create my > >> own conf file using irrecord, it receives no signal as well > >> (errors with: 'irrecord: gap not found, can't continue' when > >> instructed to hold down a button). > >> > >> My experience with linux is respectable (mostly server > >> oriented), but I am by no means qualified to be writing drivers. > >> I have browsed through the atiusb source and noticed that the > >> same vendor and product code is shared by a RW1. This would > >> explain why it is detected by the driver. Aside from that, the > >> code is rather greekish to me. > >> > >> The following is all the relevant information I could think to > >> gather from my system. Please let me know where I should look > >> or what else I can offer to help achieve support of this remote. > >> I'd prefer to spend the necessary time to get this working > >> rather than having to purchase another remote. Thanks. > >> > >> -Drew Conner > >> > >> > >> #lsusb -vvv > >> > >> Bus 002 Device 003: ID 0bc7:0004 X10 Wireless Technology, Inc. > >> X10 Receiver Device Descriptor: > >> bLength 18 > >> bDescriptorType 1 > >> bcdUSB 1.10 > >> bDeviceClass 0 (Defined at Interface level) > >> bDeviceSubClass 0 > >> bDeviceProtocol 0 > >> bMaxPacketSize0 8 > >> idVendor 0x0bc7 X10 Wireless Technology, Inc. > >> idProduct 0x0004 X10 Receiver > >> bcdDevice 2.00 > >> iManufacturer 1 X10 Wireless Technology Inc > >> iProduct 2 USB Receiver > >> iSerial 0 > >> bNumConfigurations 1 > >> Configuration Descriptor: > >> bLength 9 > >> bDescriptorType 2 > >> wTotalLength 32 > >> bNumInterfaces 1 > >> bConfigurationValue 1 > >> iConfiguration 0 > >> bmAttributes 0xa0 > >> Remote Wakeup > >> MaxPower 2mA > >> Interface Descriptor: > >> bLength 9 > >> bDescriptorType 4 > >> bInterfaceNumber 0 > >> bAlternateSetting 0 > >> bNumEndpoints 2 > >> bInterfaceClass 255 Vendor Specific Class > >> bInterfaceSubClass 0 > >> bInterfaceProtocol 0 > >> iInterface 0 > >> 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 > >> Endpoint Descriptor: > >> bLength 7 > >> bDescriptorType 5 > >> bEndpointAddress 0x02 EP 2 OUT > >> bmAttributes 3 > >> Transfer Type Interrupt > >> Synch Type None > >> Usage Type Data > >> wMaxPacketSize 0x0008 1x 8 bytes > >> bInterval 10 > >> > >> > >> # usbmodules -d /proc/bus/usb/002/003 > >> > >> lirc_atiusb > >> > >> > >> # dmesg | grep lirc > >> > >> lirc_dev: IR Remote Control driver registered, at major 61 > >> lirc_atiusb: USB remote driver for LIRC v0.4 > >> lirc_atiusb: Paul Miller <pmi...@us...> > >> lirc_dev: lirc_register_plugin:sample_rate: 0 > >> lirc_atiusb[3]: X10 Wireless Technology Inc USB Receiver on > >> usb2:3 usbcore: registered new driver lirc_atiusb > >> > >> > >> # cat /var/log/everything/current | grep lirc > >> > >> [kernel] lirc_dev: IR Remote Control driver registered, at major > >> 61 [kernel] lirc_dev: lirc_register_plugin:sample_rate: 0 > >> [kernel] lirc_atiusb[3]: X10 Wireless Technology Inc USB > >> Receiver on usb2:3 [lircd 0.7.1] lircd(atiusb) ready > >> > >> > >> > >> > >> ------------------------------------------------------- > >> SF.Net email is sponsored by: Discover Easy Linux Migration > >> Strategies from IBM. Find simple to follow Roadmaps, > >> straightforward articles, informative Webcasts and more! Get > >> everything you need to get up to speed, fast. > >> http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > > > > ------------------------------------------------------- > > SF.Net email is sponsored by: Discover Easy Linux Migration > > Strategies from IBM. Find simple to follow Roadmaps, > > straightforward articles, informative Webcasts and more! Get > > everything you need to get up to speed, fast. > > http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration > Strategies from IBM. Find simple to follow Roadmaps, > straightforward articles, informative Webcasts and more! Get > everything you need to get up to speed, fast. > http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click |
From: Drew C. <li...@dr...> - 2005-08-02 02:41:06
|
When running irrecord, I receive an error after instructed to hold down a button: Hold down an arbitrary button. irrecord: gap not found, can't continue Also, when I run lircd in no-daemon mode and open irw in a seperate console, I get no messages in either window after pressing every button. Hope this helps. Thanks. -Drew Conner Quoting Paul Miller <pmi...@us...>: > Could you also run irrecord and see if it prints anything in the logs > when you press different buttons? > > On Monday 01 August 2005 02:44 pm, Drew Conner wrote: >> Here's the output when the driver is loaded with the debug option. >> Let me know >> if there's anything else I can post that would be useful. >> >> - Drew Conner >> >> #dmesg >> >> lirc_dev: IR Remote Control driver registered, at major 61 >> >> lirc_atiusb: USB remote driver for LIRC v0.4 >> lirc_atiusb: Paul Miller <pmi...@us...> >> lirc_atiusb: debug mode enabled: $Id: lirc_atiusb.c,v 1.49 >> 2005/03/12 11:32:14 lirc Exp $ >> lirc_atiusb[3]: usb_remote_probe: dev:ffff81003a843000, >> intf:ffff8100389f1e00, id:ffffffff88413bd0) >> lirc_atiusb[3]: scanning remote_list... >> lirc_atiusb[3]: remote type = 0 >> lirc_atiusb[3]: adding remote to list >> lirc_atiusb[3]: processing endpoint 0 >> lirc_atiusb[3]: acceptable inbound endpoint (0x81) found (maxp=8 >> len=5) lirc_atiusb[3]: adding ep=0x81 to list >> lirc_atiusb[3]: processing endpoint 1 >> lirc_atiusb[3]: acceptable outbound endpoint (0x2) found >> lirc_dev: lirc_register_plugin: sample_rate: 0 >> lirc_atiusb[3]: X10 Wireless Technology Inc USB Receiver on usb2:3 >> lirc_atiusb[3]: usb_remote_probe: initializing outbound ep >> lirc_atiusb[3]: send called (0x8004) >> lirc_atiusb[3]: usb out called >> lirc_atiusb[3]: send complete (0x8004) >> lirc_atiusb[3]: send called (0x8007) >> lirc_atiusb[3]: usb out called >> lirc_atiusb[3]: send complete (0x8007) >> usbcore: registered new driver lirc_atiusb >> >> Quoting Paul Miller <pmi...@us...>: >> > Your remote should be detected as a RW1. Could you load the >> > driver with debug=1 and post all the debugging information? >> > >> > Thanks! >> > -Paul >> > >> > On Friday 29 July 2005 10:43 am, Drew Conner wrote: >> >> Greetings all, >> >> I am in the final stages of converting my HTPC from WinMCE to >> >> MythTV (Gentoo based). The one piece of hardware that has >> >> caused me trouble is the aforementioned remote. I have searched >> >> the web, forums, and this list's archives and found information >> >> on this remote to be sparse at best. >> >> >> >> This remote is not the same as the Remote Wonder 2, as some have >> >> assumed. The following links offer some images and physical >> >> comparisons with the previous versions. >> >> >> >> http://ati.com/products/remotewonderplus/index.html >> >> http://www.hothardware.com/printarticle.cfm?articleid=650 >> >> (scroll down) http://remotew.free.fr/index.htm >> >> >> >> What I have been able to determine is that this remote uses X10 >> >> hardware like the original Remote Wonder rather than Philips >> >> (RW2), which explains why it's receiver is physically identical >> >> (externally, at least) to the RW1. Because of this, I hope >> >> support for this remote will not be terribly hard to acquire. >> >> >> >> I have installed lirc (0.7.1) with the atiusb driver. The >> >> remote is indeed detected by the driver and lircd loads with no >> >> errors. However, irw reports no input. When I try to create my >> >> own conf file using irrecord, it receives no signal as well >> >> (errors with: 'irrecord: gap not found, can't continue' when >> >> instructed to hold down a button). >> >> >> >> My experience with linux is respectable (mostly server >> >> oriented), but I am by no means qualified to be writing drivers. >> >> I have browsed through the atiusb source and noticed that the >> >> same vendor and product code is shared by a RW1. This would >> >> explain why it is detected by the driver. Aside from that, the >> >> code is rather greekish to me. >> >> >> >> The following is all the relevant information I could think to >> >> gather from my system. Please let me know where I should look >> >> or what else I can offer to help achieve support of this remote. >> >> I'd prefer to spend the necessary time to get this working >> >> rather than having to purchase another remote. Thanks. >> >> >> >> -Drew Conner >> >> >> >> >> >> #lsusb -vvv >> >> >> >> Bus 002 Device 003: ID 0bc7:0004 X10 Wireless Technology, Inc. >> >> X10 Receiver Device Descriptor: >> >> bLength 18 >> >> bDescriptorType 1 >> >> bcdUSB 1.10 >> >> bDeviceClass 0 (Defined at Interface level) >> >> bDeviceSubClass 0 >> >> bDeviceProtocol 0 >> >> bMaxPacketSize0 8 >> >> idVendor 0x0bc7 X10 Wireless Technology, Inc. >> >> idProduct 0x0004 X10 Receiver >> >> bcdDevice 2.00 >> >> iManufacturer 1 X10 Wireless Technology Inc >> >> iProduct 2 USB Receiver >> >> iSerial 0 >> >> bNumConfigurations 1 >> >> Configuration Descriptor: >> >> bLength 9 >> >> bDescriptorType 2 >> >> wTotalLength 32 >> >> bNumInterfaces 1 >> >> bConfigurationValue 1 >> >> iConfiguration 0 >> >> bmAttributes 0xa0 >> >> Remote Wakeup >> >> MaxPower 2mA >> >> Interface Descriptor: >> >> bLength 9 >> >> bDescriptorType 4 >> >> bInterfaceNumber 0 >> >> bAlternateSetting 0 >> >> bNumEndpoints 2 >> >> bInterfaceClass 255 Vendor Specific Class >> >> bInterfaceSubClass 0 >> >> bInterfaceProtocol 0 >> >> iInterface 0 >> >> 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 >> >> Endpoint Descriptor: >> >> bLength 7 >> >> bDescriptorType 5 >> >> bEndpointAddress 0x02 EP 2 OUT >> >> bmAttributes 3 >> >> Transfer Type Interrupt >> >> Synch Type None >> >> Usage Type Data >> >> wMaxPacketSize 0x0008 1x 8 bytes >> >> bInterval 10 >> >> >> >> >> >> # usbmodules -d /proc/bus/usb/002/003 >> >> >> >> lirc_atiusb >> >> >> >> >> >> # dmesg | grep lirc >> >> >> >> lirc_dev: IR Remote Control driver registered, at major 61 >> >> lirc_atiusb: USB remote driver for LIRC v0.4 >> >> lirc_atiusb: Paul Miller <pmi...@us...> >> >> lirc_dev: lirc_register_plugin:sample_rate: 0 >> >> lirc_atiusb[3]: X10 Wireless Technology Inc USB Receiver on >> >> usb2:3 usbcore: registered new driver lirc_atiusb >> >> >> >> >> >> # cat /var/log/everything/current | grep lirc >> >> >> >> [kernel] lirc_dev: IR Remote Control driver registered, at major >> >> 61 [kernel] lirc_dev: lirc_register_plugin:sample_rate: 0 >> >> [kernel] lirc_atiusb[3]: X10 Wireless Technology Inc USB >> >> Receiver on usb2:3 [lircd 0.7.1] lircd(atiusb) ready >> >> >> >> >> >> >> >> >> >> ------------------------------------------------------- >> >> SF.Net email is sponsored by: Discover Easy Linux Migration >> >> Strategies from IBM. Find simple to follow Roadmaps, >> >> straightforward articles, informative Webcasts and more! Get >> >> everything you need to get up to speed, fast. >> >> http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click >> > >> > ------------------------------------------------------- >> > SF.Net email is sponsored by: Discover Easy Linux Migration >> > Strategies from IBM. Find simple to follow Roadmaps, >> > straightforward articles, informative Webcasts and more! Get >> > everything you need to get up to speed, fast. >> > http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click >> >> ------------------------------------------------------- >> SF.Net email is sponsored by: Discover Easy Linux Migration >> Strategies from IBM. Find simple to follow Roadmaps, >> straightforward articles, informative Webcasts and more! Get >> everything you need to get up to speed, fast. >> http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > |
From: Paul M. <pmi...@us...> - 2005-08-03 00:24:03
|
So you loaded the driver in debug mode and when you press a button in irrecord, nothing shows up in the logs? Perhaps your remote needs a different init string. You may have to intercept the code that the Windows driver sends to the remote... I don't know how to do this. Perhaps someone else on this list knows. -Paul On Monday 01 August 2005 07:41 pm, Drew Conner wrote: > When running irrecord, I receive an error after instructed to hold > down a button: > > Hold down an arbitrary button. > irrecord: gap not found, can't continue > > Also, when I run lircd in no-daemon mode and open irw in a seperate > console, I get no messages in either window after pressing every > button. Hope this helps. > Thanks. > > -Drew Conner > > Quoting Paul Miller <pmi...@us...>: > > Could you also run irrecord and see if it prints anything in the > > logs when you press different buttons? > > > > On Monday 01 August 2005 02:44 pm, Drew Conner wrote: > >> Here's the output when the driver is loaded with the debug > >> option. Let me know > >> if there's anything else I can post that would be useful. > >> > >> - Drew Conner > >> > >> #dmesg > >> > >> lirc_dev: IR Remote Control driver registered, at major 61 > >> > >> lirc_atiusb: USB remote driver for LIRC v0.4 > >> lirc_atiusb: Paul Miller <pmi...@us...> > >> lirc_atiusb: debug mode enabled: $Id: lirc_atiusb.c,v 1.49 > >> 2005/03/12 11:32:14 lirc Exp $ > >> lirc_atiusb[3]: usb_remote_probe: dev:ffff81003a843000, > >> intf:ffff8100389f1e00, id:ffffffff88413bd0) > >> lirc_atiusb[3]: scanning remote_list... > >> lirc_atiusb[3]: remote type = 0 > >> lirc_atiusb[3]: adding remote to list > >> lirc_atiusb[3]: processing endpoint 0 > >> lirc_atiusb[3]: acceptable inbound endpoint (0x81) found (maxp=8 > >> len=5) lirc_atiusb[3]: adding ep=0x81 to list > >> lirc_atiusb[3]: processing endpoint 1 > >> lirc_atiusb[3]: acceptable outbound endpoint (0x2) found > >> lirc_dev: lirc_register_plugin: sample_rate: 0 > >> lirc_atiusb[3]: X10 Wireless Technology Inc USB Receiver on > >> usb2:3 lirc_atiusb[3]: usb_remote_probe: initializing outbound > >> ep lirc_atiusb[3]: send called (0x8004) > >> lirc_atiusb[3]: usb out called > >> lirc_atiusb[3]: send complete (0x8004) > >> lirc_atiusb[3]: send called (0x8007) > >> lirc_atiusb[3]: usb out called > >> lirc_atiusb[3]: send complete (0x8007) > >> usbcore: registered new driver lirc_atiusb > >> > >> Quoting Paul Miller <pmi...@us...>: > >> > Your remote should be detected as a RW1. Could you load the > >> > driver with debug=1 and post all the debugging information? > >> > > >> > Thanks! > >> > -Paul > >> > > >> > On Friday 29 July 2005 10:43 am, Drew Conner wrote: > >> >> Greetings all, > >> >> I am in the final stages of converting my HTPC from WinMCE to > >> >> MythTV (Gentoo based). The one piece of hardware that has > >> >> caused me trouble is the aforementioned remote. I have > >> >> searched the web, forums, and this list's archives and found > >> >> information on this remote to be sparse at best. > >> >> > >> >> This remote is not the same as the Remote Wonder 2, as some > >> >> have assumed. The following links offer some images and > >> >> physical comparisons with the previous versions. > >> >> > >> >> http://ati.com/products/remotewonderplus/index.html > >> >> http://www.hothardware.com/printarticle.cfm?articleid=650 > >> >> (scroll down) http://remotew.free.fr/index.htm > >> >> > >> >> What I have been able to determine is that this remote uses > >> >> X10 hardware like the original Remote Wonder rather than > >> >> Philips (RW2), which explains why it's receiver is physically > >> >> identical (externally, at least) to the RW1. Because of > >> >> this, I hope support for this remote will not be terribly > >> >> hard to acquire. > >> >> > >> >> I have installed lirc (0.7.1) with the atiusb driver. The > >> >> remote is indeed detected by the driver and lircd loads with > >> >> no errors. However, irw reports no input. When I try to > >> >> create my own conf file using irrecord, it receives no signal > >> >> as well (errors with: 'irrecord: gap not found, can't > >> >> continue' when instructed to hold down a button). > >> >> > >> >> My experience with linux is respectable (mostly server > >> >> oriented), but I am by no means qualified to be writing > >> >> drivers. I have browsed through the atiusb source and noticed > >> >> that the same vendor and product code is shared by a RW1. > >> >> This would explain why it is detected by the driver. Aside > >> >> from that, the code is rather greekish to me. > >> >> > >> >> The following is all the relevant information I could think > >> >> to gather from my system. Please let me know where I should > >> >> look or what else I can offer to help achieve support of this > >> >> remote. I'd prefer to spend the necessary time to get this > >> >> working rather than having to purchase another remote. > >> >> Thanks. > >> >> > >> >> -Drew Conner > >> >> > >> >> > >> >> #lsusb -vvv > >> >> > >> >> Bus 002 Device 003: ID 0bc7:0004 X10 Wireless Technology, > >> >> Inc. X10 Receiver Device Descriptor: > >> >> bLength 18 > >> >> bDescriptorType 1 > >> >> bcdUSB 1.10 > >> >> bDeviceClass 0 (Defined at Interface level) > >> >> bDeviceSubClass 0 > >> >> bDeviceProtocol 0 > >> >> bMaxPacketSize0 8 > >> >> idVendor 0x0bc7 X10 Wireless Technology, Inc. > >> >> idProduct 0x0004 X10 Receiver > >> >> bcdDevice 2.00 > >> >> iManufacturer 1 X10 Wireless Technology Inc > >> >> iProduct 2 USB Receiver > >> >> iSerial 0 > >> >> bNumConfigurations 1 > >> >> Configuration Descriptor: > >> >> bLength 9 > >> >> bDescriptorType 2 > >> >> wTotalLength 32 > >> >> bNumInterfaces 1 > >> >> bConfigurationValue 1 > >> >> iConfiguration 0 > >> >> bmAttributes 0xa0 > >> >> Remote Wakeup > >> >> MaxPower 2mA > >> >> Interface Descriptor: > >> >> bLength 9 > >> >> bDescriptorType 4 > >> >> bInterfaceNumber 0 > >> >> bAlternateSetting 0 > >> >> bNumEndpoints 2 > >> >> bInterfaceClass 255 Vendor Specific Class > >> >> bInterfaceSubClass 0 > >> >> bInterfaceProtocol 0 > >> >> iInterface 0 > >> >> 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 > >> >> Endpoint Descriptor: > >> >> bLength 7 > >> >> bDescriptorType 5 > >> >> bEndpointAddress 0x02 EP 2 OUT > >> >> bmAttributes 3 > >> >> Transfer Type Interrupt > >> >> Synch Type None > >> >> Usage Type Data > >> >> wMaxPacketSize 0x0008 1x 8 bytes > >> >> bInterval 10 > >> >> > >> >> > >> >> # usbmodules -d /proc/bus/usb/002/003 > >> >> > >> >> lirc_atiusb > >> >> > >> >> > >> >> # dmesg | grep lirc > >> >> > >> >> lirc_dev: IR Remote Control driver registered, at major 61 > >> >> lirc_atiusb: USB remote driver for LIRC v0.4 > >> >> lirc_atiusb: Paul Miller <pmi...@us...> > >> >> lirc_dev: lirc_register_plugin:sample_rate: 0 > >> >> lirc_atiusb[3]: X10 Wireless Technology Inc USB Receiver on > >> >> usb2:3 usbcore: registered new driver lirc_atiusb > >> >> > >> >> > >> >> # cat /var/log/everything/current | grep lirc > >> >> > >> >> [kernel] lirc_dev: IR Remote Control driver registered, at > >> >> major 61 [kernel] lirc_dev: lirc_register_plugin:sample_rate: > >> >> 0 [kernel] lirc_atiusb[3]: X10 Wireless Technology Inc USB > >> >> Receiver on usb2:3 [lircd 0.7.1] lircd(atiusb) ready > >> >> > >> >> > >> >> > >> >> > >> >> ------------------------------------------------------- > >> >> SF.Net email is sponsored by: Discover Easy Linux Migration > >> >> Strategies from IBM. Find simple to follow Roadmaps, > >> >> straightforward articles, informative Webcasts and more! Get > >> >> everything you need to get up to speed, fast. > >> >> http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > >> > > >> > ------------------------------------------------------- > >> > SF.Net email is sponsored by: Discover Easy Linux Migration > >> > Strategies from IBM. Find simple to follow Roadmaps, > >> > straightforward articles, informative Webcasts and more! Get > >> > everything you need to get up to speed, fast. > >> > http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > >> > >> ------------------------------------------------------- > >> SF.Net email is sponsored by: Discover Easy Linux Migration > >> Strategies from IBM. Find simple to follow Roadmaps, > >> straightforward articles, informative Webcasts and more! Get > >> everything you need to get up to speed, fast. > >> http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > > > > ------------------------------------------------------- > > SF.Net email is sponsored by: Discover Easy Linux Migration > > Strategies from IBM. Find simple to follow Roadmaps, > > straightforward articles, informative Webcasts and more! Get > > everything you need to get up to speed, fast. > > http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration > Strategies from IBM. Find simple to follow Roadmaps, > straightforward articles, informative Webcasts and more! Get > everything you need to get up to speed, fast. > http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click |