hi kenny, just geting started, but i notice the lirc-imon script is not posted here yet. t hx!

matt

hi kenny,

wow! that actually works! both the volume knob and the remote transmit signals, and both are interpreted correctly by lirc.

if that had just worked the first time I wouldn’t have learned ANYTHING…

two quick notes:
typo:
sudo wget -O /etc/apt/sources.list.d/kennynet-testing.test
^list

also, i had the legacy is_lcd option in modprobe.d/options after following some other guide, and that option is apparently deprecated now — modules loaded fine after I removed it.

hthanks much,
matt

Hi Kenny,

I just bought an Antec Case now and want it to work with Ubuntu. So the timing was absolutely perfect. Thanks a million for that.

Right now the only problem is to get your key added to apt so it shuts up about the key being dangerous and all – I pasted the command so maybe there’s a typo.

Anyway, I want the whole thing to work with XBMC. Are you using that as well? And what about the display? Is that supposed to work now also?

Thanks,

Klaus

Hi again Kenny,

It appears you have the exact same hardware as I have – and yet neither the VFD or the volume knob seems to work. The VFD is just DEAD. I loaded the lirc_imon module with the display_type=1 arg so it forces to VFD – yet nothing happens.

Same thing with the volume knob. Just nothing when I fire up irw and twist the knob..

Any idea what could be wrong?

/klaus

Hi Kenny,

Regarding display_type=1 I got an error spamming my syslog with this:

lirc_imon: lcd_write: invalid payload size: 32 (expecting

So I googled the error and read someone suggesting that. After that the error dissapeared, so I assumed that the display was a VFD (without really knowing it . Since I do have a 152c:0038, I guess I was wrong.

I tried changing it to display_type=2 and the same error comes back – and it still doesn’t work.

lsusb:
Bus 004 Device 002: ID 046d:c505 Logitech, Inc. Cordless Mouse+Keyboard Receiver
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 15c2:0038 SoundGraph Inc.
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
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

ls -la /dev/lirc* /dev/lcd*:
crw-rw—- 1 root root 180, 144 2009-04-02 22:39 /dev/lcd0
crw-rw—- 1 root root 180, 145 2009-04-02 22:39 /dev/lcd1
crw-rw—- 1 root root 61, 0 2009-04-02 22:39 /dev/lirc0
crw-rw—- 1 root root 61, 1 2009-04-02 22:39 /dev/lirc1
srw-rw-rw- 1 root root 0 2009-04-02 22:40 /dev/lircd

apt-cache policy lirc:
lirc:
Installed: 0.8.5~pre1-0ubuntu1~km1
Candidate: 0.8.5~pre1-0ubuntu1~km1
Version table:
*** 0.8.5~pre1-0ubuntu1~km1 0
500 http://packages.kennynet.co.uk intrepid-testing/main Packages
100 /var/lib/dpkg/status
0.8.3-0ubuntu2 0
500 http://dk.archive.ubuntu.com intrepid/universe Packages

apt-cache policy lirc-modules-source:
lirc-modules-source:
Installed: 0.8.5~pre1-0ubuntu1~km1
Candidate: 0.8.5~pre1-0ubuntu1~km1
Version table:
*** 0.8.5~pre1-0ubuntu1~km1 0
500 http://packages.kennynet.co.uk intrepid-testing/main Packages
100 /var/lib/dpkg/status
0.8.3-0ubuntu2 0
500 http://dk.archive.ubuntu.com intrepid/universe Packages

cat /etc/lircd.conf:
#This configuration has been automatically generated via
#the Ubuntu LIRC package maintainer scripts.
#
#It includes the default configuration for the remote and/or
#transmitter that you have selected during package installation.
#
#Feel free to add any custom remotes to the configuration
#via additional include directives or below the existing
#Ubuntu include directives from your selected remote and/or
#transmitter.

include “/usr/share/lirc/remotes/imon/lircd.conf.imon-antec-veris”

I hope you can make something useful out of this.

/k

hmmm… I have a 15c2:0038 – NOT a 152c:0038… Why does it have to be so damn complicated?

Anyways, that is probably why the display doesn’t work.. It’ll probably be fixed in the next lirc release… so in the meantime I’ll just live without it – unless there is some other way..

Thanks,

/klaus

Hi Kenny,

apt-cache policy lcdproc:
lcdproc:
Installed: 0.5.2-0ubuntu3~km1
Candidate: 0.5.2-0ubuntu3~km1
Version table:
*** 0.5.2-0ubuntu3~km1 0
500 http://packages.kennynet.co.uk intrepid-testing/main Packages
100 /var/lib/dpkg/status
0.5.2-0ubuntu2 0
500 http://dk.archive.ubuntu.com intrepid/universe Packages

grep “Driver=” /etc/LCDd.conf:
Driver=imon

grep -A5 “[imonlcd]” /etc/LCDd.conf
(there’s no [imonlcd] section, so I guess you mean [imon],,

[imon]

# select the device to use
Device=/dev/lcd0

# display dimensions
Size=16×2

Hey – thanks for helping me out. And I am not really sure about the typo-thing.. Who knows

/k

Hi Kenny.

I did as instructed.. and nothing changed. Still nothing in the display – except light. I double checked the manual to see if I assembled something wrong. It appears as if it’s hard to do wrong.. So it looks as that’s not the problem – at least.

Do you have any other ideas on what to try?

Thanks,

/klaus

Hi again,

Woohoo !. I got it. I screwed up – let me admit it. I followed a guide saying to modify the init.d script, and forgot all about it.

Yesterday I wondered why the syslog said something about wrong parameters to the LCDd.. So after fixing that, things started to work and the LCD lit up like a tree at christmas (in a good way .

So – thanks a bunch for your help. You’ve saved from patch-hell.

/klaus

Thank you so very much. All went well other than the the problem Matt had.

Matt Price :
…also, i had the legacy is_lcd option in modprobe.d/options after following some other guide, and that option is apparently deprecated now — modules loaded fine after I removed it.
hthanks much,
matt

thanks Matt, it seemed to work for me as well. This is the first time I’ve been able to use the sensor and the remote that shipped with the case.

I’ve yet to actually reboot the system and test all the functions, but thanks for getting me started in the right direction.

Nope, I was wrong. After reboot I had no remote. No irw responses with the RM200 or the MCE remote . The display is working nicely but no volume knob. Same issue I’ve always had. I’ll try again another day and use the keyboard (sigh) for now. I’m still grateful for your instructions, to date they are by far the easiest and most precise.

Hi,

there are plenty of Howtos available on the net and I went through most of them but couldn’t make it work…

Now with your packages it works just great! Thanks a lot!

Robsta

Hi Kenny,

Have you made packages for Jaunty? Or are the patches included? Do you know?

Thanks,

/klaus

you’re a savior! been trying for 2 weeks to get this bloody IR working in ubuntu jaunty – thanks a million kenny!

you’re my hero for the day, worked like a charm, thanks!

Hi Kenny,

The packages for jaunty works fine so far. I’ll let you know if that changes

/k

Hi Kenny,

I’m struggling for quite some time now to get this working.
Ubuntu version: jaunty with the same hardware (15c2:0038)

I’m stuck with the step after you make the startup script executable:

roos@XBMC:/etc/init.d$ sudo modprobe -r lirc_dev lirc_imon
WARNING: All config files need .conf: /etc/modprobe.d/options, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/options, it will be ignored in a future release.
roos@XBMC:/etc/init.d$ sudo /etc/init.d/lirc-imon start
Starting lirc-imon…WARNING: All config files need .conf: /etc/modprobe.d/options, it will be ignored in a future release.
FATAL: Error inserting lirc_imon (/lib/modules/2.6.28-11-generic/updates/dkms/lirc_imon.ko): Unknown symbol in module, or unknown parameter (see dmesg)
done.

What is going wrong here?

Regards, Johan

here it is:
/etc/init.d$ dmesg | grep lirc
[ 9.457724] lirc_dev: IR Remote Control driver registered, major 61
[ 9.468729] lirc_imon: Unknown parameter `is_lcd’
[ 9.683870] lirc_imon: Unknown parameter `is_lcd’
[ 10.763859] lirc_imon: Unknown parameter `is_lcd’
[ 13.669180] lirc_imon: Unknown parameter `is_lcd’
[ 3677.378731] lirc_dev: IR Remote Control driver registered, major 61
[ 3677.380481] lirc_imon: Unknown parameter `is_lcd’
[ 3744.078507] lirc_dev: IR Remote Control driver registered, major 61
[ 3744.080261] lirc_imon: Unknown parameter `is_lcd’

this feedback looks better.

Starting lirc-imon…WARNING: All config files need .conf: /etc/modprobe.d/options, it will be ignored in a future release.
WARNING: /etc/modprobe.d/options line 2: ignoring bad line starting with ‘options’
lircd: there seems to already be a lircd process with pid 20204
lircd: otherwise delete stale lockfile /var/run/lirc0.pid
lircd: there seems to already be a lircd process with pid 20206
lircd: otherwise delete stale lockfile /var/run/lirc1.pid
done.

I’m installing anyway… I can test the official backport for you if you like.
Should I remove lirc and reinstall with the new PPA ?
Can you point me the direction for testing your package?

Thx

Oh, and I forgot;
“irw” does not connect :

roos@XBMC:~/Bureaublad/lirc$ irw
connect: No such file or directory

Though, this has never worked before, in any attempt for making this running.

As far as I can see, this guideline was the best I could find

So to return to the feedback of the start command: I’ve stopped the other lirc processes with:
roos@XBMC: sudo /etc/init.d/lirc stop

then:

roos@XBMC: sudo /etc/init.d/lirc-imon start
Starting lirc-imon…WARNING: All config files need .conf: /etc/modprobe.d/options, it will be ignored in a future release.
WARNING: /etc/modprobe.d/options line 2: ignoring bad line starting with ‘options’
done.

so is it ok that in the options file the whole line is not correct at all?

Stopping: (lirc or lirc-imon ?) > i took both

roos@XBMC:~/Bureaublad/lirc$ sudo /etc/init.d/lirc stop
* Stopping remote control daemon(s): LIRC [fail]

roos@XBMC:~/Bureaublad/lirc$ sudo /etc/init.d/lirc-imon stop
Stopping lirc-imon…WARNING: All config files need .conf: /etc/modprobe.d/options, it will be ignored in a future release.
WARNING: /etc/modprobe.d/options line 2: ignoring bad line starting with ‘options’
done.

Remove:
there is no such file with “lirc”

Restart:
roos@XBMC:/var/run$ sudo /etc/init.d/lirc-imon start
Starting lirc-imon…WARNING: All config files need .conf: /etc/modprobe.d/options, it will be ignored in a future release.
WARNING: /etc/modprobe.d/options line 2: ignoring bad line starting with ‘options’
done.

(the killing worked ok, no feedback)

Good news!

After so many attempts, for fixing this issue, I’ve decided to reinstall Ubuntu Jaunty.

Result:
This is the first time irw seems not to fail.
In the procedure though, automatically the ./setup.sh script is running, and asks for picking a remote.

I picked ‘none’, which results in no feedback on stdout when I press the remote buttons.

For the Antec remote, what remote should I pick? It looks not to be listed…
Can I rerun the procedure to make the knob on the case work?
and rerun to pick another remote?

Guess what… the shipped batteries with the remote were not strong enough.
Finally the irw gives me some feedback

This procedure works, it’s the right path to heaven!
Thanks so much Kenny for the article. You must know I’m a Linux newbie, so it says alot about your article. If I can do this, everyone can

Now getting the LCD working… cause this one seems to be blanced out…
Looking for the right path to a working LCD.

I’ll post my findings later on.

Thanks again

Kenny,

I’ve tried your version of lcdproc setting the configuration as you specify above, but I the LCD acts oddly, showing the (incorrect) time and then all of the pixels turn on and then off. I have a Soundgraph LCD (15c2:0038) so I have set Protocol=1 and Size=16×2. In dmesg, I get a pair of errors that repeat:

lirc_imon: send_packet: packet tx failed (-32)
lirc_imon: lcd_write: send packet failed!

Any idea what could be happening?

I’ve added the section in lcdproc.conf.
the driver was already set in LCDd.conf.

I’ve rebooted, but no effect. Did I forgot something?

Kenny,

How do I make sure I have the right version of your compiled patched LCD code?
Remove returns:
sudo apt-get remove lcdproc
Pakketlijsten worden ingelezen… Klaar
Boom van vereisten wordt opgebouwd
De status informatie wordt gelezen… Klaar
De volgende pakketten zullen VERWIJDERD worden:
lcdproc
0 pakketten opgewaardeerd, 0 pakketten nieuw geïnstalleerd, 1 te verwijderen en 0 niet opgewaardeerd.
Door deze operatie zal er 1237kB schijfruimte vrijkomen.
Wilt u doorgaan [J/n]? J
(Database inlezen … 127220 bestanden en mappen geïnstalleerd.)
lcdproc wordt verwijderd …
Stopping LCDd: LCDd.
Processing triggers for man-db …

sudo apt-get isntall lcdproc
Pakketlijsten worden ingelezen… Klaar
Boom van vereisten wordt opgebouwd
De status informatie wordt gelezen… Klaar
De volgende NIEUWE pakketten zullen geïnstalleerd worden:
lcdproc
0 pakketten opgewaardeerd, 1 pakketten nieuw geïnstalleerd, 0 te verwijderen en 0 niet opgewaardeerd.
Er moeten 0B/391kB aan archieven opgehaald worden.
Door deze operatie zal er 1237kB extra schijfruimte gebruikt worden.
Selecteren van voorheen niet geselecteerd pakket lcdproc.
(Database inlezen … 127153 bestanden en mappen geïnstalleerd.)
Uitpakken van lcdproc (uit …/lcdproc_0.5.2-0ubuntu3~ppa2~km2_amd64.deb) …
Processing triggers for man-db …
Instellen van lcdproc (0.5.2-0ubuntu3~ppa2~km2) …
Starting LCDd: LCDd.

Still, nothing on my LCD.
The LCDd.conf is changed now with
“Driver=imonlcd”

[imonlcd]
Size=16×2
Device=/dev/lcd0
Contrast=200
Protocol=1

Sorry for the Dutch, but is this the correct version installed?

Hi Kenny,

LCDd -f -r 4 returns:

LCDd version 0.5.2 starting
Built on Apr 3 2009, protocol version 0.3, API version 0.5
Using Configuration File: /etc/LCDd.conf
Set report level to 4, output to stderr
LCDd 0.5.2, LCDproc Protocol 0.3
Part of the LCDproc suite
Copyright (C) …(skipped).., USA.

Server running in foreground
Listening for queries on 127.0.0.1:13666
Could not open driver module server/drivers/imonlcd.so: server/drivers/imonlcd.so: cannot open shared object file: No such file or directory
Driver [imonlcd] binding failed
Module server/drivers/imonlcd.so could not be loaded
Could not load driver imonlcd
There is no output driver
Critical error while initializing, abort.

Any interesting info you could point me to?

Regards, Johan

Hi All,

some update on my status

* IRW is reacting to all buttons of my remote (RM200)
* I managed to make the LCD to react on the “sudo LCDd -f -r 4″ command. (time comes up in futuristic format)

One small thing missing in this guideline

LCDd.conf contains also a parameter DriverPath. It should be set to:
DriverPath=/usr/lib/lcdproc/

Kenny, is it possible to remove the clutter posts?
They are not of so much use, since my first posts were based on a system contaminated with to many attempts without success.

Regards, Johan

roos@XBMC:~$ apt-cache policy lcdproc
lcdproc:
Geïnstalleerd: 0.5.2-0ubuntu3~ppa2~km2
Kandidaat: 0.5.2-0ubuntu3~ppa2~km2
Versietabel:
*** 0.5.2-0ubuntu3~ppa2~km2 0
500 http://packages.kennynet.co.uk jaunty-testing/main Packages
100 /var/lib/dpkg/status

Think it was the right version, no?

Many thanks again!

I get:
* Unable to load LIRC kernel modules
after configuring with Soundgraph Imon IR/LCD and None as transmitter

Can you help me with that?

I’m running the veris basic receiver :0043 but I should get away with using your howto aside from the remote codes themselves?

I forgot to add… apparently the newest driver in lirc cvs no longer creates 2 different lirc devices… and makes imon work much closer to its windows drivers.

I just don’t have enough knowhow to go down that path as there’s no pretty howto to follow =(

Did anyone get a step by step guide for getting the LCD working?

Hi! First of all – great guide, best I’ve found (which, to me, seems odd seeing how many use this case)!

I’ve almost got it working (I think), the knob seems to be working:

mediasmurf@mediasmurf:~$ irw
01000000000002ee 00 KEY_VOLUMEDOWN Antec_Veris_Premiere
00010000000002ee 00 KEY_VOLUMEUP Antec_Veris_Premiere
01000000000002ee 00 KEY_VOLUMEDOWN Antec_Veris_Premiere

but, the problem is, I don’t get any output from the remote. I can, however, use the on/off on it, but I suppose that is ’cause it’s hardwired.

I get the “LCDproc Server, Cli: 0, Scr: 0″ output, along with the heart and stuff on the LCD, so that seems to be working (although I have no idea where to go from there, to actually get info on it).

I’ll paste some info you’ve requested from the other posters:

mediasmurf@mediasmurf:~$ lsusb | grep -i sound
Bus 003 Device 004: ID 15c2:0038 SoundGraph Inc.

mediasmurf@mediasmurf:~$ ls -la /dev/lirc* /dev/lcd*
crw-rw—- 1 root root 180, 144 2009-09-03 01:21 /dev/lcd0
crw-rw—- 1 root root 180, 145 2009-09-03 01:21 /dev/lcd1
crw-rw—- 1 root root 61, 0 2009-09-03 01:21 /dev/lirc0
crw-rw—- 1 root root 61, 1 2009-09-03 01:21 /dev/lirc1
srw-rw-rw- 1 root root 0 2009-09-03 01:28 /dev/lircd

mediasmurf@mediasmurf:~$ apt-cache policy lirc
lirc:
Installerad: 0.8.5~pre1-0ubuntu1~km2
Kandidat: 0.8.5~pre1-0ubuntu1~km2
Versionstabell:
*** 0.8.5~pre1-0ubuntu1~km2 0
500 http://packages.kennynet.co.uk jaunty-testing/main Packages
100 /var/lib/dpkg/status
0.8.4a-0ubuntu5 0
500 http://se.archive.ubuntu.com jaunty/universe Packages

mediasmurf@mediasmurf:~$ apt-cache policy lirc-modules-source
lirc-modules-source:
Installerad: 0.8.5~pre1-0ubuntu1~km2
Kandidat: 0.8.5~pre1-0ubuntu1~km2
Versionstabell:
*** 0.8.5~pre1-0ubuntu1~km2 0
500 http://packages.kennynet.co.uk jaunty-testing/main Packages
100 /var/lib/dpkg/status
0.8.4a-0ubuntu5 0
500 http://se.archive.ubuntu.com jaunty/universe Packages

mediasmurf@mediasmurf:~$ cat /etc/lircd.conf
[...snip...]
include “/usr/share/lirc/remotes/imon/lircd.conf.imon-antec-veris”

mediasmurf@mediasmurf:~$ apt-cache policy lcdproc
lcdproc:
Installerad: 0.5.2-0ubuntu3~ppa2~km2
Kandidat: 0.5.2-0ubuntu3~ppa2~km2
Versionstabell:
*** 0.5.2-0ubuntu3~ppa2~km2 0
500 http://packages.kennynet.co.uk jaunty-testing/main Packages
100 /var/lib/dpkg/status
0.5.2-0ubuntu2 0
500 http://se.archive.ubuntu.com jaunty/universe Packages

mediasmurf@mediasmurf:~$ grep “Driver=” /etc/LCDd.conf
Driver=imonlcd

mediasmurf@mediasmurf:~$ grep -A5 “[imonlcd]” /etc/LCDd.conf
## SoundMon iMon LCD
[imonlcd]
# Specify which iMon protocol should be used [default: 0=15c2:ffdc device; legal: 1=15c2:0038 device]
Protocol=1
# Set the exit behavior [default: 1=show the big clock; legal: 0=leave shutdown message, 2=blank device and turn backlight off]
OnExit=2
# Select the output device to use [default: /dev/lcd0]
Device=/dev/lcd0
# Select the displays contrast [default: 200; legal: 0-1000]
Contrast=200
# Specify the size of the display in pixels [default:96x16]
Size=96×16
# Set the backlight state [default: 1=on; legal: 0=off]
Backlight=1
# Set the disc mode [default: 0=spin the "slim" disc - two disc segments; legal: 1=their complement spinning]
#DiscMode=0

When I execute the last command, the entire LCDd.conf is pasted, not just the [imonlcd] section, could that have something to do with it? Maybe I forgot something somewhere when I edited the file, or is that expected behavior?

Any ideas?

Btw, I’m using kubuntu 9.04 (which I suppose is the same as ubuntu 9.04), if that makes a difference.

I removed all the lines in the lircd.conf except the include line, which were only comments, and rebooted, this is immediately after reboot:

mediasmurf@mediasmurf:~$ irw
01000000000002ee 00 KEY_VOLUMEDOWN Antec_Veris_Premiere
00010000000002ee 04 KEY_VOLUMEUP Antec_Veris_Premiere
^C
mediasmurf@mediasmurf:~$

The knob reacts, but nothing from the buttons.
“ps -ef | grep -i lirc” gives me:

mediasmurf@mediasmurf:~$ ps -ef | grep -i lirc
root 1598 1 0 15:30 ? 00:00:00 /usr/sbin/lircd –device=/dev/lirc0
root 2997 1 0 15:30 ? 00:00:00 /usr/sbin/lircd –driver=default –device=/dev/lirc0 –pidfile=/var/run/lirc0.pid –listen=8765
root 2999 1 0 15:30 ? 00:00:01 /usr/sbin/lircd –driver=default –device=/dev/lirc1 –pidfile=/var/run/lirc1.pid –output=/dev/lircd –connect=localhost 8765
1000 3570 3515 0 15:34 pts/1 00:00:00 grep -i lirc
mediasmurf@mediasmurf:~$

I played around for a bit, and found this:

1. Killing LCDd doesn’t affect lirc (expected)

mediasmurf@mediasmurf:~$ sudo /etc/init.d/LCDd stop
Stopping LCDd: LCDd.
mediasmurf@mediasmurf:~$ ps -ef | grep -i lirc
root 1598 1 0 15:30 ? 00:00:00 /usr/sbin/lircd –device=/dev/lirc0
root 2997 1 0 15:30 ? 00:00:00 /usr/sbin/lircd –driver=default –device=/dev/lirc0 –pidfile=/var/run/lirc0.pid –listen=8765
root 2999 1 0 15:30 ? 00:00:02 /usr/sbin/lircd –driver=default –device=/dev/lirc1 –pidfile=/var/run/lirc1.pid –output=/dev/lircd –connect=localhost 8765
1000 3583 3515 0 15:35 pts/1 00:00:00 grep -i lirc
mediasmurf@mediasmurf:~$ irw
01000000000002ee 00 KEY_VOLUMEDOWN Antec_Veris_Premiere
00010000000002ee 00 KEY_VOLUMEUP Antec_Veris_Premiere
^C

2. Killing lirc, irw doesn’t work and the processes go away and the modules get unloaded (also expected)

mediasmurf@mediasmurf:~$ sudo /etc/init.d/lirc-imon stop
Stopping lirc-imon…done.
mediasmurf@mediasmurf:~$ irw
connect: Connection refused
mediasmurf@mediasmurf:~$ ps -ef | grep -i lirc
1000 3621 3515 0 15:36 pts/1 00:00:00 grep -i lirc
mediasmurf@mediasmurf:~$ lsmod | grep -i lirc

3. Starting lirc back up, only one process is found (is this expected?)

mediasmurf@mediasmurf:~$ sudo /etc/init.d/lirc-imon start
Starting lirc-imon…done.
mediasmurf@mediasmurf:~$ ps -ef | grep -i lirc
root 3693 1 0 15:36 ? 00:00:00 /usr/sbin/lircd –device=/dev/lirc0
1000 3695 3515 0 15:36 pts/1 00:00:00 grep -i lirc
mediasmurf@mediasmurf:~$

4. Starting LCDd back up, still only one process (is this expected?):

mediasmurf@mediasmurf:~$ sudo /etc/init.d/LCDd start
Starting LCDd: LCDd.
mediasmurf@mediasmurf:~$ ps -ef | grep -i lirc
root 3693 1 0 15:36 ? 00:00:00 /usr/sbin/lircd –device=/dev/lirc0
1000 3707 3515 0 15:39 pts/1 00:00:00 grep -i lirc
mediasmurf@mediasmurf:~$

5. Running irw, now the knob doesn’t react (probably since there is only one process?)

mediasmurf@mediasmurf:~$ irw
^C
mediasmurf@mediasmurf:~$

6. Restarting lirc, with LCDd still running (hence the FATAL warning), the process get started:

mediasmurf@mediasmurf:~$ sudo /etc/init.d/lirc-imon restart
Stopping lirc-imon…FATAL: Module lirc_imon is in use.
done.
Starting lirc-imon…done.
mediasmurf@mediasmurf:~$ ps -ef | grep -i lirc
root 3693 1 0 15:36 ? 00:00:00 /usr/sbin/lircd –device=/dev/lirc0
root 3893 1 0 15:41 ? 00:00:00 /usr/sbin/lircd –driver=default –device=/dev/lirc0 –pidfile=/var/run/lirc0.pid –listen=8765
root 3895 1 0 15:41 ? 00:00:00 /usr/sbin/lircd –driver=default –device=/dev/lirc1 –pidfile=/var/run/lirc1.pid –output=/dev/lircd –connect=localhost 8765
1000 3897 3515 0 15:41 pts/1 00:00:00 grep -i lirc
mediasmurf@mediasmurf:~$

7. And, as expected, the knob works:

mediasmurf@mediasmurf:~$ irw
01000000000002ee 00 KEY_VOLUMEDOWN Antec_Veris_Premiere
00010000000002ee 00 KEY_VOLUMEUP Antec_Veris_Premiere
^C
mediasmurf@mediasmurf:~$

Is all this expected behavior? Or should lirc start all three processes from the beginning, or atleast when LCDd is started? Or is LCDd supposed to be required to start first, to get lirc to start all its processes?

The bottom line is, the knob works when I boot up, but the buttons don’t, and they wont fire any events even after removing the lines. Any more suggestions?

Perhaps I have some paths wrong, so it’s looking in the wrong place? Seems unlikely since the knob is working, and the LCD is working (I suppose, haven’t really tested it).

Also, could this all be due to a hardware/wiring issue?
I have an antec fusion remote silver/black (http://www.antec.com/Believe_it/product.php?id=NzE3), and the first time I tried to fix this I followed another guide (http://www.avenard.org/media/Patches_&_Add-Ons/Entries/2009/4/10_LIRC_to_work_with_Antec_Fusion_Remote_Black_%28jaunty%29.html) and got the remote working (irw gave me output, never tried the knob though), but then did some fiddling inside the case, trying to get the remote to start the system, and haven’t gotten it working inside ubuntu/kubuntu after that. I can power up/down the system though, and therefore I know the IR and remote is working.

Arr, I’m all out of ideas here.

Atleast I got the LCD displaying system info (however it doesn’t look the way I want it, probably ’cause the display is so friggin small (actually, the display isn’t but the part that is used is)). Some progress, atleast.

Yep, tried it, didn’t work. :/

Hi Kenny,

Is your patch required for karmic still? If so, do you plan to make a package for that as well?

Thanks,

/klaus