Linux Infrared Remote Control

On Jul 29, 2009, at 3:40 PM, Lee Nugent wrote:

> I am running a fresh copy of Ubuntu Jaunty and installed LIRC via:
>
> sudo apt-get install LIRC
>
> which installed version 8.0.4a.  During the install, I chose  
> Soundgraph
> IR/LCD when prompted as I have the ffdc version shown when running:
>
> sudo lsusb
>
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 002: ID 15c2:ffdc SoundGraph Inc. iMON PAD Remote
> Controller
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> I ran IRW and used the iMON remote but no output was displayed.  I  
> then
> looked in /etc/lirc/lircd.conf and noticed that the file pointed to:
>
> Include "/usr/share/lirc/remotes/imon/lircd.conf.imon"
>
> This file had incorrect codes for my remote.  I then examined the
> lircd.conf.imon-pad file and it contained the correct codes so I  
> changed
> the include path in /etc/lirc/lircd.conf.  Now when I run IRW and  
> press
> buttons on the iMON remote I see the correct output.  The only thing
> that doesn't work is the soft directional pad in the middle of the
> remote, but that doesn't matter at this point as using the iMON remote
> is not my end game.

And its not the lirc project's fault, its ubuntu that did that  
incorrectly for you. If you wish to see that resolved, file a bug in  
launchpad.


> The end game is to use an MCE remote with the iMON receiver.  I have 4
> XBMC HTPC's around the house and they are all using an MCE USB dongle
> with an MCE remote and everyone in the house already knows how to use
> them.  So I ran IRRECORD and followed all the instructions using my  
> MCE
> remote.  Copied the new lircd.conf file to /etc/lirc and edited the
> hardware.conf file to look at /etc/lirc/lircd.conf for the config.
> Restarted LIRC and ran IRW.
>
> Big problems!
>
> For example, when I press Play, the output shows Stop, then Red, then
> Blue.  Basically, for every one button press I get anywhere from 1  
> to 3
> responses (all recognized as 00 so not repeat commands) where all are
> usually incorrect for the button pressed.  I have scoured the net
> looking for others that have this problem, but can't find a single  
> one.

Yeah, you're Doing It Wrong. :) The iMON devices do onboard decoding  
of IR signals, they can't be used with just any device. Current lirc  
cvs, the imon driver *does* support mce remotes though. You have to  
load the lirc_imon driver (built from cvs) with the parameter  
'ir_protocol=1', otherwise its in standard iMON IR mode, and you need  
to use the imon-mceusb lircd.conf, also in lirc cvs. What you're  
running now ONLY supports using remotes talking the iMON's IR protocol.

-- 
Jarod Wilson
jarod@...

OK, so I have another problem then.  Once I couldn't get 8.0.4a working
with my MCE remote, I decided to build LIRC from CVS following this
procedure:

sudo apt-get install cvs build-essential dialog libtool automake
autoconf

cvs -d:pserver:anonymous@... login
cvs -z8 -d:pserver:anonymous@... co
lirc
cd lirc
./autogen.sh
./setup.sh

Selected Soundgraph IR/LCD when prompted.

Make
Sudo make install
Sudo dpkg-reconfigure lirc-modules-source

But I get the following error:

Removing all DKMS Modules
Done.
Adding Module to DKMS build system
Doing initial module build

Error!  Build of lirc_imon.ko failed for: 2.6.28-13-generic (i686)
Consult the make.log in the build directory
/var/lib/dkms/lirc/0.8.4a/build/ for more information.
Installing initial module

Error! Could not locate lirc_atiusb.ko for module lirc in the DKMS tree.
You must run a dkms build for kernel 2.6.28-13-generic (i686) first.
Done.

The above is specifig to Ubuntu I guess so I just tried:

Sudo modprobe lirc_imon

But then when I try to run IRW it says it can't be found.

I am missing something very easy apparently.


Thanks,
Lee



-----Original Message-----
From: Jarod Wilson [mailto:jarod@...] 
Sent: Wednesday, July 29, 2009 3:20 PM
To: Nugent, Lee
Cc: lirc-list@...
Subject: Re: MCE Remote and iMON Reciever

On Jul 29, 2009, at 3:40 PM, Lee Nugent wrote:

> I am running a fresh copy of Ubuntu Jaunty and installed LIRC via:
>
> sudo apt-get install LIRC
>
> which installed version 8.0.4a.  During the install, I chose  
> Soundgraph
> IR/LCD when prompted as I have the ffdc version shown when running:
>
> sudo lsusb
>
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 002: ID 15c2:ffdc SoundGraph Inc. iMON PAD Remote
> Controller
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> I ran IRW and used the iMON remote but no output was displayed.  I  
> then
> looked in /etc/lirc/lircd.conf and noticed that the file pointed to:
>
> Include "/usr/share/lirc/remotes/imon/lircd.conf.imon"
>
> This file had incorrect codes for my remote.  I then examined the
> lircd.conf.imon-pad file and it contained the correct codes so I  
> changed
> the include path in /etc/lirc/lircd.conf.  Now when I run IRW and  
> press
> buttons on the iMON remote I see the correct output.  The only thing
> that doesn't work is the soft directional pad in the middle of the
> remote, but that doesn't matter at this point as using the iMON remote
> is not my end game.

And its not the lirc project's fault, its ubuntu that did that  
incorrectly for you. If you wish to see that resolved, file a bug in  
launchpad.


> The end game is to use an MCE remote with the iMON receiver.  I have 4
> XBMC HTPC's around the house and they are all using an MCE USB dongle
> with an MCE remote and everyone in the house already knows how to use
> them.  So I ran IRRECORD and followed all the instructions using my  
> MCE
> remote.  Copied the new lircd.conf file to /etc/lirc and edited the
> hardware.conf file to look at /etc/lirc/lircd.conf for the config.
> Restarted LIRC and ran IRW.
>
> Big problems!
>
> For example, when I press Play, the output shows Stop, then Red, then
> Blue.  Basically, for every one button press I get anywhere from 1  
> to 3
> responses (all recognized as 00 so not repeat commands) where all are
> usually incorrect for the button pressed.  I have scoured the net
> looking for others that have this problem, but can't find a single  
> one.

Yeah, you're Doing It Wrong. :) The iMON devices do onboard decoding  
of IR signals, they can't be used with just any device. Current lirc  
cvs, the imon driver *does* support mce remotes though. You have to  
load the lirc_imon driver (built from cvs) with the parameter  
'ir_protocol=1', otherwise its in standard iMON IR mode, and you need  
to use the imon-mceusb lircd.conf, also in lirc cvs. What you're  
running now ONLY supports using remotes talking the iMON's IR protocol.

-- 
Jarod Wilson
jarod@...

On 07/29/2009 05:00 PM, Lee Nugent wrote:
> OK, so I have another problem then.  Once I couldn't get 8.0.4a working
> with my MCE remote, I decided to build LIRC from CVS following this
> procedure:
>
> sudo apt-get install cvs build-essential dialog libtool automake
> autoconf
>
> cvs -d:pserver:anonymous@... login
> cvs -z8 -d:pserver:anonymous@... co
> lirc
> cd lirc
> ./autogen.sh
> ./setup.sh
>
> Selected Soundgraph IR/LCD when prompted.
>
> Make
> Sudo make install
> Sudo dpkg-reconfigure lirc-modules-source
>
> But I get the following error:
>
> Removing all DKMS Modules
> Done.

Having both the dkms builds *and* cvs builds at the same time is bound 
to lead to problems. I suspect your "removing all dkms modules" bit 
there may have undone the 'sudo make install' you did from cvs earlier, 
as if I recall correctly, the ubuntu dkms stuff puts the modules in the 
same place lirc cvs's make install does...


> Adding Module to DKMS build system
> Doing initial module build
>
> Error!  Build of lirc_imon.ko failed for: 2.6.28-13-generic (i686)
> Consult the make.log in the build directory
> /var/lib/dkms/lirc/0.8.4a/build/ for more information.
> Installing initial module
>
> Error! Could not locate lirc_atiusb.ko for module lirc in the DKMS tree.
> You must run a dkms build for kernel 2.6.28-13-generic (i686) first.
> Done.
>
> The above is specifig to Ubuntu I guess so I just tried:
>
> Sudo modprobe lirc_imon
>
> But then when I try to run IRW it says it can't be found.
>
> I am missing something very easy apparently.

Get rid of the dkms stuff for now, remove lirc-module-sources, and only 
work with lirc cvs.


> -----Original Message-----
> From: Jarod Wilson [mailto:jarod@...]
> Sent: Wednesday, July 29, 2009 3:20 PM
> To: Nugent, Lee
> Cc: lirc-list@...
> Subject: Re: MCE Remote and iMON Reciever
>
> On Jul 29, 2009, at 3:40 PM, Lee Nugent wrote:
>
>> I am running a fresh copy of Ubuntu Jaunty and installed LIRC via:
>>
>> sudo apt-get install LIRC
>>
>> which installed version 8.0.4a.  During the install, I chose
>> Soundgraph
>> IR/LCD when prompted as I have the ffdc version shown when running:
>>
>> sudo lsusb
>>
>> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 004 Device 002: ID 15c2:ffdc SoundGraph Inc. iMON PAD Remote
>> Controller
>> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>
>> I ran IRW and used the iMON remote but no output was displayed.  I
>> then
>> looked in /etc/lirc/lircd.conf and noticed that the file pointed to:
>>
>> Include "/usr/share/lirc/remotes/imon/lircd.conf.imon"
>>
>> This file had incorrect codes for my remote.  I then examined the
>> lircd.conf.imon-pad file and it contained the correct codes so I
>> changed
>> the include path in /etc/lirc/lircd.conf.  Now when I run IRW and
>> press
>> buttons on the iMON remote I see the correct output.  The only thing
>> that doesn't work is the soft directional pad in the middle of the
>> remote, but that doesn't matter at this point as using the iMON remote
>> is not my end game.
>
> And its not the lirc project's fault, its ubuntu that did that
> incorrectly for you. If you wish to see that resolved, file a bug in
> launchpad.
>
>
>> The end game is to use an MCE remote with the iMON receiver.  I have 4
>> XBMC HTPC's around the house and they are all using an MCE USB dongle
>> with an MCE remote and everyone in the house already knows how to use
>> them.  So I ran IRRECORD and followed all the instructions using my
>> MCE
>> remote.  Copied the new lircd.conf file to /etc/lirc and edited the
>> hardware.conf file to look at /etc/lirc/lircd.conf for the config.
>> Restarted LIRC and ran IRW.
>>
>> Big problems!
>>
>> For example, when I press Play, the output shows Stop, then Red, then
>> Blue.  Basically, for every one button press I get anywhere from 1
>> to 3
>> responses (all recognized as 00 so not repeat commands) where all are
>> usually incorrect for the button pressed.  I have scoured the net
>> looking for others that have this problem, but can't find a single
>> one.
>
> Yeah, you're Doing It Wrong. :) The iMON devices do onboard decoding
> of IR signals, they can't be used with just any device. Current lirc
> cvs, the imon driver *does* support mce remotes though. You have to
> load the lirc_imon driver (built from cvs) with the parameter
> 'ir_protocol=1', otherwise its in standard iMON IR mode, and you need
> to use the imon-mceusb lircd.conf, also in lirc cvs. What you're
> running now ONLY supports using remotes talking the iMON's IR protocol.
>

OK, so I re-imaged by installation (image taken right before any LIRC stuff) and did the pure CVS approach.  After sudo make install, I run:
 
"modprobe lirc_imon"
 
I then examine the /etc/lirc/lircd.conf file and it is for the iMON remote, so I replace it with lircd.conf.imon-mceusb and call it lircd.conf.  I then see that there is no hardware.conf file so I create one and point lircd to the new conf file I created above.  At this point I don't think that lircd is actually running as I don't see any lirc* when running:
 
"ps -a"
 
I go to /usr/local/sbin and run:
 
"sudo lircd --device=/dev/lirc0" 
 
but it errors out saying:
 
"lircd: can't open or create /var/run/lirc/lircd.pid
lircd: No such file or directory"

Plus I can't run IRW from /usr/local/bin as it errors out with similar output.  I'm guessing I need to get lircd running somehow, but I am not sure.  In /dev/ I only have lirc0, shouldn't I also need lirc?  Also you said that I need to add the parameter ir_protocol=1 to the imon driver, so how do I do that?
 
Sorry for the questions, but this has been frustrating me for about a week now.  It doesn't help that I am re-aquainting myself with Linux after 10+ years of Windows.
 
 
 
Thanks,
Lee

________________________________

From: Jarod Wilson [mailto:jarod@...]
Sent: Wed 7/29/2009 9:51 PM
To: Nugent, Lee
Cc: lirc-list@...
Subject: Re: MCE Remote and iMON Reciever



On 07/29/2009 05:00 PM, Lee Nugent wrote:
> OK, so I have another problem then.  Once I couldn't get 8.0.4a working
> with my MCE remote, I decided to build LIRC from CVS following this
> procedure:
>
> sudo apt-get install cvs build-essential dialog libtool automake
> autoconf
>
> cvs -d:pserver:anonymous@... login
> cvs -z8 -d:pserver:anonymous@... co
> lirc
> cd lirc
> ./autogen.sh
> ./setup.sh
>
> Selected Soundgraph IR/LCD when prompted.
>
> Make
> Sudo make install
> Sudo dpkg-reconfigure lirc-modules-source
>
> But I get the following error:
>
> Removing all DKMS Modules
> Done.

Having both the dkms builds *and* cvs builds at the same time is bound
to lead to problems. I suspect your "removing all dkms modules" bit
there may have undone the 'sudo make install' you did from cvs earlier,
as if I recall correctly, the ubuntu dkms stuff puts the modules in the
same place lirc cvs's make install does...


> Adding Module to DKMS build system
> Doing initial module build
>
> Error!  Build of lirc_imon.ko failed for: 2.6.28-13-generic (i686)
> Consult the make.log in the build directory
> /var/lib/dkms/lirc/0.8.4a/build/ for more information.
> Installing initial module
>
> Error! Could not locate lirc_atiusb.ko for module lirc in the DKMS tree.
> You must run a dkms build for kernel 2.6.28-13-generic (i686) first.
> Done.
>
> The above is specifig to Ubuntu I guess so I just tried:
>
> Sudo modprobe lirc_imon
>
> But then when I try to run IRW it says it can't be found.
>
> I am missing something very easy apparently.

Get rid of the dkms stuff for now, remove lirc-module-sources, and only
work with lirc cvs.


> -----Original Message-----
> From: Jarod Wilson [mailto:jarod@...]
> Sent: Wednesday, July 29, 2009 3:20 PM
> To: Nugent, Lee
> Cc: lirc-list@...
> Subject: Re: MCE Remote and iMON Reciever
>
> On Jul 29, 2009, at 3:40 PM, Lee Nugent wrote:
>
>> I am running a fresh copy of Ubuntu Jaunty and installed LIRC via:
>>
>> sudo apt-get install LIRC
>>
>> which installed version 8.0.4a.  During the install, I chose
>> Soundgraph
>> IR/LCD when prompted as I have the ffdc version shown when running:
>>
>> sudo lsusb
>>
>> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 004 Device 002: ID 15c2:ffdc SoundGraph Inc. iMON PAD Remote
>> Controller
>> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>
>> I ran IRW and used the iMON remote but no output was displayed.  I
>> then
>> looked in /etc/lirc/lircd.conf and noticed that the file pointed to:
>>
>> Include "/usr/share/lirc/remotes/imon/lircd.conf.imon"
>>
>> This file had incorrect codes for my remote.  I then examined the
>> lircd.conf.imon-pad file and it contained the correct codes so I
>> changed
>> the include path in /etc/lirc/lircd.conf.  Now when I run IRW and
>> press
>> buttons on the iMON remote I see the correct output.  The only thing
>> that doesn't work is the soft directional pad in the middle of the
>> remote, but that doesn't matter at this point as using the iMON remote
>> is not my end game.
>
> And its not the lirc project's fault, its ubuntu that did that
> incorrectly for you. If you wish to see that resolved, file a bug in
> launchpad.
>
>
>> The end game is to use an MCE remote with the iMON receiver.  I have 4
>> XBMC HTPC's around the house and they are all using an MCE USB dongle
>> with an MCE remote and everyone in the house already knows how to use
>> them.  So I ran IRRECORD and followed all the instructions using my
>> MCE
>> remote.  Copied the new lircd.conf file to /etc/lirc and edited the
>> hardware.conf file to look at /etc/lirc/lircd.conf for the config.
>> Restarted LIRC and ran IRW.
>>
>> Big problems!
>>
>> For example, when I press Play, the output shows Stop, then Red, then
>> Blue.  Basically, for every one button press I get anywhere from 1
>> to 3
>> responses (all recognized as 00 so not repeat commands) where all are
>> usually incorrect for the button pressed.  I have scoured the net
>> looking for others that have this problem, but can't find a single
>> one.
>
> Yeah, you're Doing It Wrong. :) The iMON devices do onboard decoding
> of IR signals, they can't be used with just any device. Current lirc
> cvs, the imon driver *does* support mce remotes though. You have to
> load the lirc_imon driver (built from cvs) with the parameter
> 'ir_protocol=1', otherwise its in standard iMON IR mode, and you need
> to use the imon-mceusb lircd.conf, also in lirc cvs. What you're
> running now ONLY supports using remotes talking the iMON's IR protocol.
>

On Jul 30, 2009, at 12:00 AM, Lee Nugent wrote:

> OK, so I re-imaged by installation (image taken right before any  
> LIRC stuff) and did the pure CVS approach.  After sudo make install,  
> I run:
>
> "modprobe lirc_imon"
>
> I then examine the /etc/lirc/lircd.conf file and it is for the iMON  
> remote, so I replace it with lircd.conf.imon-mceusb and call it  
> lircd.conf.  I then see that there is no hardware.conf file so I  
> create one and point lircd to the new conf file I created above.  At  
> this point I don't think that lircd is actually running as I don't  
> see any lirc* when running:
>
> "ps -a"
>
> I go to /usr/local/sbin and run:
>
> "sudo lircd --device=/dev/lirc0"
>
> but it errors out saying:
>
> "lircd: can't open or create /var/run/lirc/lircd.pid
> lircd: No such file or directory"

$ sudo mkdir /var/run/lirc

The pid file needs to go in that directory with current cvs, used to  
be in just /var/run, iirc, so you likely don't have that directory yet.

> Plus I can't run IRW from /usr/local/bin as it errors out with  
> similar output.  I'm guessing I need to get lircd running somehow,  
> but I am not sure.  In /dev/ I only have lirc0, shouldn't I also  
> need lirc?

I think you mean the lircd socket file. With current cvs, its /var/run/ 
lirc/lircd now. Should work after the above directory creation.

> Also you said that I need to add the parameter ir_protocol=1 to the  
> imon driver, so how do I do that?

create a file /etc/modprobe.d/imon.conf, and add to it 'options  
lirc_imon ir_protocol=1'. Reload lirc_imon, and you should be all set.

-- 
Jarod Wilson
jarod@...

Jarod,

I really appreciate all the help as I feel I am so close.

I did:

Sudo mkdir /var/run/lirc
Sudo nano /etc/modprobe.d/imon.conf
	inserted: options lirc_imon ir_protocol=1
sudo reboot

Upon reboot, I noticed two things.  The lirc directory in /var/run was
no longer there.  So I had to recreate the lirc directory.  Also, I ran:

Sudo mount -t usbfs none /proc/bus/usb
Sudo cat /proc/bus/usb/devices

And it showed that my imon device had no driver loaded, so I did:

Sudo modprobe lirc_imon

But this time it gave me an error (it didn't yesterday):

FATAL: Error inserting lirc_imon
(/lib/modules/2.6.28-13-generic/kernel/ubuntu/lirc/lirc_imon/lirc_imon.k
o): Operation not permitted

I did some snooping and noticed that there are two locations with
/lib/modules/2.6.28-13-generic that contain the lirc_imon.ko file.  The
first is:

/lib/modules/2.6.28-13-generic/kernel/ubuntu/lirc/lirc_imon/lirc_imon.ko

And the next is:

/lib/modules/2.6.28-13-generic/misc/lirc_imon.ko

The latter directory only contains the lirc_dev.ko and lirc_imon.ko
files.  I'm guessing that the above error has to do with this.  Should I
delete the lirc_imon.ko file in
/lib/modules/2.6...generic/kernel/ubuntu/lirc/lirc_imon and create a sym
link to the lirc_imon.ko file in /lib/modules/2...generic/misc?



Thanks,
Lee 


-----Original Message-----
From: Jarod Wilson [mailto:jarod@...] 
Sent: Thursday, July 30, 2009 7:57 AM
To: Nugent, Lee
Cc: lirc-list@...
Subject: Re: MCE Remote and iMON Reciever


On Jul 30, 2009, at 12:00 AM, Lee Nugent wrote:

> OK, so I re-imaged by installation (image taken right before any  
> LIRC stuff) and did the pure CVS approach.  After sudo make install,  
> I run:
>
> "modprobe lirc_imon"
>
> I then examine the /etc/lirc/lircd.conf file and it is for the iMON  
> remote, so I replace it with lircd.conf.imon-mceusb and call it  
> lircd.conf.  I then see that there is no hardware.conf file so I  
> create one and point lircd to the new conf file I created above.  At  
> this point I don't think that lircd is actually running as I don't  
> see any lirc* when running:
>
> "ps -a"
>
> I go to /usr/local/sbin and run:
>
> "sudo lircd --device=/dev/lirc0"
>
> but it errors out saying:
>
> "lircd: can't open or create /var/run/lirc/lircd.pid
> lircd: No such file or directory"

$ sudo mkdir /var/run/lirc

The pid file needs to go in that directory with current cvs, used to  
be in just /var/run, iirc, so you likely don't have that directory yet.

> Plus I can't run IRW from /usr/local/bin as it errors out with  
> similar output.  I'm guessing I need to get lircd running somehow,  
> but I am not sure.  In /dev/ I only have lirc0, shouldn't I also  
> need lirc?

I think you mean the lircd socket file. With current cvs, its /var/run/ 
lirc/lircd now. Should work after the above directory creation.

> Also you said that I need to add the parameter ir_protocol=1 to the  
> imon driver, so how do I do that?

create a file /etc/modprobe.d/imon.conf, and add to it 'options  
lirc_imon ir_protocol=1'. Reload lirc_imon, and you should be all set.

-- 
Jarod Wilson
jarod@...

On Jul 30, 2009, at 11:39 AM, Lee Nugent wrote:

> Jarod,
>
> I really appreciate all the help as I feel I am so close.

Yep, inching closer... ;)


> I did:
>
> Sudo mkdir /var/run/lirc
> Sudo nano /etc/modprobe.d/imon.conf
> 	inserted: options lirc_imon ir_protocol=1
> sudo reboot
>
> Upon reboot, I noticed two things.  The lirc directory in /var/run was
> no longer there.  So I had to recreate the lirc directory.

?!? That's odd...

> Also, I ran:
>
> Sudo mount -t usbfs none /proc/bus/usb
> Sudo cat /proc/bus/usb/devices
>
> And it showed that my imon device had no driver loaded, so I did:
>
> Sudo modprobe lirc_imon
>
> But this time it gave me an error (it didn't yesterday):
>
> FATAL: Error inserting lirc_imon
> (/lib/modules/2.6.28-13-generic/kernel/ubuntu/lirc/lirc_imon/ 
> lirc_imon.k
> o): Operation not permitted

Okay, yeah, that's yet *another* lirc_imon that needs to go away...


> I did some snooping and noticed that there are two locations with
> /lib/modules/2.6.28-13-generic that contain the lirc_imon.ko file.   
> The
> first is:
>
> /lib/modules/2.6.28-13-generic/kernel/ubuntu/lirc/lirc_imon/ 
> lirc_imon.ko
>
> And the next is:
>
> /lib/modules/2.6.28-13-generic/misc/lirc_imon.ko

This is the right one. I'd forgot about the fact ubuntu has both lirc  
drivers provided with its kernel package *and* the dkms ones... (I  
don't use ubuntu much at all myself, but did throw it on a spare  
machine to get a better idea of the differences from my usual distro)

> The latter directory only contains the lirc_dev.ko and lirc_imon.ko
> files.  I'm guessing that the above error has to do with this.   
> Should I
> delete the lirc_imon.ko file in
> /lib/modules/2.6...generic/kernel/ubuntu/lirc/lirc_imon and create a  
> sym
> link to the lirc_imon.ko file in /lib/modules/2...generic/misc?

It *should* be enough to simply run 'sudo depmod -ae' to get the  
correct module to take precedence here. If not, I'd just nuke the  
entire /lib/modules/2.6.28-13-generic/kernel/ubuntu/lirc directory  
from orbit, run depmod one more time, and be happy. :)

-- 
Jarod Wilson
jarod@...

OK.

Nuked the /lib/modules/2...generic/kernel/ubuntu/lirc directory and ran:
Sudo depmod -ae

With no issues (yeah).  But then I then ran:

Sudo modprobe lirc_imon

And got this error:

FATAL: Error inserting lirc_imon
(/lib/modules/2.6.28-13-generic/misc/lirc_imon.ko): Unknown symbol in
module, or unknown parameter (see dmesg)

And dmesg show this:

[   38.499197] lirc_imon: Unknown parameter `ir_protocol'
[  207.151724] lirc_imon: Unknown parameter `ir_protocol'
[ 2648.357562] lirc_imon: Unknown symbol lirc_unregister_driver
[ 2648.358115] lirc_imon: Unknown symbol lirc_register_driver
[ 2738.425026] lirc_imon: Unknown symbol lirc_unregister_driver
[ 2738.425578] lirc_imon: Unknown symbol lirc_register_driver
[ 2953.572735] lirc_imon: Unknown symbol lirc_unregister_driver
[ 2953.573289] lirc_imon: Unknown symbol lirc_register_driver
[ 3105.736606] lirc_imon: Unknown symbol lirc_unregister_driver
[ 3105.737158] lirc_imon: Unknown symbol lirc_register_driver


Well it looks like my imon.conf file in /etc/modprobe.d is wrong.  This
is exactly what my conf file has in it:

options lirc_imon ir_protocol=1

Do I need quotes somewhere, am I missing something?  Or is my driver not
correct?




Thanks,
Lee



-----Original Message-----
From: Jarod Wilson [mailto:jarod@...] 
Sent: Thursday, July 30, 2009 10:48 AM
To: Nugent, Lee
Cc: lirc-list@...
Subject: Re: MCE Remote and iMON Reciever

On Jul 30, 2009, at 11:39 AM, Lee Nugent wrote:

> Jarod,
>
> I really appreciate all the help as I feel I am so close.

Yep, inching closer... ;)


> I did:
>
> Sudo mkdir /var/run/lirc
> Sudo nano /etc/modprobe.d/imon.conf
> 	inserted: options lirc_imon ir_protocol=1
> sudo reboot
>
> Upon reboot, I noticed two things.  The lirc directory in /var/run was
> no longer there.  So I had to recreate the lirc directory.

?!? That's odd...

> Also, I ran:
>
> Sudo mount -t usbfs none /proc/bus/usb
> Sudo cat /proc/bus/usb/devices
>
> And it showed that my imon device had no driver loaded, so I did:
>
> Sudo modprobe lirc_imon
>
> But this time it gave me an error (it didn't yesterday):
>
> FATAL: Error inserting lirc_imon
> (/lib/modules/2.6.28-13-generic/kernel/ubuntu/lirc/lirc_imon/ 
> lirc_imon.k
> o): Operation not permitted

Okay, yeah, that's yet *another* lirc_imon that needs to go away...


> I did some snooping and noticed that there are two locations with
> /lib/modules/2.6.28-13-generic that contain the lirc_imon.ko file.   
> The
> first is:
>
> /lib/modules/2.6.28-13-generic/kernel/ubuntu/lirc/lirc_imon/ 
> lirc_imon.ko
>
> And the next is:
>
> /lib/modules/2.6.28-13-generic/misc/lirc_imon.ko

This is the right one. I'd forgot about the fact ubuntu has both lirc  
drivers provided with its kernel package *and* the dkms ones... (I  
don't use ubuntu much at all myself, but did throw it on a spare  
machine to get a better idea of the differences from my usual distro)

> The latter directory only contains the lirc_dev.ko and lirc_imon.ko
> files.  I'm guessing that the above error has to do with this.   
> Should I
> delete the lirc_imon.ko file in
> /lib/modules/2.6...generic/kernel/ubuntu/lirc/lirc_imon and create a  
> sym
> link to the lirc_imon.ko file in /lib/modules/2...generic/misc?

It *should* be enough to simply run 'sudo depmod -ae' to get the  
correct module to take precedence here. If not, I'd just nuke the  
entire /lib/modules/2.6.28-13-generic/kernel/ubuntu/lirc directory  
from orbit, run depmod one more time, and be happy. :)

-- 
Jarod Wilson
jarod@...

On Thursday 30 July 2009 12:32:01 Lee Nugent wrote:
> OK.
> 
> Nuked the /lib/modules/2...generic/kernel/ubuntu/lirc directory and ran:
> Sudo depmod -ae
> 
> With no issues (yeah).  But then I then ran:
> 
> Sudo modprobe lirc_imon
> 
> And got this error:
> 
> FATAL: Error inserting lirc_imon
> (/lib/modules/2.6.28-13-generic/misc/lirc_imon.ko): Unknown symbol in
> module, or unknown parameter (see dmesg)
> 
> And dmesg show this:
> 
> [   38.499197] lirc_imon: Unknown parameter `ir_protocol'
> [  207.151724] lirc_imon: Unknown parameter `ir_protocol'
> [ 2648.357562] lirc_imon: Unknown symbol lirc_unregister_driver
> [ 2648.358115] lirc_imon: Unknown symbol lirc_register_driver
> [ 2738.425026] lirc_imon: Unknown symbol lirc_unregister_driver
> [ 2738.425578] lirc_imon: Unknown symbol lirc_register_driver
> [ 2953.572735] lirc_imon: Unknown symbol lirc_unregister_driver
> [ 2953.573289] lirc_imon: Unknown symbol lirc_register_driver
> [ 3105.736606] lirc_imon: Unknown symbol lirc_unregister_driver
> [ 3105.737158] lirc_imon: Unknown symbol lirc_register_driver
> 
> 
> Well it looks like my imon.conf file in /etc/modprobe.d is wrong.  This
> is exactly what my conf file has in it:
> 
> options lirc_imon ir_protocol=1
> 
> Do I need quotes somewhere, am I missing something?  Or is my driver not
> correct?

Somehow or another, you're still not loading the right lirc_imon there.

The param is definitely ir_protocol, see modinfo lirc_imon output from
my box:

$ modinfo lirc_imon
filename:       /lib/modules/2.6.31-0.112.rc4.git3.fc12.x86_64/kernel/drivers/input/lirc/lirc_imon.ko
license:        GPL
version:        0.6
description:    Driver for SoundGraph iMON MultiMedia IR/Display
...
parm:           debug:Debug messages: 0=no, 1=yes(default: no) (int)
parm:           display_type:Type of attached display. 0=autodetect, 1=vfd, 2=lcd, 3=vga, 4=none (default: autodetect) (int)
parm:           ir_protocol:Which IR protocol to use. 0=native iMON, 1=Windows Media Center Ed. (RC-6) (default: native iMON) (int)
parm:           nomouse:Disable mouse input device mode when IR device is open. 0=don't disable, 1=disable. (default: don't disable) (int)


-- 
Jarod Wilson
jarod@...

Jarrod,

I am so close I can taste it!

I re-imaged again but this time I used:

"sudo locate -i lirc"

And deleted everything associated with lirc from the system and then
reboot.

I then did the CVS thing, then I ran modprobe:

"sudo modprobe lirc_imon"

With no errors.  Then made sure that lirc_imon driver was loaded for my
ffdc device:

"sudo cat /proc/bus/usb/devices"

And it was.  Then I ran:

"sudo lircd --device=/dev/lirc0"

And it started no problem.  I checked to make sure I was loading the
correct lirc_imon using:

"sudo modprobe lirc_imon"

And I am getting the exact output you did for your command.

I examined the /etc/lirc/lircd.conf and found that it was setup for the
iMON remote so I copied the imon-mceusb conf file to /etc/lirc as such:

"sudo mv lircd.conf.imon-mceusb /etc/lirc/lircd.conf"

Then realized I didn't have a /etc/lirc/hardware.conf so I created one
with the following contents:

# /etc/lirc/hardware.conf
#
#Chosen Remote Control
REMOTE="Soundgraph iMON IR/LCD"
REMOTE_MODULES="lirc_dev lirc_imon"
REMOTE_DRIVER=""
REMOTE_DEVICE="/dev/lirc0"
REMOTE_LIRCD_CONF="/etc/lirc/lircd.conf"
REMOTE_LIRCD_ARGS=""

#Chosen IR Transmitter
TRANSMITTER="None"
TRANSMITTER_MODULES=""
TRANSMITTER_DRIVER=""
TRANSMITTER_DEVICE=""
TRANSMITTER_LIRCD_CONF=""
TRANSMITTER_LIRCD_ARGS=""

#Enable lircd
START_LIRCD="true"

#Don't start lircmd even if there seems to be a good config file
#START_LIRCMD="false"

#Try to load appropriate kernel modules
LOAD_MODULES="true"

# Default configuration files for your hardware if any
LIRCMD_CONF=""

#Forcing noninteractive reconfiguration
#If lirc is to be reconfigured by an external application
#that doesn't have a debconf frontend available, the noninteractive
#frontend can be invoked and set to parse REMOTE and TRANSMITTER
#It will then populate all other variables without any user input
#If you would like to configure lirc via standard methods, be sure
#to leave this set to "false"
FORCE_NONINTERACTIVE_RECONFIGURATION="false"
START_LIRCMD=""
START_LIRCMD=""

I did another reboot and ran IRW.  Again no output from IRW using this
remote:

http://www.newegg.com/Product/Product.aspx?Item=N82E16880121003

I examined the lircd.conf file and commented out all Antec stuff at the
bottom, reboot (b/c I don't know how to restart LIRC at this point) and
tried again.  IRW produced no output again.  So I tried doing IRRECORD
again.  I created about 10 buttons just as a test, saved it and moved it
to the /etc/lirc directory.  Rebooted again and ran IRW, this time I was
getting output from IRW, but it was as before.  I press the power button
and I would get KEY_ZOOM instead of KEY_POWER.  I would press zoom and
would get KEY_AUDIO.  Basically IRRECORD is having the same behavior as
on 0.8.4a.

So, is my hardware.conf file correct or has that syntax changed with the
new version?

BTW - I have the options lirc_imon ir_protocol=1 setting in imon.conf.

Any other suggestions?




Thanks,
Lee

-----Original Message-----
From: Jarod Wilson [mailto:jarod@...] 
Sent: Thursday, July 30, 2009 8:48 PM
To: Nugent, Lee
Cc: lirc-list@...
Subject: Re: MCE Remote and iMON Reciever

On Thursday 30 July 2009 12:32:01 Lee Nugent wrote:
> OK.
> 
> Nuked the /lib/modules/2...generic/kernel/ubuntu/lirc directory and
ran:
> Sudo depmod -ae
> 
> With no issues (yeah).  But then I then ran:
> 
> Sudo modprobe lirc_imon
> 
> And got this error:
> 
> FATAL: Error inserting lirc_imon
> (/lib/modules/2.6.28-13-generic/misc/lirc_imon.ko): Unknown symbol in
> module, or unknown parameter (see dmesg)
> 
> And dmesg show this:
> 
> [   38.499197] lirc_imon: Unknown parameter `ir_protocol'
> [  207.151724] lirc_imon: Unknown parameter `ir_protocol'
> [ 2648.357562] lirc_imon: Unknown symbol lirc_unregister_driver
> [ 2648.358115] lirc_imon: Unknown symbol lirc_register_driver
> [ 2738.425026] lirc_imon: Unknown symbol lirc_unregister_driver
> [ 2738.425578] lirc_imon: Unknown symbol lirc_register_driver
> [ 2953.572735] lirc_imon: Unknown symbol lirc_unregister_driver
> [ 2953.573289] lirc_imon: Unknown symbol lirc_register_driver
> [ 3105.736606] lirc_imon: Unknown symbol lirc_unregister_driver
> [ 3105.737158] lirc_imon: Unknown symbol lirc_register_driver
> 
> 
> Well it looks like my imon.conf file in /etc/modprobe.d is wrong.
This
> is exactly what my conf file has in it:
> 
> options lirc_imon ir_protocol=1
> 
> Do I need quotes somewhere, am I missing something?  Or is my driver
not
> correct?

Somehow or another, you're still not loading the right lirc_imon there.

The param is definitely ir_protocol, see modinfo lirc_imon output from
my box:

$ modinfo lirc_imon
filename:
/lib/modules/2.6.31-0.112.rc4.git3.fc12.x86_64/kernel/drivers/input/lirc
/lirc_imon.ko
license:        GPL
version:        0.6
description:    Driver for SoundGraph iMON MultiMedia IR/Display
...
parm:           debug:Debug messages: 0=no, 1=yes(default: no) (int)
parm:           display_type:Type of attached display. 0=autodetect,
1=vfd, 2=lcd, 3=vga, 4=none (default: autodetect) (int)
parm:           ir_protocol:Which IR protocol to use. 0=native iMON,
1=Windows Media Center Ed. (RC-6) (default: native iMON) (int)
parm:           nomouse:Disable mouse input device mode when IR device
is open. 0=don't disable, 1=disable. (default: don't disable) (int)


-- 
Jarod Wilson
jarod@...

Just thought I'd chime in as another Ubuntu user:  Note that when Ubuntu
auto-updates your kernel at some point in the future (Update Manager),
all this work will be undone and you'll have to make these changes to
/lib/modules/... again.  This seems to happen about once a month.

Jarod, what's your distro of choice?  I like a lot of Ubuntu, but there
sure are some painful things :)

I've been toying with the idea of creating an updated set of lirc 0.8.6
packages for Ubuntu that fix some of these issues and posting it in a
PPA: https://launchpad.net/ubuntu/+ppas

I did a bunch of the work required against a CVS version a while back,
but a lot has changed since then...

Jeremy


Jarod Wilson wrote the following on 7/30/2009 9:48 PM:
> On Thursday 30 July 2009 12:32:01 Lee Nugent wrote:
>   
>> OK.
>>
>> Nuked the /lib/modules/2...generic/kernel/ubuntu/lirc directory and ran:
>> Sudo depmod -ae
>>
>> With no issues (yeah).  But then I then ran:
>>
>> Sudo modprobe lirc_imon
>>
>> And got this error:
>>
>> FATAL: Error inserting lirc_imon
>> (/lib/modules/2.6.28-13-generic/misc/lirc_imon.ko): Unknown symbol in
>> module, or unknown parameter (see dmesg)
>>
>> And dmesg show this:
>>
>> [   38.499197] lirc_imon: Unknown parameter `ir_protocol'
>> [  207.151724] lirc_imon: Unknown parameter `ir_protocol'
>> [ 2648.357562] lirc_imon: Unknown symbol lirc_unregister_driver
>> [ 2648.358115] lirc_imon: Unknown symbol lirc_register_driver
>> [ 2738.425026] lirc_imon: Unknown symbol lirc_unregister_driver
>> [ 2738.425578] lirc_imon: Unknown symbol lirc_register_driver
>> [ 2953.572735] lirc_imon: Unknown symbol lirc_unregister_driver
>> [ 2953.573289] lirc_imon: Unknown symbol lirc_register_driver
>> [ 3105.736606] lirc_imon: Unknown symbol lirc_unregister_driver
>> [ 3105.737158] lirc_imon: Unknown symbol lirc_register_driver
>>
>>
>> Well it looks like my imon.conf file in /etc/modprobe.d is wrong.  This
>> is exactly what my conf file has in it:
>>
>> options lirc_imon ir_protocol=1
>>
>> Do I need quotes somewhere, am I missing something?  Or is my driver not
>> correct?
>>     
>
> Somehow or another, you're still not loading the right lirc_imon there.
>
> The param is definitely ir_protocol, see modinfo lirc_imon output from
> my box:
>
> $ modinfo lirc_imon
> filename:       /lib/modules/2.6.31-0.112.rc4.git3.fc12.x86_64/kernel/drivers/input/lirc/lirc_imon.ko
> license:        GPL
> version:        0.6
> description:    Driver for SoundGraph iMON MultiMedia IR/Display
> ...
> parm:           debug:Debug messages: 0=no, 1=yes(default: no) (int)
> parm:           display_type:Type of attached display. 0=autodetect, 1=vfd, 2=lcd, 3=vga, 4=none (default: autodetect) (int)
> parm:           ir_protocol:Which IR protocol to use. 0=native iMON, 1=Windows Media Center Ed. (RC-6) (default: native iMON) (int)
> parm:           nomouse:Disable mouse input device mode when IR device is open. 0=don't disable, 1=disable. (default: don't disable) (int)
>
>
>

On Jul 31, 2009, at 12:19 PM, Lee Nugent wrote:

> Jarrod,
>
> I am so close I can taste it!
>
> I re-imaged again but this time I used:
>
> "sudo locate -i lirc"
>
> And deleted everything associated with lirc from the system and then
> reboot.
>
> I then did the CVS thing, then I ran modprobe:
>
> "sudo modprobe lirc_imon"
>
> With no errors.  Then made sure that lirc_imon driver was loaded for  
> my
> ffdc device:
>
> "sudo cat /proc/bus/usb/devices"
>
> And it was.  Then I ran:
>
> "sudo lircd --device=/dev/lirc0"
>
> And it started no problem.  I checked to make sure I was loading the
> correct lirc_imon using:
>
> "sudo modprobe lirc_imon"
>
> And I am getting the exact output you did for your command.
>
> I examined the /etc/lirc/lircd.conf and found that it was setup for  
> the
> iMON remote so I copied the imon-mceusb conf file to /etc/lirc as  
> such:
>
> "sudo mv lircd.conf.imon-mceusb /etc/lirc/lircd.conf"

So far, looks good to me...

> Then realized I didn't have a /etc/lirc/hardware.conf so I created one
> with the following contents:

All looks sane enough too...

> I did another reboot and ran IRW.  Again no output from IRW using this
> remote:
>
> http://www.newegg.com/Product/Product.aspx?Item=N82E16880121003
>
> I examined the lircd.conf file and commented out all Antec stuff at  
> the
> bottom, reboot (b/c I don't know how to restart LIRC at this point)  
> and
> tried again.  IRW produced no output again.  So I tried doing IRRECORD
> again.  I created about 10 buttons just as a test, saved it and  
> moved it
> to the /etc/lirc directory.  Rebooted again and ran IRW, this time I  
> was
> getting output from IRW, but it was as before.  I press the power  
> button
> and I would get KEY_ZOOM instead of KEY_POWER.  I would press zoom and
> would get KEY_AUDIO.  Basically IRRECORD is having the same behavior  
> as
> on 0.8.4a.

Sounds to me like the ir_protocol=1 param isn't taking for some reason.

> So, is my hardware.conf file correct or has that syntax changed with  
> the
> new version?
>
> BTW - I have the options lirc_imon ir_protocol=1 setting in imon.conf.
>
> Any other suggestions?

sudo modprobe -r lirc_imon

sudo modprobe lirc_imon ir_protocol=1 debug=1

Then try irw w/the mce remote. If it works, something is buggered with  
ubuntu's handling of modprobe options. If not, hopefully some of the  
spew that ends up in dmesg will help us understand what's going on.

-- 
Jarod Wilson
jarod@...

On Jul 31, 2009, at 4:28 PM, Jeremy Yoder wrote:

> Just thought I'd chime in as another Ubuntu user:  Note that when  
> Ubuntu
> auto-updates your kernel at some point in the future (Update Manager),
> all this work will be undone and you'll have to make these changes to
> /lib/modules/... again.  This seems to happen about once a month.

I thought the update from 2.6.28-11-generic to 2.6.28-11-generic was  
rather amusing... At least the last update was a different number...

> Jarod, what's your distro of choice?

Fedora.

> I like a lot of Ubuntu, but there sure are some painful things :)

I find its shiny on the outside, but for folks who do any sort of  
development work, it just gets in the way, being overly "helpful"...  
But part of that I'm sure is just me not having ever been able to  
tolerate using it for more than an hour or two at a time. I know where  
most of the warts are hiding and what most of the tricks are for  
Fedora. It also helps that I work in the same office as a ton of the  
core Fedora developers, who are also core upstream developers... (If  
its not obvious yet, I work for Red Hat). :)

> I've been toying with the idea of creating an updated set of lirc  
> 0.8.6
> packages for Ubuntu that fix some of these issues and posting it in a
> PPA: https://launchpad.net/ubuntu/+ppas
>
> I did a bunch of the work required against a CVS version a while back,
> but a lot has changed since then...

Eh, not too much that its that much work. I only had to make minor  
changes to update Fedora's lirc userspace to 0.8.6pre1. The bigger  
work was patching up lirc_i2c to work with 2.6.31's i2c changes (well,  
and the imon driver updates and mceusb driver merge, but those should  
be mostly irrelevant from a packaging standpoint).

-- 
Jarod Wilson
jarod@...

If I can get this working (using I loosely as it really will be Jarod),
then that will be unfortunate that all this work will have to be
repeated due to updates.  Can't I just comment out the update source
from /etc/sources.list so that it can't update unless I am ready to do
so?

Also, I have lived most my life in Windows and just recently want to
switch my HTPC running XBMC to Ubuntu as that is the distro that Team
XBMC supports.  I'm not against moving to another distro, but I have
learned so much about ubuntu in the past few weeks that I really don't
want to switch at this point.




Thanks,
Lee

-----Original Message-----
From: Jarod Wilson [mailto:jarod@...] 
Sent: Friday, July 31, 2009 3:44 PM
To: Jeremy Yoder
Cc: Nugent, Lee; lirc-list@...
Subject: Re: MCE Remote and iMON Reciever

On Jul 31, 2009, at 4:28 PM, Jeremy Yoder wrote:

> Just thought I'd chime in as another Ubuntu user:  Note that when  
> Ubuntu
> auto-updates your kernel at some point in the future (Update Manager),
> all this work will be undone and you'll have to make these changes to
> /lib/modules/... again.  This seems to happen about once a month.

I thought the update from 2.6.28-11-generic to 2.6.28-11-generic was  
rather amusing... At least the last update was a different number...

> Jarod, what's your distro of choice?

Fedora.

> I like a lot of Ubuntu, but there sure are some painful things :)

I find its shiny on the outside, but for folks who do any sort of  
development work, it just gets in the way, being overly "helpful"...  
But part of that I'm sure is just me not having ever been able to  
tolerate using it for more than an hour or two at a time. I know where  
most of the warts are hiding and what most of the tricks are for  
Fedora. It also helps that I work in the same office as a ton of the  
core Fedora developers, who are also core upstream developers... (If  
its not obvious yet, I work for Red Hat). :)

> I've been toying with the idea of creating an updated set of lirc  
> 0.8.6
> packages for Ubuntu that fix some of these issues and posting it in a
> PPA: https://launchpad.net/ubuntu/+ppas
>
> I did a bunch of the work required against a CVS version a while back,
> but a lot has changed since then...

Eh, not too much that its that much work. I only had to make minor  
changes to update Fedora's lirc userspace to 0.8.6pre1. The bigger  
work was patching up lirc_i2c to work with 2.6.31's i2c changes (well,  
and the imon driver updates and mceusb driver merge, but those should  
be mostly irrelevant from a packaging standpoint).

-- 
Jarod Wilson
jarod@...