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 'install-commandir.sh' script. 
 
Step 1:  On your MythBuntu box, download install-commandir.sh 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/install-commandir.sh

There will be a few prompts that require your attention. 

 

Expected output (sample):

 
matthew@mythbuntu904test2:~$ sudo bash ~/Desktop/install-commandir.sh
[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 http://security.ubuntu.com jaunty-security Release.gpg
Ign http://security.ubuntu.com jaunty-security/main Translation-en_US
Get:1 http://us.archive.ubuntu.com jaunty Release.gpg [189B]
Ign http://us.archive.ubuntu.com jaunty/main Translation-en_US
Get:2 http://ppa.launchpad.net jaunty Release.gpg [307B]
Ign http://ppa.launchpad.net jaunty/main Translation-en_US
Ign http://security.ubuntu.com jaunty-security/restricted Translation-en_US
Ign http://security.ubuntu.com jaunty-security/universe Translation-en_US
Ign http://security.ubuntu.com jaunty-security/multiverse Translation-en_US
Hit http://security.ubuntu.com jaunty-security Release
Ign http://us.archive.ubuntu.com jaunty/restricted Translation-en_US
Ign http://us.archive.ubuntu.com jaunty/universe Translation-en_US
Ign http://us.archive.ubuntu.com jaunty/multiverse Translation-en_US
Hit http://us.archive.ubuntu.com jaunty-updates Release.gpg
Ign http://us.archive.ubuntu.com jaunty-updates/main Translation-en_US
Ign http://us.archive.ubuntu.com jaunty-updates/restricted Translation-en_US
Ign http://us.archive.ubuntu.com jaunty-updates/universe Translation-en_US
Ign http://us.archive.ubuntu.com jaunty-updates/multiverse Translation-en_US
Get:3 http://us.archive.ubuntu.com jaunty Release [74.6kB]
Get:4 http://ppa.launchpad.net jaunty Release [52.9kB]
Hit http://security.ubuntu.com jaunty-security/main Packages
Hit http://security.ubuntu.com jaunty-security/restricted Packages
Hit http://security.ubuntu.com jaunty-security/main Sources
Hit http://security.ubuntu.com jaunty-security/restricted Sources
Hit http://security.ubuntu.com jaunty-security/universe Packages
Hit http://security.ubuntu.com jaunty-security/universe Sources
Hit http://security.ubuntu.com jaunty-security/multiverse Packages
Hit http://security.ubuntu.com jaunty-security/multiverse Sources
Ign http://ppa.launchpad.net jaunty Release
Hit http://us.archive.ubuntu.com jaunty-updates Release
Ign http://ppa.launchpad.net jaunty/main Packages
Get:5 http://us.archive.ubuntu.com jaunty/main Packages [1251kB]
Get:6 http://ppa.launchpad.net jaunty/main Packages [1782B]
Get:7 http://us.archive.ubuntu.com jaunty/restricted Packages [8653B]
Get:8 http://us.archive.ubuntu.com jaunty/main Sources [550kB]
Get:9 http://us.archive.ubuntu.com jaunty/restricted Sources [3156B]
Get:10 http://us.archive.ubuntu.com jaunty/universe Packages [4759kB]
Get:11 http://us.archive.ubuntu.com jaunty/universe Sources [2374kB]
Get:12 http://us.archive.ubuntu.com jaunty/multiverse Packages [199kB]
Get:13 http://us.archive.ubuntu.com jaunty/multiverse Sources [107kB]
Hit http://us.archive.ubuntu.com jaunty-updates/main Packages
Hit http://us.archive.ubuntu.com jaunty-updates/restricted Packages
Hit http://us.archive.ubuntu.com jaunty-updates/main Sources
Hit http://us.archive.ubuntu.com jaunty-updates/restricted Sources
Hit http://us.archive.ubuntu.com jaunty-updates/universe Packages
Hit http://us.archive.ubuntu.com jaunty-updates/universe Sources
Hit http://us.archive.ubuntu.com jaunty-updates/multiverse Packages
Hit http://us.archive.ubuntu.com jaunty-updates/multiverse Sources
Fetched 9383kB in 49s (188kB/s)
Reading package lists... Done
W: GPG error: http://ppa.launchpad.net 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:
  setserial
Suggested packages:
  lirc-modules-source lirc-x
The following NEW packages will be installed:
  setserial
The following packages will be upgraded:
  lirc
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!
  lirc
Install these packages without verification [y/N]? y
Get:1 http://ppa.launchpad.net jaunty/main lirc 0.8.4a-1ubuntu0 [494kB]
Get:2 http://us.archive.ubuntu.com 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
install-commandir.sh finished.
matthew@mythbuntu904test2:~$ 
 
  

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

Troubleshooting Tip #1 - Unplug and re-plug the CommandIR after running install-commandir.sh

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)"
REMOTE_MODULES=""
REMOTE_DRIVER="commandir"
REMOTE_DEVICE=""
REMOTE_LIRCD_CONF="hauppauge/lircd.conf.hauppauge"
REMOTE_LIRCD_ARGS=""

#Chosen IR Transmitter
TRANSMITTER="Command IR : Dish Receiver"
TRANSMITTER_MODULES=""
TRANSMITTER_DRIVER="commandir"
TRANSMITTER_DEVICE=""
TRANSMITTER_LIRCD_CONF="dish/general.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="false"

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

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
 
[ Back ]
  



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