LCD on Fusion remote black

I had some difficulties to enable the LCD on this HTPC. Just for reference a couple of

At first I followed the instructions as in:
The fresh build imon driver didn’t work for me.

Then I stumbled upon:, suggesting me patching the current lcdproc-0.5.2 package to use the imonlcd driver instead.

Update: in the meantime fully documented here. In short in my case:

Install lcdproc:

sudo apt-get install lcdproc

Edit /etc/LCDd.conf and adjust:

Driver= imonlcd

For the imonlcd driver go do the imonlcd section and adjust:

Protocol= 1

You should also check the output-device. I had to change: Device=/dev/lcd0 to Device=/dev/lcd1

Restart service:

sudo /etc/init.d/LCDd stop; sudo /etc/init.d/LCDd start

You can edit /etc/LCD.conf and add a welcome and goodbye message:

# Hello message: each entry represents a display line; default: builtin
Hello=”Welcome to”
Hello=”my mythbox”

# GoodBye message: each entry represents a display line; default: builtin
GoodBye=”So long&thanks”
GoodBye=”4 all the fish!”

Update of runlevels at boot with: (debian already does this during install)

:~#update-rc.d LCDd defaults

Next I added support for the volume knob to .lircrc:

  prog = mythtv
  button = WheelCW
  repeat = 1
  config = ]
  prog = mythtv
  button = WheelCC
  repeat = 1
  config = [

After I switched on support for LCD device in the settings of myth-frontend sometimes after boot connection to the LCD-server seems to get lost.
I found a solution to this by adding a static IP in /etc/network/interfaces instead of using an DHCP-address.

4 thoughts on “LCD on Fusion remote black

  1. You should check:

    I used the native remote only for a short time. I didn’t like it. Mostly because I always had to point very precise with the remote targeting the Fusionbox in order to make the keys do something. I also disliked the unstable rubber keys of the remote.

    I switched to a Ati remote wonder which uses RF instead of IR for connection. Much better in my opinion. (

    Look for them on ebay. They’re really cheap.

    • Yes, it’s probably your Xorg.conf. Please check every line and every character in it for mistakes. If you make one mistake, X won’t start properly indeed. I you copied and pasted from my website maybe the quotes “” are not copied well. You should check this double.

      For details you might also check your Xorg log-file. Switch to first console with CTRL+ALT+F1 and execute: tail -f /var/log/Xorg.0.log
      Switch to second console and restart X and show what you Xorg-log displays about the misconfiguration.

      Good luck!

Leave a Reply

Your email address will not be published. Required fields are marked *