<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">Ok, we shall see if I finally figured out how to reply to a thread or if I just made a really<br>ugly looking new thread.<br><br>@Helen<br>I tried to get the tutorial to work based on what is on that page and you have said<br>but, I am a bit lost. Like I said, I am a complete noob when it comes to Linux so, baby<br>steps are the best thing for me. If you have something I can copy/paste, that would<br>be easiest for me. Thanks for the help so far by the way!<br><br>Here is what I have been able to do:<br><br>matthew@Matthew-DVR:~$ modinfo ir-kbd-i2c<br>filename:
/lib/modules/2.6.32-22-generic/kernel/drivers/media/video/ir-kbd-i2c.ko<br>license:
GPL<br>description: input driver for i2c IR remote controls<br>author:
Gerd Knorr, Michal Kochanowicz, Christoph Bartelmus, Ulrich Mueller<br>srcversion:
F6E0A1147E5A9580A049F6C<br>depends: ir-core,ir-common<br>vermagic:
2.6.32-22-generic SMP mod_unload modversions <br>parm:
debug:int<br>parm: hauppauge:Specify Hauppauge remote:
0=black, 1=grey (defaults to 0) (int)<br><br><br>I also got the files copied to /usr/local/bin via bastardizing some commands used for<br>updating the firmware on the mythtv 1600 page:<br><br>sudo cp hauppauge_remote.conf /usr/local/bin<br><br>sudo cp enable_hauppauge_remote.sh /usr/local/bin/<br><br>That all went well but below is where things kind of fell apart. Also, where do I find<br>this perpetual 0 to change to a 1 for my gray remote?<br><br>matthew@Matthew-DVR:~/Downloads/fix_hauppauge_remote$ sudo sh
enable_hauppauge_remote.sh<br>ERROR: Module ir_kbd_i2c is in use<br>ir_kbd_i2c
9735 1 - Loading 0xffffffffa00ef000<br>ir_common 6131 3
ir_kbd_i2c,cx88xx,bttv, Live
0xffffffffa05bf000<br>ir_core 15762 10
rc_hauppauge_new,ir_kbd_i2c,cx88xx,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,bttv,ir_rc5_decoder,ir_nec_decoder,ir_common,
Live 0xffffffffa05b4000<br><br>matthew@Matthew-DVR:~$ sudo rmmod ir-kbd-i2c<br>[sudo] password for
matthew: <br>ERROR: Module ir_kbd_i2c is in use<br>matthew@Matthew-DVR:~$
sudo rmmod ir-core<br>ERROR: Module ir_core is in use by
rc_hauppauge_new,ir_kbd_i2c,cx88xx,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,bttv,ir_rc5_decoder,ir_nec_decoder,ir_common<br>matthew@Matthew-DVR:~$
sudo rmmod ir-common<br>ERROR: Module ir_common is in use by
ir_kbd_i2c,cx88xx,bttv<br>matthew@Matthew-DVR:~$ sudo rmmod ir-kbd-i2c
-f<br>ERROR: Removing 'ir_kbd_i2c': Device or resource busy<br><br>Not sure if I just missed something or if there is some way for me to turn off all of those<br>dependent modules without having to find a way to rmmod each and every one of them.<br><br>Lastly, not sure if this helps but this is from a different tutorial that someone else posted<br>on ubuntuforums.org It was recommended if I had issues with it I should run the following<br>command and this is the result of it. As a note, I only have one keyboard hooked up and<br>am not using a Mac mouse so, I am unsure why those things load the way they do. I<br>was also able to reset my changes after the tutorial failed so I am back to where I<br>started off at.<br><br>matthew@Matthew-DVR:~$ cat /proc/bus/input/devices<br>I: Bus=0019 Vendor=0000 Product=0001 Version=0000<br>N: Name="Power Button"<br>P: Phys=PNP0C0C/button/input0<br>S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0<br>U:
Uniq=<br>H: Handlers=kbd event0 <br>B: EV=3<br>B: KEY=10000000000000 0<br><br>I: Bus=0019 Vendor=0000 Product=0001 Version=0000<br>N: Name="Power Button"<br>P: Phys=LNXPWRBN/button/input0<br>S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1<br>U: Uniq=<br>H: Handlers=kbd event1 <br>B: EV=3<br>B: KEY=10000000000000 0<br><br>I: Bus=0017 Vendor=0001 Product=0001 Version=0100<br>N: Name="Macintosh mouse button emulation"<br>P: Phys=<br>S: Sysfs=/devices/virtual/input/input2<br>U: Uniq=<br>H: Handlers=mouse0 event2 <br>B: EV=7<br>B: KEY=70000 0 0 0 0<br>B: REL=3<br><br>I: Bus=0003 Vendor=062a Product=0201 Version=0110<br>N: Name="USB-compliant keyboard"<br>P: Phys=usb-0000:00:13.0-1/input0<br>S: Sysfs=/devices/pci0000:00/0000:00:13.0/usb5/5-1/5-1:1.0/input/input3<br>U: Uniq=<br>H: Handlers=kbd event3 <br>B: EV=120013<br>B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe<br>B: MSC=10<br>B: LED=7<br><br>I: Bus=0003 Vendor=062a
Product=0201 Version=0110<br>N: Name="USB-compliant keyboard"<br>P: Phys=usb-0000:00:13.0-1/input1<br>S: Sysfs=/devices/pci0000:00/0000:00:13.0/usb5/5-1/5-1:1.1/input/input4<br>U: Uniq=<br>H: Handlers=kbd mouse1 event4 <br>B: EV=1f<br>B: KEY=fe00000 0 0 877fff002c3027 bf00444400000000 1 c040a27c000 267bfad941dfed 9e000000000000 0<br>B: REL=143<br>B: ABS=100000000<br>B: MSC=10<br><br>I: Bus=0003 Vendor=15d9 Product=0a4c Version=0111<br>N: Name=" USB OPTICAL MOUSE"<br>P: Phys=usb-0000:00:13.0-2/input0<br>S: Sysfs=/devices/pci0000:00/0000:00:13.0/usb5/5-2/5-2:1.0/input/input5<br>U: Uniq=<br>H: Handlers=mouse2 event5 <br>B: EV=17<br>B: KEY=70000 0 0 0 0<br>B: REL=103<br>B: MSC=10<br><br>I: Bus=0001 Vendor=10ec Product=0885 Version=0001<br>N: Name="HDA Digital PCBeep"<br>P: Phys=card0/codec#0/beep0<br>S: Sysfs=/devices/pci0000:00/0000:00:14.2/input/input6<br>U: Uniq=<br>H: Handlers=kbd event6 <br>B: EV=40001<br>B: SND=6<br><br><br>@D. Hugh
Redelmeier<br><br>My issue with simply getting it to work was a change I had to do during installation.<br>Basically, when I was installing it the first few times, way to many times by the way,<br>I kept installing the AMD graphical drivers rather than the open source ones. Finally,<br>on one of my final installs, it popped into my head to give it a try and that was issue<br>number 1. Other issues with sporadic operation were directly linked to the cx18 driver<br>itself. If I start and have no picture, which happens quite often, I need to rmmod then<br>modprobe cx18. However, after updating my v4l database, which did indeed complete<br>successfully without error, I need to rmmod cx18_alsa first because now apparently<br>alsa got lonely and decided to cling to cx18 for whatever reason. Then I rmmod cx18,<br>then modprobe cx18, then just for good measure, modprobe the clingy cx18_alsa.<br>That is what I have to do to get picture. To get sound after
picture is back, I just<br>power off/on my TV and audio then works. Oh, and shutdown/turn back on the backend<br>of course.<br></td></tr></table><br>