<br><br>
<div class="gmail_quote">On Fri, Mar 28, 2008 at 12:02 AM, Phill Edwards <<a href="mailto:philledwards@gmail.com">philledwards@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="Ih2E3d">> It just so happens I made a post last night about how to do this on debian.<br>> <a href="http://codeka.com/forums/viewtopic.php?f=3&t=23&start=30#p213" target="_blank">http://codeka.com/forums/viewtopic.php?f=3&t=23&start=30#p213</a><br>
<br></div>Thanks for that. It doesn't seem to prevent the device being<br>recognised as when I do lsusb it's still there even after a reboot. </blockquote>
<div> </div>
<div>lsmod tells you the kernel modules loaded, </div>
<div> </div>
<div>lsusb will show you all devices on usb, even if they dont have a kernel driver loaded. the driver loaded determines how it functions</div>
<div> </div>
<div>you would have to check <a href="http://lirc.org">lirc.org</a> to check for instructions for your specific remote. and reciever.</div>
<div> </div>
<div>My Remote is an ATI Remote Wonder, </div>
<div> </div>
<div>lspci shows </div>
<div>Bus 001 Device 003: ID 0bc7:0004 X10 Wireless Technology, Inc. X10 Receiver<br></div>
<div>I check dmesg to see what kernel module loads when I plug in the reciever and if its not lirc_atiusb I blacklist it (I dont remember what it used to come up us, typicall usb-hid of some form making sure you arent using a usb keyboard or mouse that would need that module) then setup lirc to start loading the module for your specific device, </div>
<div> </div>
<div> </div></div>