Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
LIRC: irrecord is working...but irw is not
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Multimedia
View previous topic :: View next topic  
Author Message
mani001
Apprentice
Apprentice


Joined: 04 Dec 2004
Posts: 238
Location: Oleiros

PostPosted: Sun Feb 19, 2012 1:27 pm    Post subject: LIRC: irrecord is working...but irw is not Reply with quote

Hi,

I'm having a problem to properly setup lirc 0.8.7 with an Avermedia Volar X.
After loading the module dvb_usb_af9015, irrecord recognizes the remote and I was able to generate my own lircd.conf with
Code:

irrecord -H dev/input -f -d /dev/input/event9 /tmp/lircd.conf

Also, if I do
Code:

cat /dev/input/event9

and push buttons on the remote, I get a lot of crap on the screen (that means the remote is working, right?), but then if I start the lirc daemon
Code:

$lircd -n -H dev/input -d name=*DVB*
lircd-0.8.7[6871]: lircd(devinput) ready, using /var/run/lirc/lircd

and run irw, which is listened by the daemon at the sight of:
Code:

lircd-0.8.7[6871]: accepted new client on /var/run/lirc/lircd
lircd-0.8.7[6871]: initializing 'name=*DVB*'

it gets stuck waiting for input but shows nothing no matter what I press on the remote.

Funny enough, if I just run the lirc daemon and press a number it's echoed after the output of the daemon
Code:

$lircd -n -H dev/input -d name=*DVB*
lircd-0.8.7[7150]: lircd(devinput) ready, using /var/run/lirc/lircd
7781274666

and the volume keys even turn up or down the volume of the system (KDE) 8O

Any idea?

Greetings!!
Back to top
View user's profile Send private message
miroR
Apprentice
Apprentice


Joined: 05 Mar 2008
Posts: 228

PostPosted: Tue Apr 10, 2012 6:53 am    Post subject: Reply with quote

Little idea I might have, but so far, this post of yours is the closest cal to my attempts.
I'll try to post the relevant output here.

Code:
myBox # cat /proc/bus/input/devices
...[snip]...
I: Bus=0001 Vendor=0070 Product=1402 Version=0001
N: Name="cx88 IR (Hauppauge WinTV-HVR300"
P: Phys=pci-0000:05:15.0/ir0
S: Sysfs=/devices/pci0000:00/0000:00:1a.0/0000:05:15.0/rc/rc0/input4
U: Uniq=
H: Handlers=kbd event4
B: PROP=0
B: EV=100013
B: KEY=10afc312 214201700000000 0 118000 41a800004801 9e16c000000000 10000ffc
B: MSC=10

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="MCE IR Keyboard/Mouse (cx88xx)"
P: Phys=/input0
S: Sysfs=/devices/virtual/input/input5
U: Uniq=
H: Handlers=sysrq kbd mouse1 event5
B: PROP=0
B: EV=100017
B: KEY=30000 7 ff87207ac14057ff febeffdfffefffff fffffffffffffffe
B: REL=3
B: MSC=10


Here follow my attempts.
Code:
myBox # irrecord -H devinput pci-0000:05:15.0/ir0
irrecord: could not open file pci-0000:05:15.0/ir0
irrecord: No such file or directory
myBox # lircd -n -H dev/input -d name=*DVB*
lircd: there seems to already be a lircd process with pid 2554
lircd: otherwise delete stale lockfile /var/run/lirc/lircd.pid


Here I deleted that pid file in other konsole (and stopped the running /etc/init.d/lircd which I should've done first).
Code:

myBox # lircd -n -H dev/input -d name=*DVB*
lircd-0.9.0[4130]: lircd(devinput) ready, using /var/run/lirc/lircd
lircd-0.9.0[4130]: accepted new client on /var/run/lirc/lircd
lircd-0.9.0[4130]: initializing 'name=*DVB*'
lircd-0.9.0[4130]: unable to find 'name=*DVB*'
lircd-0.9.0[4130]: Failed to initialize hardware
^Clircd-0.9.0[4130]: caught signal
lircd-0.9.0[4130]: closing 'name=*DVB*'

myBox # lircd -n -H dev/input -d name="cx88 IR (Hauppauge WinTV-HVR300"
lircd-0.9.0[4162]: lircd(devinput) ready, using /var/run/lirc/lircd
lircd-0.9.0[4162]: accepted new client on /var/run/lirc/lircd
lircd-0.9.0[4162]: initializing 'name=cx88 IR (Hauppauge WinTV-HVR300'



During the attempts above I had a
Code:
myBox # irw

fired up in another konsole, but there was no nothing whatsoever to be seen, no garbage of the kind that would mean something, nothing at all.
While the irw actually is working, tested it on keyboard event (not shown).
And the batteries are fine in the remote, and I wonder, could it be what is hinted at:
/etc/conf.d/lircd
Code:
...[snip]...
# This should work, Bug #235107
#LIRCD_OPTS="-H devinput -d name=*DVB*"

more precisely is:
https://bugs.gentoo.org/show_bug.cgi?id=235107#c3
where it says how, translating for my card, this:

Code:
^Clircd-0.9.0[4162]: caught signal
lircd-0.9.0[4162]: closing '/dev/input/irremote'

myBox # lircd -n -H dev/input -d name="*WinTV-HVR300*"
lircd-0.9.0[4555]: lircd(devinput) ready, using /var/run/lirc/lircd
lircd-0.9.0[4555]: accepted new client on /var/run/lirc/lircd
lircd-0.9.0[4555]: initializing 'name=*WinTV-HVR300*'

That bug there is fixed, but I (yet) don't get it.
What should I do?
The card works fine otherwise. Remote used to work fine on it, as well. It is probably still fine...
Any ideas?
I'll be back. I need remote on my TV cards. I had it working months ago, but then something changed and the guides wouldn't work anymore... I spent days on it and didn't figure it out back then... Wish me luck! I need this!
Back to top
View user's profile Send private message
miroR
Apprentice
Apprentice


Joined: 05 Mar 2008
Posts: 228

PostPosted: Tue Apr 10, 2012 7:34 am    Post subject: Reply with quote

Similarly here:
http://www.mythtv.org/wiki/LIRC
(search for Gentoo)
the writer didn't get any output with irw...
So maybe I'm still on the right track.
On the other hand, the writer there says the modules
Quote:
lirc_dev and lirc_mceusb which are the old drivers. They aren't needed so I deleted them on my system to avoid confusion in the future. After that I restart lircd and irw and could see my keypresses being captured.

Should I try that?
I mean, I don't have the mceusb because mine is a PCI card (the remote though is likely same or similar, isn't it?), but I do have the other one, the lirc_dev module.

Code:

myBox # kmod list | grep lirc
ir_lirc_codec           4493  0
lirc_dev                9129  1 ir_lirc_codec
rc_core                11948  11 ir_nec_decoder,ir_rc5_decoder,ir_rc6_decoder,ir_jvc_decoder,cx88xx,ir_sony_decoder,ir_sanyo_decoder,ir_mce_kbd_decoder,ir_lirc_codec,rc_hauppauge
myBox #



Also, I am used to removing things bookishly (such as when the packege is done away with "emerge -C"...
Should I rather blacklist the lirc_dev?

Sorry it this is slow motion, I need to understand this, and at older age in life it doesn't work out so fast..

On the other hand, I don't get why I have the Microsoft MCE remote control listed, when I don't have one, if that is what this line from the /proc/bus/input/devices means:
Code:
N: Name="MCE IR Keyboard/Mouse (cx88xx)"

(pls. see in my previous post for more of that output)...
There I guess is something wrong.
But how do I correct it?
What do I do now?... Phew!
Back to top
View user's profile Send private message
miroR
Apprentice
Apprentice


Joined: 05 Mar 2008
Posts: 228

PostPosted: Tue Apr 10, 2012 7:45 am    Post subject: Reply with quote

Here's more. Crucial info:
https://bugs.gentoo.org/show_bug.cgi?id=345833
if that saves nerve wreckage to someone else, I'll be glad.
Soo... staging I go now and enable in the kernel.
Curently:
Code:
myBox # eselect kernel list
Available kernel symlink targets:
  [1]   linux-3.2.11-hardened
  [2]   linux-3.3.1-hardened
  [3]   linux-3.3.1-hardened-r1 *
myBox #

and
Code:
myBox # grep STAGING /boot/config-3.3.1-hardened-r1
# CONFIG_STAGING is not set
myBox #
Back to top
View user's profile Send private message
miroR
Apprentice
Apprentice


Joined: 05 Mar 2008
Posts: 228

PostPosted: Tue Apr 10, 2012 7:58 am    Post subject: Reply with quote

Code:
myBox linux # diff .config*
1836c1836
...[snip]...
< # CONFIG_IR_MCE_KBD_DECODER is not set
---
...[snip]...
> CONFIG_IR_MCE_KBD_DECODER=m
...[snip]...
1855c1855
< CONFIG_RC_LOOPBACK=m
---
> # CONFIG_RC_LOOPBACK is not set
2639,2703c2639
< CONFIG_STAGING=y
...[snip]...
< CONFIG_STAGING_MEDIA=y
...[snip]...
< CONFIG_LIRC_STAGING=y
myBox linux #

And I hope I'm closer to having control of my video playings without having to get up and run around...
Back to top
View user's profile Send private message
miroR
Apprentice
Apprentice


Joined: 05 Mar 2008
Posts: 228

PostPosted: Tue Apr 10, 2012 8:42 am    Post subject: Reply with quote

cat /var/log/daemon.log

Code:

...[snip]...
Apr 10 10:25:31 at8-g250-c lircd-0.9.0[3917]: lircd(devinput) ready, using /var/run/lirc/lircd
Apr 10 10:25:35 at8-g250-c lircd-0.9.0[3917]: accepted new client on /var/run/lirc/lircd
Apr 10 10:25:35 at8-g250-c lircd-0.9.0[3917]: initializing '/dev/input/by-path/pci-0000\:05\:15.1-event-ir'
Apr 10 10:25:35 at8-g250-c lircd-0.9.0[3917]: unable to open '/dev/input/by-path/pci-0000\:05\:15.1-event-ir'
Apr 10 10:25:35 at8-g250-c lircd-0.9.0[3917]: Failed to initialize hardware
Apr 10 10:25:58 at8-g250-c lircd-0.9.0[3917]: removed client
Apr 10 10:25:58 at8-g250-c lircd-0.9.0[3917]: closing '/dev/input/by-path/pci-0000\:05\:15.1-event-ir'

That above is at least saying more than so far (potentally getting me closer to what is still wrong).
OK, I got rid of the MCE which is not my hardware, but what is responsible for the lirc_dev and how to get rid of iti (if I understand the MythTV page correctly) in appropriate way?
Code:
# kmod list | grep lirc
ir_lirc_codec           4493  0
lirc_dev                9129  1 ir_lirc_codec
rc_core                11764  6 ir_rc5_decoder,ir_rc6_decoder,cx88xx,ir_lirc_codec,rc_hauppauge
#

I guess I didn't need rc6_decoder either... But I don't know really.
The /proc/bus/input/devices is slightly different, apart from no more mce there), "15.0" is changed to"15.1":

Code:

I: Bus=0001 Vendor=0070 Product=1402 Version=0001
N: Name="cx88 IR (Hauppauge WinTV-HVR300"
P: Phys=pci-0000:05:15.1/ir0
S: Sysfs=/devices/pci0000:00/0000:00:1a.0/0000:05:15.1/rc/rc0/input4
U: Uniq=
H: Handlers=kbd event4
B: PROP=0
B: EV=100013
B: KEY=10afc312 214201700000000 0 118000 41a800004801 9e16c000000000 10000ffc
B: MSC=10


So I change the line in /etc/conf.d/lircd to reflect that.

#LIRCD_OPTS="-H devinput -d /dev/input/by-path/pci-0000\:05\:15.0-event-ir"
LIRCD_OPTS="-H devinput -d /dev/input/by-path/pci-0000\:05\:15.1-event-ir"

But irw is still unresponsive.
Back to top
View user's profile Send private message
miroR
Apprentice
Apprentice


Joined: 05 Mar 2008
Posts: 228

PostPosted: Tue Apr 10, 2012 9:00 am    Post subject: Reply with quote

Similar to how this thread began, I issued the command
Code:
# irrecord -H dev/input -f -d /dev/input/event4 /tmp/lircd.conf

which after a while ends up like this:

Code:
...[snip]... Hold down an arbitrary button.
irrecord: gap not found, can't continue
irrecord: closing '/dev/input/event4'

irw giving nothing all throughout...

daemon.log giving those lines just the same, as well...

I can see more things to try, and how other thread like this one of mine, don't get solved...
http://forums.gentoo.org/viewtopic-p-6949120.html#6949120
But I'll try and be persistent for a longer while this time around.
This ruins my Linux experience if I don't solve it.
Help would be appreciated. Also, if someone knows beyond doubt this can not be done, and tells us, it will be counted as help.
Back to top
View user's profile Send private message
Matthijs70
n00b
n00b


Joined: 01 Oct 2006
Posts: 43
Location: the Netherlands

PostPosted: Tue Apr 10, 2012 7:32 pm    Post subject: Reply with quote

Yes.... I got it working but after reboot I have to manually set the correct keys etc again :-(

http://forums.gentoo.org/viewtopic-p-6948530.html

http://forums.gentoo.org/viewtopic-t-915966-highlight-irkeytable.html

PS (1) .. you do not need LIRC package as it's now part of the latest kernel (3 and up?).

PS (2) .. and NO, IRW command didn't work for me either. But still the keys work in x.org and I testes the key strokes with the command "ir-keytable -t".

PS (3) .. I use my remote with MythTV and it seems I had to remap all keys with the correct keyboard key (example KEY_STOP = KEY_ESC), like when you press the keyboard ... ;-)

Hope this points you in the correct direction.

Little note: I use the Hauppauge WinTV PVR-150, I think the most imported thing to check within x.org (if you use this) for the following lines:
Code:
[    93.496] (II) config/udev: Adding input device i2c IR (Hauppauge WinTV PVR-150 (/dev/input/event4)
[    93.496] (**) i2c IR (Hauppauge WinTV PVR-150: Applying InputClass "evdev keyboard catchall"
[    93.496] (II) Using input driver 'evdev' for 'i2c IR (Hauppauge WinTV PVR-150'
[    93.496] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
[    93.496] (**) i2c IR (Hauppauge WinTV PVR-150: always reports core events
[    93.496] (**) i2c IR (Hauppauge WinTV PVR-150: Device: "/dev/input/event4"
[    93.496] (--) i2c IR (Hauppauge WinTV PVR-150: Found keys
[    93.496] (II) i2c IR (Hauppauge WinTV PVR-150: Configuring as keyboard
[    93.496] (**) Option "config_info" "udev:/sys/devices/virtual/rc/rc0/input4/event4"
[    93.496] (II) XINPUT: Adding extended input device "i2c IR (Hauppauge WinTV PVR-150" (type: KEYBOARD, id 9)


PS .. sorry I had to edit this a view times ... to correct my mistakes and add more details to it ;-)
Back to top
View user's profile Send private message
miroR
Apprentice
Apprentice


Joined: 05 Mar 2008
Posts: 228

PostPosted: Tue Apr 10, 2012 7:57 pm    Post subject: Reply with quote

Matthijs70 wrote:
Yes.... I got it working but...
...[snip]...
...and add more details to it ;-)

Hi Matthijs70!
Your words are precious and I am now going to delve with all my might into your recount!
So, I wanted to say a big thanks in the first place!
Allow me for some time, since, you know, I'm not fresh, in my mid-fifties... :?
Back to top
View user's profile Send private message
miroR
Apprentice
Apprentice


Joined: 05 Mar 2008
Posts: 228

PostPosted: Tue Apr 10, 2012 8:14 pm    Post subject: Reply with quote

OK. Just before the gentle reply from Matthijs70, I also noticed that I missed other stuff.
This package was not installed (there was no ir-keytable). So I emerged it:
Code:
myBox # emerge -qavtuDN v4l-utils
[ebuild  N    ] media-tv/v4l-utils-0.8.6  USE="-qt4"

Now I get:
Code:
myBox # ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event4) with:
        Driver cx88xx, table rc-hauppauge
        Supported protocols: RC-5 RC-6 LIRC
        Enabled protocols: RC-5 RC-6 LIRC
        Repeat delay = 500 ms, repeat period = 125 ms
myBox # cat /sys/class/rc/rc0/protocols
[rc-5] [rc-6] [lirc]
myBox #


And now I go and change my (wrong) direction, to the right one.
I'll be back when I unmerge lirc, and do some more (latter days kind of) researches. :wink:
Back to top
View user's profile Send private message
miroR
Apprentice
Apprentice


Joined: 05 Mar 2008
Posts: 228

PostPosted: Tue Apr 10, 2012 8:55 pm    Post subject: Reply with quote

app-misc/lirc is uinmerged.
I left:
Code:

*  app-misc/inputlircd
      Latest version available: 0.0.1_pre15
      Latest version installed: 0.0.1_pre15

though.
Now, /var/log/Xorg.0.log
Code:
[    53.168] (II) config/udev: Adding input device cx88 IR (Hauppauge WinTV-HVR300 (/dev/in
put/event4)
[    53.168] (**) cx88 IR (Hauppauge WinTV-HVR300: Applying InputClass "evdev keyboard catc
hall"
[    53.168] (**) cx88 IR (Hauppauge WinTV-HVR300: Applying InputClass "keyboard-all"
[    53.168] (II) Using input driver 'evdev' for 'cx88 IR (Hauppauge WinTV-HVR300'
[    53.168] (**) cx88 IR (Hauppauge WinTV-HVR300: always reports core events
[    53.168] (**) evdev: cx88 IR (Hauppauge WinTV-HVR300: Device: "/dev/input/event4"
[    53.168] (--) evdev: cx88 IR (Hauppauge WinTV-HVR300: Vendor 0x70 Product 0x1402
[    53.168] (--) evdev: cx88 IR (Hauppauge WinTV-HVR300: Found keys
[    53.168] (II) evdev: cx88 IR (Hauppauge WinTV-HVR300: Configuring as keyboard
[    53.169] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/0000:05:15.1/rc/rc0/input4/event4"
[    53.169] (II) XINPUT: Adding extended input device "cx88 IR (Hauppauge WinTV-HVR300" (type: KEYBOARD, id 8)

But:
Code:
myBox # ir-keytable -t
Testing events. Please, press CTRL-C to abort.


is dumb, deadly dumb.

On the differences btwn your remote and mine. I had the one that you probably have, it's probably the so called gray.
Mine is the so called silver. I don't think there should be such difference. Both might be just similarly supported, Both are Philips IR RC5 (also refered to as RC-5) standard, I think, but that would need hours of googleing to make sure...
Left out of ideas what else to try now.
Back to top
View user's profile Send private message
miroR
Apprentice
Apprentice


Joined: 05 Mar 2008
Posts: 228

PostPosted: Tue Apr 10, 2012 9:10 pm    Post subject: Reply with quote

Currently:
Code:
myBox # emerge -pvt x11-base/xorg-server x11-base/xorg-drivers x11-drivers/xf86-input-evdev

These are the packages that would be merged, in reverse order:

Calculating dependencies... done!
[ebuild   R    ] x11-base/xorg-drivers-1.12  INPUT_DEVICES="evdev -acecad -aiptek -elographics -fpit -hyperpen -joystick -keyboard -mouse -mutouch -penmount -synaptics -tslib -vmmouse -void -wacom" VIDEO_CARDS="radeon -ark -ast -cirrus -dummy -epson -fbdev -fglrx (-geode) -glint -i128 (-i740) -intel -mach64 -mga -neomagic (-newport) -nouveau -nv (-nvidia) (-omapfb) -qxl -r128 -s3 -savage -siliconmotion -sis (-sunbw2) (-suncg14) (-suncg3) (-suncg6) (-sunffb) (-sunleo) (-suntcx) -tdfx -tga -trident -v4l -vesa -via -virtualbox -vmware (-voodoo)" 0 kB
[ebuild   R    ]  x11-drivers/xf86-input-evdev-2.7.0  0 kB
[ebuild   R    ]   x11-base/xorg-server-1.12.0-r1  USE="nptl udev xorg -dmx -doc -ipv6 -kdrive -minimal (-selinux) -static-libs -tslib -xnest -xvfb" 0 kB

Total: 3 packages (3 reinstalls), Size of downloads: 0 kB
myBox #

And I think, who knows, maybe the use flag v4l is needed for x11-base/xorg-drivers?
Won't be so expensive to try...
Added:
Code:
x11-base/xorg-drivers v4l

to package.use, but it doesn't do a thing... (it remains "-v4l" in emerge output).
But in absence of any clues, I'll reinstall those packages above anyway.
Back to top
View user's profile Send private message
miroR
Apprentice
Apprentice


Joined: 05 Mar 2008
Posts: 228

PostPosted: Tue Apr 10, 2012 10:17 pm    Post subject: Reply with quote

I do get this output.
I understand little of it.
Code:
myBox # ir-keytable -r
scancode 0x0000 = KEY_0 (0x0b)
scancode 0x0001 = KEY_1 (0x02)
scancode 0x0002 = KEY_2 (0x03)
scancode 0x0003 = KEY_3 (0x04)
scancode 0x0004 = KEY_4 (0x05)
scancode 0x0005 = KEY_5 (0x06)
scancode 0x0006 = KEY_6 (0x07)
scancode 0x0007 = KEY_7 (0x08)
scancode 0x0008 = KEY_8 (0x09)
scancode 0x0009 = KEY_9 (0x0a)
scancode 0x000c = KEY_RADIO (0x181)
scancode 0x000d = KEY_MUTE (0x71)
scancode 0x0010 = KEY_VOLUMEUP (0x73)
scancode 0x0011 = KEY_VOLUMEDOWN (0x72)
scancode 0x001e = KEY_RED (0x18e)
scancode 0x001f = KEY_TV (0x179)
scancode 0x0020 = KEY_CHANNELUP (0x192)
scancode 0x0021 = KEY_CHANNELDOWN (0x193)
scancode 0x0022 = KEY_VIDEO (0x189)
scancode 0x0026 = KEY_SLEEP (0x8e)
scancode 0x002e = KEY_ZOOM (0x174)
scancode 0x1d00 = KEY_0 (0x0b)
scancode 0x1d01 = KEY_1 (0x02)
scancode 0x1d02 = KEY_2 (0x03)
scancode 0x1d03 = KEY_3 (0x04)
scancode 0x1d04 = KEY_4 (0x05)
scancode 0x1d05 = KEY_5 (0x06)
scancode 0x1d06 = KEY_6 (0x07)
scancode 0x1d07 = KEY_7 (0x08)
scancode 0x1d08 = KEY_8 (0x09)
scancode 0x1d09 = KEY_9 (0x0a)
scancode 0x1d0a = KEY_TEXT (0x184)
scancode 0x1d0d = KEY_MENU (0x8b)
scancode 0x1d0f = KEY_MUTE (0x71)
scancode 0x1d10 = KEY_VOLUMEUP (0x73)
scancode 0x1d11 = KEY_VOLUMEDOWN (0x72)
scancode 0x1d12 = KEY_PREVIOUS (0x19c)
scancode 0x1d14 = KEY_UP (0x67)
scancode 0x1d15 = KEY_DOWN (0x6c)
scancode 0x1d16 = KEY_LEFT (0x69)
scancode 0x1d17 = KEY_RIGHT (0x6a)
scancode 0x1d1c = KEY_TV (0x179)
scancode 0x1d1e = KEY_NEXT (0x197)
scancode 0x1d1f = KEY_EXIT (0xae)
scancode 0x1d20 = KEY_CHANNELUP (0x192)
scancode 0x1d21 = KEY_CHANNELDOWN (0x193)
scancode 0x1d24 = KEY_LAST (0x195)
scancode 0x1d25 = KEY_OK (0x160)
scancode 0x1d30 = KEY_PAUSE (0x77)
scancode 0x1d32 = KEY_REWIND (0xa8)
scancode 0x1d34 = KEY_FASTFORWARD (0xd0)
scancode 0x1d35 = KEY_PLAY (0xcf)
scancode 0x1d36 = KEY_STOP (0x80)
scancode 0x1d37 = KEY_RECORD (0xa7)
scancode 0x1d3b = KEY_GOTO (0x162)
scancode 0x1d3d = KEY_POWER (0x74)
scancode 0x1d3f = KEY_HOME (0x66)
scancode 0x1e00 = KEY_0 (0x0b)
scancode 0x1e01 = KEY_1 (0x02)
scancode 0x1e02 = KEY_2 (0x03)
scancode 0x1e03 = KEY_3 (0x04)
scancode 0x1e04 = KEY_4 (0x05)
scancode 0x1e05 = KEY_5 (0x06)
scancode 0x1e06 = KEY_6 (0x07)
scancode 0x1e07 = KEY_7 (0x08)
scancode 0x1e08 = KEY_8 (0x09)
scancode 0x1e09 = KEY_9 (0x0a)
scancode 0x1e0a = KEY_TEXT (0x184)
scancode 0x1e0b = KEY_RED (0x18e)
scancode 0x1e0c = KEY_RADIO (0x181)
scancode 0x1e0d = KEY_MENU (0x8b)
scancode 0x1e0e = KEY_SUBTITLE (0x172)
scancode 0x1e0f = KEY_MUTE (0x71)
scancode 0x1e10 = KEY_VOLUMEUP (0x73)
scancode 0x1e11 = KEY_VOLUMEDOWN (0x72)
scancode 0x1e12 = KEY_PREVIOUS (0x19c)
scancode 0x1e14 = KEY_UP (0x67)
scancode 0x1e15 = KEY_DOWN (0x6c)
scancode 0x1e16 = KEY_LEFT (0x69)
scancode 0x1e17 = KEY_RIGHT (0x6a)
scancode 0x1e18 = KEY_VIDEO (0x189)
scancode 0x1e19 = KEY_AUDIO (0x188)
scancode 0x1e1a = KEY_CAMERA (0xd4)
scancode 0x1e1b = KEY_EPG (0x16d)
scancode 0x1e1c = KEY_TV (0x179)
scancode 0x1e1e = KEY_NEXTSONG (0xa3)
scancode 0x1e1f = KEY_EXIT (0xae)
scancode 0x1e20 = KEY_CHANNELUP (0x192)
scancode 0x1e21 = KEY_CHANNELDOWN (0x193)
scancode 0x1e24 = KEY_PREVIOUSSONG (0xa5)
scancode 0x1e25 = KEY_OK (0x160)
scancode 0x1e29 = KEY_BLUE (0x191)
scancode 0x1e2e = KEY_GREEN (0x18f)
scancode 0x1e30 = KEY_PAUSE (0x77)
scancode 0x1e32 = KEY_REWIND (0xa8)
scancode 0x1e34 = KEY_FASTFORWARD (0xd0)
scancode 0x1e35 = KEY_PLAY (0xcf)
scancode 0x1e36 = KEY_STOP (0x80)
scancode 0x1e37 = KEY_RECORD (0xa7)
scancode 0x1e38 = KEY_YELLOW (0x190)
scancode 0x1e3b = KEY_SELECT (0x161)
scancode 0x1e3d = KEY_POWER2 (0x164)
scancode 0x1f00 = KEY_0 (0x0b)
scancode 0x1f01 = KEY_1 (0x02)
scancode 0x1f02 = KEY_2 (0x03)
scancode 0x1f03 = KEY_3 (0x04)
scancode 0x1f04 = KEY_4 (0x05)
scancode 0x1f05 = KEY_5 (0x06)
scancode 0x1f06 = KEY_6 (0x07)
scancode 0x1f07 = KEY_7 (0x08)
scancode 0x1f08 = KEY_8 (0x09)
scancode 0x1f09 = KEY_9 (0x0a)
scancode 0x1f0b = KEY_RED (0x18e)
scancode 0x1f0c = KEY_RADIO (0x181)
scancode 0x1f0d = KEY_MENU (0x8b)
scancode 0x1f0f = KEY_MUTE (0x71)
scancode 0x1f10 = KEY_VOLUMEUP (0x73)
scancode 0x1f11 = KEY_VOLUMEDOWN (0x72)
scancode 0x1f1e = KEY_NEXTSONG (0xa3)
scancode 0x1f1f = KEY_EXIT (0xae)
scancode 0x1f20 = KEY_CHANNELUP (0x192)
scancode 0x1f21 = KEY_CHANNELDOWN (0x193)
scancode 0x1f24 = KEY_PREVIOUSSONG (0xa5)
scancode 0x1f25 = KEY_ENTER (0x1c)
scancode 0x1f29 = KEY_BLUE (0x191)
scancode 0x1f2e = KEY_GREEN (0x18f)
scancode 0x1f30 = KEY_PAUSE (0x77)
scancode 0x1f32 = KEY_REWIND (0xa8)
scancode 0x1f34 = KEY_FASTFORWARD (0xd0)
scancode 0x1f35 = KEY_PLAY (0xcf)
scancode 0x1f36 = KEY_STOP (0x80)
scancode 0x1f37 = KEY_RECORD (0xa7)
scancode 0x1f38 = KEY_YELLOW (0x190)
scancode 0x1f3b = KEY_SELECT (0x161)
scancode 0x1f3c = KEY_ZOOM (0x174)
scancode 0x1f3d = KEY_POWER2 (0x164)
Enabled protocols: RC-5
myBox #

The above seems fine, but I don't understand why the:
Code:
myBox  # ir-keytable -t
Testing events. Please, press CTRL-C to abort.
^C
myBox #

is dead mute?
What I will do now, is clone the system to another box with HVR-400 card (very similar).
That will further reduce the number of suspects for no work yet.
Back to top
View user's profile Send private message
miroR
Apprentice
Apprentice


Joined: 05 Mar 2008
Posts: 228

PostPosted: Wed Apr 11, 2012 2:15 am    Post subject: Reply with quote

Our cars are different.
http://www.mythtv.org/wiki/Hauppauge_PVR-150
probably with one of these:
http://www.mythtv.org/wiki/MCE_Remote
and mine:
http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-3000
and:
http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-4000
with the same remote (as the pictures show), but different than yours, probably.
And the remote hardware/drivers are not the same...
Back to top
View user's profile Send private message
Matthijs70
n00b
n00b


Joined: 01 Oct 2006
Posts: 43
Location: the Netherlands

PostPosted: Wed Apr 11, 2012 4:43 pm    Post subject: Reply with quote

Not sure... but I think you are much closer now...

This looks promising:
myBox # ir-keytable
Code:
Found /sys/class/rc/rc0/ (/dev/input/event4) with:
        Driver cx88xx, table rc-hauppauge
        Supported protocols: RC-5 RC-6 LIRC
        Enabled protocols: RC-5 RC-6 LIRC
        Repeat delay = 500 ms, repeat period = 125 ms


And your Xorg log looks also very good:
Code:
[    53.168] (II) config/udev: Adding input device cx88 IR (Hauppauge WinTV-HVR300 (/dev/input/event4)
[    53.168] (**) cx88 IR (Hauppauge WinTV-HVR300: Applying InputClass "evdev keyboard catchall"
[    53.168] (**) cx88 IR (Hauppauge WinTV-HVR300: Applying InputClass "keyboard-all"
[    53.168] (II) Using input driver 'evdev' for 'cx88 IR (Hauppauge WinTV-HVR300'
[    53.168] (**) cx88 IR (Hauppauge WinTV-HVR300: always reports core events
[    53.168] (**) evdev: cx88 IR (Hauppauge WinTV-HVR300: Device: "/dev/input/event4"
[    53.168] (--) evdev: cx88 IR (Hauppauge WinTV-HVR300: Vendor 0x70 Product 0x1402
[    53.168] (--) evdev: cx88 IR (Hauppauge WinTV-HVR300: Found keys
[    53.168] (II) evdev: cx88 IR (Hauppauge WinTV-HVR300: Configuring as keyboard
[    53.169] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/0000:05:15.1/rc/rc0/input4/event4"
[    53.169] (II) XINPUT: Adding extended input device "cx88 IR (Hauppauge WinTV-HVR300" (type: KEYBOARD, id 8)


To me it shows the IR module is detected and ready to use as keyboard or input device.

BTW ... what did you see in the kernel logging? Guess it just detect it correctly.

And I guess you also compiled your kernel with the correct settings? Also with the v4l (Video for Linux) part?

When I press any key on the remote when using "ir-keytable -t" I get:
Code:
ir-keytable -t
Testing events. Please, press CTRL-C to abort.
1334161936.855798: event MSC: scancode = 1e15
1334161936.855804: event key down: KEY_DOWN (0x006c)
1334161936.855807: event sync
1334161936.955800: event MSC: scancode = 1e15
1334161936.955803: event sync
1334161937.204255: event key up: KEY_DOWN (0x006c)
1334161937.204257: event sync
1334161937.655951: event MSC: scancode = 1e14
1334161937.655957: event key down: KEY_UP (0x0067)
1334161937.655960: event sync
1334161937.755793: event MSC: scancode = 1e14
1334161937.755797: event sync
1334161938.004254: event key up: KEY_UP (0x0067)
1334161938.004257: event sync
1334161938.255798: event MSC: scancode = 1e17
1334161938.255804: event key down: KEY_RIGHT (0x006a)
1334161938.255806: event sync
1334161938.504254: event key up: KEY_RIGHT (0x006a)
1334161938.504256: event sync
1334161938.655855: event MSC: scancode = 1e16
1334161938.655862: event key down: KEY_LEFT (0x0069)
1334161938.655864: event sync
1334161938.755798: event MSC: scancode = 1e16
1334161938.755801: event sync
1334161939.004254: event key up: KEY_LEFT (0x0069)
1334161939.004256: event sync


You must be close, but than again I have:
Kernel 3.2.1-gentoo-r2 (x86_64)
x11-drivers/xf86-input-evdev-2.6.0
media-tv/v4l-utils-0.8.5
media-tv/ivtv-1.2.0-r1
Hauppauge WinTV PVR-150

But easy it is not, I took me weeks to get it working :-(

Good luck,
Matthijs
Back to top
View user's profile Send private message
mani001
Apprentice
Apprentice


Joined: 04 Dec 2004
Posts: 238
Location: Oleiros

PostPosted: Wed Apr 11, 2012 7:33 pm    Post subject: Reply with quote

Hi,

I got it working now...furthermore, with a cheap (2 or 3 euros, if I remember correctly :) ) lousy remote

http://www.google.es/imgres?q=deal+extreme+remote+tv&um=1&hl=es&sa=N&biw=1680&bih=921&tbm=isch&tbnid=VEhYWrMgmComGM:&imgrefurl=http://www.wonkywelly.com/boxee.php&docid=iwOdQLOCPcyZDM&imgurl=http://www.wonkywelly.com/images/remote.JPG&w=395&h=601&ei=odmFT-GjGtCHhQfetYXMCA&zoom=1&iact=rc&dur=425&sig=116237945067033635291&page=2&tbnh=140&tbnw=93&start=45&ndsp=49&ved=1t:429,r:30,s:45,i:233&tx=35&ty=60

In the kernel I have under "Device Drivers"->"Multimedia support"->"Remote Controller Adapters":

<*> Compile Remote Controller keymap modules
<*> Enable IR raw decoder for the NEC protocol
<*> Enable IR to LIRC bridge

(I don't really know if all those are needed )

In /etc/conf.d/lirc, I have
Code:

LIRCD_OPTS="-H devinput -d /dev/input/by-id/usb-073a_2230-event-mouse"


Also, I added a file containing
Code:

Section "InputClass"
        Identifier "Ignore DealExtreme PC Remote"
        MatchProduct "073a:2230"
        Option "Ignore" "on"
EndSection

under /etc/xorg.conf.d, so that the device is ignored by Xorg

About "/etc/lirc/lircd.conf" I just downloaded a generic one from the lirc webpage (I gave up building one myself because irrecord was giving me a lot of troubles...)

Last, I'm using "stable" lirc 0.8.7

That's my two cents...

If you want more info about my setup or want me to try something, just let me know.

Cheers!!
Back to top
View user's profile Send private message
miroR
Apprentice
Apprentice


Joined: 05 Mar 2008
Posts: 228

PostPosted: Wed Apr 11, 2012 7:37 pm    Post subject: Reply with quote

I was a little unwell.
Acknowledging your kind reply.
As sadly is the truth, I need quite some time to work this out. I am working...
Thanks for the solidarity, dear Matthijs, the gentle Dutch!
Hopefully once we make it, others will benefit too. Hopefully...
I strongly favor GNU Linux over any OS whatsoever, for the freedom of it, and the benefit to everybody, without a minority profiteering of any kind (politically I am a tollerant rightwing, decisively right and strongly tollerant to my best!)!
May the Good and the Peace of the Universe be with all the readers!
Back to top
View user's profile Send private message
miroR
Apprentice
Apprentice


Joined: 05 Mar 2008
Posts: 228

PostPosted: Wed Apr 11, 2012 8:35 pm    Post subject: Reply with quote

Hi Mani!
mani001 wrote:
I got it working now...furthermore, with a cheap (2 or 3 euros, if I remember correctly :) ) lousy remote


Did you just mean:
http://www.wonkywelly.com/images/remote.JPG?

mani001 wrote:
In /etc/conf.d/lirc, I have
[code]
LIRCD_OPTS="-H devinput -d /dev/input/by-id/usb-073a_2230-event-mouse"

...[snip]...

If you want more info about my setup or want me to try something, just let me know.

Cheers!!

Your near concurrent reply (4 minutes difference, and I'm on Tor browser, because I just hate surveillance), has been acknowledged and will be studied!
Thanks, good Spaniard (if I'm correct), I might be needing some of your experience, but I really am slow at figuring out these hard exercises for my leaking old brain :x ! No, no, this simple one smiley: :) LOL... I mean, I have to go over some of those a few times to get it really... but it's OK.
Back to top
View user's profile Send private message
miroR
Apprentice
Apprentice


Joined: 05 Mar 2008
Posts: 228

PostPosted: Thu Apr 12, 2012 6:36 am    Post subject: Reply with quote

I did go through your suggestions and replies, both the Dutch and the Spaniard Gentoo friends of mine.
But I also had to take it wider.
And did find new stuff of interest.
First, I couldn't get any of my systems (three TV-card-on and one no-TV-card Gentoo linux cloned systems, perfectly cloned, anyone thinks could benefit from my experience, let me know!, same type MBO in all four and similar other hardware only)... But I was saying I couldn't get any of my systems to show satellite programs with the newest Gentoo kernel.
So that was a priority.
I think I am on the right track to solving that.
Have a look here:
http://hftom.free.fr/phpBB2/viewtopic.php?p=2190#2190
Esp. this link is very promissing:
http://mercurial.intuxication.org/hg/s2-liplianin/file/c02ee79e78e9/linux/Documentation/video4linux/CARDLIST.cx88
There not only both of my cards (in the same driver, and I remember having issues earlier to get the other TV-cards to work on the cloned drivers from the source system clone), both:
Code:
Hauppauge WinTV-HVR4000 DVB-S/S2/T/Hybrid

and
Code:
Hauppauge WinTV-HVR3000 TriMode Analog/DVB-S/DVB-T

But also:
Code:
Hauppauge WinTV-IR Only

Sure I now have to first investigate that with my slow-motion mind :x erhm :) !
Back to top
View user's profile Send private message
miroR
Apprentice
Apprentice


Joined: 05 Mar 2008
Posts: 228

PostPosted: Thu Apr 12, 2012 7:01 am    Post subject: Reply with quote

Oh, and this is also a weird info that leaves me still awonder.
http://www.mythtv.org/wiki/Digital_Tuner_Cards
Have a look at HVR-3000 and HVR-4000 and esp. whether their remote is supported?
Huh?
Heh, heh! Unknown for HVR-4000, supported for HVR-3000, and those are knowledgeable people who wrote that.
"This page was last modified on 3 November 2011." in bottom.
Fits in with the new liplianin drivers timing. I mean the page dates at previous time or around there to drivers being honed off by Igor the Russian.
Back to top
View user's profile Send private message
Matthijs70
n00b
n00b


Joined: 01 Oct 2006
Posts: 43
Location: the Netherlands

PostPosted: Thu Apr 12, 2012 8:01 am    Post subject: Reply with quote

So.. did you check the kernel log as suggested in the wiki? (see http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-3000)

Do I understand correctly that nothing is working on your Gentoo box? No satellite, no remote etc?
Back to top
View user's profile Send private message
miroR
Apprentice
Apprentice


Joined: 05 Mar 2008
Posts: 228

PostPosted: Thu Apr 12, 2012 10:18 am    Post subject: Reply with quote

Matthijs70 wrote:
So.. did you check the kernel log as suggested in the wiki? (see http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-3000)

That's one of the pages I know almost by heart. :x
Matthijs70 wrote:
Do I understand correctly that nothing is working on your Gentoo box? No satellite, no remote etc?

No! The old kernel, the 3.2 is fine. The 3.3 not! The precise kernel versions are there:
http://hftom.free.fr/phpBB2/viewtopic.php?p=2190#2190
(it's not advisable to repeat info too many times).
It's quite complex.
But I can tell what more I found.
I found that this wasn't enables:
CONFIG_I2C_CHARDEV
Now is. After, of course, I reread:
http://www.linuxtv.org/wiki/index.php/Cx88_devices_%28cx2388x%29
The advice is there, under different guise:
Quote:
<M> I2C device interface

That could have a lot to do with the remote!
P.S. after gotten the first scancodes out: Nah! I got the first scancodes and some ability (volume up and down checked at this time) on older kernel, 3.2.11-harderned and that driver is neither compiled in the kernel nor loaded.
New conf kernel recompiled, some more compiling of new packages done as well, be back to tell you more once I try things with the new kernel!


Last edited by miroR on Sat Apr 14, 2012 6:41 am; edited 1 time in total
Back to top
View user's profile Send private message
Matthijs70
n00b
n00b


Joined: 01 Oct 2006
Posts: 43
Location: the Netherlands

PostPosted: Thu Apr 12, 2012 10:34 am    Post subject: Reply with quote

As I said:
Matthijs70 wrote:
And I guess you also compiled your kernel with the correct settings? Also with the v4l (Video for Linux) part?


That's why I also asked if you checked the kernel logging to see what is says...

So I think the module for "I2C device interface" will fix this, but their may be other settings needed as well.

Good luck ;-)
Back to top
View user's profile Send private message
miroR
Apprentice
Apprentice


Joined: 05 Mar 2008
Posts: 228

PostPosted: Fri Apr 13, 2012 8:25 am    Post subject: Reply with quote

Sure.
I was unwell again, and busy when got better.
Never had time since my last post. Need a little longer.
Thanks for your care!
Back to top
View user's profile Send private message
miroR
Apprentice
Apprentice


Joined: 05 Mar 2008
Posts: 228

PostPosted: Sat Apr 14, 2012 5:45 am    Post subject: Reply with quote

I got something working.
On the third TV card (attempts on two previous, one HVR-4000, one HVR-3000 failed, concerning remote).
Code:
myBox # ir-keytable -t
Testing events. Please, press CTRL-C to abort.
1334380991.099457: event MSC: scancode = 1e10
1334380991.099465: event key down: KEY_VOLUMEUP (0x0073)
1334380991.099468: event sync
1334380991.211472: event MSC: scancode = 1e10
1334380991.211477: event sync
1334380991.460734: event key up: KEY_VOLUMEUP (0x0073)
1334380991.460738: event sync
1334380994.147642: event MSC: scancode = 1e10
1334380994.147651: event key down: KEY_VOLUMEUP (0x0073)
1334380994.147654: event sync
1334380994.396733: event key up: KEY_VOLUMEUP (0x0073)
1334380994.396736: event sync
1334380998.483856: event MSC: scancode = 1e11
1334380998.483865: event key down: KEY_VOLUMEDOWN (0x0072)
1334380998.483868: event sync
1334380998.733733: event key up: KEY_VOLUMEDOWN (0x0072)
1334380998.733736: event sync
1334380999.699918: event MSC: scancode = 1e11
1334380999.699927: event key down: KEY_VOLUMEDOWN (0x0072)
1334380999.699930: event sync
1334380999.949727: event key up: KEY_VOLUMEDOWN (0x0072)
1334380999.949730: event sync
1334381002.188052: event MSC: scancode = 1e0f
1334381002.188061: event key down: KEY_MUTE (0x0071)
1334381002.188064: event sync
1334381002.437730: event key up: KEY_MUTE (0x0071)
1334381002.437733: event sync
1334381004.540176: event MSC: scancode = 1e11
1334381004.540185: event key down: KEY_VOLUMEDOWN (0x0072)
1334381004.540188: event sync
1334381004.789734: event key up: KEY_VOLUMEDOWN (0x0072)
1334381004.789737: event sync
1334381008.300376: event MSC: scancode = 1e20
1334381008.300385: event key down: KEY_CHANNELUP (0x0192)
1334381008.300388: event sync
1334381008.549733: event key up: KEY_CHANNELUP (0x0192)
1334381008.549736: event sync
1334381011.388540: event MSC: scancode = 1e21
1334381011.388548: event key down: KEY_CHANNELDOWN (0x0193)
1334381011.388552: event sync
1334381011.637728: event key up: KEY_CHANNELDOWN (0x0193)
1334381011.637731: event sync
1334381013.564654: event MSC: scancode = 1e12
1334381013.564663: event key down: KEY_PREVIOUS (0x019c)
1334381013.564666: event sync
1334381013.684661: event MSC: scancode = 1e12
1334381013.684666: event sync
1334381013.933728: event key up: KEY_PREVIOUS (0x019c)
1334381013.933732: event sync
1334381020.445018: event MSC: scancode = 1e01
1334381020.445025: event key down: KEY_1 (0x0002)
1334381020.445029: event sync
11111334381020.694740: event key up: KEY_1 (0x0002)
1334381020.694743: event sync
1334381021.749088: event MSC: scancode = 1e02
1334381021.749098: event key down: KEY_2 (0x0003)
1334381021.749101: event sync
22221334381021.998729: event key up: KEY_2 (0x0003)
1334381021.998733: event sync
1334381022.437123: event MSC: scancode = 1e03
1334381022.437132: event key down: KEY_3 (0x0004)
1334381022.437135: event sync
33331334381022.686730: event key up: KEY_3 (0x0004)
1334381022.686734: event sync
1334381026.845359: event MSC: scancode = 1e05
1334381026.845367: event key down: KEY_5 (0x0006)
1334381026.845370: event sync
51334381026.965363: event MSC: scancode = 1e05
1334381026.965369: event sync
5555555551334381027.214735: event key up: KEY_5 (0x0006)
1334381027.214738: event sync
1334381031.645607: event MSC: scancode = 1e04
1334381031.645614: event key down: KEY_4 (0x0005)
1334381031.645618: event sync
44441334381031.894731: event key up: KEY_4 (0x0005)
1334381031.894735: event sync
1334381033.597710: event MSC: scancode = 1e06
1334381033.597718: event key down: KEY_6 (0x0007)
1334381033.597721: event sync
61334381033.709753: event MSC: scancode = 1e06
1334381033.709758: event sync
666666661334381033.959733: event key up: KEY_6 (0x0007)
1334381033.959736: event sync
1334381035.413811: event MSC: scancode = 1e07
1334381035.413820: event key down: KEY_7 (0x0008)
1334381035.413824: event sync
77771334381035.663730: event key up: KEY_7 (0x0008)
1334381035.663733: event sync
1334381036.517867: event MSC: scancode = 1e08
1334381036.517875: event key down: KEY_8 (0x0009)
1334381036.517879: event sync
81334381036.629876: event MSC: scancode = 1e08
1334381036.629881: event sync
888888881334381036.879737: event key up: KEY_8 (0x0009)
1334381036.879740: event sync
1334381037.669925: event MSC: scancode = 1e09
1334381037.669932: event key down: KEY_9 (0x000a)
1334381037.669936: event sync
91334381037.781937: event MSC: scancode = 1e09
1334381037.781941: event sync
999999991334381038.031729: event key up: KEY_9 (0x000a)
1334381038.031732: event sync
1334381039.150004: event MSC: scancode = 1e0e
1334381039.150011: event key down: KEY_SUBTITLE (0x0172)
1334381039.150014: event sync
1334381039.270018: event MSC: scancode = 1e0e
1334381039.270024: event sync
1334381039.519727: event key up: KEY_SUBTITLE (0x0172)
1334381039.519730: event sync
1334381045.182323: event MSC: scancode = 1e00
1334381045.182331: event key down: KEY_0 (0x000b)
1334381045.182334: event sync
00001334381045.431731: event key up: KEY_0 (0x000b)
1334381045.431735: event sync
1334381046.422397: event MSC: scancode = 1e0a
1334381046.422406: event key down: KEY_TEXT (0x0184)
1334381046.422410: event sync
1334381046.534401: event MSC: scancode = 1e0a
1334381046.534406: event sync
1334381046.783738: event key up: KEY_TEXT (0x0184)
1334381046.783742: event sync
1334381047.774464: event MSC: scancode = 1e0b
1334381047.774474: event key down: KEY_RED (0x018e)
1334381047.774477: event sync
1334381047.894468: event MSC: scancode = 1e0b
1334381047.894474: event sync
1334381048.143727: event key up: KEY_RED (0x018e)
1334381048.143731: event sync
1334381048.614508: event MSC: scancode = 1e2e
1334381048.614516: event key down: KEY_GREEN (0x018f)
1334381048.614519: event sync
1334381048.734519: event MSC: scancode = 1e2e
1334381048.734524: event sync
1334381048.983728: event key up: KEY_GREEN (0x018f)
1334381048.983732: event sync
1334381049.566558: event MSC: scancode = 1e38
1334381049.566566: event key down: KEY_YELLOW (0x0190)
1334381049.566569: event sync
1334381049.815738: event key up: KEY_YELLOW (0x0190)
1334381049.815741: event sync
1334381050.550611: event MSC: scancode = 1e29
1334381050.550619: event key down: KEY_BLUE (0x0191)
1334381050.550622: event sync
1334381050.662618: event MSC: scancode = 1e29
1334381050.662622: event sync
1334381050.911738: event key up: KEY_BLUE (0x0191)
1334381050.911742: event sync
1334381054.206802: event MSC: scancode = 1e3b
1334381054.206809: event key down: KEY_SELECT (0x0161)
1334381054.206813: event sync
1334381054.326812: event MSC: scancode = 1e3b
1334381054.326818: event sync
1334381054.576730: event key up: KEY_SELECT (0x0161)
1334381054.576733: event sync
1334381056.454927: event MSC: scancode = 1e3b
1334381056.454935: event key down: KEY_SELECT (0x0161)
1334381056.454939: event sync
1334381056.574929: event MSC: scancode = 1e3b
1334381056.574935: event sync
1334381056.824736: event key up: KEY_SELECT (0x0161)
1334381056.824739: event sync
1334381058.231017: event MSC: scancode = 1e1c
1334381058.231026: event key down: KEY_TV (0x0179)
1334381058.231030: event sync
1334381058.343023: event MSC: scancode = 1e1c
1334381058.343028: event sync
1334381058.592733: event key up: KEY_TV (0x0179)
1334381058.592737: event sync
1334381060.047109: event MSC: scancode = 1e18
1334381060.047116: event key down: KEY_VIDEO (0x0189)
1334381060.047120: event sync
1334381060.159116: event MSC: scancode = 1e18
1334381060.159121: event sync
1334381060.408732: event key up: KEY_VIDEO (0x0189)
1334381060.408735: event sync
1334381061.271177: event MSC: scancode = 1e19
1334381061.271186: event key down: KEY_AUDIO (0x0188)
1334381061.271189: event sync
1334381061.391185: event MSC: scancode = 1e19
1334381061.391190: event sync
1334381061.640728: event key up: KEY_AUDIO (0x0188)
1334381061.640731: event sync
1334381062.487244: event MSC: scancode = 1e1a
1334381062.487252: event key down: KEY_CAMERA (0x00d4)
1334381062.487256: event sync
1334381062.599248: event MSC: scancode = 1e1a
1334381062.599254: event sync
1334381062.848732: event key up: KEY_CAMERA (0x00d4)
1334381062.848736: event sync
1334381064.279336: event MSC: scancode = 1e3d
1334381064.279345: event key down: KEY_POWER2 (0x0164)
1334381064.279349: event sync
1334381064.399346: event MSC: scancode = 1e3d
1334381064.399352: event sync
1334381064.648732: event key up: KEY_POWER2 (0x0164)
1334381064.648736: event sync
1334381066.135435: event MSC: scancode = 1e3d
1334381066.135443: event key down: KEY_POWER2 (0x0164)
1334381066.135447: event sync
1334381066.247441: event MSC: scancode = 1e3d
1334381066.247446: event sync
1334381066.496729: event key up: KEY_POWER2 (0x0164)
1334381066.496732: event sync
1334381069.511609: event MSC: scancode = 1e25
1334381069.511617: event key down: KEY_OK (0x0160)
1334381069.511620: event sync
1334381069.623620: event MSC: scancode = 1e25
1334381069.623625: event sync
1334381069.872730: event key up: KEY_OK (0x0160)
1334381069.872734: event sync
1334381070.903689: event MSC: scancode = 1e25
1334381070.903698: event key down: KEY_OK (0x0160)
1334381070.903701: event sync
1334381071.015694: event MSC: scancode = 1e25
1334381071.015699: event sync
1334381071.264741: event key up: KEY_OK (0x0160)
1334381071.264745: event sync
1334381074.655885: event MSC: scancode = 1e36
1334381074.655894: event key down: KEY_STOP (0x0080)
1334381074.655897: event sync
1334381074.767890: event MSC: scancode = 1e36
1334381074.767896: event sync
1334381075.017725: event key up: KEY_STOP (0x0080)
1334381075.017728: event sync
1334381076.199964: event MSC: scancode = 1e37
1334381076.199972: event key down: KEY_RECORD (0x00a7)
1334381076.199975: event sync
1334381076.319975: event MSC: scancode = 1e37
1334381076.319980: event sync
1334381076.569733: event key up: KEY_RECORD (0x00a7)
1334381076.569736: event sync
1334381078.488089: event MSC: scancode = 1e0f
1334381078.488097: event key down: KEY_MUTE (0x0071)
1334381078.488101: event sync
1334381078.600093: event MSC: scancode = 1e0f
1334381078.600098: event sync
1334381078.849731: event key up: KEY_MUTE (0x0071)
1334381078.849735: event sync
1334381080.016163: event MSC: scancode = 1e12
1334381080.016170: event key down: KEY_PREVIOUS (0x019c)
1334381080.016173: event sync
1334381080.136173: event MSC: scancode = 1e12
1334381080.136178: event sync
1334381080.385730: event key up: KEY_PREVIOUS (0x019c)
1334381080.385733: event sync
1334381081.064220: event MSC: scancode = 1e10
1334381081.064229: event key down: KEY_VOLUMEUP (0x0073)
1334381081.064232: event sync
1334381081.313735: event key up: KEY_VOLUMEUP (0x0073)
1334381081.313739: event sync
1334381082.144277: event MSC: scancode = 1e12
1334381082.144285: event key down: KEY_PREVIOUS (0x019c)
1334381082.144288: event sync
1334381082.256289: event MSC: scancode = 1e12
1334381082.256293: event sync
1334381082.505729: event key up: KEY_PREVIOUS (0x019c)
1334381082.505732: event sync
1334381083.736372: event MSC: scancode = 1e0d
1334381083.736381: event key down: KEY_MENU (0x008b)
1334381083.736385: event sync
1334381083.985733: event key up: KEY_MENU (0x008b)
1334381083.985736: event sync
1334381085.016430: event MSC: scancode = 1e0d
1334381085.016438: event key down: KEY_MENU (0x008b)
1334381085.016442: event sync
1334381085.265737: event key up: KEY_MENU (0x008b)
1334381085.265740: event sync
1334381087.136541: event MSC: scancode = 1e15
1334381087.136548: event key down: KEY_DOWN (0x006c)
1334381087.136552: event sync
^[[B1334381087.256555: event MSC: scancode = 1e15
1334381087.256561: event sync
^[[B^[[B^[[B^[[B^[[B^[[B^[[B^[[B1334381087.505739: event key up: KEY_DOWN (0x006c)
1334381087.505742: event sync
1334381088.776633: event MSC: scancode = 1e15
1334381088.776641: event key down: KEY_DOWN (0x006c)
1334381088.776644: event sync
^[[B^[[B^[[B^[[B1334381089.025738: event key up: KEY_DOWN (0x006c)
1334381089.025742: event sync
1334381089.992692: event MSC: scancode = 1e14
1334381089.992699: event key down: KEY_UP (0x0067)
1334381089.992702: event sync
^[[A1334381090.112705: event MSC: scancode = 1e14
1334381090.112711: event sync
^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A1334381090.362728: event key up: KEY_UP (0x0067)
1334381090.362731: event sync
1334381091.488778: event MSC: scancode = 1e16
1334381091.488788: event key down: KEY_LEFT (0x0069)
1334381091.488791: event sync
^[[D^[[D^[[D^[[D1334381091.738729: event key up: KEY_LEFT (0x0069)
1334381091.738733: event sync
1334381092.328821: event MSC: scancode = 1e17
1334381092.328830: event key down: KEY_RIGHT (0x006a)
1334381092.328834: event sync
^[[C^[[C^[[C^[[C1334381092.578733: event key up: KEY_RIGHT (0x006a)
1334381092.578737: event sync
^C
myBox #

I had long hours of ordinary and extraordinary emerge syncing and updating of my testing branch cloneready Gentoo, since my last post.
I had other things to fix recounting of which doesn't belong in this thread.
I got these scancodes, and they are all exactly matching the keys on the remote, because HVR-3000/4000 is still, just search properly on WWW, broadly supported, I guess more in Europe, the home of my future (if I make it, because I attempted a few times in vain so far) vdr setup (myth is also very much of interest, I hope both is possible just fine.
I haven't yet got it with kaffeine, because the issue described in the page above, here again for convenience of readers: http://hftom.free.fr/phpBB2/viewtopic.php?p=2190, hasn't gone away.
I'll try and fix that and be back to relate the story.
Thanks for those, as Matthijs and Dani, who helped/offered their help!
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Multimedia All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum