From: Jarod W. <ja...@wi...> - 2009-06-27 14:10:02
|
On Jun 23, 2009, at 5:32 PM, eddy_crim wrote: > > Hi guys im really struggling geting this compro remote going. I > think i must > be missing something. Any pointers would be greatly appreciated. > > Im on a plain ubuntu jaunty 9.0.4 setup > > so > > lsusb | grep Compro > > returns > > Bus 001 Device 002: ID 185b:3082 Compro > > I check out the latest cvs from LIRC > > i open ~/lirc/drivers/lirc_mceusb2/lirc_mceusb2.c > > and i can see that the device listed in the file > > i run ./lirc/autogen.sh -runs without error > I run ./lirc/setup.sh - select option 1->8(usb device) ->x (MCE new > version) > in option 2 (software config) i leave the defaults > save and run configure > make ( lots happens here but i dont see any errors) > sudo make install seems to install fine > > sudo rmmod lirc_mceusb2 > sudo modprobe lirc_mceusb2 > > /var/log/messages gives me > > Jun 23 22:07:44 ed-media kernel: [ 2155.660313] usbcore: deregistering > interface driver lirc_mceusb2 > Jun 23 22:08:25 ed-media kernel: [ 2197.122890] > Jun 23 22:08:25 ed-media kernel: [ 2197.122895] lirc_mceusb2: > Philips eHome > USB IR Transceiver and Microsoft MCE 2005 Remote Control driver for > LIRC > $Revision: 1.51 $ > Jun 23 22:08:25 ed-media kernel: [ 2197.122899] lirc_mceusb2: Daniel > Melander <li...@ra...>, Martin Blatter > <mar...@ya...> > Jun 23 22:08:25 ed-media kernel: [ 2197.126473] usbcore: registered > new > interface driver lirc_mceusb2 > > then i sudo /etc/init.d/lirc restart > > if i do a mode2 -d /dev/licr0 i get nothing im afraid > > am i missing something obvious? Yep. It looks like the lirc_mceusb2 that shipped with your distro is being loaded when you modprobe, instead of the one you built. There should be output along the lines of... lirc_mceusb2[2]: SMK CORPORATION MCE TRANCEIVR Emulator Device 2006 on usb5:2 ...in your log. (The above is from one of my own mceusb2 devices). If you look at the output of 'modinfo lirc_mceusb2', you should see an alias line for your device if you're loading the right module. If not, its gotta be the old one. After you installed the updated kernel module, did you run depmod? Worst-case, you might need to move the stock one out of the way entirely and run depmod again (or overwrite the original w/the new), but sane distros should be set up such that the path the hand-built module lands in overrides the shipped module. I tend to just drop hand- built kernel modules into /lib/modules/<kver>/extra/ myself, then run depmod, and be on my way. -- Jarod Wilson ja...@wi... |