Struggling with Philips OVU4120 and RC197 on Linux - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111) +---- Forum: Linux (https://forum.kodi.tv/forumdisplay.php?fid=52) +---- Thread: Struggling with Philips OVU4120 and RC197 on Linux (/showthread.php?tid=112782) |
Struggling with Philips OVU4120 and RC197 on Linux - evilweasil - 2011-10-19 Hi All, I really hope someone can help. I've recently bought an Acer Aspire Revo and installed the latest version of XBMC from the live disk. Initially I planned on using my iPhone to control it, but that quickly proved to be a bad idea, so I decided to buy a remote. A Dell remote came up on eBay, and with it being almost identical to the Philips SRM 5100, I decided to go for it, especially after reading that it should work straight out of the box. Alas, it didn't. So, I think I've narrowed it down to something, although I don't know what that something is. The following is a few things I've found: Lirc is installed and it's running on version 0.8.6 andy@XBMCLive:~$ lsusb Bus 002 Device 005: ID 0471:2093 Philips So the device is recognised by the USB bus, but it's not listed in /proc/bus/input/devices: andy@XBMCLive:~$ cat /proc/bus/input/devices I: Bus=0019 Vendor=0000 Product=0001 Version=0000 N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0 U: Uniq= H: Handlers=kbd event0 B: EV=3 B: KEY=100000 0 0 0 I: Bus=0019 Vendor=0000 Product=0001 Version=0000 N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: EV=3 B: KEY=100000 0 0 0 I: Bus=0017 Vendor=0001 Product=0001 Version=0100 N: Name="Macintosh mouse button emulation" P: Phys= S: Sysfs=/devices/virtual/input/input2 U: Uniq= H: Handlers=mouse0 event2 B: EV=7 B: KEY=70000 0 0 0 0 0 0 0 0 B: REL=3 I: Bus=0001 Vendor=10ec Product=0662 Version=0001 N: Name="HDA Digital PCBeep" P: Phys=card0/codec#0/beep0 S: Sysfs=/devices/pci0000:00/0000:00:08.0/input/input3 U: Uniq= H: Handlers=kbd event3 B: EV=40001 B: SND=6 Does anyone know why it wouldn't show here? Have I done something wrong? All I did was plug in, find it didn't work, then google to the high heavens! The only thing I can think to blame is the receiver itself as nothing happened when I plugged it into my MacBook….but that isn't really conclusive evidence. I have no windows machine to test with. Thanks in advance guys, any questions just let me know. Edit: I'm running Kernel 2.6.32-29 Bump - evilweasil - 2011-10-22 Bit of a bump, I'm really stuck on this... - boosted - 2011-10-22 Can you see any reference to it in dmesg also does 'irw' display the key codes. Also post '/etc/lirc/hardware.conf' and 'etc/lirc/lircd.conf' Files might be in '/etc' if running slackware. When you installed lirc did it ask what type of reciever you have? - evilweasil - 2011-10-22 Hi, I haven't got that far yet. irw yeilds nothing. Dmesg reads as follows: usb 2-4: new full speed USB device using ohci_hcd and address 4 usb 2-4: configuration #1 chosen from choice 1 and it just stops there. I've seen much more detailed outputs from other people that show info about the remote, but this is all I get. Any ideas? /etc/lirc/hardware.conf Just the basic config for now, does this need to be modified for the kernel to recognise the remote when I plug it in? If yes then this is what I need to play with. Does anyone have the right config for my remote? Thanks for your help, it is greatly appreciated. - vikjon0 - 2011-10-22 I have a RC197 and it works out of the box. Did you install or touch anything at all? Of course the receiver could be different from mine and then it is a different ball game. - boosted - 2011-10-23 evilweasil Wrote:Hi, Can you unplug / plug the receiver in and post dmesg output - just the part for the receiver. copy of # /etc/lirc/hardware.conf # #Chosen Remote Control REMOTE="Windows Media Center Transceivers/Remotes (all)" REMOTE_MODULES="lirc_dev mceusb" REMOTE_DRIVER="" REMOTE_DEVICE="/dev/lirc0" REMOTE_SOCKET="" REMOTE_LIRCD_CONF="mceusb/lircd.conf.mceusb" REMOTE_LIRCD_ARGS="" #Chosen IR Transmitter TRANSMITTER="None" TRANSMITTER_MODULES="" TRANSMITTER_DRIVER="" TRANSMITTER_DEVICE="" TRANSMITTER_SOCKET="" TRANSMITTER_LIRCD_CONF="" TRANSMITTER_LIRCD_ARGS="" #Enable lircd START_LIRCD="true" #Don't start lircmd even if there seems to be a good config file #START_LIRCMD="false" #Try to load appropriate kernel modules LOAD_MODULES="true" # Default configuration files for your hardware if any LIRCMD_CONF="" #Forcing noninteractive reconfiguration #If lirc is to be reconfigured by an external application #that doesn't have a debconf frontend available, the noninteractive #frontend can be invoked and set to parse REMOTE and TRANSMITTER #It will then populate all other variables without any user input #If you would like to configure lirc via standard methods, be sure #to leave this set to "false" FORCE_NONINTERACTIVE_RECONFIGURATION="false" START_LIRCMD="" and # /etc/lirc/lircd.conf #Configuration for the Windows Media Center Transceivers/Remotes (all) remote: include "/usr/share/lirc/remotes/mceusb/lircd.conf.mceusb" - evilweasil - 2011-10-25 Hi there, I've updated my hardware.conf to the same given, and it still returns the following: usb 2-4: new full speed USB device using ohci_hcd and address 4 usb 2-4: configuration #1 chosen from choice 1 - boosted - 2011-10-26 evilweasil Wrote:Hi there, Was that what you got from dmesg? Did you restart 'lirc' or reboot? You may need to get help from someone with the same setup. Found this http://forum.xbmc.org/showthread.php?tid=45346 - evilweasil - 2011-10-26 Sorry about the short last post, I was in a serious rush. Anyway, yes the output was from dmesg, and it just won't go beyond: usb 2-4: configuration #1 chosen from choice 1 I've seen much more detailed outputs where the kernel recognises the receiver, but mine just seems to give up *shrug* I rebooted the machine after the reconfig of hardware.conf, so I have no idea what's going on. I'm wondering if my kernel has the built in modules of the 2.6.38 kernels :-S no idea, I'm obviously clutching at straws here! - evilweasil - 2011-10-26 AH HA! Ok, I've just found something new: When running /etc/init.d/lirc start * Loading LIRC modules ...done. * Unable to load LIRC kernel modules. Verify your * selected kernel modules in /etc/lirc/hardware.conf Ideas? So hardware.conf says: # /etc/lirc/hardware.conf # #Chosen Remote Control REMOTE="Windows Media Centre Transceivers/Remote (All)" REMOTE_MODULES="lirc_dev mceusb" REMOTE_DRIVER="" REMOTE_DEVICE="/dev/lirc0" REMOTE_LIRCD_CONF="mceusb/lircd.conf.mceusb" REMOTE_LIRCD_ARGS="" I've removed the rest as it's exactly as above. I hope this sheds some new light on the scenario.... - evilweasil - 2011-10-27 Broken again: Modified the following: REMOTE_MODULES="lirc_dev mceusb" to REMOTE_MODULES="lirc_dev lirc_mceusb" and lirc start worked, but the receiver still isn't recognised. - balrog74 - 2011-12-03 I have the same remote, off ebay china as well. I'm using the XBMC live installation on a new gigabyte i3 board, os is only modified to accept my newer nVidia vid card. Bus 002 Device 005: ID 0471:2093 Philips I rebuilt the module per https://help.ubuntu.com/community/LIRC so now the mod loads, but I cannot get any output of irw /dev/lircd. If I plug it into a winders box it works fine so I know it's not a bum device. This is the line I added to /usr/src/lirc-0.8.6/drivers/lirc_mceusb/lirc_mceusb.c /* Philips Infrared Transceiver - DELL branded */ { USB_DEVICE(VENDOR_PHILIPS, 0x2093) }, After this the module loads when restarting lirc but nada else, Ideas? |