I am trying to setup the LIRC daemon so that I can use a Hauppauge PRV-350 remote to control my media center. Running SuSE 11.2 x86_64, KDE 4.4.2 and have been seeking advice on the mthyTV and LIRC groups. From what I have been able to grok, it appears that something is broke, both with how YaST is setting up the LIRC daemon and with a kernel module - ir-kbd-i2c When using the TV setup in YaST, it configures the /etc/sysconfig/lirc file with the LIRC_MODULE="ir_kbd_i2c" but it sets the LIRCD_DRIVER="/dev/lircd" I am being told that this LIRCD_DRIVER setting is wrong for usage with the ir_kbd_i2c kernel module. (I am told that /dev/lircd is the socket for the lirc daemon when using the lirc_i2c kernel module) Instead it should be something in /dev/input/??? I don't know what but in /dev/input there is a link called ir that links to /dev/input/event7 and guessing by the name "ir" (infrared???) that looks like a possible candidate?? As the LIRC configuration currently stands, using low level utilities such as xev, showkey -s and showkey -k I am finding an inconsistent pattern in what buttons are being recognized from the remote. All of these utilities recognize the numeric buttons and the volume up/down but what seems weird (to me) is that as for the rest of the buttons, some are recognized by each of these utilities but not the same set of buttons! Each recognizes a different set, even showkey -k and showkey -s respond to different sets of the buttons from my remote! To this non-expert that seems especially odd. What I am being told is that this is due to an improperly defined "key map" which is some kind of table in the ir_kbd_i2c module. Incidentally this ir_kbd_i2c is mapping the numeric buttons and the volume up/down into equivalent key strokes as can be seen by bringing up an empty shell and seeing the corresponding numeric letters being shown. (That, as I later found out, renders the utilities - ircat and irw useless (and confusing) in determining what the LIRC daemon is doing.) Incidentally, I also tried to follow the instructions given at http://www.mythtv.org/wiki/Ir-kbd-i2c to set the option for the hauppauge=1 as I am using the gray remote. - modprobe ir-kbd-i2c hauppauge=1 and I created the file named /etc/modprobe.d/hauppauge-remote containing the following line: options ir-kbd-i2c hauppauge=1 and when I restarted the lirc daemon it complained about the hauppauge-remote file not having a .conf extension. So I renamed that file and got no more complaints. I guess that the kernel and/or lirc daemon magically finds all .conf files in this directory and executes them??? Anywise bottom line is that this made no difference in what was being recognized from my remote... 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! So guess I thought I would ask for some expert guidance before I proceed any further... Someone apparently decided not to allow YaST to offer the usage of the lirc_i2c module as a fallback so to me that seems like a warning flag not to change the kernel. So what will I break if I do this, or am I on my own in some unexplored territory and left to experiment with my system? If I fallback to using the lirc_i2c module, I think I understand the rest of the process of setting up the lircd.conf and .lircrc files needed to get mythTV up and working with the remote.... Much appreciate any and all offers of advice/help in getting the remote to work... Marc...