Linux Infrared Remote Control

On Sun, Mar 20, 2005 at 10:59:27PM -0600, Jim Oltman wrote:
> I have been using apt-get to install LIRC.  Axel hasn't had time to
> setup lirc with the driver for the new MCE Philips IR adapter.=20

What makes you think that?

> somone on the mythtv mailing list told me to take the code he posted
> and substitute it for the code in the lirc_mceusb.h then compile.

This for instance is something ATrpms would never do. Any patch has to
get through this list and lirc developers' hands.

Unless there are real strong reasons to do otherwise, ATrpms will
stick to the lirc release model and only incorporate patches as
sanctioned by lirc developers (usually Christoph).

(well, the above is half-true, sometimes prereleases/release
candidates are built at ATrpms and placed in the bleeding repo for
_testers_, not users!)
--=20
Axel.Thimm at ATrpms.net

Jim Oltman wrote:

>I really wanted to get this adapter working, somone on the mythtv
>mailing list told me to take the code he posted and substitute it for
>the code in the lirc_mceusb.h then compile.
>
Actually if you use my code you'll need to replace lirc_mceusb.c and 
change line 62 from
lirc_philipsusb to lirc_mceusb. Make sure no other instances of 
lirc_mceusb.ko and
lirc_dev.ko are on your system before you install the new drivers.

>He then told me that
>after the compile, I should take the lirc_dev and lirc_mceusb and move
>them into the driver directory that the APT-GET LIRC was installed
>into and reboot.  
>
The driver goes into /lib/modules/{kernel version}/misc/. If you do a 
"make install"
it should go in the right directory automatically.

>I managed to get the compile to work correctly and
>am getting this error when I reboot/load up the new lirc driver.
>
>Mar 20 19:04:54 mythfrontend kernel: ohci_hcd 0000:00:02.1: wakeup
>Mar 20 19:04:54 mythfrontend kernel: usb 3-3: new full speed USB
>device using ohci_hcd and address 3
>Mar 20 19:04:54 mythfrontend kernel: lirc_dev:
>lirc_register_plugin:sample_rate: 80
>Mar 20 19:04:54 mythfrontend kernel:
>/home/mythtv/compile/lirc-0.7.0/drivers/lirc_mceusb/lirc_mceusb.c:
>mceusb_setup2 - Unsuccessful initialization
>
This doesn't look like my driver. You can find the latest release which 
is already designed
as a plug-in replacement for the old mce driver on:

http://blatter.com/mceusb/

regards
martin

Axel,

I didn't mean anything by saying you didn't have time to include this
into LIRC.  I completely understand why you would never put this code
in.  Sorry for the confusion.  I will try Martin's version of the code
he posted.

Jim

On Mon, 21 Mar 2005 09:08:41 +0100, Axel Thimm <Axel.Thimm@...> wrote:
> On Sun, Mar 20, 2005 at 10:59:27PM -0600, Jim Oltman wrote:
> > I have been using apt-get to install LIRC.  Axel hasn't had time to
> > setup lirc with the driver for the new MCE Philips IR adapter.
> 
> What makes you think that?
> 
> > somone on the mythtv mailing list told me to take the code he posted
> > and substitute it for the code in the lirc_mceusb.h then compile.
> 
> This for instance is something ATrpms would never do. Any patch has to
> get through this list and lirc developers' hands.
> 
> Unless there are real strong reasons to do otherwise, ATrpms will
> stick to the lirc release model and only incorporate patches as
> sanctioned by lirc developers (usually Christoph).
> 
> (well, the above is half-true, sometimes prereleases/release
> candidates are built at ATrpms and placed in the bleeding repo for
> _testers_, not users!)
> --
> Axel.Thimm at ATrpms.net
> 
> 
>

Well, I am at work and decided this couldn't wait!  I compilied with
Martin's code and I didn't receive any errors.  It says it registered
the device and it looks like it went well.  Over lunch I am going to
go home and see if I get anything out of my remote with irrecord. 
Martin, I just copied and pasted the dev and mceusb.ko.files into my
already setup lirc directory (through APT-GET).  Do you think the
version of irrecord from APT_GET will have any problems using the new
drivers as opposed to the one I just compiled?  Thanks for your help!

Jim


On Mon, 21 Mar 2005 09:41:17 +0100, Martin Blatter <mblatter@...> wrote:
> Jim Oltman wrote:
> 
> >I really wanted to get this adapter working, somone on the mythtv
> >mailing list told me to take the code he posted and substitute it for
> >the code in the lirc_mceusb.h then compile.
> >
> Actually if you use my code you'll need to replace lirc_mceusb.c and
> change line 62 from
> lirc_philipsusb to lirc_mceusb. Make sure no other instances of
> lirc_mceusb.ko and
> lirc_dev.ko are on your system before you install the new drivers.
> 
> >He then told me that
> >after the compile, I should take the lirc_dev and lirc_mceusb and move
> >them into the driver directory that the APT-GET LIRC was installed
> >into and reboot.
> >
> The driver goes into /lib/modules/{kernel version}/misc/. If you do a
> "make install"
> it should go in the right directory automatically.
> 
> >I managed to get the compile to work correctly and
> >am getting this error when I reboot/load up the new lirc driver.
> >
> >Mar 20 19:04:54 mythfrontend kernel: ohci_hcd 0000:00:02.1: wakeup
> >Mar 20 19:04:54 mythfrontend kernel: usb 3-3: new full speed USB
> >device using ohci_hcd and address 3
> >Mar 20 19:04:54 mythfrontend kernel: lirc_dev:
> >lirc_register_plugin:sample_rate: 80
> >Mar 20 19:04:54 mythfrontend kernel:
> >/home/mythtv/compile/lirc-0.7.0/drivers/lirc_mceusb/lirc_mceusb.c:
> >mceusb_setup2 - Unsuccessful initialization
> >
> This doesn't look like my driver. You can find the latest release which
> is already designed
> as a plug-in replacement for the old mce driver on:
> 
> http://blatter.com/mceusb/
> 
> regards
> martin
>

I am home now (left work early) and I am not getting anything from
irrecord.  I am using this command:

irrecord --device=/dev/lircd temp

This is the only command that doesn't give me an error.  I also have a
/dev/lirc /dev/lirc0 /dev/lircd.  I have this in my modprobe.conf:

# LIRC Setup
alias char-major-61 lirc_mceusb

I have also followed Jarod's instructions on patching the rc.sysinit
to get lirc to start early in the boot process.  What am I doing
wrong?

On Mon, 21 Mar 2005 10:50:16 -0600, Jim Oltman <cnliberal@...> wrote:
> Well, I am at work and decided this couldn't wait!  I compilied with
> Martin's code and I didn't receive any errors.  It says it registered
> the device and it looks like it went well.  Over lunch I am going to
> go home and see if I get anything out of my remote with irrecord.
> Martin, I just copied and pasted the dev and mceusb.ko.files into my
> already setup lirc directory (through APT-GET).  Do you think the
> version of irrecord from APT_GET will have any problems using the new
> drivers as opposed to the one I just compiled?  Thanks for your help!
> 
> Jim
> 
> 
> On Mon, 21 Mar 2005 09:41:17 +0100, Martin Blatter <mblatter@...> wrote:
> > Jim Oltman wrote:
> >
> > >I really wanted to get this adapter working, somone on the mythtv
> > >mailing list told me to take the code he posted and substitute it for
> > >the code in the lirc_mceusb.h then compile.
> > >
> > Actually if you use my code you'll need to replace lirc_mceusb.c and
> > change line 62 from
> > lirc_philipsusb to lirc_mceusb. Make sure no other instances of
> > lirc_mceusb.ko and
> > lirc_dev.ko are on your system before you install the new drivers.
> >
> > >He then told me that
> > >after the compile, I should take the lirc_dev and lirc_mceusb and move
> > >them into the driver directory that the APT-GET LIRC was installed
> > >into and reboot.
> > >
> > The driver goes into /lib/modules/{kernel version}/misc/. If you do a
> > "make install"
> > it should go in the right directory automatically.
> >
> > >I managed to get the compile to work correctly and
> > >am getting this error when I reboot/load up the new lirc driver.
> > >
> > >Mar 20 19:04:54 mythfrontend kernel: ohci_hcd 0000:00:02.1: wakeup
> > >Mar 20 19:04:54 mythfrontend kernel: usb 3-3: new full speed USB
> > >device using ohci_hcd and address 3
> > >Mar 20 19:04:54 mythfrontend kernel: lirc_dev:
> > >lirc_register_plugin:sample_rate: 80
> > >Mar 20 19:04:54 mythfrontend kernel:
> > >/home/mythtv/compile/lirc-0.7.0/drivers/lirc_mceusb/lirc_mceusb.c:
> > >mceusb_setup2 - Unsuccessful initialization
> > >
> > This doesn't look like my driver. You can find the latest release which
> > is already designed
> > as a plug-in replacement for the old mce driver on:
> >
> > http://blatter.com/mceusb/
> >
> > regards
> > martin
> >
>

Jim Oltman wrote:

># LIRC Setup
>alias char-major-61 lirc_mceusb
>  
>
please add the following right below the above line in
modprobe.conf:
options lirc_mceusb  debug=1

then reboot your machine without the transciever plugged in.
(lircd doesn't need to run after rebooting!). plug in the ir transciever,
wait a few seconds, press a few keys on the remote and mail me
the output of /var/log/mesages.

am i right in the assumption that you have an ohci type usb
host controller? because all the people I know who use the driver
sucessfully have an uhci/ehci (e.g. intel) usb host controller. there
may be a problem related to ohci host controllers. but it's just a
guess.

regards
martin

u r right in saying i have ohci.  NForce2 mobo


On Mon, 21 Mar 2005 18:15:10 -0600, Jim Oltman <cnliberal@...> wrote:
> I only received this data once.  I have rebooted 2 times (no changes
> to config other than the initial debug) and haven't received it again.
>  There is a lot here because I wanted to include the length 10
> message:
> 
> Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 81
> 5f 9f 01 01 9f 15 00 00 80  (length=10)
> Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> b4 13 88 0a  (length=5)
> Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> 88 0a 88 13  (length=5)
> Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> 87 12 9a 14  (length=5)
> Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> 87 0a 88 0c  (length=5)
> Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> 86 09 88 0a  (length=5)
> Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> 88 0b 87 0b  (length=5)
> Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> 87 0c 86 0b  (length=5)
> Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> 86 0b 87 0d  (length=5)
> Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> 8d 0a 88 1d  (length=5)
> Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> 86 0f 82 28  (length=5)
> Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> 86 0b 87 0d  (length=5)
> Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> 8d 15 86 0e  (length=5)
> Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> 83 0b 87 0b  (length=5)
> Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> 87 10 8b 27  (length=5)
> Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> 85 7f 7f 7f  (length=5)
> Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> 7f 7f 7f 7f  (length=5)
> Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 81
> 5f 9f 01 01 9f 15 00 00 80  (length=10)
> 
> 
> On Tue, 22 Mar 2005 00:26:16 +0100, Martin Blatter <mblatter@...> wrote:
> > Jim Oltman wrote:
> >
> > ># LIRC Setup
> > >alias char-major-61 lirc_mceusb
> > >
> > >
> > please add the following right below the above line in
> > modprobe.conf:
> > options lirc_mceusb  debug=1
> >
> > then reboot your machine without the transciever plugged in.
> > (lircd doesn't need to run after rebooting!). plug in the ir transciever,
> > wait a few seconds, press a few keys on the remote and mail me
> > the output of /var/log/mesages.
> >
> > am i right in the assumption that you have an ohci type usb
> > host controller? because all the people I know who use the driver
> > sucessfully have an uhci/ehci (e.g. intel) usb host controller. there
> > may be a problem related to ohci host controllers. but it's just a
> > guess.
> >
> > regards
> > martin
> >
> >
>

Mon, 21 Mar 2005 15:51:08 -0600 | Jim Oltman <cnliberal@...>

::-I am home now (left work early) and I am not getting anything from
::-irrecord.  I am using this command:
::-
::-irrecord --device=/dev/lircd temp
::-
::-This is the only command that doesn't give me an error.  I also have a
::-/dev/lirc /dev/lirc0 /dev/lircd.

I believe you are going to want the --device flag to point to the lirc device node:
/dev/lirc or /dev/lirc/0, not the lircd socket.  Lircd also shouldnt be running with
irrecord

//ec

I'll look into that. Need to find someone who owns an ohci mobo ;-)
Otherwise the output looks good. It's the raw data from the remote.

Jim Oltman wrote:

>u r right in saying i have ohci.  NForce2 mobo
>
>
>On Mon, 21 Mar 2005 18:15:10 -0600, Jim Oltman <cnliberal@...> wrote:
>  
>
>>I only received this data once.  I have rebooted 2 times (no changes
>>to config other than the initial debug) and haven't received it again.
>> There is a lot here because I wanted to include the length 10
>>message:
>>
>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 81
>>5f 9f 01 01 9f 15 00 00 80  (length=10)
>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>b4 13 88 0a  (length=5)
>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>88 0a 88 13  (length=5)
>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>87 12 9a 14  (length=5)
>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>87 0a 88 0c  (length=5)
>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>86 09 88 0a  (length=5)
>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>88 0b 87 0b  (length=5)
>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>87 0c 86 0b  (length=5)
>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>86 0b 87 0d  (length=5)
>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>8d 0a 88 1d  (length=5)
>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>86 0f 82 28  (length=5)
>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>86 0b 87 0d  (length=5)
>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>8d 15 86 0e  (length=5)
>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>83 0b 87 0b  (length=5)
>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>87 10 8b 27  (length=5)
>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>85 7f 7f 7f  (length=5)
>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>7f 7f 7f 7f  (length=5)
>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 81
>>5f 9f 01 01 9f 15 00 00 80  (length=10)
>>
>>
>>On Tue, 22 Mar 2005 00:26:16 +0100, Martin Blatter <mblatter@...> wrote:
>>    
>>
>>>Jim Oltman wrote:
>>>
>>>      
>>>
>>>># LIRC Setup
>>>>alias char-major-61 lirc_mceusb
>>>>
>>>>
>>>>        
>>>>
>>>please add the following right below the above line in
>>>modprobe.conf:
>>>options lirc_mceusb  debug=1
>>>
>>>then reboot your machine without the transciever plugged in.
>>>(lircd doesn't need to run after rebooting!). plug in the ir transciever,
>>>wait a few seconds, press a few keys on the remote and mail me
>>>the output of /var/log/mesages.
>>>
>>>am i right in the assumption that you have an ohci type usb
>>>host controller? because all the people I know who use the driver
>>>sucessfully have an uhci/ehci (e.g. intel) usb host controller. there
>>>may be a problem related to ohci host controllers. but it's just a
>>>guess.
>>>
>>>regards
>>>martin
>>>
>>>
>>>      
>>>
>
>  
>

Why am I only getting it once?  Why does irrecord only work with
/dev/lircd?  SO CONFUSED!!  Thanks Martin and EC!


On Tue, 22 Mar 2005 01:30:32 +0100, Martin Blatter <mblatter@...> wrote:
> I'll look into that. Need to find someone who owns an ohci mobo ;-)
> Otherwise the output looks good. It's the raw data from the remote.
> 
> Jim Oltman wrote:
> 
> >u r right in saying i have ohci.  NForce2 mobo
> >
> >
> >On Mon, 21 Mar 2005 18:15:10 -0600, Jim Oltman <cnliberal@...> wrote:
> >
> >
> >>I only received this data once.  I have rebooted 2 times (no changes
> >>to config other than the initial debug) and haven't received it again.
> >> There is a lot here because I wanted to include the length 10
> >>message:
> >>
> >>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 81
> >>5f 9f 01 01 9f 15 00 00 80  (length=10)
> >>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> >>b4 13 88 0a  (length=5)
> >>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> >>88 0a 88 13  (length=5)
> >>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> >>87 12 9a 14  (length=5)
> >>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> >>87 0a 88 0c  (length=5)
> >>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> >>86 09 88 0a  (length=5)
> >>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> >>88 0b 87 0b  (length=5)
> >>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> >>87 0c 86 0b  (length=5)
> >>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> >>86 0b 87 0d  (length=5)
> >>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> >>8d 0a 88 1d  (length=5)
> >>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> >>86 0f 82 28  (length=5)
> >>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> >>86 0b 87 0d  (length=5)
> >>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> >>8d 15 86 0e  (length=5)
> >>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> >>83 0b 87 0b  (length=5)
> >>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> >>87 10 8b 27  (length=5)
> >>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> >>85 7f 7f 7f  (length=5)
> >>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> >>7f 7f 7f 7f  (length=5)
> >>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 81
> >>5f 9f 01 01 9f 15 00 00 80  (length=10)
> >>
> >>
> >>On Tue, 22 Mar 2005 00:26:16 +0100, Martin Blatter <mblatter@...> wrote:
> >>
> >>
> >>>Jim Oltman wrote:
> >>>
> >>>
> >>>
> >>>># LIRC Setup
> >>>>alias char-major-61 lirc_mceusb
> >>>>
> >>>>
> >>>>
> >>>>
> >>>please add the following right below the above line in
> >>>modprobe.conf:
> >>>options lirc_mceusb  debug=1
> >>>
> >>>then reboot your machine without the transciever plugged in.
> >>>(lircd doesn't need to run after rebooting!). plug in the ir transciever,
> >>>wait a few seconds, press a few keys on the remote and mail me
> >>>the output of /var/log/mesages.
> >>>
> >>>am i right in the assumption that you have an ohci type usb
> >>>host controller? because all the people I know who use the driver
> >>>sucessfully have an uhci/ehci (e.g. intel) usb host controller. there
> >>>may be a problem related to ohci host controllers. but it's just a
> >>>guess.
> >>>
> >>>regards
> >>>martin
> >>>
> >>>
> >>>
> >>>
> >
> >
> >
> 
>

Jim Oltman wrote:

>Why am I only getting it once?  Why does irrecord only work with
>/dev/lircd?  SO CONFUSED!!  Thanks Martin and EC!
>  
>
I'm as puzzled as you are. Try mode2 for testing. You don't need 
irrecord, there's
already a working config file in the tar archive on my download page.

I just installed lirc-0.7.0 with my version of lirc-mceusb.c on top on a 
freshly installed
machine (stock SuSE 9.2 with updated kernel). Works fine. mode2 gives me 
output
each time I press a button. It's a UHCI machine though.

And note that initialization of the USB device does not work reliably on 
kernels
older than 2.6.10. If you have problems with initialization (it says 
something
like "receive request FAILED!" in /var/log/messages after plugging in 
the device),
try to remove the device and plug it in again after a few seconds.

Thanks for testing.

>On Tue, 22 Mar 2005 01:30:32 +0100, Martin Blatter <mblatter@...> wrote:
>  
>
>>I'll look into that. Need to find someone who owns an ohci mobo ;-)
>>Otherwise the output looks good. It's the raw data from the remote.
>>
>>Jim Oltman wrote:
>>
>>    
>>
>>>u r right in saying i have ohci.  NForce2 mobo
>>>
>>>
>>>On Mon, 21 Mar 2005 18:15:10 -0600, Jim Oltman <cnliberal@...> wrote:
>>>
>>>
>>>      
>>>
>>>>I only received this data once.  I have rebooted 2 times (no changes
>>>>to config other than the initial debug) and haven't received it again.
>>>>There is a lot here because I wanted to include the length 10
>>>>message:
>>>>
>>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 81
>>>>5f 9f 01 01 9f 15 00 00 80  (length=10)
>>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>>>b4 13 88 0a  (length=5)
>>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>>>88 0a 88 13  (length=5)
>>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>>>87 12 9a 14  (length=5)
>>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>>>87 0a 88 0c  (length=5)
>>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>>>86 09 88 0a  (length=5)
>>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>>>88 0b 87 0b  (length=5)
>>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>>>87 0c 86 0b  (length=5)
>>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>>>86 0b 87 0d  (length=5)
>>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>>>8d 0a 88 1d  (length=5)
>>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>>>86 0f 82 28  (length=5)
>>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>>>86 0b 87 0d  (length=5)
>>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>>>8d 15 86 0e  (length=5)
>>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>>>83 0b 87 0b  (length=5)
>>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>>>87 10 8b 27  (length=5)
>>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>>>85 7f 7f 7f  (length=5)
>>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
>>>>7f 7f 7f 7f  (length=5)
>>>>Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 81
>>>>5f 9f 01 01 9f 15 00 00 80  (length=10)
>>>>
>>>>
>>>>On Tue, 22 Mar 2005 00:26:16 +0100, Martin Blatter <mblatter@...> wrote:
>>>>
>>>>
>>>>        
>>>>
>>>>>Jim Oltman wrote:
>>>>>
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>>># LIRC Setup
>>>>>>alias char-major-61 lirc_mceusb
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>            
>>>>>>
>>>>>please add the following right below the above line in
>>>>>modprobe.conf:
>>>>>options lirc_mceusb  debug=1
>>>>>
>>>>>then reboot your machine without the transciever plugged in.
>>>>>(lircd doesn't need to run after rebooting!). plug in the ir transciever,
>>>>>wait a few seconds, press a few keys on the remote and mail me
>>>>>the output of /var/log/mesages.
>>>>>
>>>>>am i right in the assumption that you have an ohci type usb
>>>>>host controller? because all the people I know who use the driver
>>>>>sucessfully have an uhci/ehci (e.g. intel) usb host controller. there
>>>>>may be a problem related to ohci host controllers. but it's just a
>>>>>guess.
>>>>>
>>>>>regards
>>>>>martin
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>          
>>>>>
>>>
>>>      
>>>
>>    
>>
>
>  
>

I also have this problem, but with NForce3 mobo.  If I rmmod lirc_dev
and lirc_mceusb, then plug in the reciever, by the third time it
usually works.  You mentioned using Jarod's instructions.  Are you
also using FC3?

- patrick


On Mon, 21 Mar 2005 18:23:10 -0600, Jim Oltman <cnliberal@...> wrote:
> u r right in saying i have ohci.  NForce2 mobo
> 
> On Mon, 21 Mar 2005 18:15:10 -0600, Jim Oltman <cnliberal@...> wrote:
> > I only received this data once.  I have rebooted 2 times (no changes
> > to config other than the initial debug) and haven't received it again.
> >  There is a lot here because I wanted to include the length 10
> > message:
> >
> > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 81
> > 5f 9f 01 01 9f 15 00 00 80  (length=10)
> > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > b4 13 88 0a  (length=5)
> > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > 88 0a 88 13  (length=5)
> > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > 87 12 9a 14  (length=5)
> > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > 87 0a 88 0c  (length=5)
> > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > 86 09 88 0a  (length=5)
> > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > 88 0b 87 0b  (length=5)
> > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > 87 0c 86 0b  (length=5)
> > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > 86 0b 87 0d  (length=5)
> > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > 8d 0a 88 1d  (length=5)
> > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > 86 0f 82 28  (length=5)
> > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > 86 0b 87 0d  (length=5)
> > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > 8d 15 86 0e  (length=5)
> > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > 83 0b 87 0b  (length=5)
> > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > 87 10 8b 27  (length=5)
> > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > 85 7f 7f 7f  (length=5)
> > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > 7f 7f 7f 7f  (length=5)
> > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 81
> > 5f 9f 01 01 9f 15 00 00 80  (length=10)
> >
> >
> > On Tue, 22 Mar 2005 00:26:16 +0100, Martin Blatter <mblatter@...> wrote:
> > > Jim Oltman wrote:
> > >
> > > ># LIRC Setup
> > > >alias char-major-61 lirc_mceusb
> > > >
> > > >
> > > please add the following right below the above line in
> > > modprobe.conf:
> > > options lirc_mceusb  debug=1
> > >
> > > then reboot your machine without the transciever plugged in.
> > > (lircd doesn't need to run after rebooting!). plug in the ir transciever,
> > > wait a few seconds, press a few keys on the remote and mail me
> > > the output of /var/log/mesages.
> > >
> > > am i right in the assumption that you have an ohci type usb
> > > host controller? because all the people I know who use the driver
> > > sucessfully have an uhci/ehci (e.g. intel) usb host controller. there
> > > may be a problem related to ohci host controllers. but it's just a
> > > guess.
> > >
> > > regards
> > > martin
> > >
> > >
> >
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>

I am using Jarod's guide on an FC3 system running 2.6.10-1.770 kernel.
 I will try out what you did.  Thanks!


On Mon, 21 Mar 2005 16:59:31 -0800, Patrick Kelley <kelnic@...> wrote:
> I also have this problem, but with NForce3 mobo.  If I rmmod lirc_dev
> and lirc_mceusb, then plug in the reciever, by the third time it
> usually works.  You mentioned using Jarod's instructions.  Are you
> also using FC3?
> 
> - patrick
> 
> 
> On Mon, 21 Mar 2005 18:23:10 -0600, Jim Oltman <cnliberal@...> wrote:
> > u r right in saying i have ohci.  NForce2 mobo
> >
> > On Mon, 21 Mar 2005 18:15:10 -0600, Jim Oltman <cnliberal@...> wrote:
> > > I only received this data once.  I have rebooted 2 times (no changes
> > > to config other than the initial debug) and haven't received it again.
> > >  There is a lot here because I wanted to include the length 10
> > > message:
> > >
> > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 81
> > > 5f 9f 01 01 9f 15 00 00 80  (length=10)
> > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > b4 13 88 0a  (length=5)
> > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > 88 0a 88 13  (length=5)
> > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > 87 12 9a 14  (length=5)
> > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > 87 0a 88 0c  (length=5)
> > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > 86 09 88 0a  (length=5)
> > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > 88 0b 87 0b  (length=5)
> > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > 87 0c 86 0b  (length=5)
> > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > 86 0b 87 0d  (length=5)
> > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > 8d 0a 88 1d  (length=5)
> > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > 86 0f 82 28  (length=5)
> > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > 86 0b 87 0d  (length=5)
> > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > 8d 15 86 0e  (length=5)
> > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > 83 0b 87 0b  (length=5)
> > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > 87 10 8b 27  (length=5)
> > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > 85 7f 7f 7f  (length=5)
> > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > 7f 7f 7f 7f  (length=5)
> > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 81
> > > 5f 9f 01 01 9f 15 00 00 80  (length=10)
> > >
> > >
> > > On Tue, 22 Mar 2005 00:26:16 +0100, Martin Blatter <mblatter@...> wrote:
> > > > Jim Oltman wrote:
> > > >
> > > > ># LIRC Setup
> > > > >alias char-major-61 lirc_mceusb
> > > > >
> > > > >
> > > > please add the following right below the above line in
> > > > modprobe.conf:
> > > > options lirc_mceusb  debug=1
> > > >
> > > > then reboot your machine without the transciever plugged in.
> > > > (lircd doesn't need to run after rebooting!). plug in the ir transciever,
> > > > wait a few seconds, press a few keys on the remote and mail me
> > > > the output of /var/log/mesages.
> > > >
> > > > am i right in the assumption that you have an ohci type usb
> > > > host controller? because all the people I know who use the driver
> > > > sucessfully have an uhci/ehci (e.g. intel) usb host controller. there
> > > > may be a problem related to ohci host controllers. but it's just a
> > > > guess.
> > > >
> > > > regards
> > > > martin
> > > >
> > > >
> > >
> >
> > -------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT Products from real users.
> > Discover which products truly live up to the hype. Start reading now.
> > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> >
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>

do you have an nvidia nforce mobo?


On Mon, 21 Mar 2005 19:39:34 -0800, Patrick Kelley <kelnic@...> wrote:
> here, try jim cottrell's driver, it isn't irq driven but it worked for
> me first try
> 
> 
> On Mon, 21 Mar 2005 19:08:26 -0600, Jim Oltman <cnliberal@...> wrote:
> > I am using Jarod's guide on an FC3 system running 2.6.10-1.770 kernel.
> >  I will try out what you did.  Thanks!
> >
> >
> > On Mon, 21 Mar 2005 16:59:31 -0800, Patrick Kelley <kelnic@...> wrote:
> > > I also have this problem, but with NForce3 mobo.  If I rmmod lirc_dev
> > > and lirc_mceusb, then plug in the reciever, by the third time it
> > > usually works.  You mentioned using Jarod's instructions.  Are you
> > > also using FC3?
> > >
> > > - patrick
> > >
> > >
> > > On Mon, 21 Mar 2005 18:23:10 -0600, Jim Oltman <cnliberal@...> wrote:
> > > > u r right in saying i have ohci.  NForce2 mobo
> > > >
> > > > On Mon, 21 Mar 2005 18:15:10 -0600, Jim Oltman <cnliberal@...> wrote:
> > > > > I only received this data once.  I have rebooted 2 times (no changes
> > > > > to config other than the initial debug) and haven't received it again.
> > > > >  There is a lot here because I wanted to include the length 10
> > > > > message:
> > > > >
> > > > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 81
> > > > > 5f 9f 01 01 9f 15 00 00 80  (length=10)
> > > > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > > > b4 13 88 0a  (length=5)
> > > > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > > > 88 0a 88 13  (length=5)
> > > > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > > > 87 12 9a 14  (length=5)
> > > > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > > > 87 0a 88 0c  (length=5)
> > > > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > > > 86 09 88 0a  (length=5)
> > > > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > > > 88 0b 87 0b  (length=5)
> > > > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > > > 87 0c 86 0b  (length=5)
> > > > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > > > 86 0b 87 0d  (length=5)
> > > > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > > > 8d 0a 88 1d  (length=5)
> > > > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > > > 86 0f 82 28  (length=5)
> > > > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > > > 86 0b 87 0d  (length=5)
> > > > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > > > 8d 15 86 0e  (length=5)
> > > > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > > > 83 0b 87 0b  (length=5)
> > > > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > > > 87 10 8b 27  (length=5)
> > > > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > > > 85 7f 7f 7f  (length=5)
> > > > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 84
> > > > > 7f 7f 7f 7f  (length=5)
> > > > > Mar 21 18:03:53 mythfrontend kernel: lirc_mceusb[2]: data received 81
> > > > > 5f 9f 01 01 9f 15 00 00 80  (length=10)
> > > > >
> > > > >
> > > > > On Tue, 22 Mar 2005 00:26:16 +0100, Martin Blatter <mblatter@...> wrote:
> > > > > > Jim Oltman wrote:
> > > > > >
> > > > > > ># LIRC Setup
> > > > > > >alias char-major-61 lirc_mceusb
> > > > > > >
> > > > > > >
> > > > > > please add the following right below the above line in
> > > > > > modprobe.conf:
> > > > > > options lirc_mceusb  debug=1
> > > > > >
> > > > > > then reboot your machine without the transciever plugged in.
> > > > > > (lircd doesn't need to run after rebooting!). plug in the ir transciever,
> > > > > > wait a few seconds, press a few keys on the remote and mail me
> > > > > > the output of /var/log/mesages.
> > > > > >
> > > > > > am i right in the assumption that you have an ohci type usb
> > > > > > host controller? because all the people I know who use the driver
> > > > > > sucessfully have an uhci/ehci (e.g. intel) usb host controller. there
> > > > > > may be a problem related to ohci host controllers. but it's just a
> > > > > > guess.
> > > > > >
> > > > > > regards
> > > > > > martin
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > -------------------------------------------------------
> > > > SF email is sponsored by - The IT Product Guide
> > > > Read honest & candid reviews on hundreds of IT Products from real users.
> > > > Discover which products truly live up to the hype. Start reading now.
> > > > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> > > >
> > >
> > > -------------------------------------------------------
> > > SF email is sponsored by - The IT Product Guide
> > > Read honest & candid reviews on hundreds of IT Products from real users.
> > > Discover which products truly live up to the hype. Start reading now.
> > > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> > >
> >
> > -------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT Products from real users.
> > Discover which products truly live up to the hype. Start reading now.
> > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> >
> 
> 
>

Hi,

Another data point. 

I have an NForce 3 motherboard with ohci usb. At least one NForce 3
motherboard works - Asus K8N-E DELUXE nForce3 250Gb.

kernel: 2.6.10

modprobe lirc_dev 
lirc_dev: IR Remote Control driver registered, at major 61

modprobe lirc_mceusb
lirc_mceusb: no version for "lirc_unregister_plugin" found: kernel tainted.
lirc_mceusb: USB remote driver for LIRC v0.2
lirc_mceusb: Martin Blatter <martin_a_blatter@...>
lirc_dev: lirc_register_plugin:sample_rate: 0
lirc_mceusb[3]: Philips eHome Infrared Transceiver on usb2:3
usbcore: registered new driver lirc_mceusb

/usr/local/sbin/lircd
lircd is loaded without any device option. It is loaded
automatically when the module lirc_mceusb loads. 

in /dev I have the following:
/dev/lirc  /dev/lirc0  /dev/lircd  /dev/lircm

/etc/modprobe.d/local contains the following:
alias char-major-61     lirc_mceusb
install lirc_mceusb /sbin/modprobe --ignore-install lirc_mceusb ; /usr/local/sbi
n/lircd 

/etc/udev/rules.d/local contains the following:
KERNEL="lirc0", SYMLINK="lirc"

That's it and it works like a charm. Thanks for the driver because I
purchased the remote and found I had a new one that didn't work with
the old driver. I don't have to plug the receiver in but one time and
it works, and it works every time weather from boot or removing and
then pluging the device in. Also the other driver that was posted in
this group worked fine also.

Alan

Patrick Kelley wrote:

>I also have this problem, but with NForce3 mobo.  If I rmmod lirc_dev
>and lirc_mceusb, then plug in the reciever, by the third time it
>usually works.  You mentioned using Jarod's instructions.  Are you
>also using FC3?
>
OHCI doesn't seem to be the cause, it works fine on Alan's system. This 
rather sounds like
the bug in the Linux USB stack that caused problems with earlier kernels 
and the MCE
transciever.
How kosher are the FC3 kernels? Did you try a vanilla 2.6.10 or 2.6.11?

regards
martin

If I went to a 2.6.11 kernel, i would have to grab the RPM for
it...then reload my nvidia drivers...and lirc.  Maybe I will just
invest in an IR keyboard and mouse...haha


On Tue, 22 Mar 2005 09:21:03 +0100, Martin Blatter <mblatter@...> wrote:
> Patrick Kelley wrote:
> 
> >I also have this problem, but with NForce3 mobo.  If I rmmod lirc_dev
> >and lirc_mceusb, then plug in the reciever, by the third time it
> >usually works.  You mentioned using Jarod's instructions.  Are you
> >also using FC3?
> >
> OHCI doesn't seem to be the cause, it works fine on Alan's system. This
> rather sounds like
> the bug in the Linux USB stack that caused problems with earlier kernels
> and the MCE
> transciever.
> How kosher are the FC3 kernels? Did you try a vanilla 2.6.10 or 2.6.11?
> 
> regards
> martin
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>

After compiling Jim Cottrell's code, I am getting alot of these errors:

Mar 22 18:17:13 mythfrontend last message repeated 22 times
Mar 22 18:17:13 mythfrontend lircd 0.7.0[4236]: removed client
Mar 22 18:17:13 mythfrontend kernel: usb 3-3: lirc_dev timed out on ep1in
Mar 22 18:17:25 mythfrontend last message repeated 43 times
Mar 22 18:17:25 mythfrontend irrecord: could not open /dev/lirc
Mar 22 18:17:25 mythfrontend irrecord: default_init(): Device or resource busy
Mar 22 18:17:25 mythfrontend kernel: usb 3-3: lirc_dev timed out on ep1in
Mar 22 18:17:56 mythfrontend last message repeated 117 times

Plus mode2 is giving me these errors.  

[root@... mythtv]# mode2
mode2: error opening /dev/lirc
mode2: Device or resource busy
[root@... mythtv]# mode2 --device=/dev/lirc0
mode2: error opening /dev/lirc0
mode2: Device or resource busy

I am about ready to rebuild my frontend because I think there is some
lirc garbage in there and I don't know where it is coming from.  I
will be saving the .ko files (Martin's and Jim's).  Besides, what else
is there to do on a Tuesday night?


On Tue, 22 Mar 2005 17:40:43 -0600, Jim Oltman <cnliberal@...> wrote:
> Do you use the usbirt driver?  I think I will wait until you get it
> and have it working before I spend MORE cash.  haha
> 
> 
> On Tue, 22 Mar 2005 14:27:27 -0800, Patrick Kelley <kelnic@...> wrote:
> > ya, I was thinking like that, I just ordered the ira3 here:
> > http://www.home-electro.com/products.php
> > It will work with the plain lirc rpms.
> > I'm still going to use the MCE remote with it.
> >
> >
> > On Tue, 22 Mar 2005 16:07:21 -0600, Jim Oltman <cnliberal@...> wrote:
> > > If I went to a 2.6.11 kernel, i would have to grab the RPM for
> > > it...then reload my nvidia drivers...and lirc.  Maybe I will just
> > > invest in an IR keyboard and mouse...haha
> > >
> > >
> > > On Tue, 22 Mar 2005 09:21:03 +0100, Martin Blatter <mblatter@...> wrote:
> > > > Patrick Kelley wrote:
> > > >
> > > > >I also have this problem, but with NForce3 mobo.  If I rmmod lirc_dev
> > > > >and lirc_mceusb, then plug in the reciever, by the third time it
> > > > >usually works.  You mentioned using Jarod's instructions.  Are you
> > > > >also using FC3?
> > > > >
> > > > OHCI doesn't seem to be the cause, it works fine on Alan's system. This
> > > > rather sounds like
> > > > the bug in the Linux USB stack that caused problems with earlier kernels
> > > > and the MCE
> > > > transciever.
> > > > How kosher are the FC3 kernels? Did you try a vanilla 2.6.10 or 2.6.11?
> > > >
> > > > regards
> > > > martin
> > > >
> > > > -------------------------------------------------------
> > > > SF email is sponsored by - The IT Product Guide
> > > > Read honest & candid reviews on hundreds of IT Products from real users.
> > > > Discover which products truly live up to the hype. Start reading now.
> > > > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> > > >
> > >
> > > -------------------------------------------------------
> > > This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
> > > Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
> > > for the chance to win $25,000 and application distribution. Enter today at
> > > http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click
> > >
> >
>

Martin THANKS!  I reloaded my frontend and used the drivers you
provided and I am getting a response from irrecord after every reboot.
 Still on kernel 2.6.10-1.770.  MythTV doesn't like it but that might
be a lircrc problem.  Not sure.  Thanks to all for the many response
emails!!  I hope this LARGE thread helps others with this remote.

Jim


On Wed, 23 Mar 2005 17:32:53 -0600, Jim Oltman <cnliberal@...> wrote:
> After SEVERAL (on the order of 10) reboots, debug=1 is printing out
> raw data in /var/log/messages.  I have run irrecord and IT is actually
> printing dots like it should.  Nothing is getting dumped into the temp
> file I have listed, but it is a huge step forward.  Now just to load
> myth.  This functionality will probably disappear after a reboot.
> What is the harm with leave debug=1 on permanently?
> 
> 
> On Tue, 22 Mar 2005 21:01:30 -0800, Patrick Kelley <kelnic@...> wrote:
> > I'll let you know how the serial reciever goes
> >
> >
> > On Tue, 22 Mar 2005 18:22:27 -0600, Jim Oltman <cnliberal@...> wrote:
> > > After compiling Jim Cottrell's code, I am getting alot of these errors:
> > >
> > > Mar 22 18:17:13 mythfrontend last message repeated 22 times
> > > Mar 22 18:17:13 mythfrontend lircd 0.7.0[4236]: removed client
> > > Mar 22 18:17:13 mythfrontend kernel: usb 3-3: lirc_dev timed out on ep1in
> > > Mar 22 18:17:25 mythfrontend last message repeated 43 times
> > > Mar 22 18:17:25 mythfrontend irrecord: could not open /dev/lirc
> > > Mar 22 18:17:25 mythfrontend irrecord: default_init(): Device or resource busy
> > > Mar 22 18:17:25 mythfrontend kernel: usb 3-3: lirc_dev timed out on ep1in
> > > Mar 22 18:17:56 mythfrontend last message repeated 117 times
> > >
> > > Plus mode2 is giving me these errors.
> > >
> > > [root@... mythtv]# mode2
> > > mode2: error opening /dev/lirc
> > > mode2: Device or resource busy
> > > [root@... mythtv]# mode2 --device=/dev/lirc0
> > > mode2: error opening /dev/lirc0
> > > mode2: Device or resource busy
> > >
> > > I am about ready to rebuild my frontend because I think there is some
> > > lirc garbage in there and I don't know where it is coming from.  I
> > > will be saving the .ko files (Martin's and Jim's).  Besides, what else
> > > is there to do on a Tuesday night?
> > >
> > >
> > > On Tue, 22 Mar 2005 17:40:43 -0600, Jim Oltman <cnliberal@...> wrote:
> > > > Do you use the usbirt driver?  I think I will wait until you get it
> > > > and have it working before I spend MORE cash.  haha
> > > >
> > > >
> > > > On Tue, 22 Mar 2005 14:27:27 -0800, Patrick Kelley <kelnic@...> wrote:
> > > > > ya, I was thinking like that, I just ordered the ira3 here:
> > > > > http://www.home-electro.com/products.php
> > > > > It will work with the plain lirc rpms.
> > > > > I'm still going to use the MCE remote with it.
> > > > >
> > > > >
> > > > > On Tue, 22 Mar 2005 16:07:21 -0600, Jim Oltman <cnliberal@...> wrote:
> > > > > > If I went to a 2.6.11 kernel, i would have to grab the RPM for
> > > > > > it...then reload my nvidia drivers...and lirc.  Maybe I will just
> > > > > > invest in an IR keyboard and mouse...haha
> > > > > >
> > > > > >
> > > > > > On Tue, 22 Mar 2005 09:21:03 +0100, Martin Blatter <mblatter@...> wrote:
> > > > > > > Patrick Kelley wrote:
> > > > > > >
> > > > > > > >I also have this problem, but with NForce3 mobo.  If I rmmod lirc_dev
> > > > > > > >and lirc_mceusb, then plug in the reciever, by the third time it
> > > > > > > >usually works.  You mentioned using Jarod's instructions.  Are you
> > > > > > > >also using FC3?
> > > > > > > >
> > > > > > > OHCI doesn't seem to be the cause, it works fine on Alan's system. This
> > > > > > > rather sounds like
> > > > > > > the bug in the Linux USB stack that caused problems with earlier kernels
> > > > > > > and the MCE
> > > > > > > transciever.
> > > > > > > How kosher are the FC3 kernels? Did you try a vanilla 2.6.10 or 2.6.11?
> > > > > > >
> > > > > > > regards
> > > > > > > martin
> > > > > > >
> > > > > > > -------------------------------------------------------
> > > > > > > SF email is sponsored by - The IT Product Guide
> > > > > > > Read honest & candid reviews on hundreds of IT Products from real users.
> > > > > > > Discover which products truly live up to the hype. Start reading now.
> > > > > > > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> > > > > > >
> > > > > >
> > > > > > -------------------------------------------------------
> > > > > > This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
> > > > > > Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
> > > > > > for the chance to win $25,000 and application distribution. Enter today at
> > > > > > http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click
> > > > > >
> > > > >
> > > >
> > >
> >
>

That's good news! I'm glad it worked out. Don't forget to put the 
lircd.conf.mceusb
provided with the driver in /etc/lircd.conf.

I've provided a lircrc file for mythfrontend to put in your .myth directory.
You can download it from:

http://blatter.com/mceusb/lircrc_MYTH_EXAMPLE

regards
martin

Jim Oltman wrote:

>Martin THANKS!  I reloaded my frontend and used the drivers you
>provided and I am getting a response from irrecord after every reboot.
> Still on kernel 2.6.10-1.770.  MythTV doesn't like it but that might
>be a lircrc problem.  Not sure.  Thanks to all for the many response
>emails!!  I hope this LARGE thread helps others with this remote.
>  
>

I was using my old Hauppauge remote instead of the mce remote.  The
reason is because I have a lircrc already built for the Hauppauge
remote (mythtv, xine, mplayer).  I think it might be running low on
batteries.  If batteries don't fix it, I will use your lircrc and
lircd.conf.  So after I get the lircd.conf and lircrc put in, this
should "Just Work" in Myth, correct?


On Thu, 24 Mar 2005 09:05:58 +0100, Martin Blatter <mblatter@...> wrote:
> That's good news! I'm glad it worked out. Don't forget to put the
> lircd.conf.mceusb
> provided with the driver in /etc/lircd.conf.
> 
> I've provided a lircrc file for mythfrontend to put in your .myth directory.
> You can download it from:
> 
> http://blatter.com/mceusb/lircrc_MYTH_EXAMPLE
> 
> regards
> martin
> 
> Jim Oltman wrote:
> 
> >Martin THANKS!  I reloaded my frontend and used the drivers you
> >provided and I am getting a response from irrecord after every reboot.
> > Still on kernel 2.6.10-1.770.  MythTV doesn't like it but that might
> >be a lircrc problem.  Not sure.  Thanks to all for the many response
> >emails!!  I hope this LARGE thread helps others with this remote.
> >
> >
>

Yeah....I lied.  Not working.  Joy.  I guess I will have to reboot 15
times.  Oh well.


On Thu, 24 Mar 2005 08:36:32 -0600, Jim Oltman <cnliberal@...> wrote:
> I was using my old Hauppauge remote instead of the mce remote.  The
> reason is because I have a lircrc already built for the Hauppauge
> remote (mythtv, xine, mplayer).  I think it might be running low on
> batteries.  If batteries don't fix it, I will use your lircrc and
> lircd.conf.  So after I get the lircd.conf and lircrc put in, this
> should "Just Work" in Myth, correct?
> 
> 
> On Thu, 24 Mar 2005 09:05:58 +0100, Martin Blatter <mblatter@...> wrote:
> > That's good news! I'm glad it worked out. Don't forget to put the
> > lircd.conf.mceusb
> > provided with the driver in /etc/lircd.conf.
> >
> > I've provided a lircrc file for mythfrontend to put in your .myth directory.
> > You can download it from:
> >
> > http://blatter.com/mceusb/lircrc_MYTH_EXAMPLE
> >
> > regards
> > martin
> >
> > Jim Oltman wrote:
> >
> > >Martin THANKS!  I reloaded my frontend and used the drivers you
> > >provided and I am getting a response from irrecord after every reboot.
> > > Still on kernel 2.6.10-1.770.  MythTV doesn't like it but that might
> > >be a lircrc problem.  Not sure.  Thanks to all for the many response
> > >emails!!  I hope this LARGE thread helps others with this remote.
> > >
> > >
> >
>

I have a question about this.
 
I purchased a MCE USB Recevier and Remote. I am more concerned with just
using the receiver as I have a Huappauge PVR-250 remote that I like.
 
I am running version 0.7.0 of lirc. I don't get any errors when I start up
lircd or when the machine boots and installs the modules for the mceusb
driver, but I get no response for my remote. I do have a the hauppauge
remote file setup.
 
Does the new version of the receiver not work at all with Lirc? Or is it
just the remote that doesn't work?
 
Thanks,
Robert Birch
 I was using my old Hauppauge remote instead of the mce remote.  The

 reason is because I have a lircrc already built for the Hauppauge

 remote (mythtv, xine, mplayer).  I think it might be running low on

 batteries.  If batteries don"t fix it, I will use your lircrc and

 lircd.conf.  So after I get the lircd.conf and lircrc put in, this

 should "Just Work" in Myth, correct?

 

 

 On Thu, 24 Mar 2005 09:05:58 +0100, Martin Blatter <mblatter@......> wrote:

 > That"s good news! I"m glad it worked out. Don"t forget to put the

 > lircd.conf.mceusb

 > provided with the driver in /etc/lircd.conf.

 > 

 > I"ve provided a lircrc file for mythfrontend to put in your .myth
directory.

 > You can download it from:

 > 

 > http://blatter.com/mceusb/lircrc_MYTH_EXAMPLE

 > 

 > regards

 > martin

 > 

 > Jim Oltman wrote:

 > 

 > >Martin THANKS!  I reloaded my frontend and used the drivers you

 > >provided and I am getting a response from irrecord after every reboot.

 > > Still on kernel 2.6.10-1.770.  MythTV doesn"t like it but that might

 > >be a lircrc problem.  Not sure.  Thanks to all for the many response

 > >emails!!  I hope this LARGE thread helps others with this remote.

 > >

 > >

 >

Martin Blatter wrote:
> Patrick Kelley wrote:
>> I also have this problem, but with NForce3 mobo.  If I rmmod lirc_dev
>> and lirc_mceusb, then plug in the reciever, by the third time it
>> usually works. 
>>
> OHCI doesn't seem to be the cause, it works fine on Alan's system. This 
> rather sounds like
> the bug in the Linux USB stack that caused problems with earlier kernels 
> and the MCE transciever.

As another data point I'm seeing much the same thing.

I'm using the mceusb.0.2-20050322.tar.bz2 package on a NForce3 based 
Athlon64 platform.  The rest of the lirc set if the ATrpms 0.7.0 
package, and the kernel is the 2.6.10-1.770_14.rhfc3.at (again ATrpms set).


> How kosher are the FC3 kernels? Did you try a vanilla 2.6.10 or 2.6.11?

FC3 kernels are relatively standard - there is quite a push to keep them 
close to mainline.  I've not tried a vanilla kernel because it requires 
a fair bit of other stuff to match the kernel rev (and I'm not 
overblessed with bandwidth here).

So far I have got the lirc_mceusb to work once, in several (8 or so) 
boot or module unload/replug attempts.  There appear to be 2 patterns - 
a non-working one where the callback reports a negative status, and a 
working one where the callback status is zero.  I've attached a trace of 
each (the first is the non-working - that continues up to me trying to 
use irrecord), the second is a working one which completes at the point 
where the callbacks appeared OK

Nonworking:-
   ohci_hcd 0000:00:02.0: wakeup
   usb 2-1: new full speed USB device using ohci_hcd and address 3
   lirc_dev: IR Remote Control driver registered, at major 61
   lirc_mceusb: USB remote driver for LIRC v0.2
   lirc_mceusb: Martin Blatter <martin_a_blatter@...>
   lirc_mceusb: debug mode enabled
   lirc_mceusb: usb probe called
   lirc_mceusb: acceptable outbound endpoint found
   lirc_mceusb: acceptable inbound endpoint found
   lirc_dev: lirc_register_plugin:sample_rate: 0
   lirc_mceusb[2]: Philips eHome Infrared Transceiver on usb2:2
   lirc_mceusb[2]: receive request called (size=0x10)
   lirc_mceusb[2]: receive request complete (res=0)
   lirc_mceusb[2]: receive request called (size=0x10)
   lirc_mceusb[2]: receive request complete (res=0)
   lirc_mceusb[2]: receive request called (size=0x5)
   lirc_mceusb[2]: receive request complete (res=0)
   lirc_mceusb[2]: receive request called (size=0x10)
   lirc_mceusb[2]: receive request complete (res=0)
   lirc_mceusb[2]: receive request called (size=0x2)
   lirc_mceusb[2]: receive request complete (res=0)
   lirc_mceusb[2]: receive request called (size=0x10)
   lirc_mceusb[2]: receive request complete (res=0)
   usbcore: registered new driver lirc_mceusb
   lirc_mceusb[2]: callback called (status=-110 len=0)
   last message repeated 4 times
   lirc_mceusb[2]: setup answer received 0 bytes
   lirc_mceusb[2]: set use inc
   lirc_mceusb[2]: set use dec


Working:
   ohci_hcd 0000:00:02.0: wakeup
   usb 2-1: new full speed USB device using ohci_hcd and address 4
   lirc_dev: IR Remote Control driver registered, at major 61
   lirc_mceusb: USB remote driver for LIRC v0.2
   lirc_mceusb: Martin Blatter <martin_a_blatter@...>
   lirc_mceusb: debug mode enabled
   lirc_mceusb: usb probe called
   lirc_mceusb: acceptable outbound endpoint found
   lirc_mceusb: acceptable inbound endpoint found
   lirc_dev: lirc_register_plugin:sample_rate: 0
   lirc_mceusb[4]: Philips eHome Infrared Transceiver on usb2:4
   lirc_mceusb[4]: receive request called (size=0x10)
   lirc_mceusb[4]: receive request complete (res=0)
   lirc_mceusb[4]: receive request called (size=0x10)
   lirc_mceusb[4]: receive request complete (res=0)
   lirc_mceusb[4]: receive request called (size=0x5)
   lirc_mceusb[4]: receive request complete (res=0)
   lirc_mceusb[4]: receive request called (size=0x10)
   lirc_mceusb[4]: receive request complete (res=0)
   lirc_mceusb[4]: receive request called (size=0x2)
   lirc_mceusb[4]: receive request complete (res=0)
   lirc_mceusb[4]: receive request called (size=0x10)
   lirc_mceusb[4]: receive request complete (res=0)
   usbcore: registered new driver lirc_mceusb
   lirc_mceusb[4]: callback called (status=0 len=5)
   lirc_mceusb[4]: data received 00 ff aa ff 0b  (length=5)
   lirc_mceusb[4]: callback called (status=-121 len=6)
   lirc_mceusb[4]: data received ff 0b 50 ff 1b 40  (length=6)
   lirc_mceusb[4]: callback called (status=0 len=2)
   lirc_mceusb[4]: data received ff 18  (length=2)
   lirc_mceusb[4]: callback called (status=-121 len=6)
   lirc_mceusb[4]: data received ff 18 00 00 00 00  (length=6)

Hope that helps a little

	Nigel.