On 4/1/2010 11:15 AM, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2010-04-01 18:02, Marc Chamberlin wrote:
So, I am being advised to stop using the ir_kbd_i2c module and use the older lirc_i2c module instead. (also according to the LIRC website I am suppose to install the lirc_dev module also) Since I am not an expert on managing kernel modules, my research leads me to believe I use the following commands to accomplish this -
rmmod ir_kbd_i2c insmod lirc_i2c insmod lirc_dev
or should I use
modprobe -r ir_kbd_i2c modprobe lirc_i2c modprobe lirc_dev
Not sure what the difference between these commands are exactly... And tinkering with the kernel kinda makes me nervous!
At the very worst the system would crash, and I doubt it. At normal worst, if things go bad you could loose use of the remote, which is no big deal, and perhaps have to reboot to recover to a "known status". Changes are not permanent, just the current runtime. Fear not :-)
The first group of commands remove/load kernel modules (from memory) directly, no questions asked. The second group ask a few questions (of the config files) and may load/unload other modules it thinks are needed to complete the request.
More in the respective manual pages.
About your main question, how to get the remote working, sorry, no idea.
Thanks Carlos for replying, I always feel it is a good idea to get second opinions before I do something that I don't fully understand... So I took the plunge and removed the kernel module ir_kbd_i2c and installed the two kernel modules lirc_i2c and lirc_dev. Changed the config file /etc/sysconfig/lirc manually to use the lirc_i2c module and restarted the lirc daemon... No Joy! Now nothing from my remote is recognized anymore and I believe the rest of my lirc configuration files are correct... So I am stuck! and dunno what to try next... Any lirc gurus around? Marc...