From: Cymen V. <cym...@gm...> - 2006-02-08 01:17:41
Attachments:
lirc_atiusb.c-diff.txt
|
I believe that I have found the correct init code(s) for the Remote Wonder Plus. I used a snooping program on Windows. I made the following changes to drivers/lirc_atiusb/lirc_atiusb.c: ---------------------------------------------------------------------------= ------------------ --- lirc_atiusb.c 2006-01-29 12:25:57.000000000 -0600 +++ ../../../lirc-good/drivers/lirc_atiusb/lirc_atiusb.c =20 2006-02-07 19:07:03.362306424 -0600 @@ -147,9 +147,9 @@ static struct usb_device_id usb_remote_t /* init strings */ #define USB_OUTLEN 7 -static char init1[] =3D {0x01, 0x00, 0x20, 0x14}; -static char init2[] =3D {0x01, 0x00, 0x20, 0x14, 0x20, 0x20, 0x20}; - +static char init1[] =3D {0x80, 0x05, 0x1b, 0x15, 0x14, 0x20, 0x24, 0x15}; +static char init2[] =3D {0x83, 0x03}; +static char init3[] =3D {0x84, 0xd7, 0x020}; struct in_endpt { @@ -1034,8 +1034,9 @@ static void send_outbound_init(struct ir usb_sndintpipe(ir->usbdev, oep->ep->bEndpointAddress), oep->buf, USB_OUTLEN, usb_remote_send, oep, oep->ep->bInterva= l); - send_packet(oep, 0x8004, init1); - send_packet(oep, 0x8007, init2); + send_packet(oep, 0x8007, init1); + send_packet(oep, 0x8002, init2); + send_packet(oep, 0x8003, init3); } } ---------------------------------------------------------------------------= ------------------ The mode2 results: [19:02:18] mythtv tools # # 1st with RW1/2 pressing keys 1,2,3 [19:02:23] mythtv tools # ./mode2 -d /dev/lirc/0 code: 0x14e20d0000 code: 0x14e20d0000 code: 0x14e30e0000 code: 0x14e30e0000 code: 0x14e40f0000 code: 0x14e40f0000 [19:02:35] mythtv tools # # now with Remote Wonder Plus pressing keys 1,2,3 [19:02:48] mythtv tools # ./mode2 -d /dev/lirc/0 code: 0x14b31b0000 code: 0x15e20d0000 code: 0x15e20d0000 code: 0x15638e0000 code: 0x15638e0000 code: 0x14c81f0000 code: 0x15e40f0000 code: 0x15e40f0000 code: 0x155a8d0000 code: 0x15628d0000 code: 0x15628d0000 code: 0x15e30e0000 code: 0x15e30e0000 code: 0x15648f0000 code: 0x15648f0000 It seems like the keys are 0x15 instead of 0x14 but every once in a while the 0x1564..instead of 0x15e.. pops up. I tried irw and the old remote is still spitting out keypresses but the new one isn't there yet. I am not surprised but I'm new to the lirc source so I'm going to poke around there next. Advice is welcomed! I believe only have one of the two older remotes so I do not know if all three are now functional or if one got borked by my change. Cymen |
From: Aidan C. <ai...@mi...> - 2006-03-11 22:30:13
|
Hi, I am a relative newbie to linux & c, but I have an ATI Remote Wonder Plus that I am trying to get to work with LIRC. I followed your changes as best as I could, but am now getting the following error: > /usr/local/sbin/lircd --nodaemon lircd: lircd(atiusb) ready (then as soon as I try & run irw..) lircd: accepted new client on /dev/lircd lircd: could not open /dev/lirc lircd: default_init(): No such device lircd: caught signal Terminated ---- To get to this stage: I downloaded the latest CVS version. I modified the lirc_atiusb.c file manually because applying a diff file did not work: I replaced: static char init1[] = {0x01, 0x00, 0x20, 0x14}; static char init2[] = {0x01, 0x00, 0x20, 0x14, 0x20, 0x20, 0x20}; With: static char init1[] = {0x80, 0x05, 0x1b, 0x15, 0x14, 0x20, 0x24, 0x15}; static char init2[] = {0x83, 0x03}; static char init3[] = {0x84, 0xd7, 0x020}; And: send_packet(oep, 0x8004, init1); send_packet(oep, 0x8007, init2); With: send_packet(oep, 0x8007, init1); send_packet(oep, 0x8002, init2); send_packet(oep, 0x8003, init3); Then ran ./setup (choosing the atiusb driver), make, make install Everything compiled without errors. I put the lircd.conf file in /etc/ Here is all the relevant info I can think of: (I am running FC4) > /sbin/lsusb Bus 003 Device 003: ID 0bc7:0004 X10 Wireless Technology, Inc. X10 Receiver Bus 003 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 I have this line in /etc/modprobe.conf: alias char-major-61 lirc_atiusb >ls /dev/lirc* /dev/lirc /dev/lircd /dev/lircm >dmesg | grep lirc lirc_dev: IR Remote Control driver registered, at major 61 lirc_atiusb: USB remote driver for LIRC v0.5 lirc_atiusb: Paul Miller <pmi...@us...> usbcore: registered new driver lirc_atiusb --- If you have any ideas that could help me, I'd really appreciate them. Thanks in advance! Aidan ------------------ Cymen Vig wrote: > I believe that I have found the correct init code(s) for the Remote > Wonder Plus. I used a snooping program on Windows. I made the > following changes to drivers/lirc_atiusb/lirc_atiusb.c: > > --------------------------------------------------------------------------------------------- > --- lirc_atiusb.c 2006-01-29 12:25:57.000000000 -0600 > +++ ../../../lirc-good/drivers/lirc_atiusb/lirc_atiusb.c > 2006-02-07 19:07:03.362306424 -0600 > @@ -147,9 +147,9 @@ static struct usb_device_id usb_remote_t > /* init strings */ > #define USB_OUTLEN 7 > > -static char init1[] = {0x01, 0x00, 0x20, 0x14}; > -static char init2[] = {0x01, 0x00, 0x20, 0x14, 0x20, 0x20, 0x20}; > - > +static char init1[] = {0x80, 0x05, 0x1b, 0x15, 0x14, 0x20, 0x24, 0x15}; > +static char init2[] = {0x83, 0x03}; > +static char init3[] = {0x84, 0xd7, 0x020}; > > > struct in_endpt { > @@ -1034,8 +1034,9 @@ static void send_outbound_init(struct ir > usb_sndintpipe(ir->usbdev, > oep->ep->bEndpointAddress), oep->buf, > USB_OUTLEN, usb_remote_send, oep, > oep->ep->bInterval); > > - send_packet(oep, 0x8004, init1); > - send_packet(oep, 0x8007, init2); > + send_packet(oep, 0x8007, init1); > + send_packet(oep, 0x8002, init2); > + send_packet(oep, 0x8003, init3); > } > } > --------------------------------------------------------------------------------------------- > > The mode2 results: > > [19:02:18] mythtv tools # # 1st with RW1/2 pressing keys 1,2,3 > [19:02:23] mythtv tools # ./mode2 -d /dev/lirc/0 > code: 0x14e20d0000 > code: 0x14e20d0000 > code: 0x14e30e0000 > code: 0x14e30e0000 > code: 0x14e40f0000 > code: 0x14e40f0000 > > [19:02:35] mythtv tools # # now with Remote Wonder Plus pressing keys > [1,2,3 19:02:48] mythtv tools # ./mode2 -d /dev/lirc/0 > code: 0x14b31b0000 > code: 0x15e20d0000 > code: 0x15e20d0000 > code: 0x15638e0000 > code: 0x15638e0000 > code: 0x14c81f0000 > code: 0x15e40f0000 > code: 0x15e40f0000 > code: 0x155a8d0000 > code: 0x15628d0000 > code: 0x15628d0000 > code: 0x15e30e0000 > code: 0x15e30e0000 > code: 0x15648f0000 > code: 0x15648f0000 > > It seems like the keys are 0x15 instead of 0x14 but every once in a > while the 0x1564..instead of 0x15e.. pops up. > > I tried irw and the old remote is still spitting out keypresses but > the new one isn't there yet. I am not surprised but I'm new to the > lirc source so I'm going to poke around there next. Advice is > welcomed! I believe only have one of the two older remotes so I do not > know if all three are now functional or if one got borked by my > change. > > Cymen |
From: Buzz <bu...@os...> - 2006-03-12 14:04:53
|
Are you sure you have the correct device file? Ie where in /dev or /dev/usb or /dev/input is your USB device? Ie: --device=/dev/??? lircd --nodaemon --driver=atiusb --device=/dev/??? If you aren't sure, it's the device that, if you 'cat /dev/xxxx' it, and press keys on the remote, they you get binary stuff on your screen. Buzz. > -----Original Message----- > From: lir...@li... > [mailto:lir...@li...] On Behalf Of > Aidan Crook > Sent: Sunday, 12 March 2006 8:12 AM > To: lir...@li... > Subject: Re: Progress with ATI Remote Wonder Plus > > Hi, > I am a relative newbie to linux & c, but I have an ATI Remote > Wonder Plus that I am trying to get to work with LIRC. I > followed your changes as best as I could, but am now getting > the following error: > > > /usr/local/sbin/lircd --nodaemon > lircd: lircd(atiusb) ready > > (then as soon as I try & run irw..) > > lircd: accepted new client on /dev/lircd > lircd: could not open /dev/lirc > lircd: default_init(): No such device > lircd: caught signal > Terminated > > ---- > > To get to this stage: > > I downloaded the latest CVS version. > I modified the lirc_atiusb.c file manually because applying a > diff file did not work: > > I replaced: > static char init1[] = {0x01, 0x00, 0x20, 0x14}; static char > init2[] = {0x01, 0x00, 0x20, 0x14, 0x20, 0x20, 0x20}; > > With: > static char init1[] = {0x80, 0x05, 0x1b, 0x15, 0x14, 0x20, > 0x24, 0x15}; static char init2[] = {0x83, 0x03}; static char > init3[] = {0x84, 0xd7, 0x020}; > > And: > send_packet(oep, 0x8004, init1); > send_packet(oep, 0x8007, init2); > With: > send_packet(oep, 0x8007, init1); > send_packet(oep, 0x8002, init2); > send_packet(oep, 0x8003, init3); > > Then ran ./setup (choosing the atiusb driver), make, make > install Everything compiled without errors. > > I put the lircd.conf file in /etc/ > > Here is all the relevant info I can think of: > (I am running FC4) > > > /sbin/lsusb > Bus 003 Device 003: ID 0bc7:0004 X10 Wireless Technology, > Inc. X10 Receiver Bus 003 Device 001: ID 0000:0000 Bus 002 > Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 > > I have this line in /etc/modprobe.conf: > alias char-major-61 lirc_atiusb > > >ls /dev/lirc* > /dev/lirc /dev/lircd /dev/lircm > > >dmesg | grep lirc > lirc_dev: IR Remote Control driver registered, at major 61 > lirc_atiusb: USB remote driver for LIRC v0.5 > lirc_atiusb: Paul Miller <pmi...@us...> > usbcore: registered new driver lirc_atiusb > > > --- > If you have any ideas that could help me, I'd really appreciate them. > > Thanks in advance! > > Aidan > > > ------------------ > > > > > Cymen Vig wrote: > > > I believe that I have found the correct init code(s) for the Remote > > Wonder Plus. I used a snooping program on Windows. I made the > > following changes to drivers/lirc_atiusb/lirc_atiusb.c: > > > > > -------------------------------------------------------------- > ------------------------------- > > --- lirc_atiusb.c 2006-01-29 12:25:57.000000000 -0600 > > +++ ../../../lirc-good/drivers/lirc_atiusb/lirc_atiusb.c > > 2006-02-07 19:07:03.362306424 -0600 > > @@ -147,9 +147,9 @@ static struct usb_device_id usb_remote_t > > /* init strings */ > > #define USB_OUTLEN 7 > > > > -static char init1[] = {0x01, 0x00, 0x20, 0x14}; -static > char init2[] > > = {0x01, 0x00, 0x20, 0x14, 0x20, 0x20, 0x20}; > > - > > +static char init1[] = {0x80, 0x05, 0x1b, 0x15, 0x14, 0x20, 0x24, > > +0x15}; static char init2[] = {0x83, 0x03}; static char init3[] = > > +{0x84, 0xd7, 0x020}; > > > > > > struct in_endpt { > > @@ -1034,8 +1034,9 @@ static void send_outbound_init(struct ir > > usb_sndintpipe(ir->usbdev, > > oep->ep->bEndpointAddress), oep->buf, > > USB_OUTLEN, usb_remote_send, oep, > > oep->ep->bInterval); > > > > - send_packet(oep, 0x8004, init1); > > - send_packet(oep, 0x8007, init2); > > + send_packet(oep, 0x8007, init1); > > + send_packet(oep, 0x8002, init2); > > + send_packet(oep, 0x8003, init3); > > } > > } > > > -------------------------------------------------------------- > ------------------------------- > > > > The mode2 results: > > > > [19:02:18] mythtv tools # # 1st with RW1/2 pressing keys 1,2,3 > > [19:02:23] mythtv tools # ./mode2 -d /dev/lirc/0 > > code: 0x14e20d0000 > > code: 0x14e20d0000 > > code: 0x14e30e0000 > > code: 0x14e30e0000 > > code: 0x14e40f0000 > > code: 0x14e40f0000 > > > > [19:02:35] mythtv tools # # now with Remote Wonder Plus > pressing keys > > [1,2,3 19:02:48] mythtv tools # ./mode2 -d /dev/lirc/0 > > code: 0x14b31b0000 > > code: 0x15e20d0000 > > code: 0x15e20d0000 > > code: 0x15638e0000 > > code: 0x15638e0000 > > code: 0x14c81f0000 > > code: 0x15e40f0000 > > code: 0x15e40f0000 > > code: 0x155a8d0000 > > code: 0x15628d0000 > > code: 0x15628d0000 > > code: 0x15e30e0000 > > code: 0x15e30e0000 > > code: 0x15648f0000 > > code: 0x15648f0000 > > > > It seems like the keys are 0x15 instead of 0x14 but every once in a > > while the 0x1564..instead of 0x15e.. pops up. > > > > I tried irw and the old remote is still spitting out keypresses but > > the new one isn't there yet. I am not surprised but I'm new to the > > lirc source so I'm going to poke around there next. Advice is > > welcomed! I believe only have one of the two older remotes > so I do not > > know if all three are now functional or if one got borked by my > > change. > > > > Cymen > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking > scripting language that extends applications into web and > mobile media. Attend the live webcast and join the prime > developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720& > dat=121642 > |
From: Aidan C. <ai...@mi...> - 2006-03-13 05:06:24
|
Hi, Thanks for your suggestion. I believe you are correct - I don't in fact have the correct device - however I don't know how I make it recognize my USB device as the correct device: ls /dev/lirc* /dev/lirc /dev/lircd /dev/lircm >cat /dev/lirc cat: /dev/lirc: No such device >/sbin/lsusb Bus 003 Device 001: ID 0000:0000 Bus 002 Device 006: ID 0bc7:0004 X10 Wireless Technology, Inc. X10 Receiver Bus 002 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 >ls /dev/usbdev* /dev/usbdev1.1 /dev/usbdev2.1 /dev/usbdev2.6 /dev/usbdev3.1 >cat /dev/usbdev2.6 (this just returns me to a prompts right away - I don't get the chance to push any buttons) >/usr/local/sbin/lircd --nodaemon --device=/dev/usbdev2.6 lircd: lircd(atiusb) ready (then I run irw) lircd: accepted new client on /dev/lircd lircd: could not get hardware features lircd: this device driver does not support the new LIRC interface lircd: major number of /dev/usbdev2.6 is 189 lircd: LIRC major number is 61 lircd: check if /dev/usbdev2.6 is a LIRC device lircd: caught signal Terminated I have also noticed that on the dmesg output I get: >dmesg | grep lirc lirc_dev: IR Remote Control driver registered, at major 61 lirc_atiusb: USB remote driver for LIRC v0.5 lirc_atiusb: Paul Miller <pmi...@us...> usbcore: registered new driver lirc_atiusb whereas the expected output (according to http://www.mythtv.org/wiki/index.php/ATI_Remote_Wonder_II) is: lirc_atiusb: USB remote driver for LIRC v0.4 lirc_atiusb: Paul Miller <pmi...@us...> usb.c: registered new driver lirc_atiusb lirc_dev: lirc_register_plugin:sample_rate: 0 lirc_atiusb[5]: on usb2:5 (notice the addition of the last line) I recompiled lirc with the orginal lirc_atiusb.c code and I get the same problem. So it is nothing to do with the modifications - it is the fact that lirc is not registering my usb receiver, even though it is definitely plugged in & recognized by linux. (I have also tested the remote under Windows XP and it works properly.) Do you have any idea how to fix this? Thanks, Aidan Buzz wrote: > Are you sure you have the correct device file? Ie where in /dev or > /dev/usb or /dev/input is your USB device? > Ie: --device=/dev/??? > > lircd --nodaemon --driver=atiusb --device=/dev/??? > > If you aren't sure, it's the device that, if you 'cat /dev/xxxx' it, and > press keys on the remote, they you get binary stuff on your screen. > > Buzz. > >> -----Original Message----- >> From: lir...@li... >> [mailto:lir...@li...] >> [On Behalf Of >> Aidan Crook >> Sent: Sunday, 12 March 2006 8:12 AM >> To: lir...@li... >> Subject: Re: Progress with ATI Remote Wonder Plus >> >> Hi, >> I am a relative newbie to linux & c, but I have an ATI Remote >> Wonder Plus that I am trying to get to work with LIRC. I >> followed your changes as best as I could, but am now getting >> the following error: >> >> > /usr/local/sbin/lircd --nodaemon >> lircd: lircd(atiusb) ready >> >> (then as soon as I try & run irw..) >> >> lircd: accepted new client on /dev/lircd >> lircd: could not open /dev/lirc >> lircd: default_init(): No such device >> lircd: caught signal >> Terminated >> >> ---- >> >> To get to this stage: >> >> I downloaded the latest CVS version. >> I modified the lirc_atiusb.c file manually because applying a >> diff file did not work: >> >> I replaced: >> static char init1[] = {0x01, 0x00, 0x20, 0x14}; static char >> init2[] = {0x01, 0x00, 0x20, 0x14, 0x20, 0x20, 0x20}; >> >> With: >> static char init1[] = {0x80, 0x05, 0x1b, 0x15, 0x14, 0x20, >> 0x24, 0x15}; static char init2[] = {0x83, 0x03}; static char >> init3[] = {0x84, 0xd7, 0x020}; >> >> And: >> send_packet(oep, 0x8004, init1); >> send_packet(oep, 0x8007, init2); >> With: >> send_packet(oep, 0x8007, init1); >> send_packet(oep, 0x8002, init2); >> send_packet(oep, 0x8003, init3); >> >> Then ran ./setup (choosing the atiusb driver), make, make >> install Everything compiled without errors. >> >> I put the lircd.conf file in /etc/ >> >> Here is all the relevant info I can think of: >> (I am running FC4) >> >> > /sbin/lsusb >> Bus 003 Device 003: ID 0bc7:0004 X10 Wireless Technology, >> Inc. X10 Receiver Bus 003 Device 001: ID 0000:0000 Bus 002 >> Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 >> >> I have this line in /etc/modprobe.conf: >> alias char-major-61 lirc_atiusb >> >> >ls /dev/lirc* >> /dev/lirc /dev/lircd /dev/lircm >> >> >dmesg | grep lirc >> lirc_dev: IR Remote Control driver registered, at major 61 >> lirc_atiusb: USB remote driver for LIRC v0.5 >> lirc_atiusb: Paul Miller >> <pmi...@us...> usbcore: >> registered new driver lirc_atiusb >> >> >> --- >> If you have any ideas that could help me, I'd really appreciate them. >> >> Thanks in advance! >> >> Aidan >> >> >> ------------------ >> >> >> >> >> Cymen Vig wrote: >> >> > I believe that I have found the correct init code(s) for the Remote >> > Wonder Plus. I used a snooping program on Windows. I made the >> > following changes to drivers/lirc_atiusb/lirc_atiusb.c: >> > >> > >> -------------------------------------------------------------- >> ------------------------------- >> > --- lirc_atiusb.c 2006-01-29 12:25:57.000000000 -0600 >> > +++ ../../../lirc-good/drivers/lirc_atiusb/lirc_atiusb.c >> > 2006-02-07 19:07:03.362306424 -0600 >> > @@ -147,9 +147,9 @@ static struct usb_device_id usb_remote_t >> > /* init strings */ >> > #define USB_OUTLEN 7 >> > >> > -static char init1[] = {0x01, 0x00, 0x20, 0x14}; -static >> char init2[] >> > = {0x01, 0x00, 0x20, 0x14, 0x20, 0x20, 0x20}; >> > - >> > +static char init1[] = {0x80, 0x05, 0x1b, 0x15, 0x14, 0x20, 0x24, >> > +0x15}; static char init2[] = {0x83, 0x03}; static char init3[] = >> > +{0x84, 0xd7, 0x020}; >> > >> > >> > struct in_endpt { >> > @@ -1034,8 +1034,9 @@ static void send_outbound_init(struct ir >> > usb_sndintpipe(ir->usbdev, >> > oep->ep->bEndpointAddress), oep->buf, >> > USB_OUTLEN, usb_remote_send, oep, >> > oep->ep->bInterval); >> > >> > - send_packet(oep, 0x8004, init1); >> > - send_packet(oep, 0x8007, init2); >> > + send_packet(oep, 0x8007, init1); >> > + send_packet(oep, 0x8002, init2); >> > + send_packet(oep, 0x8003, init3); >> > } >> > } >> > >> -------------------------------------------------------------- >> ------------------------------- >> > >> > The mode2 results: >> > >> > [19:02:18] mythtv tools # # 1st with RW1/2 pressing keys 1,2,3 >> > [19:02:23] mythtv tools # ./mode2 -d /dev/lirc/0 >> > code: 0x14e20d0000 >> > code: 0x14e20d0000 >> > code: 0x14e30e0000 >> > code: 0x14e30e0000 >> > code: 0x14e40f0000 >> > code: 0x14e40f0000 >> > >> > [19:02:35] mythtv tools # # now with Remote Wonder Plus >> pressing keys >> > [1,2,3 19:02:48] mythtv tools # ./mode2 -d /dev/lirc/0 >> > code: 0x14b31b0000 >> > code: 0x15e20d0000 >> > code: 0x15e20d0000 >> > code: 0x15638e0000 >> > code: 0x15638e0000 >> > code: 0x14c81f0000 >> > code: 0x15e40f0000 >> > code: 0x15e40f0000 >> > code: 0x155a8d0000 >> > code: 0x15628d0000 >> > code: 0x15628d0000 >> > code: 0x15e30e0000 >> > code: 0x15e30e0000 >> > code: 0x15648f0000 >> > code: 0x15648f0000 >> > >> > It seems like the keys are 0x15 instead of 0x14 but every once in a >> > while the 0x1564..instead of 0x15e.. pops up. >> > >> > I tried irw and the old remote is still spitting out keypresses but >> > the new one isn't there yet. I am not surprised but I'm new to the >> > lirc source so I'm going to poke around there next. Advice is >> > welcomed! I believe only have one of the two older remotes >> so I do not >> > know if all three are now functional or if one got borked by my >> > change. >> > >> > Cymen >> >> >> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by xPML, a groundbreaking >> scripting language that extends applications into web and >> mobile media. Attend the live webcast and join the prime >> developer group breaking into this new coding territory! >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720& >> dat=121642 >> > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language that extends applications into web and mobile media. Attend the > live webcast and join the prime developer group breaking into this new > coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 |
From: Buzz <bu...@os...> - 2006-03-15 01:52:05
|
This is just a guess, but looking at your dmesg output, there is a line stating that the 'lirc_dev' (I'm assuming it's a kernel module) was registered "at major 61". Can you go looking for all devices in /dev that have a major number or 61? Buzz. > -----Original Message----- > From: lir...@li... > [mailto:lir...@li...] On Behalf Of > Aidan Crook > Sent: Monday, 13 March 2006 3:06 PM > To: lir...@li... > Subject: RE: Progress with ATI Remote Wonder Plus > > Hi, > Thanks for your suggestion. I believe you are correct - I > don't in fact have the correct device - however I don't know > how I make it recognize my USB device as the correct device: > > ls /dev/lirc* > /dev/lirc /dev/lircd /dev/lircm > > >cat /dev/lirc > cat: /dev/lirc: No such device > > >/sbin/lsusb > Bus 003 Device 001: ID 0000:0000 > Bus 002 Device 006: ID 0bc7:0004 X10 Wireless Technology, > Inc. X10 Receiver Bus 002 Device 001: ID 0000:0000 Bus 001 > Device 001: ID 0000:0000 > > >ls /dev/usbdev* > /dev/usbdev1.1 /dev/usbdev2.1 /dev/usbdev2.6 /dev/usbdev3.1 > > >cat /dev/usbdev2.6 > (this just returns me to a prompts right away - I don't get > the chance to push any buttons) > > >/usr/local/sbin/lircd --nodaemon --device=/dev/usbdev2.6 > lircd: lircd(atiusb) ready > > (then I run irw) > > lircd: accepted new client on /dev/lircd > lircd: could not get hardware features > lircd: this device driver does not support the new LIRC interface > lircd: major number of /dev/usbdev2.6 is 189 > lircd: LIRC major number is 61 > lircd: check if /dev/usbdev2.6 is a LIRC device > lircd: caught signal > Terminated > > I have also noticed that on the dmesg output I get: > >dmesg | grep lirc > lirc_dev: IR Remote Control driver registered, at major 61 > lirc_atiusb: USB remote driver for LIRC v0.5 > lirc_atiusb: Paul Miller <pmi...@us...> > usbcore: registered new driver lirc_atiusb > > whereas the expected output (according to > http://www.mythtv.org/wiki/index.php/ATI_Remote_Wonder_II) is: > > lirc_atiusb: USB remote driver for LIRC v0.4 > lirc_atiusb: Paul Miller <pmi...@us...> > usb.c: registered new driver lirc_atiusb > lirc_dev: lirc_register_plugin:sample_rate: 0 > lirc_atiusb[5]: on usb2:5 > > (notice the addition of the last line) > > I recompiled lirc with the orginal lirc_atiusb.c code and I > get the same problem. So it is nothing to do with the > modifications - it is the fact that lirc is not registering > my usb receiver, even though it is definitely plugged in & > recognized by linux. > > (I have also tested the remote under Windows XP and it works > properly.) > > Do you have any idea how to fix this? > Thanks, > Aidan > > > Buzz wrote: > > > Are you sure you have the correct device file? Ie where in /dev or > > /dev/usb or /dev/input is your USB device? > > Ie: --device=/dev/??? > > > > lircd --nodaemon --driver=atiusb --device=/dev/??? > > > > If you aren't sure, it's the device that, if you 'cat > /dev/xxxx' it, > > and press keys on the remote, they you get binary stuff on > your screen. > > > > Buzz. > > > >> -----Original Message----- > >> From: lir...@li... > >> > [mailto:lir...@li...] > >> [On Behalf Of > >> Aidan Crook > >> Sent: Sunday, 12 March 2006 8:12 AM > >> To: lir...@li... > >> Subject: Re: Progress with ATI Remote Wonder Plus > >> > >> Hi, > >> I am a relative newbie to linux & c, but I have an ATI > Remote Wonder > >> Plus that I am trying to get to work with LIRC. I followed your > >> changes as best as I could, but am now getting the following error: > >> > >> > /usr/local/sbin/lircd --nodaemon > >> lircd: lircd(atiusb) ready > >> > >> (then as soon as I try & run irw..) > >> > >> lircd: accepted new client on /dev/lircd > >> lircd: could not open /dev/lirc > >> lircd: default_init(): No such device > >> lircd: caught signal > >> Terminated > >> > >> ---- > >> > >> To get to this stage: > >> > >> I downloaded the latest CVS version. > >> I modified the lirc_atiusb.c file manually because applying a diff > >> file did not work: > >> > >> I replaced: > >> static char init1[] = {0x01, 0x00, 0x20, 0x14}; static > char init2[] = > >> {0x01, 0x00, 0x20, 0x14, 0x20, 0x20, 0x20}; > >> > >> With: > >> static char init1[] = {0x80, 0x05, 0x1b, 0x15, 0x14, 0x20, 0x24, > >> 0x15}; static char init2[] = {0x83, 0x03}; static char init3[] = > >> {0x84, 0xd7, 0x020}; > >> > >> And: > >> send_packet(oep, 0x8004, init1); > >> send_packet(oep, 0x8007, init2); > >> With: > >> send_packet(oep, 0x8007, init1); > >> send_packet(oep, 0x8002, init2); > >> send_packet(oep, 0x8003, init3); > >> > >> Then ran ./setup (choosing the atiusb driver), make, make install > >> Everything compiled without errors. > >> > >> I put the lircd.conf file in /etc/ > >> > >> Here is all the relevant info I can think of: > >> (I am running FC4) > >> > >> > /sbin/lsusb > >> Bus 003 Device 003: ID 0bc7:0004 X10 Wireless Technology, Inc. X10 > >> Receiver Bus 003 Device 001: ID 0000:0000 Bus 002 Device 001: ID > >> 0000:0000 Bus 001 Device 001: ID 0000:0000 > >> > >> I have this line in /etc/modprobe.conf: > >> alias char-major-61 lirc_atiusb > >> > >> >ls /dev/lirc* > >> /dev/lirc /dev/lircd /dev/lircm > >> > >> >dmesg | grep lirc > >> lirc_dev: IR Remote Control driver registered, at major 61 > >> lirc_atiusb: USB remote driver for LIRC v0.5 > >> lirc_atiusb: Paul Miller > >> <pmi...@us...> usbcore: > >> registered new driver lirc_atiusb > >> > >> > >> --- > >> If you have any ideas that could help me, I'd really > appreciate them. > >> > >> Thanks in advance! > >> > >> Aidan > >> > >> > >> ------------------ > >> > >> > >> > >> > >> Cymen Vig wrote: > >> > >> > I believe that I have found the correct init code(s) for > the Remote > >> > Wonder Plus. I used a snooping program on Windows. I made the > >> > following changes to drivers/lirc_atiusb/lirc_atiusb.c: > >> > > >> > > >> -------------------------------------------------------------- > >> ------------------------------- > >> > --- lirc_atiusb.c 2006-01-29 12:25:57.000000000 -0600 > >> > +++ ../../../lirc-good/drivers/lirc_atiusb/lirc_atiusb.c > >> > 2006-02-07 19:07:03.362306424 -0600 @@ -147,9 +147,9 @@ static > >> > struct usb_device_id usb_remote_t > >> > /* init strings */ > >> > #define USB_OUTLEN 7 > >> > > >> > -static char init1[] = {0x01, 0x00, 0x20, 0x14}; -static > >> char init2[] > >> > = {0x01, 0x00, 0x20, 0x14, 0x20, 0x20, 0x20}; > >> > - > >> > +static char init1[] = {0x80, 0x05, 0x1b, 0x15, 0x14, > 0x20, 0x24, > >> > +0x15}; static char init2[] = {0x83, 0x03}; static char > init3[] = > >> > +{0x84, 0xd7, 0x020}; > >> > > >> > > >> > struct in_endpt { > >> > @@ -1034,8 +1034,9 @@ static void send_outbound_init(struct ir > >> > usb_sndintpipe(ir->usbdev, > >> > oep->ep->bEndpointAddress), oep->buf, > >> > USB_OUTLEN, usb_remote_send, oep, > >> > oep->ep->bInterval); > >> > > >> > - send_packet(oep, 0x8004, init1); > >> > - send_packet(oep, 0x8007, init2); > >> > + send_packet(oep, 0x8007, init1); > >> > + send_packet(oep, 0x8002, init2); > >> > + send_packet(oep, 0x8003, init3); > >> > } > >> > } > >> > > >> -------------------------------------------------------------- > >> ------------------------------- > >> > > >> > The mode2 results: > >> > > >> > [19:02:18] mythtv tools # # 1st with RW1/2 pressing keys 1,2,3 > >> > [19:02:23] mythtv tools # ./mode2 -d /dev/lirc/0 > >> > code: 0x14e20d0000 > >> > code: 0x14e20d0000 > >> > code: 0x14e30e0000 > >> > code: 0x14e30e0000 > >> > code: 0x14e40f0000 > >> > code: 0x14e40f0000 > >> > > >> > [19:02:35] mythtv tools # # now with Remote Wonder Plus > >> pressing keys > >> > [1,2,3 19:02:48] mythtv tools # ./mode2 -d /dev/lirc/0 > >> > code: 0x14b31b0000 > >> > code: 0x15e20d0000 > >> > code: 0x15e20d0000 > >> > code: 0x15638e0000 > >> > code: 0x15638e0000 > >> > code: 0x14c81f0000 > >> > code: 0x15e40f0000 > >> > code: 0x15e40f0000 > >> > code: 0x155a8d0000 > >> > code: 0x15628d0000 > >> > code: 0x15628d0000 > >> > code: 0x15e30e0000 > >> > code: 0x15e30e0000 > >> > code: 0x15648f0000 > >> > code: 0x15648f0000 > >> > > >> > It seems like the keys are 0x15 instead of 0x14 but > every once in a > >> > while the 0x1564..instead of 0x15e.. pops up. > >> > > >> > I tried irw and the old remote is still spitting out > keypresses but > >> > the new one isn't there yet. I am not surprised but I'm > new to the > >> > lirc source so I'm going to poke around there next. Advice is > >> > welcomed! I believe only have one of the two older remotes > >> so I do not > >> > know if all three are now functional or if one got borked by my > >> > change. > >> > > >> > Cymen > >> > >> > >> > >> > >> > >> ------------------------------------------------------- > >> This SF.Net email is sponsored by xPML, a groundbreaking scripting > >> language that extends applications into web and mobile > media. Attend > >> the live webcast and join the prime developer group breaking into > >> this new coding territory! > >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720& > >> dat=121642 > >> > > > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by xPML, a groundbreaking scripting > > language that extends applications into web and mobile > media. Attend > > the live webcast and join the prime developer group > breaking into this > > new coding territory! > > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=1216 > > 42 > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking > scripting language that extends applications into web and > mobile media. Attend the live webcast and join the prime > developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720& > dat=121642 > |
From: Aidan C. <AidanC@MIT.EDU> - 2006-03-15 05:27:25
|
Am I right in thinking that the major is the 1st number after the device name? If so, then there are no such devices! ?? >ls -l | grep 61 crw-rw---- 1 root tty 4, 61 Mar 13 19:44 tty61 It's possible I have missed a line needed in one of the startup files. Everything that is present is mentioned in the original email. Aidan On Wed, 2006-03-15 at 11:51 +1000, Buzz wrote: > This is just a guess, but looking at your dmesg output, there is a line > stating that the 'lirc_dev' (I'm assuming it's a kernel module) was > registered "at major 61". Can you go looking for all devices in /dev that > have a major number or 61? > > Buzz. > > > -----Original Message----- > > From: lir...@li... > > [mailto:lir...@li...] On Behalf Of > > Aidan Crook > > Sent: Monday, 13 March 2006 3:06 PM > > To: lir...@li... > > Subject: RE: Progress with ATI Remote Wonder Plus > > > > Hi, > > Thanks for your suggestion. I believe you are correct - I > > don't in fact have the correct device - however I don't know > > how I make it recognize my USB device as the correct device: > > > > ls /dev/lirc* > > /dev/lirc /dev/lircd /dev/lircm > > > > >cat /dev/lirc > > cat: /dev/lirc: No such device > > > > >/sbin/lsusb > > Bus 003 Device 001: ID 0000:0000 > > Bus 002 Device 006: ID 0bc7:0004 X10 Wireless Technology, > > Inc. X10 Receiver Bus 002 Device 001: ID 0000:0000 Bus 001 > > Device 001: ID 0000:0000 > > > > >ls /dev/usbdev* > > /dev/usbdev1.1 /dev/usbdev2.1 /dev/usbdev2.6 /dev/usbdev3.1 > > > > >cat /dev/usbdev2.6 > > (this just returns me to a prompts right away - I don't get > > the chance to push any buttons) > > > > >/usr/local/sbin/lircd --nodaemon --device=/dev/usbdev2.6 > > lircd: lircd(atiusb) ready > > > > (then I run irw) > > > > lircd: accepted new client on /dev/lircd > > lircd: could not get hardware features > > lircd: this device driver does not support the new LIRC interface > > lircd: major number of /dev/usbdev2.6 is 189 > > lircd: LIRC major number is 61 > > lircd: check if /dev/usbdev2.6 is a LIRC device > > lircd: caught signal > > Terminated > > > > I have also noticed that on the dmesg output I get: > > >dmesg | grep lirc > > lirc_dev: IR Remote Control driver registered, at major 61 > > lirc_atiusb: USB remote driver for LIRC v0.5 > > lirc_atiusb: Paul Miller <pmi...@us...> > > usbcore: registered new driver lirc_atiusb > > > > whereas the expected output (according to > > http://www.mythtv.org/wiki/index.php/ATI_Remote_Wonder_II) is: > > > > lirc_atiusb: USB remote driver for LIRC v0.4 > > lirc_atiusb: Paul Miller <pmi...@us...> > > usb.c: registered new driver lirc_atiusb > > lirc_dev: lirc_register_plugin:sample_rate: 0 > > lirc_atiusb[5]: on usb2:5 > > > > (notice the addition of the last line) > > > > I recompiled lirc with the orginal lirc_atiusb.c code and I > > get the same problem. So it is nothing to do with the > > modifications - it is the fact that lirc is not registering > > my usb receiver, even though it is definitely plugged in & > > recognized by linux. > > > > (I have also tested the remote under Windows XP and it works > > properly.) > > > > Do you have any idea how to fix this? > > Thanks, > > Aidan > > > > > > Buzz wrote: > > > > > Are you sure you have the correct device file? Ie where in /dev or > > > /dev/usb or /dev/input is your USB device? > > > Ie: --device=/dev/??? > > > > > > lircd --nodaemon --driver=atiusb --device=/dev/??? > > > > > > If you aren't sure, it's the device that, if you 'cat > > /dev/xxxx' it, > > > and press keys on the remote, they you get binary stuff on > > your screen. > > > > > > Buzz. > > > > > >> -----Original Message----- > > >> From: lir...@li... > > >> > > [mailto:lir...@li...] > > >> [On Behalf Of > > >> Aidan Crook > > >> Sent: Sunday, 12 March 2006 8:12 AM > > >> To: lir...@li... > > >> Subject: Re: Progress with ATI Remote Wonder Plus > > >> > > >> Hi, > > >> I am a relative newbie to linux & c, but I have an ATI > > Remote Wonder > > >> Plus that I am trying to get to work with LIRC. I followed your > > >> changes as best as I could, but am now getting the following error: > > >> > > >> > /usr/local/sbin/lircd --nodaemon > > >> lircd: lircd(atiusb) ready > > >> > > >> (then as soon as I try & run irw..) > > >> > > >> lircd: accepted new client on /dev/lircd > > >> lircd: could not open /dev/lirc > > >> lircd: default_init(): No such device > > >> lircd: caught signal > > >> Terminated > > >> > > >> ---- > > >> > > >> To get to this stage: > > >> > > >> I downloaded the latest CVS version. > > >> I modified the lirc_atiusb.c file manually because applying a diff > > >> file did not work: > > >> > > >> I replaced: > > >> static char init1[] = {0x01, 0x00, 0x20, 0x14}; static > > char init2[] = > > >> {0x01, 0x00, 0x20, 0x14, 0x20, 0x20, 0x20}; > > >> > > >> With: > > >> static char init1[] = {0x80, 0x05, 0x1b, 0x15, 0x14, 0x20, 0x24, > > >> 0x15}; static char init2[] = {0x83, 0x03}; static char init3[] = > > >> {0x84, 0xd7, 0x020}; > > >> > > >> And: > > >> send_packet(oep, 0x8004, init1); > > >> send_packet(oep, 0x8007, init2); > > >> With: > > >> send_packet(oep, 0x8007, init1); > > >> send_packet(oep, 0x8002, init2); > > >> send_packet(oep, 0x8003, init3); > > >> > > >> Then ran ./setup (choosing the atiusb driver), make, make install > > >> Everything compiled without errors. > > >> > > >> I put the lircd.conf file in /etc/ > > >> > > >> Here is all the relevant info I can think of: > > >> (I am running FC4) > > >> > > >> > /sbin/lsusb > > >> Bus 003 Device 003: ID 0bc7:0004 X10 Wireless Technology, Inc. X10 > > >> Receiver Bus 003 Device 001: ID 0000:0000 Bus 002 Device 001: ID > > >> 0000:0000 Bus 001 Device 001: ID 0000:0000 > > >> > > >> I have this line in /etc/modprobe.conf: > > >> alias char-major-61 lirc_atiusb > > >> > > >> >ls /dev/lirc* > > >> /dev/lirc /dev/lircd /dev/lircm > > >> > > >> >dmesg | grep lirc > > >> lirc_dev: IR Remote Control driver registered, at major 61 > > >> lirc_atiusb: USB remote driver for LIRC v0.5 > > >> lirc_atiusb: Paul Miller > > >> <pmi...@us...> usbcore: > > >> registered new driver lirc_atiusb > > >> > > >> > > >> --- > > >> If you have any ideas that could help me, I'd really > > appreciate them. > > >> > > >> Thanks in advance! > > >> > > >> Aidan > > >> > > >> > > >> ------------------ > > >> > > >> > > >> > > >> > > >> Cymen Vig wrote: > > >> > > >> > I believe that I have found the correct init code(s) for > > the Remote > > >> > Wonder Plus. I used a snooping program on Windows. I made the > > >> > following changes to drivers/lirc_atiusb/lirc_atiusb.c: > > >> > > > >> > > > >> -------------------------------------------------------------- > > >> ------------------------------- > > >> > --- lirc_atiusb.c 2006-01-29 12:25:57.000000000 -0600 > > >> > +++ ../../../lirc-good/drivers/lirc_atiusb/lirc_atiusb.c > > >> > 2006-02-07 19:07:03.362306424 -0600 @@ -147,9 +147,9 @@ static > > >> > struct usb_device_id usb_remote_t > > >> > /* init strings */ > > >> > #define USB_OUTLEN 7 > > >> > > > >> > -static char init1[] = {0x01, 0x00, 0x20, 0x14}; -static > > >> char init2[] > > >> > = {0x01, 0x00, 0x20, 0x14, 0x20, 0x20, 0x20}; > > >> > - > > >> > +static char init1[] = {0x80, 0x05, 0x1b, 0x15, 0x14, > > 0x20, 0x24, > > >> > +0x15}; static char init2[] = {0x83, 0x03}; static char > > init3[] = > > >> > +{0x84, 0xd7, 0x020}; > > >> > > > >> > > > >> > struct in_endpt { > > >> > @@ -1034,8 +1034,9 @@ static void send_outbound_init(struct ir > > >> > usb_sndintpipe(ir->usbdev, > > >> > oep->ep->bEndpointAddress), oep->buf, > > >> > USB_OUTLEN, usb_remote_send, oep, > > >> > oep->ep->bInterval); > > >> > > > >> > - send_packet(oep, 0x8004, init1); > > >> > - send_packet(oep, 0x8007, init2); > > >> > + send_packet(oep, 0x8007, init1); > > >> > + send_packet(oep, 0x8002, init2); > > >> > + send_packet(oep, 0x8003, init3); > > >> > } > > >> > } > > >> > > > >> -------------------------------------------------------------- > > >> ------------------------------- > > >> > > > >> > The mode2 results: > > >> > > > >> > [19:02:18] mythtv tools # # 1st with RW1/2 pressing keys 1,2,3 > > >> > [19:02:23] mythtv tools # ./mode2 -d /dev/lirc/0 > > >> > code: 0x14e20d0000 > > >> > code: 0x14e20d0000 > > >> > code: 0x14e30e0000 > > >> > code: 0x14e30e0000 > > >> > code: 0x14e40f0000 > > >> > code: 0x14e40f0000 > > >> > > > >> > [19:02:35] mythtv tools # # now with Remote Wonder Plus > > >> pressing keys > > >> > [1,2,3 19:02:48] mythtv tools # ./mode2 -d /dev/lirc/0 > > >> > code: 0x14b31b0000 > > >> > code: 0x15e20d0000 > > >> > code: 0x15e20d0000 > > >> > code: 0x15638e0000 > > >> > code: 0x15638e0000 > > >> > code: 0x14c81f0000 > > >> > code: 0x15e40f0000 > > >> > code: 0x15e40f0000 > > >> > code: 0x155a8d0000 > > >> > code: 0x15628d0000 > > >> > code: 0x15628d0000 > > >> > code: 0x15e30e0000 > > >> > code: 0x15e30e0000 > > >> > code: 0x15648f0000 > > >> > code: 0x15648f0000 > > >> > > > >> > It seems like the keys are 0x15 instead of 0x14 but > > every once in a > > >> > while the 0x1564..instead of 0x15e.. pops up. > > >> > > > >> > I tried irw and the old remote is still spitting out > > keypresses but > > >> > the new one isn't there yet. I am not surprised but I'm > > new to the > > >> > lirc source so I'm going to poke around there next. Advice is > > >> > welcomed! I believe only have one of the two older remotes > > >> so I do not > > >> > know if all three are now functional or if one got borked by my > > >> > change. > > >> > > > >> > Cymen > > >> > > >> > > >> > > >> > > >> > > >> ------------------------------------------------------- > > >> This SF.Net email is sponsored by xPML, a groundbreaking scripting > > >> language that extends applications into web and mobile > > media. Attend > > >> the live webcast and join the prime developer group breaking into > > >> this new coding territory! > > >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720& > > >> dat=121642 > > >> > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by xPML, a groundbreaking scripting > > > language that extends applications into web and mobile > > media. Attend > > > the live webcast and join the prime developer group > > breaking into this > > > new coding territory! > > > > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=1216 > > > 42 > > > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by xPML, a groundbreaking > > scripting language that extends applications into web and > > mobile media. Attend the live webcast and join the prime > > developer group breaking into this new coding territory! > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720& > > dat=121642 > > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 |
From: Cymen V. <cym...@gm...> - 2006-04-09 22:09:29
|
On 3/15/06, Aidan Crook <Ai...@mi...> wrote: > Am I right in thinking that the major is the 1st number after the device > name? If so, then there are no such devices! ?? > > >ls -l | grep 61 > crw-rw---- 1 root tty 4, 61 Mar 13 19:44 tty61 > > It's possible I have missed a line needed in one of the startup files. > Everything that is present is mentioned in the original email. I missed your posts to the list so I apologize for the delay. Were you able to get this working? My lirc device is /dev/lirc/0 and (perhaps Gentoo specific), my /etc/conf.d/lircd has: --- # Options to pass to the lircd process LIRCD_OPTS=3D"-d /dev/lirc/0" --- Here are the fs details: --- [screen] mythtv lirc # pwd /dev/lirc [screen] mythtv lirc # ls -al 0 crw-rw---- 1 root root 61, 0 Apr 8 21:01 0 --- Regards, Cymen |
From: Aidan C. <aidanc@MIT.EDU> - 2006-04-10 02:34:50
|
Hi, Thanks for your reply -- lirc was not registering a device at all in my case. Although now I've just managed to succeed in getting my ATI Remote Wonder Plus to work. My problem was that the ati_remote.ko kernel module was also loading by default with FC4. This is apparently a problem with all the ATI remotes - that lirc_atiusb.ko and ati_remote.ko must not both be in the kernel build direcory. Renaming ati_remote.ko to something else in the kernel-build directory & rebooting allowed lirc_atiusb to register the lirc device on major no. 61. I applied the patch located at http://raw-io.com/rwp/ manually (going through the file and altering the lines) to lirc_atiusb.c Then recompiled lirc. In my case there were 2 instances of lirc_atiusb.ko under the kernel-build directory - one inserted by compiling the source, and a second from a previous installation of lirc via yum. I had to copy the lirc_atiusb.ko from the directory where I compiled lirc over both of these before it worked. Now I have a fully functioning remote! Thanks for your help on this -- it's much appreciated! Aidan On Sun, 2006-04-09 at 17:09 -0500, Cymen Vig wrote: > On 3/15/06, Aidan Crook <Ai...@mi...> wrote: > > Am I right in thinking that the major is the 1st number after the device > > name? If so, then there are no such devices! ?? > > > > >ls -l | grep 61 > > crw-rw---- 1 root tty 4, 61 Mar 13 19:44 tty61 > > > > It's possible I have missed a line needed in one of the startup files. > > Everything that is present is mentioned in the original email. > > I missed your posts to the list so I apologize for the delay. Were you > able to get this working? My lirc device is /dev/lirc/0 and (perhaps > Gentoo specific), my /etc/conf.d/lircd has: > --- > # Options to pass to the lircd process > LIRCD_OPTS="-d /dev/lirc/0" > --- > > Here are the fs details: > > --- > [screen] mythtv lirc # pwd > /dev/lirc > [screen] mythtv lirc # ls -al 0 > crw-rw---- 1 root root 61, 0 Apr 8 21:01 0 > --- > > Regards, > Cymen |
From: Eric D. <ic...@gm...> - 2006-04-11 04:11:50
|
Thanks Aidan and Cymen! that looks like it was my problem also (duplcate lirc_* modules and the ati_remote module) after upgrading to 2.6.16 for the RWP. (i used cymen's patch to lirc_atiusb.c). after i patched+recompiled and removed/overwrote the extra kernel modules and i'm seeing all the button events with lircd+irw. yay! i've got a working remote wonder plus lircd.conf from: http://raw-io.superbios.com/rwp/lircd.conf what about the integration with mythtv? i can copy over the mythtv distributed lircrc.example to ~mythtv/.lircrc however the button names are different and not very many are defined in the rc file. is there a better .lircrc i should use? anyone want to share? :) also,my mythtv package is compiled "using_lirc" so do i still need to use irxevent? how can i debug whether mythtv is seeing the events from lircd? not seeing anything in the mythbackend logs and the docs seem kinda sparse on this to me. any pointers? background info: * distro =3D FC4 * Mythtv =3D 0.19 w/ lirc support * linux =3D 2.6.16 * remote =3D ATI remote wonder plus * lirc =3D 0.8.1-CVS + Cymen's patch thanks, eric On 4/9/06, Aidan Crook <ai...@mi...> wrote: > Hi, > > Thanks for your reply -- lirc was not registering a device at all in my > case. Although now I've just managed to succeed in getting my ATI Remote > Wonder Plus to work. My problem was that the ati_remote.ko kernel module > was also loading by default with FC4. This is apparently a problem with > all the ATI remotes - that lirc_atiusb.ko and ati_remote.ko must not > both be in the kernel build direcory. > > Renaming ati_remote.ko to something else in the kernel-build directory & > rebooting allowed lirc_atiusb to register the lirc device on major no. > 61. > > I applied the patch located at http://raw-io.com/rwp/ manually (going > through the file and altering the lines) to lirc_atiusb.c > > Then recompiled lirc. In my case there were 2 instances of > lirc_atiusb.ko under the kernel-build directory - one inserted by > compiling the source, and a second from a previous installation of lirc > via yum. I had to copy the lirc_atiusb.ko from the directory where I > compiled lirc over both of these before it worked. Now I have a fully > functioning remote! > > Thanks for your help on this -- it's much appreciated! > > Aidan > > > On Sun, 2006-04-09 at 17:09 -0500, Cymen Vig wrote: > > On 3/15/06, Aidan Crook <Ai...@mi...> wrote: > > > Am I right in thinking that the major is the 1st number after the dev= ice > > > name? If so, then there are no such devices! ?? > > > > > > >ls -l | grep 61 > > > crw-rw---- 1 root tty 4, 61 Mar 13 19:44 tty61 > > > > > > It's possible I have missed a line needed in one of the startup files= . > > > Everything that is present is mentioned in the original email. > > > > I missed your posts to the list so I apologize for the delay. Were you > > able to get this working? My lirc device is /dev/lirc/0 and (perhaps > > Gentoo specific), my /etc/conf.d/lircd has: > > --- > > # Options to pass to the lircd process > > LIRCD_OPTS=3D"-d /dev/lirc/0" > > --- > > > > Here are the fs details: > > > > --- > > [screen] mythtv lirc # pwd > > /dev/lirc > > [screen] mythtv lirc # ls -al 0 > > crw-rw---- 1 root root 61, 0 Apr 8 21:01 0 > > --- > > > > Regards, > > Cymen > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting langua= ge > that extends applications into web and mobile media. Attend the live webc= ast > and join the prime developer group breaking into this new coding territor= y! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat= =3D121642 > |
From: Aidan C. <aidanc@MIT.EDU> - 2006-04-11 05:06:58
|
Hi Eric, I used the precompiled mythtv installed via yum (which had lirc support). For this you don't need irxevent - you just replace 'irxevent' with 'mythtv' in the lircrc file. I don't know how to go about debugging it. I've posted the lircrc that works for me at http://web.mit.edu/~aidanc/www/lirc/lircrc (the script in there is the one on Jarod's Myth(TV)ology site) But I created my own lircd.conf so the button names are likely to be different. I've posted this at: http://web.mit.edu/~aidanc/www/lirc/lircd.conf I don't think I've tested all the buttons yet in mythtv so no guarantees! Hope that helps, Aidan On Mon, 2006-04-10 at 21:11 -0700, Eric DeFriez wrote: > Thanks Aidan and Cymen! that looks like it was my problem also > (duplcate lirc_* modules and the ati_remote module) after upgrading to > 2.6.16 for the RWP. (i used cymen's patch to lirc_atiusb.c). after i > patched+recompiled and removed/overwrote the extra kernel modules and > i'm seeing all the button events with lircd+irw. yay! > > i've got a working remote wonder plus lircd.conf from: > http://raw-io.superbios.com/rwp/lircd.conf > > what about the integration with mythtv? i can copy over the mythtv > distributed lircrc.example to ~mythtv/.lircrc however the button names > are different and not very many are defined in the rc file. is there > a better .lircrc i should use? anyone want to share? :) > > also,my mythtv package is compiled "using_lirc" so do i still need to > use irxevent? how can i debug whether mythtv is seeing the events > from lircd? not seeing anything in the mythbackend logs and the docs > seem kinda sparse on this to me. any pointers? > > background info: > * distro = FC4 > * Mythtv = 0.19 w/ lirc support > * linux = 2.6.16 > * remote = ATI remote wonder plus > * lirc = 0.8.1-CVS + Cymen's patch > > thanks, > eric > > > On 4/9/06, Aidan Crook <ai...@mi...> wrote: > > Hi, > > > > Thanks for your reply -- lirc was not registering a device at all in my > > case. Although now I've just managed to succeed in getting my ATI Remote > > Wonder Plus to work. My problem was that the ati_remote.ko kernel module > > was also loading by default with FC4. This is apparently a problem with > > all the ATI remotes - that lirc_atiusb.ko and ati_remote.ko must not > > both be in the kernel build direcory. > > > > Renaming ati_remote.ko to something else in the kernel-build directory & > > rebooting allowed lirc_atiusb to register the lirc device on major no. > > 61. > > > > I applied the patch located at http://raw-io.com/rwp/ manually (going > > through the file and altering the lines) to lirc_atiusb.c > > > > Then recompiled lirc. In my case there were 2 instances of > > lirc_atiusb.ko under the kernel-build directory - one inserted by > > compiling the source, and a second from a previous installation of lirc > > via yum. I had to copy the lirc_atiusb.ko from the directory where I > > compiled lirc over both of these before it worked. Now I have a fully > > functioning remote! > > > > Thanks for your help on this -- it's much appreciated! > > > > Aidan > > > > > > On Sun, 2006-04-09 at 17:09 -0500, Cymen Vig wrote: > > > On 3/15/06, Aidan Crook <Ai...@mi...> wrote: > > > > Am I right in thinking that the major is the 1st number after the device > > > > name? If so, then there are no such devices! ?? > > > > > > > > >ls -l | grep 61 > > > > crw-rw---- 1 root tty 4, 61 Mar 13 19:44 tty61 > > > > > > > > It's possible I have missed a line needed in one of the startup files. > > > > Everything that is present is mentioned in the original email. > > > > > > I missed your posts to the list so I apologize for the delay. Were you > > > able to get this working? My lirc device is /dev/lirc/0 and (perhaps > > > Gentoo specific), my /etc/conf.d/lircd has: > > > --- > > > # Options to pass to the lircd process > > > LIRCD_OPTS="-d /dev/lirc/0" > > > --- > > > > > > Here are the fs details: > > > > > > --- > > > [screen] mythtv lirc # pwd > > > /dev/lirc > > > [screen] mythtv lirc # ls -al 0 > > > crw-rw---- 1 root root 61, 0 Apr 8 21:01 0 > > > --- > > > > > > Regards, > > > Cymen > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > > that extends applications into web and mobile media. Attend the live webcast > > and join the prime developer group breaking into this new coding territory! > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > > |
From: Eric D. <ic...@gm...> - 2006-04-11 06:31:18
|
cool thanks. i found the one on jarod's site also. and there are lots of good buttons in yours there i forgot about. can't get it working without irxevent, which is weird because i'm using the precompiled mythtv packages via yum as well. oh well. its too late and i got it working so no biggie. thanks! /me happily watches his mythtv with his wireless keyboard put away... |eric On 4/10/06, Aidan Crook <ai...@mi...> wrote: > Hi Eric, > I used the precompiled mythtv installed via yum (which had lirc > support). For this you don't need irxevent - you just replace 'irxevent' > with 'mythtv' in the lircrc file. > > I don't know how to go about debugging it. > I've posted the lircrc that works for me at > http://web.mit.edu/~aidanc/www/lirc/lircrc > (the script in there is the one on Jarod's Myth(TV)ology site) > > But I created my own lircd.conf so the button names are likely to be > different. I've posted this at: > http://web.mit.edu/~aidanc/www/lirc/lircd.conf > > I don't think I've tested all the buttons yet in mythtv so no > guarantees! > > Hope that helps, > Aidan > > > On Mon, 2006-04-10 at 21:11 -0700, Eric DeFriez wrote: > > Thanks Aidan and Cymen! that looks like it was my problem also > > (duplcate lirc_* modules and the ati_remote module) after upgrading to > > 2.6.16 for the RWP. (i used cymen's patch to lirc_atiusb.c). after i > > patched+recompiled and removed/overwrote the extra kernel modules and > > i'm seeing all the button events with lircd+irw. yay! > > > > i've got a working remote wonder plus lircd.conf from: > > http://raw-io.superbios.com/rwp/lircd.conf > > > > what about the integration with mythtv? i can copy over the mythtv > > distributed lircrc.example to ~mythtv/.lircrc however the button names > > are different and not very many are defined in the rc file. is there > > a better .lircrc i should use? anyone want to share? :) > > > > also,my mythtv package is compiled "using_lirc" so do i still need to > > use irxevent? how can i debug whether mythtv is seeing the events > > from lircd? not seeing anything in the mythbackend logs and the docs > > seem kinda sparse on this to me. any pointers? > > > > background info: > > * distro =3D FC4 > > * Mythtv =3D 0.19 w/ lirc support > > * linux =3D 2.6.16 > > * remote =3D ATI remote wonder plus > > * lirc =3D 0.8.1-CVS + Cymen's patch > > > > thanks, > > eric > > > > > > On 4/9/06, Aidan Crook <ai...@mi...> wrote: > > > Hi, > > > > > > Thanks for your reply -- lirc was not registering a device at all in = my > > > case. Although now I've just managed to succeed in getting my ATI Rem= ote > > > Wonder Plus to work. My problem was that the ati_remote.ko kernel mod= ule > > > was also loading by default with FC4. This is apparently a problem wi= th > > > all the ATI remotes - that lirc_atiusb.ko and ati_remote.ko must not > > > both be in the kernel build direcory. > > > > > > Renaming ati_remote.ko to something else in the kernel-build director= y & > > > rebooting allowed lirc_atiusb to register the lirc device on major no= . > > > 61. > > > > > > I applied the patch located at http://raw-io.com/rwp/ manually (going > > > through the file and altering the lines) to lirc_atiusb.c > > > > > > Then recompiled lirc. In my case there were 2 instances of > > > lirc_atiusb.ko under the kernel-build directory - one inserted by > > > compiling the source, and a second from a previous installation of li= rc > > > via yum. I had to copy the lirc_atiusb.ko from the directory where I > > > compiled lirc over both of these before it worked. Now I have a fully > > > functioning remote! > > > > > > Thanks for your help on this -- it's much appreciated! > > > > > > Aidan > > > > > > > > > On Sun, 2006-04-09 at 17:09 -0500, Cymen Vig wrote: > > > > On 3/15/06, Aidan Crook <Ai...@mi...> wrote: > > > > > Am I right in thinking that the major is the 1st number after the= device > > > > > name? If so, then there are no such devices! ?? > > > > > > > > > > >ls -l | grep 61 > > > > > crw-rw---- 1 root tty 4, 61 Mar 13 19:44 tty61 > > > > > > > > > > It's possible I have missed a line needed in one of the startup f= iles. > > > > > Everything that is present is mentioned in the original email. > > > > > > > > I missed your posts to the list so I apologize for the delay. Were = you > > > > able to get this working? My lirc device is /dev/lirc/0 and (perhap= s > > > > Gentoo specific), my /etc/conf.d/lircd has: > > > > --- > > > > # Options to pass to the lircd process > > > > LIRCD_OPTS=3D"-d /dev/lirc/0" > > > > --- > > > > > > > > Here are the fs details: > > > > > > > > --- > > > > [screen] mythtv lirc # pwd > > > > /dev/lirc > > > > [screen] mythtv lirc # ls -al 0 > > > > crw-rw---- 1 root root 61, 0 Apr 8 21:01 0 > > > > --- > > > > > > > > Regards, > > > > Cymen > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by xPML, a groundbreaking scripting la= nguage > > > that extends applications into web and mobile media. Attend the live = webcast > > > and join the prime developer group breaking into this new coding terr= itory! > > > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&d= at=3D121642 > > > > > |