Total IR Control for Linux
Home arrow Support arrow Archive: CommandIR II arrow MythBuntu 8.10
MythBuntu 8.10 and General dpkg Setup
Update April 16th, 2009 - See MythBuntu 9.04 for the latest MythBuntu installation instructions.
Updated December 8th, 2008 - MythBuntu 8.10 --MB
Updated December 23rd, 2008 - CommandIR Mini driver fixes in "lirc - 0.8.4a-0ubuntu2~intrepid3" released today.

Upgrading LIRC package from

1. As in the instructions over at add, this line apt source to your MythBuntu /etc/apt/sources.list file:
deb intrepid main

2. Install drivers as root, or sudo:

Download the CommandIR hardware.conf (also configures MythBuntu Control Panel):

(wget command is 1 line ending with the '/etc/lirc/lircd.conf')

wget "/downloads/CommandIR II Resource Files/commandir-lircd.conf" 
  -O /etc/lirc/lircd.conf
apt-get update
apt-get install lirc
You will have to agree to install our unsigned package.

Unload old CommandIR kernel modules, if you are upgrading:

rmmod commandir
rmmod lirc_cmdir

Try some test commands with 'irw' or 'irsend'.


3. (If needed) To reconfigure your remote and/or blasting devices open up the MythBuntu Control Centre:

from the MythTV main menu select:

  • Utilities / Setup
  • Setup
  • (scroll down) MythBuntu  
Enter your password to start the MythBuntu Control Centre. 
Or from the main 'Applications' menu, choose System -> Mythbuntu Control Centre.
3.1 From the left-side menu in the MythBuntu Control Centre, choose 'Infrared Devices'.
3.2 If you downloaded the hardware.conf (above), then you just have to change the 'Configuration:' boxes for your remote and/or IR transmitter. 
To do it manually, use the 'Custom' settings as shown in the screenshot below:
CommandIR Mini and CommandIR II Configuration for MythBuntu


4. Restart MythTV, or reboot.




"No remotes work"

The most common problem is an LIRC bug when your selected remote files in hardware.conf are not included properly, and thus no remotes work.

If the running lircd manually test (plus irw in another window) yields output like this:

user@mythtv:~$ sudo lircd -n --driver=commandir
lircd-0.8.4a[4086]: lircd(commandir) ready
lircd-0.8.4a[4086]: accepted new client on /dev/lircd
lircd-0.8.4a[4118]: Child Initializing CommandIR Hardware
lircd-0.8.4a[4086]: CommandIR driver initialized
lircd-0.8.4a[4118]: Product identified as CommandIR II

and the "A" LED has changes to GREEN when 'irw' is also run - but pressing buttons on a remote only causes the CommandIR II remote LED to blink 'red' and not 'green', then try putting all your relevant lircd.conf's into the master /etc/lirc/lircd.conf



mv /etc/lirc/lircd.conf /etc/lirc/lircd-backup.conf

cat /usr/share/lirc/remotes/hauppauge/lircd.conf.hauppauge >> /etc/lirc/lircd.conf

cat /usr/share/lirc/transmitters/motorola/dctxxxx.conf >> /etc/lirc/lircd.conf

cat /home/mythbuntu/Desktop/lircd.conf.commandir >> /etc/lirc/lircd.conf


Then restart the test. 


Note, the PVR-150 lircd.conf (with "one    0  0" and "zero   0  0" lines) is specific to Hauppauge cards and not compatible with CommandIR!  Use the generic lircd.conf.hauppauge, which has the signal timings, instead. 



The 2nd most common problem is MythBuntu automatically loading the CommandIR Mini driver when a CommandIR II is plugged in:

Symptoms are 'lircd --driver=commandir -n' reporting:

  "Unable to read version request - Is CommandIR busy? Error -110"


 "lircd-0.8.4a[6064]: Unable to claim CommandIR - Is it already busy?
  lircd-0.8.4a[6064]: Try 'rmmod commandir' or check for other lircds"


Verify that none of these kernel modules are loaded:

- lirc_cmdir

- commandir

- lirc_dev

By running (as root):

rmmod lirc_cmdir commandir lirc_dev 


You can perminantly disable lirc_cmdir and commandir by blacklisting it, or deleting these files (MythBuntu 8.10):

echo "blacklist lirc_cmdir" >> /etc/modprobe.d/blacklist
echo "blacklist commandir" >> /etc/modprobe.d/blacklist




rm /lib/modules/2.6.27-7-generic/kernel/ubuntu/lirc/lirc_cmdir/lirc_cmdir.ko
rm /lib/modules/2.6.27-7-generic/kernel/ubuntu/lirc/lirc_cmdir/commandir.ko 

To find these files on a different system, use:

find /lib/modules/`uname -r`|grep commandir.ko

1. To test on the command line (Terminal), try these commands:

1.1 irw

Running 'irw' should "freeze" while waiting for you to press remote buttons. 

If you receive 'connect: Connection refused' then LIRC is not running.

If irw returns/exists immediately, then LIRC is initialy running, but isn't configured for CommandIR.  Check your MythBuntu IR Devices settings, or manually install a preconfigured hardware.conf for CommandIR on MythBuntu from CommandIR Downloads:



If 'irw' freezes but doesn't display anything when you press remote buttons, double-check that LIRC has an lircd.conf for the remote you are using. 


1.2 irsend send_once <remote name> <button name>

Running 'irsend' should cause CommandIR to transmit the remote key.

If you receive the message:

irsend: could not connect to socket
irsend: Connection refused

then LIRC (lircd) is not running.  Check your MythBuntu IR Device settings and hardware.conf.  If you don't know the name of your remote or buttons, check out your lircd.conf file.

2. CommandIR II Light "A" goes red after a remote button press 

This can happen because:

  • Old kernel module 'commandir' and/or 'lirc_cmdir' are loaded.  If running 'sudo lsmod' lists them, then remove them.
  • Your LIRC isn't the latest, as of August 11, 2008
If you still have trouble, email us:Image
Published: Sunday, 13 July 2008
Last Updated: Thursday, 31 March 2011

CommandIR Control Technologies is a division of InnovationOne Applied Technology.

(C) 2006-2012, All Rights Reserved. 

Last update: Mon Oct 29 22:23:04 EDT 2012


Privacy   Terms of Use