Total IR Control for Linux
Home arrow Support arrow Archive: CommandIR II arrow MythBuntu 9.04
MythBuntu 9.04
CommandIR installation on MythBuntu 9.04 is easier than ever with the help of the '' script. 
Step 1:  On your MythBuntu box, download to your Desktop
Step 2:  Open a terminal window (Applications Menu -> Accessories -> Terminal)
Step 3:  Run this command in the terminal window:
  sudo bash ~/Desktop/

There will be a few prompts that require your attention.


Expected output (sample):

matthew@mythbuntu904test2:~$ sudo bash ~/Desktop/
[sudo] password for matthew:
ERROR: Module commandir does not exist in /proc/modules
ERROR: Module lirc_cmdir does not exist in /proc/modules
ERROR: Module lirc_dev does not exist in /proc/modules
find: `/lib/modules/2.6.28-11-generic/kernel/ubuntu/lirc/lirc_cmdir': No such file or directory
Hit jaunty-security Release.gpg
Ign jaunty-security/main Translation-en_US
Get:1 jaunty Release.gpg [189B]
Ign jaunty/main Translation-en_US
Get:2 jaunty Release.gpg [307B]
Ign jaunty/main Translation-en_US
Ign jaunty-security/restricted Translation-en_US
Ign jaunty-security/universe Translation-en_US
Ign jaunty-security/multiverse Translation-en_US
Hit jaunty-security Release
Ign jaunty/restricted Translation-en_US
Ign jaunty/universe Translation-en_US
Ign jaunty/multiverse Translation-en_US
Hit jaunty-updates Release.gpg
Ign jaunty-updates/main Translation-en_US
Ign jaunty-updates/restricted Translation-en_US
Ign jaunty-updates/universe Translation-en_US
Ign jaunty-updates/multiverse Translation-en_US
Get:3 jaunty Release [74.6kB]
Get:4 jaunty Release [52.9kB]
Hit jaunty-security/main Packages
Hit jaunty-security/restricted Packages
Hit jaunty-security/main Sources
Hit jaunty-security/restricted Sources
Hit jaunty-security/universe Packages
Hit jaunty-security/universe Sources
Hit jaunty-security/multiverse Packages
Hit jaunty-security/multiverse Sources
Ign jaunty Release
Hit jaunty-updates Release
Ign jaunty/main Packages
Get:5 jaunty/main Packages [1251kB]
Get:6 jaunty/main Packages [1782B]
Get:7 jaunty/restricted Packages [8653B]
Get:8 jaunty/main Sources [550kB]
Get:9 jaunty/restricted Sources [3156B]
Get:10 jaunty/universe Packages [4759kB]
Get:11 jaunty/universe Sources [2374kB]
Get:12 jaunty/multiverse Packages [199kB]
Get:13 jaunty/multiverse Sources [107kB]
Hit jaunty-updates/main Packages
Hit jaunty-updates/restricted Packages
Hit jaunty-updates/main Sources
Hit jaunty-updates/restricted Sources
Hit jaunty-updates/universe Packages
Hit jaunty-updates/universe Sources
Hit jaunty-updates/multiverse Packages
Hit jaunty-updates/multiverse Sources
Fetched 9383kB in 49s (188kB/s)
Reading package lists... Done
W: GPG error: jaunty Release: The following signatures couldn't be verified 
because the public key is not available: NO_PUBKEY B74C0228B7BBBF2F
W: You may want to run apt-get update to correct these problems
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
Suggested packages:
  lirc-modules-source lirc-x
The following NEW packages will be installed:
The following packages will be upgraded:
1 upgraded, 1 newly installed, 0 to remove and 279 not upgraded.
Need to get 546kB of archives.
After this operation, 172kB of additional disk space will be used.
Do you want to continue [Y/n]? y
WARNING: The following packages cannot be authenticated!
Install these packages without verification [y/N]? y
Get:1 jaunty/main lirc 0.8.4a-1ubuntu0 [494kB]
Get:2 jaunty/main setserial 2.17-45 [51.6kB]
Fetched 546kB in 1s (398kB/s)
Preconfiguring packages ...
Selecting previously deselected package setserial.
(Reading database ... 90528 files and directories currently installed.)
Unpacking setserial (from .../setserial_2.17-45_i386.deb) ...
Preparing to replace lirc 0.8.4a-0ubuntu3 (using .../lirc_0.8.4a-1ubuntu0_i386.deb) ...
 * Stopping remote control daemon(s): LIRC                                   [fail]
Unpacking replacement lirc ...
Processing triggers for man-db ...
Processing triggers for hal ...
Regenerating hal fdi cache ...
 * Restarting Hardware abstraction layer hald                                [ OK ]
Setting up setserial (2.17-45) ...
removing the old setserial entry in the rcn.d directories
Update complete.
Saving state of known serial devices... backing up /var/lib/setserial/autoserial.conf done.

Setting up lirc (0.8.4a-1ubuntu0) ...
Installing new version of config file /etc/init.d/lirc ...
 * Reloading kernel event manager...                                         [ OK ]
 * Loading LIRC modules                                                      [ OK ]
 * Unable to load LIRC kernel modules. Verify your
 * selected kernel modules in /etc/lirc/hardware.conf

Please change your /etc/lirc/hardware.conf to not use lirc_cmdr! It should use
remote_driver="commandir" and/or transmitter_driver="commandir" with no *_modules=lirc_cmdir
 * Stopping remote control daemon(s): LIRC                                   [fail]
 * Loading LIRC modules                                                      [ OK ]
 * Unable to load LIRC kernel modules. Verify your
 * selected kernel modules in /etc/lirc/hardware.conf finished.

In the above example, the hardware.conf requires reconfiguring before the CommandIR will work.  This will depend on the settings chosen during MythBuntu installation (see #2 below for resolution).




Troubleshooting Tip #1 - Unplug and re-plug the CommandIR after running

Sometimes the old kernel modules can confuse the newer CommandIRs. The old driver is the only instance we can find that requires the unplug/replug. After running the above installation script and unplugging/replugging once, it should never be required again.


Troubleshooting Tip #2 - /etc/lirc/hardware.conf

If you see warning message about your /etc/lirc/hardware.conf - do not ignore them!  Check your /etc/lirc/hardware.conf file, which should look something like this:

# /etc/lirc/hardware.conf
#Chosen Remote Control
REMOTE="CommandIR Multi-IR Transceiver (userspace)"

#Chosen IR Transmitter
TRANSMITTER="Command IR : Dish Receiver"

#Enable lircd

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

#Try to load appropriate kernel modules

# Default configuration files for your hardware if any

#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"

To reload LIRC after changing /etc/lirc/hardware.conf manually, run:

  sudo /etc/init.d/lirc restart



Troubleshooting Tip #3 - To test immediately, you can try these commands:

irw (shows remote keys that are detected as they are pressed)

irsend send_once hauppauge power (test send command if the Hauppauge remote configuration is included)


Troubleshooting Tip #4 - Understanding CommandIR Lights:

A - LIRC (lircd) is running and is actively listening to the CommandIR (Green means good).  Any LIRC client will initialize the LIRC connection, but it does not happen by default when LIRC starts (LIRC by design) so run 'irw' or similar to force the initial connection.

B - Flashes when a new LIRC client connects (irw, irsend).  

Remote - Blinks Red when a raw remote signal is detected (carrier level), blinks Green when/if LIRC decodes that signal
Published: Thursday, 16 April 2009
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