Kodi Community Forum

Full Version: Cyberlink Remote
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hi to all.
I have this Cyberlink Remote:

Image

I read this topic, i compile & run cyberlinkusb software, but simply say "Cyberlink not connected.". I think i have a different remote control, for this i open a new topic.

I'm newbie about Linux and this kind of howto...
I understand that remote are visibile under 2 different "event device", but XBMC doesn't work, absolute no keys at all.

... What i can do? I'm out of ideas...

Thanks!

XBMC: 9.04.3 +svn24207
HW: Acer Revo (ION)
SO: Ubuntu 9.10
Kernel: 2.6.31-14-generic // uname -r

/proc/bus/input/devices :
(with 3 usb port used: keyboard, mouse, CyberLink Infrared)
Code:
root@htpczz:~# cat /proc/bus/input/devices
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/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=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0C: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=0003 Vendor=04f2 Product=0402 Version=0111
N: Name="Chicony USB Keyboard"
P: Phys=usb-0000:00:04.0-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:04.0/usb2/2-1/2-1:1.0/input/input3
U: Uniq=
H: Handlers=kbd event3
B: EV=120013
B: KEY=10000 7 ff9f207a c14057ff febeffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=04f2 Product=0402 Version=0111
N: Name="Chicony USB Keyboard"
P: Phys=usb-0000:00:04.0-1/input1
S: Sysfs=/devices/pci0000:00/0000:00:04.0/usb2/2-1/2-1:1.1/input/input4
U: Uniq=
H: Handlers=kbd event4
B: EV=13
B: KEY=2000000 387a d801d001 1e0000 0 0 0
B: MSC=10

I: Bus=0003 Vendor=046d Product=c058 Version=0111
N: Name="Logitech USB Optical Mouse"
P: Phys=usb-0000:00:04.0-3/input0
S: Sysfs=/devices/pci0000:00/0000:00:04.0/usb2/2-3/2-3:1.0/input/input5
U: Uniq=
H: Handlers=mouse1 event5
B: EV=17
B: KEY=ff0000 0 0 0 0 0 0 0 0
B: REL=143
B: MSC=10

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/input6
U: Uniq=
H: Handlers=kbd event6
B: EV=40001
B: SND=6
Sorry to be the barer of bad news but I don't think that tutorial is going to help you.

That tutorial is all about the device that shows up as a "TopSeed Tech Corp. USB IR Combo Device"

Like so:
Code:
I: Bus=0003 Vendor=0766 Product=0204 Version=0100
N: Name="TopSeed Tech Corp. USB IR Combo Device "
P: Phys=usb-0000:00:02.0-7/input0
S: Sysfs=/devices/pci0000:00/0000:00:02.0/usb2/2-7/2-7:1.0/input/input5
U: Uniq=
H: Handlers=kbd event5
B: EV=120013
B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=1f

I: Bus=0003 Vendor=0766 Product=0204 Version=0100
N: Name="TopSeed Tech Corp. USB IR Combo Device "
P: Phys=usb-0000:00:02.0-7/input1
S: Sysfs=/devices/pci0000:00/0000:00:02.0/usb2/2-7/2-7:1.1/input/input6
U: Uniq=
H: Handlers=kbd mouse2 event6
B: EV=17
B: KEY=fc112 20d0c0000000000 70000 18000 21f8d001d804 9e004000000000 0
B: REL=103
B: MSC=10
And looks more like this:
Image

However lets have a look see if there is any chance whatsoeverer:
Can you start by doing the following steps:
  • Restart the PC without the keyboard not attached
  • Run "cat /proc/bus/input/devices" on the command line
  • Restart the PC without the keyboard attached
  • Run "cat /proc/bus/input/devices" on the command line
    (this should show if the device is being detected at all)
  • run lsusb on the command line
  • sudo su
    (this will make you root)
  • cd /sys/kernel/debug/usb/usbmon
  • ls
    (at this point you should see a few items like 1u 2u 1s etc)
  • cat some of these devices, see if any of them only provide output when you press buttons on the remote.
  • apt-get pastebinit
  • dmesg | pastebinit
  • paste the url given here.

We'll go from there, I wouldn't get your hopes up though. Without a highly skilled driver developer with a strong interest in fixing this problem it is unlikely to get resolved soon.
Thanks lozbrown85 for your feedback.
lozbrown85 Wrote:However lets have a look see if there is any chance whatsoeverer
cat /proc/bus/input/devices without anything connected to USB (i run from a remote SSH)
http://pastebin.com/m2f42cc

cat /proc/bus/input/devices with ONLY Cyberlink IR connected
http://pastebin.com/m133e1f83


.... mmm... bad news, any difference...

I try it on different USB port, same result.
I try on Windows machine, work out-of-the-box.

lsusb output:
Code:
Bus 001 Device 003: ID 0bda:0159 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 147a:e032 Formosa Industrial Computing, Inc.
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

ls /sys/kernel/debug/usb/usbmon
0s 0u 1s 1t 1u 2s 2t 2u

I don't think i need to "cat" them. If can be useful, please tell me and i do that.

dmesg | pastebinit
http://pastebin.com/f1d6d9c45

lozbrown85 Wrote:We'll go from there, I wouldn't get your hopes up though. Without a highly skilled driver developer with a strong interest in fixing this problem it is unlikely to get resolved soon.
In a "optimistic-mode" i bought 6 of this device, to control many htpc.
I want only to understand if a "hope" can exists, or it's simply better if a throw away.
If anyone can really investigate on this problem, i can send one of it (free, of course).

Thanks!
6 of them?

Crazy...


Its really not good news I'm afraid, the lack of the device in here would suggest that there isin even a driver in linux for this.

Nothing however is impossible... you could be the person to write a driver for this!!

Sounds like the main circuitry is manufactured by
Formosa Industrial Computing, Inc.

A bit of googleing finds the following articles:

The following links seem to point to someone writing a driver for another remote manufactured by Formosa:
http://www.qbik.ch/usb/devices/showdev.php?id=3863
http://web.mat.bham.ac.uk/R.W.Kaye/softw...102remote/
http://braithwaite.dk/wikka/ZolidIrRemote

I suggest you see what that does for you...

From here on I can only wish you luck!!
lozbrown85 Wrote:The following links seem to point to someone writing a driver for another remote manufactured by Formosa:
http://www.qbik.ch/usb/devices/showdev.php?id=3863
http://web.mat.bham.ac.uk/R.W.Kaye/softw...102remote/
http://braithwaite.dk/wikka/ZolidIrRemote

Some progress Big Grin

- I downloaded the driver from the last link above. Don't work, but...
- I done some changes to the c source-code: changing
Code:
#define USB_PRODUCT 0xe032
to a different code, and my remote expect 3 bytes signals, not 4, and other minor changes.
- "make" & run. It talk with UDP to Lirc.
- I run
Code:
irrecord -H udp "CyberLink"
and record a lirc configuration (only few classic buttons), and copied to /etc/lirc/lircd.conf
- i run the LIRC daemon with "lircd -n -H udp"
- i run "irw", it seems to work:
Code:
root@htpczz:~/Scrivania/irzol01-1.3rc1# irw
0000000000000002 00 KEY_DOWN CyberLink
0000000000000002 00 KEY_DOWN CyberLink
0000000000000002 00 KEY_DOWN CyberLink
0000000000000002 00 KEY_DOWN CyberLink
0000000000000002 00 KEY_DOWN CyberLink
0000000000000003 00 KEY_PLAY CyberLink
0000000000000003 00 KEY_PLAY CyberLink
- I follow the instruction here about changing the "Lircmap.xml" configuration.
- But... xbmc still don't work. In xbmc.log, i don't find anything about remote events (it's normal?)

I don't know how to continue... i checked 5 times that key names & remote names are equal in Lirc and Xbmc...

If under "irw" works, must work with XBMC, right? XBMC log some information like that? to understand if receive the command but can't interpretate that, or don't work at all...

Thanks for support! Big Grin
Under Windows XP, work without any drivers, are recognized as HID device, and automatically mapped as keyboard.
How it's possible? Or... why don't work under Ubuntu? I don't think XP contain informations about this kind of device, or code-mapping...

I want only this: mapped in a manner that Ubuntu see as keyboard...

Anyone has a link that i can study about HID devices under Ubuntu?